Hi,
I have seen iBobs have strange ethernet/telnet problems when the
the clocks provided by the iADCS v1.1, in our case, wheren't AOK.
The fix was to supply valid clocks to the iADCs and then
hitting reset button or power cycling.
At a nastier level I have seen the small resistors like R474
near the 1/4 nut holding the iBob PCB down to the standoff
and mounting plate be destroyed by overly energetic use
of a nut driver when mounting the PCB to the plate.
Going down the column of resistors to check their values,
when the board is powered off, can find a destroyed part.
The fix is to replace the bad part(s) with 1% 22.1 ohm 0603
part or equivalent.
Matt
On Thu, 9 Dec 2010, G Jones wrote:
Hi Dale,
The first thing I would check is connecting an RS-232 cable to see if
you can talk to the FPGA via tiny shell that way. This will also let
you run the ifconfig command to see what the iBOB thinks it's IP
address is, to make sure there's nothing funny with that. Are you
programming the FPGA directly, or the PROM chip for standalone
operation. I have found programming the PROM chip very unreliable, so
try just programming the FPGA itself first if you haven't. If
programming the FPGA works but not programming the PROM, I have found
that trying different versions of IMPACT will sometimes help.
Glenn
On Thu, Dec 9, 2010 at 8:50 AM, Gary, Dale <[email protected]> wrote:
Hi All,
We have been running four IBOBs as a spectrometer for about a year, and
one of the IBOBs is no longer taking telnet connections via ETH0. I
checked the voltages, and all are present. I reprogrammed the FPGA,
and that was successful (as reported by Impact), but there was no
change. Is there anything else I could do to test/debug it, or should
I just send it back to Digicom?
Thanks,
Dale
