[beagleboard] can't recovery from mmc and usb

Hi,

Recovery from MMC, my board will print the bad message:
                       
40T

If recovery using USB by
             [root]# ./omap3_usbload uboot-v2.bin

the tool can not find usb device. I look through the dmesg info in
host machine, and find the omap3430 device disconnects immediately
after emmumation.

It seems the omap boot rom is destroyed ,doesn't it?

Thanks.

Recovery from MMC, my board will print the bad message:
   40T

If recovery using USB by
             [root]# ./omap3_usbload uboot-v2.bin

the tool can not find usb device. I look through the dmesg info in
host machine, and find the omap3430 device disconnects immediately
after emmumation.

It seems the omap boot rom is destroyed ,doesn't it?

Hi Lei Ming,

I think you OMAP BOOT ROM is working 100% correct and that you haven't
destroyed anything. But apparently you are doing something wrong following
the recovery procedure - i.e. not following the steps 100%.

Please have another look at: BeagleBoardRecovery - eLinux.org

The OMAP ROM code will enumerate and wait for 3 sec in order to check if the
PC want to communicate with it. In case not, it will disconnect again. The
40T message on the serial terminal is as well being send by the ROM code
checking for peripheral boot using the UART.

Keep up trying and let us know in case you are still stuck after a couple of
more attempts.

I bet you board is 100% OK :slight_smile: - Good luck
  Søren

Hi,Steen Christensen

Thanks for your reply.

I have tried many times using MMC recovery, and the result is always
failure. So I start to try USB recovery by recover_beagle.sh, the
problem seems a lot progress, but u-boot still can't continue and output
messages is here:

[lm@linux-lm beagle_recover]$ sudo ./recover_beagle.sh /dev/ttyUSB0
NOTE:
When you see the message "Waiting for USB device..", Connect USB Cable to the board with the switch S1 pressed
Keep S1 pressed for 1 second at least after connecting usb cable.
Waiting for USB device vendorID=0x451and productID=0xD009:
Dev #11: Texas Instruments - OMAP3430
  - Serial Number: N/A
Downloading file: 100.000% completed(40236/40236 bytes)
./target_files/u-boot-v2.bin downloaded successfully to target
Output:
loadb -f /dev/ram0

## Ready for binary (kermit) download to 0x00000000 offset on /dev/ram0 device at 115200 bps...
Match Found. Operation completed!
Downloading file: 100.000% completed(717372/717372 bytes)
File Download completed
Output:
go 0x80000000

## Starting application at 0x80000000 ...

U-Boot 1.3.3 (Jul 10 2008 - 16:30:47)

OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz

OMAP3 Beagle Board + LPDDR/NAND

DRAM: 128 MB

NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x01 ( AND 128MiB 3,3V 8-bit)

NAND bus width 16 instead 8 bit

0 MiB

OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 Beagle Board + LPDDR/NAND
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x01 ( AND 128MiB
3,3V 8-bit)
NAND bus width 16 instead 8 bit
0 MiB

The strange part here is why Uboot thinks the NAND chip ID is 0x01?

Looking at u-boot\drivers\mtd\nand\nand_ids.c this is the last item in the
list, which might indicate that that the NAND probing failed somehow and no
proper error handling was made - I haven't checked if this is the case, but
I could imagine :slight_smile:

I do unfortunately not have any really great ideas why this happens since
the Manufacturer ID reading is OK. The Chip ID is supposed to read 0xBA
AFAIR. Are you getting stuck at the same point when you try MMC and/or UART
booting?

Very strange - indeed
  Søren

> OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
> OMAP3 Beagle Board + LPDDR/NAND
> DRAM: 128 MB
> NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x01 ( AND 128MiB
> 3,3V 8-bit)
> NAND bus width 16 instead 8 bit
> 0 MiB

Hi again,

Surfing the web - Please consult:
http://elinux.org/BeagleBoardRecovery#MMC_recovery
I think this most likely describes the problem you had using MMC? Did you
use the special MLO_recovery version?

With respect to USB recovery it seems, that you need a special version of
U-boot and that you can't just use the standard 1.3.3 version. More
information on this from:

Good luck
  Søren

于 Sun, 7 Jun 2009 11:25:56 +0200
Søren Steen Christensen <sorenschristensen@stofanet.dk> 写道:

> > OMAP3530-GP rev 2, CPU-OPP2 L3-165MHz
> > OMAP3 Beagle Board + LPDDR/NAND
> > DRAM: 128 MB
> > NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x01 ( AND
> > 128MiB 3,3V 8-bit)
> > NAND bus width 16 instead 8 bit
> > 0 MiB

Hi again,

Surfing the web - Please consult:
BeagleBoardRecovery - eLinux.org
I think this most likely describes the problem you had using MMC? Did
you use the special MLO_recovery version?

With respect to USB recovery it seems, that you need a special
version of U-boot and that you can't just use the standard 1.3.3
version. More information on this from:
Nishanth' tech rambles: beagleboard recovery take 2

I use the u-boot compiled from latest version of
git://gitorious.org/u-boot-omap3/mainline.git, then
recover my beagle board successfully.

Thanks.

Many download links in
http://elinux.org/BeagleBoardRecovery#MMC_recovery have been
invalid, Can you give a new usable link?

BTW: It seems Link of
http://code.google.com/p/beagleboard/downloads/list is for rev C,
Is it usable for Rev B?

Thanks.