Rebuilding U-Boot...
1,066 views
Skip to first unread message
Ric.Rug
Feb 7, 2011, 4:17:52 AM2/7/11
to Beagle Board
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?
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?
Ric.Rug
Feb 7, 2011, 5:38:27 AM2/7/11
to Beagle Board
Ric.Rug
Feb 7, 2011, 6:05:02 AM2/7/11
to Beagle Board
>>>> 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
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.
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:
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 #
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
Hit any key to stop autoboot: 0
David Wiebe
Feb 7, 2011, 4:29:43 AM2/7/11
to beagl...@googlegroups.com
Boot partition formatted FAT16? Got the proper files(MLO, u-boot.bin and
uImage) in the boot partition?
uImage) in the boot partition?
Dr. H. Nikolaus Schaller
Feb 7, 2011, 4:37:44 AM2/7/11
to beagl...@googlegroups.com
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
Ric.Rug
Feb 7, 2011, 8:42:48 AM2/7/11
to Beagle Board
> 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
> uImage) in the boot partition?
rebuild of u-boot.bin!
Ric.Rug
Feb 7, 2011, 8:43:29 AM2/7/11
to Beagle Board
> 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?
> 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.
On 7 Feb, 10:37, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
Ric.Rug
Feb 7, 2011, 8:53:30 AM2/7/11
to Beagle Board
Dr. H. Nikolaus Schaller
Feb 7, 2011, 8:48:12 AM2/7/11
to beagl...@googlegroups.com
Am 07.02.2011 um 14:43 schrieb Ric.Rug:
>> 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?
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).
Ric.Rug
Feb 7, 2011, 8:57:10 AM2/7/11
to Beagle Board
May I need to configure something?
Why I have:
>>> MMC: OMAP SD/MMC: 0
Something related to my BB xM instead of BB?
Why I have:
>>> MMC: OMAP SD/MMC: 0
Something related to my BB xM instead of BB?
Ric.Rug
Feb 7, 2011, 8:58:00 AM2/7/11
to Beagle Board
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
On 7 Feb, 14:48, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
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
On 7 Feb, 14:48, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
Ric.Rug
Feb 7, 2011, 9:00:04 AM2/7/11
to Beagle Board
OK!!!
It works after NAND ERASE... Thank you very much!!!!
U-Boot 2010.12 (Feb 07 2011 - 14:43:56)
How to fix that warning?
On 7 Feb, 14:48, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
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
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
How to fix that warning?
On 7 Feb, 14:48, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
Dr. H. Nikolaus Schaller
Feb 7, 2011, 8:57:43 AM2/7/11
to beagl...@googlegroups.com
Am 07.02.2011 um 14:53 schrieb Ric.Rug:
> OMAP3 beagleboard.org # help
> Shows mmc and not mmcinit. I'm using v2010.12 on a BB xM.
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
Robert Nelson
Feb 7, 2011, 9:07:03 AM2/7/11
to beagl...@googlegroups.com
On Mon, Feb 7, 2011 at 8:00 AM, Ric.Rug <riccardo...@gmail.com> wrote:
> 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?
> 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?
ignore it, unless you store your bootargs in nand..
--
Robert Nelson
http://www.rcn-ee.com/
Ric.Rug
Feb 7, 2011, 9:10:48 AM2/7/11
to Beagle Board
Could you post your boot.cmd?
On 7 Feb, 14:57, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
On 7 Feb, 14:57, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
Dr. H. Nikolaus Schaller
Feb 7, 2011, 9:08:40 AM2/7/11
to beagl...@googlegroups.com
Am 07.02.2011 um 15:00 schrieb Ric.Rug:
> 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?
It disappears after doing savenv or the next reboot.
Dr. H. Nikolaus Schaller
Feb 7, 2011, 9:45:34 AM2/7/11
to beagl...@googlegroups.com
Am 07.02.2011 um 15:10 schrieb Ric.Rug:
> Could you post your boot.cmd?
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
Ric.Rug
Feb 7, 2011, 11:11:14 AM2/7/11
to Beagle Board
Thank you very much!
On 7 Feb, 15:45, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
On 7 Feb, 15:45, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
> Am 07.02.2011 um 15:10 schrieb Ric.Rug:
>
> > Could you post your boot.cmd?
>
> http://download.goldelico.com/gta04/ombeagle/20110202-lenny-fosdem/sr...
>
> > Could you post your boot.cmd?
>
Ric.Rug
Feb 8, 2011, 4:40:44 AM2/8/11
to Beagle Board
I need to use the UART2 through the pinmux... I should set something
into the boot.scr to enable it?
On 7 Feb, 14:57, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
into the boot.scr to enable it?
On 7 Feb, 14:57, "Dr. H. Nikolaus Schaller" <h...@goldelico.com>
wrote:
Ric.Rug
Feb 8, 2011, 4:58:01 AM2/8/11
to Beagle Board
echo a > /dev/ttyS1
-bash: echo: write error: Input/output error
-bash: echo: write error: Input/output error
Ric.Rug
Feb 8, 2011, 5:03:11 AM2/8/11
to Beagle Board
less /proc/tty/driver/OMAP-SERIAL
serinfo:1.0 driver revision:
0: uart:OMAP UART0 mmio:0x4806A000 irq:72 tx:3 rx:0 CTS|DSR|CD|RI
1: uart:OMAP UART1 mmio:0x4806C000 irq:73 tx:3 rx:3 DSR|CD|RI
2: uart:OMAP UART2 mmio:0x49020000 irq:74 tx:5872 rx:479 RTS|CTS|DTR|
DSR|CD|RI
3: uart:OMAP UART3 mmio:0x49042000 irq:80 tx:5 rx:1 brk:1 CTS|DSR|CD|
RI
It seems like UART2 is related to the db9 connector onboard... and not
the mux port!
serinfo:1.0 driver revision:
0: uart:OMAP UART0 mmio:0x4806A000 irq:72 tx:3 rx:0 CTS|DSR|CD|RI
1: uart:OMAP UART1 mmio:0x4806C000 irq:73 tx:3 rx:3 DSR|CD|RI
2: uart:OMAP UART2 mmio:0x49020000 irq:74 tx:5872 rx:479 RTS|CTS|DTR|
DSR|CD|RI
3: uart:OMAP UART3 mmio:0x49042000 irq:80 tx:5 rx:1 brk:1 CTS|DSR|CD|
RI
It seems like UART2 is related to the db9 connector onboard... and not
the mux port!
Ric.Rug
Feb 8, 2011, 6:01:56 AM2/8/11
to Beagle Board
It works (ttyO1)!
stty -F /dev/ttyO1 raw ispeed 9600 ospeed 9600 cs8 -ignpar -cstopb -
echo
stty -F /dev/ttyO1 raw ispeed 9600 ospeed 9600 cs8 -ignpar -cstopb -
echo
Reply all
Reply to author
Forward
0 new messages