How to list uBoot Overlays

hoffiz · April 29, 2018, 1:58pm

Is there a way to list currently loaded overlays after the Beagle has boot up? I’m disabling the video overlay in /boot/uEnv.txt and would like to see a before an after. Most of the print out, from other postes, seem to be with the debug port but curious of there is a way to know after it has boot up. I’m working on Beaglebone Black and this is the output of version.sh:

$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[ea6ea9fca05f36f5044398884375b0231348d6e2]
eeprom:[A335BNLT00C05014BBBK0DE2]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-01-28]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.01-00002-g9aa111a004]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.03-00002-gd12b1519b4]
kernel:[4.9.78-ti-r94]
nodejs:[v6.14.1]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg:[bb-cape-overlays]:[4.4.20180423.0-0rcnee0~stretch+20180423]
pkg:[bb-wl18xx-firmware]:[1.20180328-0rcnee2~stretch+20180328]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups: ‘debian’: no such user
groups:[]
dmesg | grep pinctrl-single
[ 1.459364] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
END

RobertCNelson · April 30, 2018, 1:12am

Your version of u-boot on the eMMC is too old thus blocking the new u-boot overlays feature.

Just save what your need and clear out the MBR in the eMMC…

sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10

Regards,

hoffiz · April 30, 2018, 1:13pm

Thanks, although that did upgrade the bootloader in the eMMC I’m still curious if there is a way to know which overlays are loaded, I used to: cat /sys/devices/platform/bone_capemgr/slots but that file does not exist anymore. I’m aware it was move to uBoot overlays just curious if there is a way to what is loaded without looking at uEnv.tx.

RobertCNelson · April 30, 2018, 6:40pm

@hoffiz sorry no, only eeprom detectable/loaded capes will show up in list dumped to /proc/cmdline, anything that’s just loaded thru /boot/uEnv.txt will not be reported anywhere outside /boot/uEnv.txt

You can see one example of that with the DLPDLCR2000 cape, as we need to issue 2 i2c commands to switch it’s display configuration on bootup:

github.com

RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L50-L59


unset detected_capes
detected_capes=$(cat /proc/cmdline | sed 's/ /\n/g' | grep uboot_detected_capes= || true)
if [ ! "x${detected_capes}" = "x" ] ; then
	got_DLPDLCR2000=$(echo ${detected_capes} | grep DLPDLCR2000 || true)
	if [ ! "x${got_DLPDLCR2000}" = "x" ] ; then
		echo "${log} found: DLPDLCR2000 init display"
		i2cset -y 2 0x1b 0x0b 0x00 0x00 0x00 0x00 i || true
		i2cset -y 2 0x1b 0x0c 0x00 0x00 0x00 0x1b i || true
	fi
fi

Regards,

hoffiz · May 2, 2018, 11:59am

Thank you. Cool cape :).