Thank you @jkridner ! Overlays are quite new to me. In the meantime I have been comparing the boot process of the official BBGW image with that of BalenaOS and have noticed that I get the below messages (These are the overlays included in UBoot by default):
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]
So I did some extensive googling and found out that the am335x-bonegreen-wireless-uboot-univ overlay references am335x-bonegreen-wireless-common-univ which overlay includes all GPIO and modes available for the BBGW.
I’ve included the overlay by creating a BitBake append file in my Yocto layer and added
am335x-bonegreen-wireless-uboot-univ.dtb to the
When I built and booted using this version the error during boot did not show up and neither did the
previous error (
Error: ENOENT: no such file or directory, open ‘/sys/devices/platform/ocp/ocp:P8_09_pinmux/state) however I have not yet verified that the actual pin state was changed.
I’m suspecting that this is a bug in the BalenaOs and should be added in linux-beagleboard_5.4.bb
Will post an update when I test the GPIO physical state.