512-861-3400Log inCreate Account

Compiling osd32mp1-brk openstlinux for stm ecosystem 4.1

Forums › Devices › OSD32MP15x › Compiling osd32mp1-brk openstlinux for stm ecosystem 4.1

Tagged: ,

Viewing 4 reply threads
  • Author
    Posts
    • January 5, 2023 at 8:44 am #13035
      bm ihebbm iheb
      Participant

        I have been trying to compile openstlinux for osd32mp1-brk from source using the layer provided in the folwwoing Github page ( meta-octavo-osd32mp1) i have been following the instructions form the comments on the kirkstone branch how ever i used the the meta layer for openstlinux ecosystem  v4.1 instead of 4.0.
        In order have a successful compilation of the project using yocto bitbake, i had to mod some files device treefiles stm32mp151.dtsi on booth the kernel source and uboot to support the exti_pwr configurations used by the original patches of osd32mp1-brk.
        The compilation worked and i was able to flash the image on the sd card and boot the board however when booting:

        – The heartbeat red LED blinks

        – USB Remote NDIS doesn’t work like the image provided in the product page –

        – I obtain the following error when probing using uart  :

        compiling and using 4.0 didn’t also work (even though i didn’t make any modifications) there were errors when booting.

        I need to use the ecosystem v4.1 version since that it offers updates on the ADC drivers.
        my question is what is that i’m doing wrong ? 

        • This topic was modified 1 year, 10 months ago by bm ihebbm iheb.
      • January 5, 2023 at 10:05 am #13045
        Michal Wolowikmwlinux
        Participant

          Hi,

          You need to change in boot partition a following record

          APPEND root=PARTUUID=491f6117-415d-4f53-88c9-6e0de54deac6 rootwait rw   console=${console},${baudrate}

          to

          APPEND root=root=/dev/mmcblk0p8 rootwait rw   console=${console},${baudrate}

          I do not remember which number is the rootfs partition, it can be 7 or 8 or 9 You need to test or check.

          Of course on the boot partition, You find two folders mmc0_extlinux and mmc1_extlinux everything depends on Your configuration.

          BR Michal

           

        • January 6, 2023 at 7:35 am #13051
          bm ihebbm iheb
          Participant

            i have tried all of the above how ever non of them worked, when i try to lsblk the SD card ,it shows partions with (ada0) not mmcblk0px i have also made the partions using the ./create_sdcard_from_flashlayout.sh script and then flash it normaly how ever it still desn’t work properly.
            the file output of this script is

            So the parth should be ” dev/mmcblk0p10″ in this case it Doesn’t work.

            • This reply was modified 1 year, 10 months ago by bm ihebbm iheb.
          • January 7, 2023 at 1:44 pm #13112
            Michal Wolowikmwlinux
            Participant

              In the U-Boot, everything looks good but during the system bring up I can’t see mmc initialization. Check sdmmc section in dts for the kernel. The next thing is NFS, I saw some records in the log, maybe You used NFS rootfs loading previously and forgot to change to mmc.

              BR Michal

            • January 10, 2023 at 6:03 pm #13241
              Neeraj Dantu
              Moderator

                bm,

                The kernel boot options can be set in an extlinux file in /boot folder of the SD card. Please see https://github.com/octavosystems/osd32mp1-build-tools/blob/master/stm32mp157c-osd32mp1-red-extlinux.sh#L26 for example. From the boot log, it looks like the kernel is looking for a partition that has a UUID of e91c4e10-16e6-4c0e-bd0e-77becf4a3582. This does not exist on your SD card. The kernel is getting this from /boot/extlinux/extlinux.conf. This is where you can change the root= from the UUID to the root partition ID of your SD card or the UUID of your root partition. You can find the UUID of the partitions of the SD card you are using by inserting it into a Linux computer and running “blkid”. The output of the command is the UUIDs of all devices and filesystem UUIDs.

                Best,

                Neeraj

            • Author
              Posts
            Viewing 4 reply threads
            • You must be logged in to reply to this topic.

            Octavo Systems LLC all rights reserved
            OCTAVO is registered in the U.S. Patent and Trademark Office. OSD, C-SiP, and the Octavo Logo are trademarks of Octavo Systems LLC.