BeagleBone Black, modified U-Boot, now getting err: Expected PARTUUID=<valid-uuid-id>[/PARTNROFF=%d]

Hi All,
I needed to modify my MLO and U-boot.img files in order to 1) chage DDR settings (I am using a different DDR chip than the stock BB chip), and also to configure autoboot settings.

I cloned u-boot, changed the settings I needed to change, compiled U-Boot and copied MLO and U-Boot.img to the correct partition on my bootable MMC card.

The BB boots fine from the SD card, with auto-boot configured as I want it to be, and also the RAM settings are fine.

However, when I try to clone my image onto the MMC, boot hangs up with the error shown in the subject line.

If I clone my image from the SD card to the MMC without my modified U-Boot, the Beagle Bone works fine. SO, in summary:

my modified u-boot files work fine when booting from SD card.

I can clone my SD card to the MMC of the BB an it works fine, using DD from an image file.

I can not clone my SD card to the MMC with the modified u-boot files… it will not boot in that circumstance.

I have tried running the script located at https://github.com/RobertCNelson/tools/tree/master/scripts to copy the SD card to the MMC (errors out with not enough space on device when copying). I have also tried loading the files through tftpboot, and still get the same error. I suspect that I have to change some setting in U-boot which has to do with load addresses, but not sure where/how to do this.

Any help would be apprectiated! My boot messages are below:

U-Boot SPL 2015.10-rc3-00297-g1a9c229-dirty (Sep 25 2015 - 18:11:28)
*** Warning - bad CRC, using default environment

reading u-boot.img
reading u-boot.img

U-Boot 2015.10-rc3-00297-g1a9c229-dirty (Sep 25 2015 - 18:11:28 -0600)

Watchdog enabled
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - bad CRC, using default environment

Net: not set. Validating first E-fuse MAC
cpsw, usb_ether
Card did not respond to voltage select!
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
reading boot.scr
** Unable to read file boot.scr **
reading uEnv.txt
716 bytes read in 5 ms (139.6 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
Running uenvcmd …
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1(part 0) is current device
3341744 bytes read in 237 ms (13.4 MiB/s)
Card did not respond to voltage select!
** Bad device mmc 0 **
24884 bytes read in 41 ms (591.8 KiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x32fdb0 ]

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Device Tree to 8fff6000, end 8ffff133 … OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.189961] omap2_mbox_probe: platform not supported
[ 0.346539] tps65217-bl tps65217-bl: no platform data provided
[ 0.410880] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.447987] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.485094] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.522203] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.542272] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.551911] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[ 0.558686] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.574192] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed
[ 0.638029] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 0.649803] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[ 0.657120] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 0.682772] dummy 0-0034: Error -121 writing to cec:0xff
[ 0.688534] tda998x 0-0070: Error -121 reading from 0xa
[ 0.694183] tda998x 0-0070: Error -121 writing to 0xa //HDMI CHIP IS REMOVED,
[ 0.750834] tda998x 0-0070: Error -121 reading from 0xa
[ 0.756434] tda998x 0-0070: Error -121 writing to 0xa
[ 0.813284] tda998x 0-0070: Error -121 reading from 0x1
[ 0.818856] tda998x 0-0070: Error -121 writing to 0x1
[ 0.824241] tda998x 0-0070: Error -121 reading from 0x1
[ 0.829808] tda998x 0-0070: Error -121 writing to 0x1
[ 0.835192] tda998x 0-0070: Error -121 writing to REG_CURPAGE
[ 0.841300] tda998x 0-0070: Error -121 writing to 0x200
[ 0.846867] tda998x 0-0070: Error -121 writing to 0x201
[ 0.852508] tda998x 0-0070: Error -121 writing to 0x202
[ 0.858079] tda998x 0-0070: Error -121 writing to 0x203
[ 0.863648] tda998x 0-0070: Error -121 writing to 0x204
[ 0.869213] tda998x 0-0070: Error -121 writing to 0x205
[ 0.874776] tda998x 0-0070: Error -121 writing to 0x20e
[ 0.880337] tda998x 0-0070: Error -121 writing to 0x211
[ 0.885900] tda998x 0-0070: Error -121 writing to 0x207
[ 0.891461] tda998x 0-0070: Error -121 writing to 0x208
[ 0.897023] tda998x 0-0070: Error -121 writing to 0x209
[ 0.902586] tda998x 0-0070: Error -121 writing to 0x20a
[ 0.908149] tda998x 0-0070: Error -121 writing to 0x206
[ 0.913708] tda998x 0-0070: Error -121 writing to REG_CURPAGE
[ 0.919816] tda998x 0-0070: Error -121 reading from 0x0
[ 0.925379] tda998x 0-0070: Error -121 reading from 0x2
[ 0.931109] tilcdc 4830e000.fb: no encoders/connectors found
[ 0.937069] tilcdc 4830e000.fb: failed to initialize mode setting
[ 1.001020] VFS: PARTUUID= is invalid.
[ 1.001020] Expected PARTUUID=[/PARTNROFF=%d]
[ 1.010925] Disabling rootwait; root= is invalid.
[ 1.016456] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.025163] [] (unwind_backtrace+0x0/0xe0) from [] (panic+0x84/0x1e0)
[ 1.033749] [] (panic+0x84/0x1e0) from [] (mount_block_root+0x1e4/0x224)
[ 1.042595] [] (mount_block_root+0x1e4/0x224) from [] (mount_root+0xe8/0x108)
[ 1.051895] [] (mount_root+0xe8/0x108) from [] (prepare_namespace+0x15c/0x1bc)
[ 1.061285] [] (prepare_namespace+0x15c/0x1bc) from [] (kernel_init+0x8/0xe4)
[ 1.070589] [] (kernel_init+0x8/0xe4) from [] (ret_from_fork+0x14/0x3c)

So, this is expected... After "2015.10-rc3" u-boot added the partuuid
patchset.. I have an idea how to safely use it, but it's untested
right now.

Just checkout v2015.10-rc3 and make your changes for the moment, don't
go beyond it..

Regards,

for reference, this is what your fighting past rc3:

http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/ti_armv7_common.h;hb=HEAD#l61

i have an idea for utilizing it, but still being compatible with older
uEnv.txt setups..

Regards,

Thanks very much, the older version of u-boot worked perfectly! I truly appreciate your help. Best of luck with getting around the issues raised by the newer U-boot versions… will upgrade when it becomes possible.

CONFIDENTIALITY NOTICE: This electronic transmission, including all attachments, is directed in confidence solely to the person(s) to whom it is addressed, or an authorized recipient, and may not otherwise be distributed, copied or disclosed. The contents of the transmission may also be subject to intellectual property rights and all such rights are expressly claimed and are not waived. If you have received this transmission in error, please notify the sender immediately by return electronic transmission and then immediately delete this transmission, including all attachments, without copying, distributing or disclosing same.