I’m building the balena os to include my custom layer. I’m building and placing the dtbo in /boot/overlays/ and then writing the path in uEnv.txt_internal hower on boot I get an error that the overlay is not found. When I ssh into the device the overlays are present so I’m guessing the reference in the uEnv.txt_internal is wrong. What is the correct syntax to use?
mmc1(part 0) is current device
SD/MMC found on device 1
1303 bytes read in 1 ms (1.2 MiB/s)
Loaded env from uEnv.txt
Importing environment from …
switch to partitions #0, OK
mmc1(part 0) is current device
] …: [enable_uboot_overlays=1
] …: [enable_uboot_cape_universal=1
debug: [uboot_base_dtb_univ=am335x-bonegreen-wireless-uboot-univ.dtb] …
uboot_overlays: [uboot_base_dtb=am335x-bonegreen-wireless-uboot-univ.dtb] …
debug: unable to find [am335x-bonegreen-wireless-uboot-univ.dtb] using [am335x-boneblack-uboot.dtb] instead …
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot.dtb] …
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] …
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb …
loading /boot/am335x-boneblack-uboot.dtb …
91852 bytes read in 45 ms (1.9 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] …
]…t_overlays: unable to find [mmc 1:2 /boot/overlays/customoverlay.dtbo
]…t_overlays: unable to find [mmc 1:2 /boot/overlays/BB-CAN0-00A0.dtbo
]…t_overlays: unable to find [mmc 1:2 /boot/overlays/BB-CAN1-00A0.dtbo
uboot_overlays: loading /boot/overlays/BB-BONE-eMMC1-01-00A0.dtbo …
1584 bytes read in 165 ms (8.8 KiB/s)
uboot_overlays: loading /boot/overlays/BB-BBGW-WL1835-00A0.dtbo …
4785 bytes read in 173 ms (26.4 KiB/s)
uboot_overlays: loading /boot/overlays/BB-ADC-00A0.dtbo …
867 bytes read in 164 ms (4.9 KiB/s)
uboot_overlays: unable to find [mmc 1:2 /boot/overlays/univ-bbgw-EW-00A0.dtbo]…
SD/MMC found on device 1
From the logs you pasted I can see BB-CAN0-00A0 can’t be found either, but eMMC1-01-00A0 and WL1835 are found and loaded, so check on your board if the overlays you added are present on the board in /boot/overlays/your_custom.dtbo, also in /mnt/sysroot/active/current/boot/
Are you able to stop in u-boot cmdline and check with
ls mmc 1:2 boot/
ls mmc 1:2 boot/overlays/
if the overlays you need are there, or at least which ones are present? I recall checking CAN overlays on 2.56.0 and 2.58 and they were loading properly, wonder if your additional yocto layer could have anything to do with this.
CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver ‘omap_hsmmc’
No match for driver ‘omap_hsmmc’
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4… Card did not respond to voltage select!
Board: BeagleBone Black
not set. Validating first E-fuse MAC
BeagleBone Black:
Model: SeeedStudio BeagleBone Green Wireless:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x54:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x55:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x56:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net: eth0: MII MODE
Could not get PHY for cpsw: addr 0
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
=> ls mmc 1:2 boot/
I assume the dtb was added in your build and was not copied manually. If so, you can share a github with your repository and we can try do a custom build like you do. Also specify what yocto machine you are using.
I suspect you started a build with aufs and then switched the storage to overlay2 for the beagle green wifi, and the resulting build got corrupt. I commented out the balena_storage you switched in your local.conf and did a build from scratch, and can see your overlays get loaded:
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /boot/overlays/wetpits-00A0.dtbo ...
1532 bytes read in 172 ms (7.8 KiB/s)
uboot_overlays: loading /boot/overlays/BB-CAN0-00A0.dtbo ...
1198 bytes read in 288 ms (3.9 KiB/s)
uboot_overlays: loading /boot/overlays/BB-CAN1-00A0.dtbo ...
1198 bytes read in 293 ms (3.9 KiB/s)
uboot_overlays: loading /boot/overlays/BB-BONE-eMMC1-01-00A0.dtbo ...
1584 bytes read in 149 ms (9.8 KiB/s)
uboot_overlays: loading /boot/overlays/BB-BBGW-WL1835-00A0.dtbo ...
4785 bytes read in 81 ms (57.6 KiB/s)
uboot_overlays: loading /boot/overlays/BB-ADC-00A0.dtbo ...
867 bytes read in 186 ms (3.9 KiB/s)
867 bytes read in 186 ms (3.9 KiB/s)
uboot_overlays: cape universal disabled, external cape enabled or detected...
SD/MMC found on device 1
13672960 bytes read in 902 ms (14.5 MiB/s)
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
reserving fdt memory region: addr=88000000 size=78000
Loading Device Tree to 8ff85000, end 8fffffff ... OK
