sd card boot fails and no luck with UART boot either

Not sure if this has been answered before.
I have a BBB running angstrom. I decided to try to change the distribution to ubuntu (which is currently flashed onto my SD card)
So to force a boot from the SD card, after I renamed (angstrom eMMC) MLO to MLO.ORIG and rebooted with the SD card in the slot.
Now I get:

======== reset board log ==========
U-Boot SPL 2013.07-00013-g469f02f (Jul 30 2013 - 12:27:41)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
spl: mmc init failed: err - -17
====== end reset board log ==========

I understand that the SPL (MLO) must match the uboot image.
So also tried to follow the steps mentioned in http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_UBoot_Board_Port
I got to a point where SPL image is loaded via xmodem, however I was never able to transfer the uboot image successfully.
Now today, even the spl image doesnt seem to go through.
Ex. using:

screen /dev/ttyusb1 115200
C-a followed by exec !! sx -o /home/yogesh/ti-sdk-am335x-evm-06.00.00.00/board-support/board-port-labs/sitara-board-port-uboot/spl/u-boot-spl.bin
I get
===== screen log =======
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: Retry Count Exceeded

Transfer incomplete
==== end screen log ====

Any help to get my BBB back or even getting to the uboot prompt will be really appreciated.

Thank you.

Follow the instructions exactly as it says on the Wiki to restore Angstrom.

http://circuitco.com/support/index.php?title=Updating_The_Software

Gerald

Not sure if this has been answered before.
I have a BBB running angstrom. I decided to try to change the distribution to ubuntu (which is currently flashed onto my SD card)
So to force a boot from the SD card, after I renamed (angstrom eMMC) MLO to MLO.ORIG and rebooted with the SD card in the slot.
Now I get:

======== reset board log ==========
U-Boot SPL 2013.07-00013-g469f02f (Jul 30 2013 - 12:27:41)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
spl: mmc init failed: err - -17

For clarity, you’re doing, in this order:

  1. remove power (including USB gadget cable)
  2. Hold ‘boot button’
  3. apply power

Do you have another SD card you can use? The above error means “I couldn’t talk with the SD card”

====== end reset board log ==========

I understand that the SPL (MLO) must match the uboot image.
So also tried to follow the steps mentioned in http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_UBoot_Board_Port
I got to a point where SPL image is loaded via xmodem, however I was never able to transfer the uboot image successfully.
Now today, even the spl image doesnt seem to go through.
Ex. using:

screen /dev/ttyusb1 115200
C-a followed by exec !! sx -o /home/yogesh/ti-sdk-am335x-evm-06.00.00.00/board-support/board-port-labs/sitara-board-port-uboot/spl/u-boot-spl.bin
I get

First up, start screen and make sure than you’re seeing a stream of ‘C’, if you are not, you cannot UART load.

===== screen log =======
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: Retry Count Exceeded

This means ‘sx’ did not see the start of an x/y/zmodem request.