STM32MP1 Distribution Package Support

Forums Reference, Evaluation, and Development Boards OSD32MP1-BRK STM32MP1 Distribution Package Support

Tagged: 

Viewing 6 reply threads
  • Author
    Posts
    • #11329
      Barrett Dukebduke
      Participant

        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?

      • #11330
        Barrett Dukebduke
        Participant

          I was recently able to create a bootable image using the STMicro distribution package. I no longer need this information.

        • #11332
          Neeraj Dantu
          Moderator

            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

          • #11359
            Rishi Bhanotrishi@smufsbio.com
            Participant

              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 tree

              Using 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.

            • #11362
              Matthew Larkinmlarkin
              Participant

                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.

                • #11365
                  Rishi Bhanotrishi@smufsbio.com
                  Participant

                    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?

                • #11368
                  Barrett Dukebduke
                  Participant

                    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/

                  • #11371
                    Rishi Bhanotrishi@smufsbio.com
                    Participant

                      Hi bduke,
                      Thanks a lot! I will give it a shot now.

                  Viewing 6 reply threads
                  • You must be logged in to reply to this topic.