Hello, I finally went and checked my iBOB, and it appears that there are already nylon and metal washers under the CX4 screws. Did Digicom start implementing this fix in the production of iBOBs? My iBOB arrived in late Aug of 2008 and the email with the associated memo went out in May of 2008, so the dates would be consistent for adjusting the manufacturing process.
Best, Laura On Fri, Nov 19, 2010 at 1:29 AM, Andrew Siemion <[email protected]> wrote: > I agree with Jason that you should definitely apply the fix, but afaik this > has only caused a problem when actually using the un-patched ports. > > - Andrew > > > > On 11/18/10 10:25 PM, "Jason Manley" <[email protected]> wrote: > >>> As far as I know, my iBOB has not been patched with >>> nylon washers. Just to clarify, this would be a problem even if I'm >>> not using 10 GbE in my design? >> Yeah, this might well be your problem. Even if it's not affecting you now, >> you >> should patch your board. Especially if you're using the iBOB faceplate (which >> seems to apply more pressure to the connector). This problem is present >> whether or not there is a cable plugged in, irrespective of your bitstream. >> There is a voltage short due to a track being routed under a screw head. See >> the aforementioned memo for details. The original email went out to the >> mailing list from Andrew Siemion on 15 May 2008 >> http://www.mail-archive.com/[email protected]/msg00187.html >> >> Jason >> >> >>> >>> >>> >>> On Thu, Nov 18, 2010 at 12:26 AM, Jason Manley <[email protected]> >>> wrote: >>>> 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 >>>>> >>>>> >>>> >>>> >> >> > > >
