beaglebone auto loading handled by U-Boot

[daniel.er...@gmail.com]

I have two beaglebone boards...both SanCloud

I am trying to use /boot/uEnv.txt to load cape overlays...

One board the cape loads, the other board the cape does not...

dmesg showing board #1 below the cape loads @ 2.526116...

[    2.368226] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,SE0A,0617BBEF49D3'

[    2.368259] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4

[    2.406037] bone_capemgr bone_capemgr: slot #0: No cape found

[    2.446033] bone_capemgr bone_capemgr: slot #1: No cape found

[    2.486034] bone_capemgr bone_capemgr: slot #2: No cape found

[    2.526036] bone_capemgr bone_capemgr: slot #3: No cape found

[    2.526074] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-SPI1-01' VER 'N/A' PR '0'

[    2.526085] bone_capemgr bone_capemgr: slot #4: override

[    2.526100] bone_capemgr bone_capemgr: Using override eeprom data at slot 4

[    2.526116] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-SPI1-01'

vs. this board #2 below that doesn't work shows "auto loading handled by U-Boot" @ 2.373229

[    2.373029] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT,SE0A,0617BBEF494F'

[    2.373063] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4

[    2.373098] bone_capemgr bone_capemgr: slot #0: auto loading handled by U-Boot

[    2.373120] bone_capemgr bone_capemgr: slot #1: auto loading handled by U-Boot

[    2.373159] bone_capemgr bone_capemgr: slot #2: auto loading handled by U-Boot

[    2.373181] bone_capemgr bone_capemgr: slot #3: auto loading handled by U-Boot

[    2.373205] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-SPI1-01' VER 'N/A' PR '0'

[    2.373216] bone_capemgr bone_capemgr: slot #4: override

[    2.373229] bone_capemgr bone_capemgr: slot #4: auto loading handled by U-Boot

Both have the same uboot version string 

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.05-00002-gc0970ed183]

cape overlay files are present on both boards @ /lib/firmware

When I update initramfs I see this...

update-initramfs: Generating /boot/initrd.img-4.4.62-ti-r105

My /boot/uEnv.txt looks like this on both boards...

#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.4.62-ti-r105

#uuid=

#dtb=

###U-Boot Overlays###

###Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

###Master Enable

enable_uboot_overlays=1

###

###Overide capes with eeprom

#uboot_overlay_addr0=/lib/firmware/<file0>.dtbo

#uboot_overlay_addr1=/lib/firmware/<file1>.dtbo

#uboot_overlay_addr2=/lib/firmware/<file2>.dtbo

#uboot_overlay_addr3=/lib/firmware/<file3>.dtbo

###

###Additional custom capes

#uboot_overlay_addr4=/lib/firmware/<file4>.dtbo

#uboot_overlay_addr5=/lib/firmware/<file5>.dtbo

#uboot_overlay_addr6=/lib/firmware/<file6>.dtbo

#uboot_overlay_addr7=/lib/firmware/<file7>.dtbo

###

###Custom Cape

#dtb_overlay=/lib/firmware/<file8>.dtbo

###

###Disable auto loading of virtual capes (emmc/video/wireless/adc)

#disable_uboot_overlay_emmc=1

#disable_uboot_overlay_video=1

#disable_uboot_overlay_audio=1

#disable_uboot_overlay_wireless=1

#disable_uboot_overlay_adc=1

###

###PRUSS OPTIONS

###pru_rproc (4.4.x-ti kernel)

uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo

###pru_uio (mainline kernel)

#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo

###

###Cape Universal Enable

#enable_uboot_cape_universal=1

###

###Debug: disable uboot autoload of Cape

#disable_uboot_overlay_addr0=1

#disable_uboot_overlay_addr1=1

#disable_uboot_overlay_addr2=1

#disable_uboot_overlay_addr3=1

###

###U-Boot fdt tweaks...

#uboot_fdt_buffer=0x60000

###U-Boot Overlays###

cmdline=coherent_pool=1M net.ifnames=0 quiet

#In the event of edid real failures, uncomment this next line:

#cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e

##Example v3.8.x

#cape_disable=capemgr.disable_partno=

#cape_enable=capemgr.enable_partno=

##Example v4.1.x

cape_disable=bone_capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

cape_enable=bone_capemgr.enable_partno=BB-SPI1-01

##enable Generic eMMC Flasher:

##make sure, these tools are installed: dosfstools rsync

#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

I presently don't have access to boot console traffic.

Why does one board report auto loading handled by U-Boot, while the other board does not (and seems to load overlays and work properly)?

[francois...@gmail.com]

Did you find a solution to your problem? I am facing the same issue...

[ve7...@gmail.com]

Also the same (or similar) problem here. Only have the one BBB, noticed it as soon as I updated to the latest Debian 9.1 image (IoT).

[Robert Nelson]

On Wed, Sep 20, 2017 at 7:03 PM, <ve7...@gmail.com> wrote:
> Also the same (or similar) problem here. Only have the one BBB, noticed it
> as soon as I updated to the latest Debian 9.1 image (IoT).

Welcome to U-Boot overlays:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

Regards,

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