u-boot loaded from SD should look to SD for boot.scr instead of using nand settings.

Bug #613866 reported by Tobin Davis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
u-boot-omap3 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: u-boot-omap3

When booting a beagleboard with the maverick image, holding down the user button while power up/reset loads x-loader & u-boot from the boot partition of the SD card, but then uses the environment settings saved in nand. The correct behavior should be to load the boot.scr from the boot partition on SD.

The following is the output from serial console:

Texas Instruments X-Loader 1.4.4ss (Jul 13 2010 - 12:38:37)
Beagle Rev C4
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2010.03-rc1 (Jun 01 2010 - 09:57:03)

OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max clock-720Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
timed out in wait_for_pin: I2C_STAT=0
I2C read: I/O error
Unrecognized expansion board: 0
Beagle Rev C4
Die ID #4ee6000400000000040373050b01f00f
OMAP3 beagleboard.org #

I currently don't have bootcmd defined in nand environment, so it drops to a u-boot prompt instead of autobooting.

tags: added: iso-testing
Revision history for this message
Ricardo Salveti (rsalveti) wrote :

This is the current expected behavior from u-boot for omap3.

By default, u-boot-omap3 is compiled to support writing the environment at NAND (addr 0x00260000), together with a default environment, but only loads the default one (that searches for boot.scr) when your NAND environment is empty. This allows user customizations at the boot loader.

You can easily notice if you're using your custom environment or the default one by a warning from u-boot:
*** Warning - bad CRC or NAND, using default environment

So we have to possibilities to fix this issue:
1 - Document about possible issues regarding setting your own u-boot environment. You can get back to defaults by getting into u-boot prompt and giving "nand erase 260000 20000";
2 - Change u-boot to disallow personal environment customization. Easy fix, good for the distribution but we remove a feature from u-boot.

What do you think?

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Remember that this is only an issue for normal Beagleboards, as xM doesn't have NAND.

Revision history for this message
Tobin Davis (gruemaster) wrote :

This is still an issue. Adding a bitesize tag to see that it gets looked at.

tags: added: bitesize
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.