I followed https://www.digi.com/resources/documentation/digidocs/embedded/dey/3.2/cc8mmini/yocto_t_install-dey
repo init -u https://github.com/digi-embedded/dey-manifest.git -b refs/tags/3.2-r3.1
I don’t find any dts files in the sources/ diorectory. I’m working with a ccimx6ulstarter and have an upgraded dts file. Where do I copy it to make sure it gets built along with bitbake core-image-base?
build new workspace project first with default device tree, then modify it in tmp folder, aka:
Replace ccimx8x with the correct platform you are using
something like arch/arm/boot/dts/imx6ul-ccimx6ulstarter-id129.dts
Thank you for this Leonid, I will try it out. But I’m still wondering where the original dts in this directory is sourced from as the tmp/ dir just gets created during the bitbake operation.
Yes, in fact the link to ccimx8x-sbc-pro was wrong, I’m using ccimx6ulstarter.
So, as suggested, I copied the modified dts and modified the original imx6ul-ccimx6ulstarter-id129.dts. I then went back and executed bitbake core-image-base again but it seemed like it didn’t pick up the change.
So, to confirm I renamed tmp/deploy/ to tmp/deploy~/ and also renamed sstate-cache/ to sstate-cache~/ but re-invocation of bitbake core-image-base still seemed to re-use some of the cached files from the previous build. How do I get the new dts in the tmp/ compiled now?
>So, as suggested, I copied the modified dts and modified the original imx6ul-ccimx6ulstarter-id129.dts. I then went back and executed bitbake core-image-base again but it seemed like it didn’t pick up the change.
Yes, this is not enough. after modifying the device tree, go back to the workspace folder and do:
bitbake -c compile -f linux-dey
bitbake -C compile virtual/kernel