From: Jay K. Robertson <gumstix@jk...> - 2008-02-19 04:19:07
I recently received a Basix 400XM-BT as a return from an RMA. The
previous board had a defective Bluetooth chip, and I am having a
completely different problem with the replacement board. I was
wondering if anyone has ever seen this before.
The new board that I was sent worked perfectly on the first boot-up.
During the first boot, I verified that Bluetooth was working, and
downloaded my software to the board via Zmodem. The software is nothing
complicated--it is a piece of software that listens on STUART and
responds via Bluetooth. No changes to the kernel or filesystem are
necessary. After uploading the software, I rebooted the board.
Suddenly, the board stopped working on the second boot. It seems like
the board is dying before it makes it through the steps of U-Boot,
before it even contemplates loading the kernel. One of three things
1. I get the normal U-Boot screen that looks like this:
U-Boot 1.1.4 (Nov 6 2006 - 11:20:03) - 400 MHz - 1161
*** Welcome to Gumstix ***
U-Boot code: A3F00000 -> A3F25DE4 BSS: -> A3F5AF00
Bank #0: a0000000 64 MB
Flash: 16 MB
Using default environment
Hit any key to stop autoboot: 0
GUM> (and then a string of up to 5 garbage characters)
Note that sometimes some the characters in the U-Boot screen get
corrupted as well.
2. I just get a string of up to 5 garbage characters--with no U-Boot
3. No output at all.
In all three cases, the console is locked up completely, and won't
accept character input. Usually, if I leave the Gumstix unplugged for a
little while (5 minutes or so), I get the U-Boot screen in #1 above. If
I try to power-cycle it immediately (without a cooldown period), I get
#2 or #3 above.
I have taken steps to make sure that my serial port and cable aren't to
blame, and I have verified this with another machine. I have used the
very same tweener, serial console cable, and 5V power supply to program
3 other 400XM-BT boards (all of which are no longer in my possession)
Any ideas, anyone? Am I just unlucky, and have another dead board? Has
anyone ever seen this behavior before?