Rebuilding U-Boot...

GoogleGroups
1

Using this command sequence:

git clone git://git.denx.de/u-boot.git u-boot-main
cd u-boot-main
git checkout v2010.12 -b omap
make CROSS_COMPILE=/opt/CodeSourcery/bin/arm-none-eabi- distclean
make CROSS_COMPILE=/opt/CodeSourcery/bin/arm-none-eabi-
omap3_beagle_config
make CROSS_COMPILE=/opt/CodeSourcery/bin/arm-none-eabi-

I receive this:
Beagle xM Rev A
No EEPROM on expansion board
Die ID #673c00011ff00000015739eb0c00e015
Hit any key to stop autoboot: 0
usage: fatload <interface> <dev[:part]> <addr> <filename> [bytes]
MMC: block number 0x1 exceeds max(0x0)
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OMAP3 beagleboard.org #

What is wrong?

2

Boot partition formatted FAT16? Got the proper files(MLO, u-boot.bin and uImage) in the boot partition?

3

You may have to erase the environment since
the commands of latest U-Boot have changed
(mmc init is a no-op and one has to execute mmc
rescan 0) and your current bootcmd may be
incompatible.

Also try mmcinfo (without space).

-- hns

4

OMAP3 beagleboard.org # mmc list
OMAP SD/MMC: 0

5

My build:

U-Boot 2010.12-dirty (Feb 07 2011 - 11:50:50)
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 #673c00011ff00000015739eb0c00e015
Hit any key to stop autoboot: 0
usage: fatload <interface> <dev[:part]> <addr> <filename> [bytes]
MMC: block number 0x1 exceeds max(0x0)
** Can't read from device 0 **

** Unable to use mmc 0:1 for fatload **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OMAP3 beagleboard.org #

the downloaded one that works:

U-Boot 2010.03 (Jan 04 2011 - 12:38:02)
OMAP3630/3730-GP ES2.0, CPU-OPP2, L3-165MHz,
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Probing for expansion boards, if none are connected you'll see a
harmless I2C error.
No EEPROM on expansion board
Beagle xM Rev A
Die ID #673c00011ff00000015739eb0c00e015
Hit any key to stop autoboot: 0

6

Boot partition formatted FAT16? Got the proper files(MLO, u-boot.bin and
uImage) in the boot partition?

Yes, it is well formatted, even because the system hangs only with my
rebuild of u-boot.bin!

7

You may have to erase the environment since
the commands of latest U-Boot have changed
(mmc init is a no-op and one has to execute mmc
rescan 0) and your current bootcmd may be
incompatible.

How should I do this?

8

1. break into u-boot console (well, you are already on the console)
2. printenv to study if that is really the problem
3. nand erase 260000 2000
4. reboot (don't issue saveenv).

9

OMAP3 beagleboard.org # help
Shows mmc and not mmcinit. I'm using v2010.12 on a BB xM.

10

May I need to configure something?
Why I have:

MMC: OMAP SD/MMC: 0

Something related to my BB xM instead of BB?

11

Yes, this is how it should be. Recent U-Boot has no "mmcinit".
It has "mmc", "mmcinfo" and "mmc subcommand". Try "help mmc".

We also have compiled our own U-Boot from git.denx.de and
had to update our boot.scr and environment because it became
incompatible.

-- hns

12

OMAP3 beagleboard.org # printenv
baudrate=115200
beaglerev=xMA
bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootdelay=2
roofstype=ext2 rw
bootcmd=mmc init; atload fatload mmc 0:1 0x80300000 uImage; bootm
0x80300000
bootdelay=3
bootscr=boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
buddy=none
camera=lbcm3m1
console=ttyS2,115200n8
defaultdisplay=dvi
dieid#=673c00011ff00000015739eb0c00e015
dvimode=640x480MR-16@60
loadaddr=0x80200000
loadbootscript=fatload mmc ${mmcdev} ${loadaddr} ${bootscr}
loadramdisk=fatload mmc ${mmcdev} ${rdaddr} ramdisk.gz
loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage
mmcargs=setenv bootargs console=${console} ${optargs} mpurate=$
{mpurate} buddy=${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:
${dvimode} omapdss.def_disp=${defaultdisplay} root=${mmcroot}
rootfstype=${mmcrootfstype}
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
mmcdev=1
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
mpurate=1000
nandargs=setenv bootargs console=${console} ${optargs} mpurate=$
{mpurate} buddy=${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:
${dvimode} omapdss.def_disp=${defaultdisplay} root=${nandroot}
rootfstype=${nandrootfstype}
nandboot=echo Booting from nand ...; run nandargs; nand read $
{loadaddr} 280000 400000; bootm ${loadaddr}
nandroot=/dev/mtdblock4 rw
nandrootfstype=jffs2
ramargs=setenv bootargs console=${console} ${optargs} mpurate=$
{mpurate} buddy=${buddy} camera=${camera} vram=${vram} omapfb.mode=dvi:
${dvimode} omapdss.def_disp=${defaultdisplay} root=${ramroot} rw
ramdisk_size=65536 initrd=${rdaddr},64M rootfstype=${ramrootfstype}
ramboot=echo Booting from ramdisk ...; run ramargs; bootm ${loadaddr}
ramroot=/dev/ram0 rw
ramrootfstype=ext2
rdaddr=0x81600000
usbtty=cdc_acm
vram=12M

Environment size: 1895/131068 bytes

13

OK!!!
It works after NAND ERASE... Thank you very much!!!!

U-Boot 2010.12 (Feb 07 2011 - 14:43:56)
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
*** Warning - bad CRC, using default environment

How to fix that warning?

14

ignore it, unless you store your bootargs in nand..

15

It disappears after doing savenv or the next reboot.

16

Could you post your boot.cmd?

17

http://download.goldelico.com/gta04/ombeagle/20110202-lenny-fosdem/src/boot.cmd

Well, it will not work with your U-Boot since we have added
private commands to initialize LCD, touch screen, GPS etc.
on our specific extension board.

-- hns

18

Thank you very much!

19

I need to use the UART2 through the pinmux... I should set something
into the boot.scr to enable it?

20

echo a > /dev/ttyS1
-bash: echo: write error: Input/output error