Hi Rurik, In the case of power-cycling and reprogramming not bringing back the port, how do you regain communication? Repeated power-cycles?
During one of the hangs, have you tried connecting an independent computer/serial port to the device to exclude a linux problem? We have *loads* of problems w/ linux and serial connections, exhibiting all types of odd behavior. Regards, Andrew On 1/27/09 9:08 PM, "Jason Manley" <[email protected]> wrote: > The KAT guys were complaining of a similar behaviour, but I can't say > I've ever experienced this myself and have been unable to reproduce > it. Is your problem repeatable? > > Have you enabled the "Load FPGA" option in Impact? > > Also check the MODE jumper settings on your IBOB. It shouldn't affect > anything if you're programming over JTAG, but might be worth a look > anyway. Should be on 3-4 if you're not using the EEPROM. > > Jason > > > On 27 Jan 2009, at 19:29, Rurik Primiani wrote: > >> Hi everyone, >> >> We've been experiencing issues with hanging serial ports when >> reprogramming our iBob's over JTAG. Our setup at the moment is a >> linux control computer with an 8-port serial-PCI card with two >> iBob's attached and four iBob's total on a JTAG chain (the first two >> being the serial-linked ones). Programming works just fine and from >> a cold start so does serial communication usually. >> >> The problem occurs when we reprogram a board with a *different* >> bitstream, the serial port hangs permanently until the iBob's are >> power cycled and reprogrammed. Programming the same bitstream >> typically does not break the port. Occasionally however even the >> power-cycling and reprogramming does not bring back the serial >> ports. It does not seem to be the specific designs because they >> usually work after this procedure, instead it seems to be linked to >> the reprogramming. >> >> Has anyone seen this behavior before, or something similar to it? It >> appears to me that during an iBob reprogramming some pin that >> controls the serial port fails to go low but perhaps it's a linux >> multi-serial port problem? >> >> Thanks for your help! >> Rurik > >
