BB not completing boot w/ updated U-Boot: changed U-Boot 2013.10-00249-g15 > U-Boot SPL 2015.10-rc2

[Chris R]

I downloaded and compiled u-boot u-boot-2015.10-rc2. I am using kernel debian-wheezy-7.2-(armhf-rootfs-3.8.13-bone30) on a Beaglebone Black.

The configuration works fine until I update u-boot to the version above.

After copying in the MLO and u-boot.img files, everything goes well until the kernel "init". At this point, the board hangs, but will continue along fine as soon as I insert an SD card (which is a clone of the internal MMC, except it has the original u-boot. 

Any help on getting this to boot would be greatly appreciated!!

I suspect it is not finding/reading the initramFS correctly, or the fdt file...  and not sure how to configure this correctly in u-boot. 

Any help would be truly appreciated!

the boot proceeds as follows:

-----------------------------------------------------------------------------------------------------------

From the updated, non working u-boot:

------------------------------------------------------------------------------------------------------------

U-Boot SPL 2015.10-rc2 (Oct 08 2015 - 04:17:11)

*** Warning - bad CRC, using default environment

reading u-boot.img

reading u-boot.img

U-Boot 2015.10-rc2 (Oct 08 2015 - 04:17:11 +0000)

       Watchdog enabled

I2C:   ready

DRAM:  512 MiB

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

*** Warning - bad CRC, using default environment

Net:   <ethaddr> 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 4 ms (174.8 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 212 ms (15 MiB/s)

24884 bytes read in 30 ms (809.6 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.189724] omap2_mbox_probe: platform not supported

[    0.346410] tps65217-bl tps65217-bl: no platform data provided

[    0.410607] bone-capemgr bone_capemgr.9: slot #0: No cape found

[    0.447713] bone-capemgr bone_capemgr.9: slot #1: No cape found

[    0.484820] bone-capemgr bone_capemgr.9: slot #2: No cape found

[    0.521930] bone-capemgr bone_capemgr.9: slot #3: No cape found

[    0.542007] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)

[    0.551647] bone-capemgr bone_capemgr.9: slot #6: Failed verification

[    0.558421] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)

[    0.573956] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed

[    0.637754] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8

[    0.649524] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22

[    0.656840] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single

----hangs here until SD card is inserted

----------------------------------------------------------------------------------------------------------------------------------------

my printenv from the non-working u-boot:

----------------------------------------------------------------------------------------------------------------------------------------

arch=arm

baudrate=115200

board=am335x

board_name=A335BNLT

board_rev=00C0

boot_fdt=try

bootcmd=run findfdt; run mmcboot;setenv mmcdev 1; setenv bootpart 1:2; run mmcboot;run nandboot;

bootcount=19

bootdelay=1

bootdir=/boot

bootenv=uEnv.txt

bootfile=zImage

bootm_size=0x10000000

bootpart=0:2

bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}

console=ttyO0,115200n8

cpu=armv7

dfu_alt_info_emmc=rawemmc raw 0 3751936

dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw raw 0x100 0x100;u-boot.img.raw raw 0x300 0x400;spl-os-args.raw raw 0x80 0x80;spl-os-image.raw raw 0x900 0x2000;spl-os-args fat 0 1;spl-os-image fat 0 1;u-boot.img fat 0 1;uEnv.txt fat 0 1

dfu_alt_info_ram=kernel ram 0x80200000 0xD80000;fdt ram 0x80F80000 0x80000;ramdisk ram 0x81000000 0x4000000

eth1addr=6c:ec:eb:8a:f7:fa

ethact=cpsw

ethaddr=6c:ec:eb:8a:f7:f8

fdt_addr_r=0x88000000

fdtaddr=0x88000000

fdtfile=undefined

findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A335BNLT; then setenv fdtfile am335x-boneblack.dtb; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name = A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi; if test $fdtfile = undefined; then echo WARNING: Could not determine device tree to use; fi;

importbootenv=echo Importing environment from mmc ...; env import -t -r $loadaddr $filesize

kernel_addr_r=0x82000000

loadaddr=0x82000000

loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootenv}

loadbootscript=load mmc ${mmcdev} ${loadaddr} boot.scr

loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}

loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}

loadramdisk=load mmc ${mmcdev} ${rdaddr} ramdisk.gz

mmcargs=setenv bootargs console=${console} ${optargs} root=${mmcroot} rootfstype=${mmcrootfstype}

mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootscript; then run bootscript;else if run loadbootenv; then echo Loaded environment from ${bootenv};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;if run loadimage; then run mmcloados;fi;fi ;fi;

mmcdev=0

mmcloados=run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdtaddr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;

mmcroot=/dev/mmcblk0p2 ro

mmcrootfstype=ext4 rootwait

netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp

netboot=echo Booting from network ...; setenv autoload no; dhcp; run netloadimage; run netloadfdt; run netargs; bootz ${loadaddr} - ${fdtaddr}

netloadfdt=tftp ${fdtaddr} ${fdtfile}

netloadimage=tftp ${loadaddr} ${bootfile}

nfsopts=nolock

partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=2MiB,size=-,uuid=${uuid_gpt_rootfs}

ramargs=setenv bootargs console=${console} ${optargs} root=${ramroot} rootfstype=${ramrootfstype}

ramboot=echo Booting from ramdisk ...; run ramargs; bootz ${loadaddr} ${rdaddr} ${fdtaddr}

ramdisk_addr_r=0x88080000

ramroot=/dev/ram0 rw

ramrootfstype=ext2

rdaddr=0x88080000

rootpath=/export/rootfs

soc=am33xx

spiargs=setenv bootargs console=${console} ${optargs} root=${spiroot} rootfstype=${spirootfstype}

spiboot=echo Booting from spi ...; run spiargs; sf probe ${spibusno}:0; sf read ${loadaddr} ${spisrcaddr} ${spiimgsize}; bootz ${loadaddr}

spibusno=0

spiimgsize=0x362000

spiroot=/dev/mtdblock4 rw

spirootfstype=jffs2

spisrcaddr=0xe0000

static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off

stderr=serial_omap

stdin=serial_omap

stdout=serial_omap

usbnet_devaddr=6c:ec:eb:8a:f7:fa

vendor=ti

ver=U-Boot 2015.10-rc2 (Oct 08 2015 - 04:17:11 +0000)

==========================================================================================================================

If I do a printenv from the older, working u-boot, I get this:

==========================================================================================================================

arch=arm

baudrate=115200

board=am335x

board_name=A335BNLT

board_rev=00C0

boot_fdt=try

bootcmd=run findfdt; run mmcboot;setenv mmcdev 1; setenv bootpart 1:2; run mmcboot;run nandboot;

bootdelay=1

bootdir=/boot

bootenv=uEnv.txt

bootfile=zImage

bootpart=0:2

console=ttyO0,115200n8

cpu=armv7

dfu_alt_info_emmc=rawemmc mmc 0 3751936

dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw mmc 100 100;u-boot.img.raw mmc 300 400;spl-os-args.raw mmc 80 80;spl-os-image.raw mmc 900 2000;spl-os-args fat 0 1;spl-os-image fat 0 1;u-boot.img fat 0 1;uEnv.txt fat 0 1

dfu_alt_info_nand=SPL part 0 1;SPL.backup1 part 0 2;SPL.backup2 part 0 3;SPL.backup3 part 0 4;u-boot part 0 5;u-boot-spl-os part 0 6;kernel part 0 8;rootfs part 0 9

dfu_alt_info_ram=kernel ram 0x80200000 0xD80000;fdt ram 0x80F80000 0x80000;ramdisk ram 0x81000000 0x4000000

ethact=cpsw

ethaddr=6c:ec:eb:8a:f7:f8

fdt_high=0xffffffff

fdtaddr=0x80F80000

fdtfile=undefined

findfdt=if test $board_name = A335BONE; then setenv fdtfile am335x-bone.dtb; fi; if test $board_name = A335BNLT; then setenv fdtfile am335x-boneblack.dtb; fi; if test $board_name = A33515BB; then setenv fdtfile am335x-evm.dtb; fi; if test $board_name = A335X_SK; then setenv fdtfile am335x-evmsk.dtb; fi; if test $fdtfile = undefined; then echo WARNING: Could not determine device tree to use; fi;

importbootenv=echo Importing environment from mmc ...; env import -t $loadaddr $filesize

loadaddr=0x80200000

loadbootenv=load mmc ${mmcdev} ${loadaddr} ${bootenv}

loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}

loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}

loadramdisk=load mmc ${mmcdev} ${rdaddr} ramdisk.gz

mmcargs=setenv bootargs console=${console} ${optargs} root=${mmcroot} rootfstype=${mmcrootfstype}

mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootenv; then echo Loaded environment from ${bootenv};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;if run loadimage; then run mmcloados;fi;fi;

mmcdev=0

mmcloados=run mmcargs; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdtaddr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;

mmcroot=/dev/mmcblk0p2 ro

mmcrootfstype=ext4 rootwait

mtdids=nand0=omap2-nand.0

mtdparts=mtdparts=omap2-nand.0:128k(SPL),128k(SPL.backup1),128k(SPL.backup2),128k(SPL.backup3),1792k(u-boot),128k(u-boot-spl-os),128k(u-boot-env),5m(kernel),-(rootfs)

nandargs=setenv bootargs console=${console} ${optargs} root=${nandroot} rootfstype=${nandrootfstype}

nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} ${nandsrcaddr} ${nandimgsize}; bootz ${loadaddr}

nandimgsize=0x500000

nandroot=ubi0:rootfs rw ubi.mtd=7,2048

nandrootfstype=ubifs rootwait=1

nandsrcaddr=0x280000

netargs=setenv bootargs console=${console} ${optargs} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp

netboot=echo Booting from network ...; setenv autoload no; dhcp; tftp ${loadaddr} ${bootfile}; tftp ${fdtaddr} ${fdtfile}; run netargs; bootz ${loadaddr} - ${fdtaddr}

nfsopts=nolock

ramargs=setenv bootargs console=${console} ${optargs} root=${ramroot} rootfstype=${ramrootfstype}

ramboot=echo Booting from ramdisk ...; run ramargs; bootz ${loadaddr} ${rdaddr} ${fdtaddr}

ramroot=/dev/ram0 rw ramdisk_size=65536 initrd=${rdaddr},64M

ramrootfstype=ext2

rdaddr=0x81000000

rootpath=/export/rootfs

soc=am33xx

spiargs=setenv bootargs console=${console} ${optargs} root=${spiroot} rootfstype=${spirootfstype}

spiboot=echo Booting from spi ...; run spiargs; sf probe ${spibusno}:0; sf read ${loadaddr} ${spisrcaddr} ${spiimgsize}; bootz ${loadaddr}

spibusno=0

spiimgsize=0x362000

spiroot=/dev/mtdblock4 rw

spirootfstype=jffs2

spisrcaddr=0xe0000

static_ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off

stderr=serial

stdin=serial

stdout=serial

usbnet_devaddr=6c:ec:eb:8a:f7:f8

vendor=ti

ver=U-Boot 2013.10-00249-g15c5cdf (Nov 17 2013 - 16:35:11)

===========================================================================================================================

and the older, working u-boot boots like this:

===========================================================================================================================

U-Boot 2013.10-00249-g15c5cdf (Nov 17 2013 - 16:35:11)

I2C:   ready

DRAM:  512 MiB

WARNING: Caches not enabled

NAND:  0 MiB

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

*** Warning - readenv() failed, using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC

cpsw, usb_ether

Hit any key to stop autoboot:  0

Card did not respond to voltage select!

mmc0(part 0) is current device

Card did not respond to voltage select!

mmc1(part 0) is current device

SD/MMC found on device 1

reading uEnv.txt

716 bytes read in 3 ms (232.4 KiB/s)

Loaded environment from uEnv.txt

Importing environment from mmc ...

Running uenvcmd ...

Card did not respond to voltage select!

mmc0(part 0) is current device

Card did not respond to voltage select!

mmc1(part 0) is current device

3341744 bytes read in 473 ms (6.7 MiB/s)

24884 bytes read in 28 ms (867.2 KiB/s)

Kernel image @ 0x80200000 [ 0x000000 - 0x32fdb0 ]

## Flattened Device Tree blob at 80f80000

   Booting using the fdt blob at 0x80f80000

   Using Device Tree in place at 80f80000, end 80f89133

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

[    0.186740] omap2_mbox_probe: platform not supported

[    0.343436] tps65217-bl tps65217-bl: no platform data provided

[    0.407601] bone-capemgr bone_capemgr.9: slot #0: No cape found

[    0.444707] bone-capemgr bone_capemgr.9: slot #1: No cape found

[    0.481814] bone-capemgr bone_capemgr.9: slot #2: No cape found

[    0.518923] bone-capemgr bone_capemgr.9: slot #3: No cape found

[    0.539034] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)

[    0.548674] bone-capemgr bone_capemgr.9: slot #6: Failed verification

[    0.555446] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)

[    0.570938] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed

[    0.634741] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8

[    0.646513] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22

[    0.653828] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single

INIT: version 2.88 booting

[info] Using makefile-style concurrent boot in runlevel S.

[ ok ] Starting the hotplug events dispatcher: udevd.

[ ok ] Synthesizing the initial hotplug events...done.

[ ok ] Waiting for /dev to be fully populated...done.

[ ok ] Setting preliminary keymap...done.

[ ok ] Activating swap...done.

[....] Checking root file system...fsck from util-linux 2.20.1

/dev/mmcblk0p2: clean, 28972/236176 files, 221822/923136 blocks

done.

[ ok ] Cleaning up temporary files... /tmp.

[ ok ] Activating lvm and md swap...done.

[....] Checking file systems...fsck from util-linux 2.20.1

done.

[ ok ] Mounting local filesystems...done.

[ ok ] Activating swapfile swap...done.

[ ok ] Cleaning up temporary files....

[ ok ] Setting kernel variables ...done.

[....] Setting up resolvconf.../etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf

done.

[....] Configuring network interfaces...Cannot find device "eth0"

Failed to bring up eth0.

done.

[ ok ] Cleaning up temporary files....

[info] Setting console screen modes.

setterm: cannot (un)set powersave mode: Inappropriate ioctl for device

[info] Skipping font and keymap setup (handled by console-setup).

[ ok ] Setting up console font and keymap...done.

[ ok ] Setting sensors limits.

INIT: Entering runlevel: 2

[info] Using makefile-style concurrent boot in runlevel 2.

[ ok ] Starting enhanced syslogd: rsyslogd.

[ ok ] Starting periodic command scheduler: cron.

[ ok ] Starting system message bus: dbus.

[ ok ] Starting OpenBSD Secure Shell server: sshd.

[Chris R]

1)As an added assistance to anyone who may want to opine on my issue, I have made this table which lists some of the differences I notice between the working printenv and bootup messages, and the non working one. There may be others.

2)Additionally, I have basically just copied MLO and u-boot.img into the 1st (fat) partition on my MMC. I have tried other methods of writing it directly (with tftp, mmc write, etc) but those seem to destroy my partition table. I don't think my methods of copying MLO and u-boot.img are at fault, but certainly a possility.

THANKS!

BOOT MESSAGES:
NOT WORKING	WORKING

Kernel image @ 0x82000000 [ 0x000000 - 0x32fdb0 ]

Kernel image @ 0x80200000 [ 0x000000 - 0x32fdb0 ]
fdt blob at 0x88000000	fdt blob at 0x80f80000

Loading Device Tree to 8fff6000, end 8ffff133 ... OK

Using Device Tree in place at 80f80000, end 80f89133
Printenv:

dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw raw 0x100 0x100;

dfu_alt_info_mmc=boot part 0 1;rootfs part 0 2;MLO fat 0 1;MLO.raw mmc 100 100
fdt_addr_r=0x88000000	fdt_high=0xffffffff
fdtaddr=0x88000000	fdtaddr=0x80F80000
loadaddr=0x82000000	loadaddr=0x80200000

[Robert Nelson]

Your "working" values actually break with v3.14+..

use: the defaults in u-boot mainline:

43 /*

44  * We setup defaults based on constraints from the Linux kernel, which should

45  * also be safe elsewhere.  We have the default load at 32MB into DDR (for

46  * the kernel), FDT above 128MB (the maximum location for the end of the

47  * kernel), and the ramdisk 512KB above that (allowing for hopefully never

48  * seen large trees).  We say all of this must be within the first 256MB

49  * as that will normally be within the kernel lowmem and thus visible via

50  * bootm_size and we only run on platforms with 256MB or more of memory.

51  */

52 #define DEFAULT_LINUX_BOOT_ENV \

53         "loadaddr=0x82000000\0" \

54         "kernel_addr_r=0x82000000\0" \

55         "fdtaddr=0x88000000\0" \

56         "fdt_addr_r=0x88000000\0" \

57         "rdaddr=0x88080000\0" \

58         "ramdisk_addr_r=0x88080000\0" \

59         "bootm_size=0x10000000\0"

Regards,

--

Robert Nelson
https://rcn-ee.com/

[Chris R]

Mr Nelson,

Thanks very much for helping me on this!

I made sure the values you specified in the previous post are in the u-boot that I am compiling. 

At this point, u-boot goes all the way up to the point, (I believe) where it mounts the root filesystem, but it looks for mmcblk1p2, instead of using mmcblk0p2. I don't think there is anything wrong with my filesystem on mmcblk0, since as soon as I put my original u-boot.img back into the boot partition of mmcblk0, it boots all the way through. I believe that somehow, it starts looking for the wrong mmc device when I update u-boot.img .

I will put the boot output below: 

==================================================================================================

[    2.220710] mmc1: BKOPS_EN bit is not set

[    2.228889] mmc1: new high speed MMC card at address 0001

[    2.235147] mmcblk0: mmc1:0001 MMC04G 3.60 GiB

[    2.240184] mmcblk0boot0: mmc1:0001 MMC04G partition 1 2.00 MiB

[    2.246631] mmcblk0boot1: mmc1:0001 MMC04G partition 2 2.00 MiB

[    2.254065]  mmcblk0: p1 p2

[    2.258902]  mmcblk0boot1: unknown partition table

[    2.265208]  mmcblk0boot0: unknown partition table

[    2.325107] tilcdc 4830e000.fb: found TDA19988

[    2.330398] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).

[    2.337346] [drm] No driver support for vblank timestamp query.

[    2.343878] tilcdc 4830e000.fb: No connectors reported connected with modes

[    2.351204] [drm] Cannot find any crtc or sizes - going 1024x768

[    2.365622] Console: switching to colour frame buffer device 128x48

[    2.377269] tilcdc 4830e000.fb: fb0:  frame buffer device

[    2.382943] tilcdc 4830e000.fb: registered panic notifier

[    2.388690] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0

[    2.443722] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6

[    2.450151] davinci_mdio 4a101000.mdio: detected phy mask fffffffe

[    2.457520] libphy: 4a101000.mdio: probed

[    2.461767] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720

[    2.471585] Detected MACID = 6c:ec:eb:8a:f7:f8

[    2.476207] cpsw 4a100000.ethernet: NAPI disabled

[    2.482583] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:44:42 UTC (946687482)

[    2.496742] ALSA device list:

[    2.499916]   #0: TI BeagleBone Black

[    2.504559] Waiting for root device /dev/mmcblk1p2...

And only if I insert the SD card, then

 2.504559] Waiting for root device /dev/mmcblk1p2...[   90.296835] mmc0: host does not support reading read-only switch. assuming write-enable.

[   90.307412] mmc0: new high speed SDHC card at address 59b4

[   90.313821] mmcblk1: mmc0:59b4 00000 14.9 GiB

[   90.321522]  mmcblk1: p1 p2 p3

[   90.396006] EXT4-fs (mmcblk1p2): INFO: recovery required on readonly filesystem

[   90.403734] EXT4-fs (mmcblk1p2): write access will be enabled during recovery

[   90.703869] EXT4-fs (mmcblk1p2): recovery complete

[   90.715617] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)

[   90.724193] VFS: Mounted root (ext4 filesystem) readonly on device 179:26.

[   90.735590] devtmpfs: mounted

[   90.739161] Freeing init memory: 292K

INIT: version 2.88 booting

[info] Using makefile-style concurrent boot in runlevel S.

etc.

==================================================================================================================

and i put the original u-boot.img file there, and boot just from the MMC:

 2.211785] mmc1: BKOPS_EN bit is not set

[    2.219985] mmc1: new high speed MMC card at address 0001

[    2.226237] mmcblk0: mmc1:0001 MMC04G 3.60 GiB

[    2.231266] mmcblk0boot0: mmc1:0001 MMC04G partition 1 2.00 MiB

[    2.237726] mmcblk0boot1: mmc1:0001 MMC04G partition 2 2.00 MiB

[    2.245161]  mmcblk0: p1 p2

[    2.249980]  mmcblk0boot1: unknown partition table

[    2.256270]  mmcblk0boot0: unknown partition table

[    2.316240] tilcdc 4830e000.fb: found TDA19988

[    2.321553] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).

[    2.328503] [drm] No driver support for vblank timestamp query.

[    2.335033] tilcdc 4830e000.fb: No connectors reported connected with modes

[    2.342361] [drm] Cannot find any crtc or sizes - going 1024x768

[    2.356778] Console: switching to colour frame buffer device 128x48

[    2.368429] tilcdc 4830e000.fb: fb0:  frame buffer device

[    2.374103] tilcdc 4830e000.fb: registered panic notifier

[    2.379856] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0

[    2.434858] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6

[    2.441281] davinci_mdio 4a101000.mdio: detected phy mask fffffffe

[    2.448700] libphy: 4a101000.mdio: probed

[    2.452949] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720

[    2.462762] Detected MACID = 6c:ec:eb:8a:f7:f8

[    2.467380] cpsw 4a100000.ethernet: NAPI disabled

[    2.473760] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:49:35 UTC (946687775)

[    2.487885] ALSA device list:

[    2.491054]   #0: TI BeagleBone Black

[    2.505237] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

[    2.513843] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.

[    2.525584] devtmpfs: mounted

[    2.529286] Freeing init memory: 292K

INIT: version 2.88 booting

[info] Using makefile-style concurrent boot in runlevel S.

[....] Starting the hotplug events dispatcher: udevd[    3.350101] udevd[197]: starting version 175

. ok

[ ok ] Synthesizing the initial hotplug events...done.

[....] Waiting for /dev to be fully populated...[    4.802195] usb 1-1: new high-speed USB device number 2 using musb-hdrc

[    4.933710] usb 1-1: New USB device found, idVendor=154b, idProduct=0095

[    4.940825] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[    4.948326] usb 1-1: Product: USB 3.0 FD

[    4.952452] usb 1-1: Manufacturer: PNY Technologies

[    4.957576] usb 1-1: SerialNumber: 1968984357

[    4.974029] scsi0 : usb-storage 1-1:1.0

etc.

[Robert Nelson]

On Thu, Oct 8, 2015 at 5:56 PM, Chris R <christoph...@iperc.com> wrote:
>> Mr Nelson,
>
> Thanks very much for helping me on this!
> I made sure the values you specified in the previous post are in the u-boot
> that I am compiling.
> At this point, u-boot goes all the way up to the point, (I believe) where it
> mounts the root filesystem, but it looks for mmcblk1p2, instead of using
> mmcblk0p2. I don't think there is anything wrong with my filesystem on
> mmcblk0, since as soon as I put my original u-boot.img back into the boot
> partition of mmcblk0, it boots all the way through. I believe that somehow,
> it starts looking for the wrong mmc device when I update u-boot.img .

Correct, when the microSD is plugged in:

u-boot:
microSD = mmc0
eMMC = mmc1

kernel:
microSD = /dev/mmcblk0
eMMC = /dev/mmcblk1

When microSD is not plugged in:

u-boot:
microSD = mmc0 (but empty)
eMMC = mmc1

kernel:
microSD = <>
eMMC = /dev/mmcblk1

aka, use an uuid/initramfs when you want to use the eMMC as rootfs
without the microSD card plugged,..

[Robert Nelson]

On Thu, Oct 8, 2015 at 6:10 PM, Robert Nelson <robert...@gmail.com> wrote:
> On Thu, Oct 8, 2015 at 5:56 PM, Chris R <christoph...@iperc.com> wrote:
>>> Mr Nelson,
>>
>> Thanks very much for helping me on this!
>> I made sure the values you specified in the previous post are in the u-boot
>> that I am compiling.
>> At this point, u-boot goes all the way up to the point, (I believe) where it
>> mounts the root filesystem, but it looks for mmcblk1p2, instead of using
>> mmcblk0p2. I don't think there is anything wrong with my filesystem on
>> mmcblk0, since as soon as I put my original u-boot.img back into the boot
>> partition of mmcblk0, it boots all the way through. I believe that somehow,
>> it starts looking for the wrong mmc device when I update u-boot.img .
>

and i screwed this up: (2nd try)

Correct, when the microSD is plugged in:

u-boot:
microSD = mmc0
eMMC = mmc1

kernel:
microSD = /dev/mmcblk0
eMMC = /dev/mmcblk1

When microSD is not plugged in:

u-boot:
microSD = mmc0 (but empty)
eMMC = mmc1

kernel:
microSD = <>

eMMC = /dev/mmcblk0

[Chris R]

"aka, use an uuid/initramfs when you want to use the eMMC as rootfs 
without the microSD card plugged,"

 

So, and I thank you for your patience- I am in the situation here where I am booted from my MMC, (sd card is not in the machine). My BB is booted up and happy. I want to copy my new u-boot.img file into partition 1, so as to dispense with auto-boot. I know that if I just copy it now, it will, upon reboot, not mount the mmc root filesystem, like it does now.

 

So I must first generate an initramfs? I did try update-initramfs -u, and that does nothing- no messages, etc... I tried update-initramfs -c, but that just tells me how to use initramfs.

 

Or do you mean I have to configure u-boot or uEnv.txt to use an initramfs? Sorry, I am quite new to this, and thanks.

[Robert Nelson]

On Thu, Oct 8, 2015 at 6:44 PM, Chris R <christoph...@iperc.com> wrote:
> "aka, use an uuid/initramfs when you want to use the eMMC as rootfs
> without the microSD card plugged,"
>
>>
>> So, and I thank you for your patience- I am in the situation here where I
>> am booted from my MMC, (sd card is not in the machine). My BB is booted up
>> and happy. I want to copy my new u-boot.img file into partition 1, so as to
>> dispense with auto-boot. I know that if I just copy it now, it will, upon
>> reboot, not mount the mmc root filesystem, like it does now.

Your other option, force root=mmcblk0p1 (but then it won't work if
your microSD is plugged in)

>> So I must first generate an initramfs? I did try update-initramfs -u, and
>> that does nothing- no messages, etc... I tried update-initramfs -c, but that
>> just tells me how to use initramfs.

sudo update-initramfs -ck `uname -r`

>> Or do you mean I have to configure u-boot or uEnv.txt to use an initramfs?
>> Sorry, I am quite new to this, and thanks.

You'll also have to configure u-boot to load the generated
initrd.img-`uname -r` as that's what is going ot decode the "uuid =
/dev/mmblkXyZ"...

you can use:

ls -lh /dev/disk/by-uuid/*

to find the uuid of the eMMC partition...

[Christopher Rowland]

Mr Nelson,

Thank you very much! When I finally saw that Kernel booting, it was more beautiful than a sunset by the ocean.

I intend to looking into the options as far as getting the UUID going; however for the moment I used your "option 1" and forced the board to boot from the MMC. I searched around for quite a while trying to find a "force root" command for u-boot, but finally understood that you meant that more figuratively. I modified uEnv.txt like this, and it works.. i just specified device 1 rather than variables. I will try the other option later down the road. I think I may have changed it more than I needed to, but it does work. Thanks again!!

mmcpart=2

optargs=fixrtc capemgr.enable_partno=BB-UART2,BB-UART4

uenvcmd=i2c mw 0x24 1 0x3e; kd=0; if test $mmcdev -eq 1; then mmc dev 1; if mmc rescan; then kd=1; fi; mmc dev 1; fi; setenv mmcroot /dev/mmcblk0p${mmcpart} ro

loadfdt=load mmc 1:${mmcpart} ${fdtaddr} ${bootdir}/dtbs/${fdtfile}

loadimage=load mmc 1:${mmcpart} ${loadaddr} ${bootdir}/${bootfile}

optargs=quiet drm.debug=7 capemgr.enable_partno=BB-I2C1

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/tWFY4RBgBgQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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.