2025-07-23 10:34 PM
Hi everyone,
I'm a beginner in Android development and currently working with the OpenST-Droid distribution. I have a question regarding the use of CubeMX: after generating the Device Tree using CubeMX, how should I integrate it into the OpenST-Droid distribution?
I’ve read the following article, but it doesn’t explain how to apply the Device Tree generated by CubeMX to OpenST-Droid:
STM32MPU Distribution Package for Android - stm32mpu
How to build OpenSTDroid distribution - stm32mpu
How to build kernel for Android - stm32mpu
Thank you in advance for your help!
2025-08-01 2:40 AM
Dear ST,
I have successfully completed the build, but I’m encountering an issue during the TF-A flashing process, which prevents it from proceeding normally.
The CPU is correctly recognized in the Yocto environment; however, in the Android system, the CPU information appears to be incorrect.
Are there any specific settings I should check, or any particular points I should pay attention to in this case?
Below are the logs from the flashing process for your reference:
Yocto Flashing Log:
NOTICE: CPU: STM32MP257DAK Rev.?
NOTICE: Model: STMicroelectronics custom STM32CubeMX board - openstlinux-6.6-yocto-scarthgap-mpu-v24.11.06
NOTICE: Reset reason (0x2035):
INFO: Power-on Reset (rst_por)
INFO: PMIC2 version = 0x11
INFO: PMIC2 product ID = 0x21
....
Android Flashing Log:
NOTICE: CPU: STM32MP257DAL Rev.B
NOTICE: Model: STMicroelectronics custom STM32CubeMX board - Android_TF-A
NOTICE: BL2: v2.8-stm32mp2-r1.1(release):lts-v2.8.15-2-g5dbb5ed12-dirty(5dbb5ed1)
NOTICE: BL2: Built : 17:54:54, Jul 28 2025
NOTICE: Core ID 5533330b
NOTICE: dwc3_get_dev_speed = HighSpeed
Thank you for your support!
2025-08-03 7:22 PM
I noticed that the tf-a-stm32mp2 patches used in Android and Yocto are different.
Android uses 0001-v2.8-stm32mp-r2-rc17.patch, while Yocto uses a newer patch: 0001-v2.10-stm32mp-r1.patch.
Would you recommend switching to the newer patch used in Yocto?