u-boot: invalid extent block

GoogleGroups
1

Hi,

I tried to upgrade to kernel 2.15.0-rc7-bone1
(http://rcn-ee.net/deb/trusty-armhf/v3.15.0-rc7-bone1/), but all I got
was an error from u-boot "invalid extent block". I am assuming this is
a bug in u-boot - is there any fix available (updated u-boot?) or
would I have to move the kernel to a fat filesystem (from an ext4 fs)
to work around the issue?

Christof

2

Yes, can you please try mainline U-Boot and see if the issue is resolved? Thanks!

3

What's the best way to test this?

I have downloaded u-boot-2014.04.tar.bz2 untarred, done a "make
omap3_beagle_config" and "make". This created a MLO (which is
significantly smaller than the one on my BBB) and a u-boot.img. Am I
supposed to copy these into /boot/uboot and just reboot or is there a
better way to test it (where I don't have to overwrite the existing
u-boot on the BBB)?

Christof

4

I should have been clearer, please try v2014.07-rc2 as there's some ext*
fixes in there which may help. For beaglebone you want either
am335x_evm or am335x_boneblack, and copy MLO and u-boot.img. You should
backup the existing MLO/u-boot.img elsewhere first, as a precaution.

5

[...]

I should have been clearer, please try v2014.07-rc2 as there's some ext*
fixes in there which may help. For beaglebone you want either
am335x_evm or am335x_boneblack, and copy MLO and u-boot.img. You should
backup the existing MLO/u-boot.img elsewhere first, as a precaution.

Finally managed to test it and the original bug is indeed fixed.

However, the default scripts built into u-boot.img seem to be somewhat
broken (particularly when you want to boot from the internal MMC, but
have a non-bootable uSD inserted). For example

  if run loadimage; then echo ok; fi

results in

  ** Invalid partition 2 **
  ok

Clearly, if it can't load the image, it shouldn't return ok.

This either results in a failure when importing uenv:

Importing environment from mmc ...
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
himport_r: can't insert "..."

or it tries to boot a kernel that it couldn't load.

Christof

6

We patched that call out in the new debian based beagleboard.org image.

https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2014.04/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch#L87

The only way it'll boot from the microSD is if a valid uEnv.txt file
is in the first partition and contains a "uenvcmd" variable
definition.

Regards,

7

I think this is related to some other command processing issues we’re sorting out in mainline right now. The ext* changes should be easily backportable however for distro folks.