Yes, and related to that is the iBOB CX4 fix with nylon washers. Has yours been patched? This causes trouble even if there's no cable plugged in as it shorts out a voltage rail. See Memo22: http://casper.berkeley.edu/papers/Science_Safety_001.pdf
Jason On 18 Nov 2010, at 07:06, Andrew Martens wrote: > Hi Laura > > I have seen strange iBOB behaviour due to an incorrectly plugged in CX4 > cable. It must have been bumped at some point and, although still plugged in, > was causing strange behaviour. The iBOB would report being successfully > programmed but the LEDs would do strange things. Not sure if this is > related to your problem though. > > Regards > Andrew > > > > On 17 November 2010 21:11, Laura Spitler <[email protected]> wrote: > Hi everyone, > > I'm having a problem with an iBOB-based spectrometer. The design is a > simple instrument used to measure neutral hydrogen for our > undergraduate radio lab course. The spectra are transmitted over the > 10/100 Mb ethernet using a modified main.c file where I read the > channels out of a shared BRAM, packetize them, and send the using UDP. > They are then grabbed using the software "gulp", which is similar to > tcpdump. > The problem is occasionally the iBOB seizes up. The "sanity LEDs" go > dark and no data is transmitted. After some about of time, the iBOB > comes back to life and things resume as normal. > > Does anyone have any idea what could cause the iBOB to "go dark" like this? > Thanks, > Laura > >
