To: | "" <> |
---|---|
Subject: | Re: [ts-7000] Re: Unexpected TS7500 reboot and read only |
From: | Walter Marvin <> |
Date: | Thu, 31 Jan 2013 12:08:28 -0800 (PST) |
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. > __._,_.___
Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required) Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe __,_._,___ |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | [ts-7000] Re: Unexpected TS7500 reboot and read only, orfanic856 |
---|---|
Next by Date: | Re: [ts-7000] Re: RS-485 full duplex sending and not recieving, Jason Stahls |
Previous by Thread: | [ts-7000] Re: Unexpected TS7500 reboot and read only, orfanic856 |
Next by Thread: | Re: [ts-7000] Re: Unexpected TS7500 reboot and read only, Petr Štetiar |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU