Good to know. It must really be short somewhere.
I also realized that most busy process is sdctl. But I am not using file I/O
commands in my scripts so much. Just a bit of error logging.
I will investigate connection with my custom board attached to 44 Pin Header.
Thanks, Vladimir.
--- In Walter Marvin wrote:
>
> I never saw heating problems with the Cavium. You may have a short somewhere
>
>
>
> ________________________________
> From: orfanic856
> To:
> Sent: Friday, February 1, 2013 6:14 AM
> Subject: [ts-7000] Re: Unexpected TS7500 reboot and read only
>
>
> Â
> I attached heat sink to the Cavium processor. Ugly solution, but it's
> working. Still, this is weird. Is the board so badly designed to be overheat
> it so easily or is it a bug?
>
> Vladimir.
>
> --- In Walter Marvin wrote:
> >
> > Its fairly easy to detect this. Look in the 7550's schematics. Its easy to
> > cut the lead that controls the watchdog and jumper it back. If the reboot
> > doesn't then occur, you've got it pegged.� The system will then hang.
> > Back out your changes until it doesn't hang any more. I could never get the
> > watchdog off to work.
> >
> >
> >
> > ________________________________
> > From: orfanic856
> > To:
> > Sent: Thursday, January 31, 2013 2:54 PM
> > Subject: [ts-7000] Re: Unexpected TS7500 reboot and read only
> >
> >
> > Ã?Â
> > Yes, could be. Solution can be quite difficult I guess.
> >
> > I tried today to kill ts7500ctl deamon, and send to watchdog value 3
> > (according wiki, to switch off FPGA watchdog). It works. No restarting.
> > But...instead of restarting, system hangs completely. Then it needs to be
> > restarted manually. Watchdog was doing good job before I switched him off.
> >
> > I am using set of python threaded scripts to control DIOs as well as
> > connected USB devices. Most probably it happens during sending control
> > commands setdio/getdio. I am using self compiled C library imported in to
> > python. But it hangs when I was communicating through sockets with dioctl
> > as well. And couple of times it happens also by setting/getting DIOs from
> > command line.
> >
> > Could it be caused by processor overheating? I do not have way to measure
> > processor package surface temperature currently, but it's in normal room
> > temperature, uncovered.
> >
> > Thanks for any hints. Vladimir.
> >
> > --- In Walter Marvin wrote:
> > >
> > > One problem That the user space architecture that Technologic uses in the
> > > 7500 and 7550 is that if you step on the code somewhere, you can lock up
> > > the "drivers". This results in the watchdog firing, and a reboot.
> > >
> > >
> > >
> > > ________________________________
> > > From: orfanic856
> > > To:
> > > Sent: Wednesday, January 30, 2013 4:09 PM
> > > Subject: [ts-7000] Unexpected TS7500 reboot and read only
> > >
> > >
> > > Ã?â??Ã?Â
> > > Hi,
> > >
> > > I am facing a problems when trying to set/get DIO pin status using sbus.c.
> > > For example this code:
> > > sbuslock();
> > > sbus_poke16(0x66, sbus_peek16(0x66) & ~(1 << dirPinOffSet));
> > > sbusunlock();
> > >
> > > It immediately restart board and a consequence I need to repair FS
> > > journals on the SD card (using linuxrc-sdroot). I was also unable to get
> > > linuxrc-sdroot-readonly working. It's unable to switch to SD card (RW
> > > plain sdroot works fine).
> > >
> > > Is it somehow watchdog related? Is there anyone with same experience?
> > >
> > > Thanks Vladimir.
> > >
> >
>
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|