This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM62A7: meta-edgeai defines a custom wks file which changes the boot and rootfs partition names

Part Number: AM62A7

I'm not sure if there is a mailing list for meta-edgeai so posting here.

Is there any reason for meta-edgeai to have its own wks file?  I'm mostly upset that it changes the standard "boot" partition to "BOOT" and "root" partition to "rootfs" which breaks all my scripts and all our standard instructions now have to be different when booting the edgeai image vs the base/default images.

This also mounts the boot partition over the kernel /boot directory. This was fixed recently in the meta-ti wks images.

git.ti.com/.../

  • This also mounts the boot partition over the kernel /boot directory. This was fixed recently in the meta-ti wks images.

    Correction I was wrong, it is just fixed in a way I wasn't expecting. It disables fstab updates in the recipe, see the above linked commit for a cleaner solution.

    WKS_FILE = "tisdk-edgeai-sdimage.wks"
    WIC_CREATE_EXTRA_ARGS += " --no-fstab-update"

  • Hi Jon,

    when digging a bit into this I noticed this ties back to your thread here: https://lists.yoctoproject.org/g/meta-arago/message/15301  And there was an internal discussion around this but it stalled. Let me see if we can move this head some.

    To give a bit more background from what I know, those AM62A and Edge-AI specific changes/customizations are made by a different team, so things are not always 100% consistent (this applies to other things too such as Yocto SDK documentation for AM62A, which is lacking/missing some key details on AM62A vs. AM62, for which I filed internal enhancement requests already to have those corrected). As for the wks-specific changes will try to find out what's the rationale behind.

    Regards, Andreas

  • Thanks Andreas, for now I'll look into bbappend-ing the tisdk-edgeai-image.

    And yes that link is correct. When I was googling I came across the git commit but I hoping to link the mailing list instead.

  • Hi Jon, I'm still waiting for some feedback from the dev team on this. I just pinged them and will update here with any news. Thanks.

  • Hi Jon,

    So apparently the reason is for software products made by the team responsible for AM62A the partitions were called BOOT and rootfs traditionally, and there's some dependencies with the associated MCU+ SDKs and some scripting those include. So the decision was made to keep this aligned when the WIC image generation process was introduced, hence the additions to meta-edgeai.

    Of course when you take a step back it and look at the greater TI offering would be nice for things to better aligned across products in this perspective, and there's definitely some discussions happening on how to perhaps get to that. But at this point I have no timeline/conclusion that I can communicate.

    So for now your best bet is you just customize / clean up things yourself in a way that works for you.

    Regards, Andreas

  • Okay, that makes sense.  Thanks for looking into this.