BeagleBoard XM not booting

Hi,

my Beagleboard has trouble booting. I tried it with Debian 7.0 and
Ubuntu 12.04, but both fail during booting. I then tried the shipped
image, which also fails. As I understand the serial output, my boot.scr
or uEnv.txt is never read. When I enter the boot commands at the u-boot
prompt, it starts like it should. I also tried switching the sd-card,
which didn't helped.

serial output:

  Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56)
  Beagle xM
  Reading boot sector
  Loading u-boot.bin from mmc
  
  U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42)
  
  OMAP3630/3730-GP ES2.0, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
  OMAP3 Beagle board + LPDDR/NAND
  I2C: ready
  DRAM: 512 MiB
  NAND: 256 MiB
  MMC: OMAP SD/MMC: 0
  In: serial
  Out: serial
  Err: serial
  Beagle xM Rev A
  No EEPROM on expansion board
  Die ID #59da00011ff00000015739eb0c019006
  Hit any key to stop autoboot: 0
  mmc - MMC sub system
  
  Usage:
  mmc read <device num> addr blk# cnt
  mmc write <device num> addr blk# cnt
  mmc rescan <device num>
  mmc part <device num> - lists available partition on mmc
  mmc list - lists available devices
  Booting from nand ...
  
  NAND read: device 0 offset 0x280000, size 0x400000
   4194304 bytes read: OK
   Wrong Image Format for bootm command
   ERROR: can't get kernel image!
   OMAP3 beagleboard.org #

Any ideas?

2011? what image did you use???

Care to retry with either:
http://elinux.org/BeagleBoardUbuntu#Demo_Image

or:
http://elinux.org/BeagleBoardDebian#Demo_Image

Regards,

Hi,

> Hi,
>
> my Beagleboard has trouble booting. I tried it with Debian 7.0 and
> Ubuntu 12.04, but both fail during booting. I then tried the shipped
> image, which also fails. As I understand the serial output, my boot.scr
> or uEnv.txt is never read. When I enter the boot commands at the u-boot
> prompt, it starts like it should. I also tried switching the sd-card,
> which didn't helped.
>
> serial output:
>
> Texas Instruments X-Loader 1.5.0 (Mar 27 2011 - 17:37:56)
> Beagle xM
> Reading boot sector
> Loading u-boot.bin from mmc
>
>
> U-Boot 2011.03-rc1-00000-g9a3cc57-dirty (Apr 01 2011 - 17:41:42)

2011? what image did you use???

it was the original image, which shipped with the board (used to work).

Care to retry with either:
or:
http://elinux.org/BeagleBoardDebian#Demo_Image

I did (http://rcn-ee.net/deb/rootfs/wheezy/debian-7.1-console-armhf-2013-07-22.tar.xz):

U-Boot SPL 2013.07-00013-gbc6f74a (Jul 30 2013 - 12:32:05)
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img

U-Boot 2013.07-00013-gbc6f74a (Jul 30 2013 - 12:32:05)

OMAP3630/3730-GP ES1.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
In: serial
Out: serial
Err: serial
Beagle xM Rev A
No EEPROM on expansion board
No EEPROM on expansion board
Die ID #59da00011ff00000015739eb0c019006
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split,
HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 1.800
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 480ab000 using PIO, IRQ 0
Net: usb_ether
Hit any key to stop autoboot: 0
mmc - MMC sub system

Usage:
mmc read addr blk# cnt
mmc write addr blk# cnt
mmc erase blk# cnt
mmc rescan
mmc part - lists available partition on current mmc device
mmc dev [dev] [part] - show or set current mmc device [partition]
mmc list - lists available devices

Booting from nand ...

NAND read: device 0 offset 0x280000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OMAP3 beagleboard.org #

Ahh.. you have one of the first run xM's with onboard nand (not
bootable nand) but someone sometime along with way typed "saveenv" and
saved a now obsolte u-boot command..

nand erase.chip

should solve the problem..

Regards,

Hi,

thx that worked. So that means I can't use the nand for boot up?

On the "xM" unless you physically modify the board, it will NOT bootup
from nand... Sure you can 'store' stuff in their an use it by
u-boot/kernel, but eventually you run into this stumbling block issue
again..

Regards,

Hi,