Had a working yocto build of st-image-weston for a custom machine based on 157-DK2, then I followed the simple instructions for update from openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06 to 6.0.3 (v25.04.30) -- just a new repo manifest tag...
https://wiki.st.com/stm32mpu/wiki/STM32_MPU_OpenSTLinux_release_note#v6-0-3
repo sync ran without errors
but now `bitbake st-image-weston` fails:
ERROR: Nothing RPROVIDES 'linux-firmware-bluetooth-bcm43xx' (but /home/aescape/Documents/projects/pensa/evon/code/dist-package/layers/openembedded-core/meta/recipes-core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'linux-firmware-bluetooth-bcm43xx' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['linux-firmware-bluetooth-bcm43xx']
NOTE: Runtime target 'packagegroup-base-extended' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-base-extended', 'linux-firmware-bluetooth-bcm43xx']
ERROR: Required build target 'st-image-weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['st-image-weston', 'packagegroup-base-extended', 'linux-firmware-bluetooth-bcm43xx']
My guess is likely a LICENSE_FLAGS_ACCEPTED thing somewhere moved or something? or license file somewhere?
My custom machine lic "layers/meta-st/meta-st-stm32mp-addons/conf/eula/stm32mp15-XXXXXXXX-mx" is in place, as well as "layers/meta-st/meta-st-stm32mp-addons/conf/eula/LICENCE.broadcom_bcm43xx"
Noticing a similar "eula" folder in "meta-st-stm32mp/conf/eula", I tried copying my custom machine file in there... then starting a fresh terminal with "envsetup.sh" - Didn't help
envsetup.sh does print "WITH_EULA_ACCEPTED: YES" so maybe it's not a licence thing, but i cant imagine the kernel firmware blob / recipe actually moved / changed
Trying a completely fresh rebuild (because "bitbake -c clean and cleansstate" both fail due to the failed RPROVIDES) and it still fails.
What gives? why would updating from 6.0.0 to 6.0.3 bork a yocto build setup using these instructions:
https://wiki.st.com/stm32mpu/wiki/How_to_create_your_own_machine
Side note, as I look into the cubemx project, there doesn't seem to be a way to update/refresh mainfest tags in the OpenSTLinux settings
I also tried a fresh DK2 project and 24.11.06 is the latest version of the dist-package cubemx 6.14.1 seems to be aware of.... bummer if i wrecked my yocto build, i guess i'll try to revert to 6.0.0 next
