STM32MP1 Distribution Package Support
Forums › Reference, Evaluation, and Development Boards › OSD32MP1-BRK › STM32MP1 Distribution Package Support
Tagged: osd32mp1-brk
- This topic has 9 replies, 4 voices, and was last updated 3 years, 7 months ago by
Neeraj Dantu.
- AuthorPosts
- March 2, 2021 at 10:13 am #11329
We would like to use the STM32MP1 Distribution Package (https://wiki.st.com/stm32mpu/wiki/STM32MP1_Distribution_Package) to customize and build images for the OSD32MP1-BRK. Do you have procedures that can be used to add support for this board to the Distribution Package, or are there plans to provide this information?
- March 3, 2021 at 2:58 pm #11330
I was recently able to create a bootable image using the STMicro distribution package. I no longer need this information.
- March 4, 2021 at 12:50 pm #11332
bduke,
Glad you were able to get it working. Distribution Package support for BRK board is in the works. In the meantime, if you can, please feel free share your knowledge for the community.
Please let us know if you have any more questions.
Best,
Neeraj
- March 16, 2021 at 6:22 am #11359
Hi bduke,
I am struggling from the last few days to build bootable image from distribution package using OSD32MP1-BRK devicetree.While trying with repo TAG= openstlinux-5.4-dunfell-mp1-20-11-12 build always failed with :
Error: /stm32mp151/build-openstlinuxweston-stm32mp1-smufs/tmp-glibc/work-shared/stm32mp1-smufs/kernel-source/arch/arm/boot/#dts/ stm32mp157c-smufs.dts:1017.1-7 Label or path optee not found | FATAL ERROR: Syntax error parsing input treeUsing repo TAG= openstlinux-5.4-dunfell-mp1-20-06-24, everything builds fine but does n’t boot 🙁
Warning i got during build was :
WARNING: st-initrd-1.0-r0 do_package: Manifest /home/rishiosd/osd32mp1/build-openstlinuxweston-stm32mp1-smufs/tmp-glibc/sstate-control/manifest-x86_64_x86_64-nativesdk-st-image-resize-initrd.packagedata not found in stm32mp1_smufs cortexa7t2hf-neon-vfpv4 cortexa7t2hf-neon cortexa7t2hf-vfp cortexa7hf-neon-vfpv4 cortexa7hf-neon cortexa7hf-vfp armv7vet2hf-neon-vfpv4 armv7vehf-neon-vfpv4 armv7vet2hf-neon armv7vehf-neon armv7vet2hf-vfp armv7vehf-vfp armv7at2hf-vfp armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp allarch x86_64_x86_64-nativesdk (variant ”)?After building the sdcard booting stops at INFO: SP_MIN: Preparing exit to normal world.
Would you like to suggest any ideas or sharing your know know.
Thanks in advance. - March 16, 2021 at 11:46 am #11362
Hi Rishi,
How are you generating the device tree blobs? Your error with dunfell 20-11-12 appears to be on dts parsing.
Did you try following https://octavosystems.com/app_notes/stm32mp1-cubemx-tutorial-for-osd32mp15x? Then copy that stuff into mx folder under meta-st-stm32mp-addons layer in the distribution package?
We have seen some odd things with the minimal config project used in CubeMX to generate device tree blobs.
- March 16, 2021 at 5:42 pm #11365
Hi mlarkin,
Thanks for your response!
May be because of my lack of understanding but i thought working device tree blobs for osd32mp1-brk board are provided by octova systems at https://github.com/octavosystems/OSD32MP1-BRK-device-tree. So i tried using these device trees as it is. I did not regenerated with there cubemx app note.
If this is the case then today i will try to generate device tree from basic cube-mx project and will see how it goes.Octova Team: Now i understand officially Octova systems is currently working on distribution package support for brk board, just wondering is this targeted in near future?
- March 17, 2021 at 9:19 am #11368
Our understanding is that the device trees provided by octavo only work with the Developer’s Package, not the Distribution Package. The only way we could get a working image with the Distribution package was to generate the files using the CubeMX project. The project attached to this post is the one that finally worked for us: https://octavosystems.com/forums/topic/yocto-source-tree-directory-for-osd32mp1-brk/
- March 17, 2021 at 7:47 pm #11371
Hi bduke,
Thanks a lot! I will give it a shot now.- March 18, 2021 at 5:20 pm #11373
Hi there,
Thanks everyone, Just an update, i was able to build my image using ST distribution package “openstlinux-5.4-dunfell-mp1-20-11-12”.Just seeing few messages in kernel log like :
….
– [0.003383] /cpus/cpu@0 missing clock-frequency property
– [0.003420] /cpus/cpu@1 missing clock-frequency property
– [ 1.540689] Unable to get STM32 DDR PMU clock
…
– [1.613845] stm32-ddr-pmu: probed (ID=0x00140061 VER=0x00000010), DDR@533MHz
– [2.940962] VREF_DDR: supplied by vin
…Anyways, thanks for support! But i guess need to test more thoroughly for stability and will see if i can fix these Cpu clock frequency properties.
Thanks, Rishi
- March 23, 2021 at 3:50 pm #11381
Rishi,
Please make sure you have cpu clock frequencies defined in your custom device trees like here:
https://github.com/STMicroelectronics/linux/blob/v5.4-stm32mp/arch/arm/boot/dts/stm32mp151.dtsi#L27 and OPP table here:
https://github.com/STMicroelectronics/linux/blob/v5.4-stm32mp/arch/arm/boot/dts/stm32mp15xa.dtsi#L7
Do you see that the board boots completely with no issues logging in and executing commands?
Best,
Neeraj
- AuthorPosts
- You must be logged in to reply to this topic.