random things I made and things I learnt making them
The STM32CubeIDE can be used to generate device tree source file (.dts) for your embedded linux image. These describe the hardware for the board on which linux will run. This is compiled into a device tree binary file (.dtb) which is included on the image and loaded by u-boot along with the Linux kernel zImage.
In this article we are going to create two STM32CubeIDE projects – a DK-2 project with all the presets and a custom project for the custom board – and compare them side-by-side.
Custom Board Design First lets discuss the hardware. There are vendor boards available: Evaluation boards are expensive due to the large number of external connectors and integrated circuitry (including FPGAs and HDMI decoders!). These are really meant for sales demos. Any development work done on these would be wasted time since your own custom design…
So you have the discovery kit and you’ve run the example image on the SD card. How do you build the image from scratch with Yocto and using a DTS file generated by STM32CubeIDE?
This is a completed version of the [What I wish I’d known about Yocto Project] page in the Yocto documentation. See https://docs.yoctoproject.org/what-i-wish-id-known.html
Some issues encountered when building the Yocto BSP for AM335x with the BeagleBone Black, and their solutions.
Using Dynamic Debug (debugfs) Check dynamic debug option is enabled in the kernel build grep CONFIG_DYNAMIC_DEBUG= /boot/config-uname -r If this is not enabled then you will need to set this option inmake menuconfigand rebuild the kernel Working with module names If you want to work with a single module use themodulequery and the module name…