• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 406 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP-L138: Regression in U-Boot 2024.04 for standalone examples?

Julien Delbergue
Prodigy 50 points
Part Number: OMAP-L138
Other Parts Discussed in Thread: OMAPL138, , AM62P

Hello,

I am trying to switch to the next ti-staging version (2024.04), but the build failes when using standalone applications:

Since commit ac44c6cf957a91cea5271334c2d6e6cd867cb5d6, it is now necessary to explicitely enable API support in order to build the examples.

If I do so, for instance by adding the following to omapl138_lcdk_defconfig:

CONFIG_API=y
CONFIG_EXAMPLES=y

then I get compilation errors from arch/arm/lib/memset.S.

In U-Boot 2023.04 this was not an issue, since only CONFIG_EXAMPLES was needed.

Thanks for your help.

Julien

  • 0
    TI__Guru**** 168721 points

    Hi Julien,

    TI SDK for OMAP-L138 hasn't migrated to 2024.04. And the issue you described doesn't seem be relevant to OMAP-L138 device, but some changes made by the U-Boot community. Please ask the community for support.

  • 0 in reply to Bin Liu
    TI__Expert 6346 points

    Bin is correct. 2024.04 is in the migration stage at this point and have not completed the port yet.

    Julien,

    1. Thanks for pointing out though , Will take a look and continue the conversation in uboot mainline mailing list. 

    2. Moreover the ti-staging u-boot 2024.04 is validated only on platforms listed here : https://software-dl.ti.com/cicd-report/linux/ All other TI soc variants you see as code/configs in the repository need to be reviewed from community support point of view (including omapl138)

  • 0 in reply to Praneeth Bajjuri
    Prodigy 50 points

    Thank you for your feedback.

    1. To be more precise, it seems that only the subfolder examples/api/ is affected.
    I guess this has been broken for some time on DaVinci, but is only showing up now with the mainline change.
    So I am not entirely sure if this is purely a mainline issue.

    2. Thanks for the CI/CD link, I did not know about it.
    What do you mean though by "need to be reviewed from community support point of view" for other platforms?
    Indeed one of my references is https://git.yoctoproject.org/meta-ti/tree/meta-ti-bsp/conf/machine, which seems to be the base for most SDKs anyway.

  • +1 in reply to Julien Delbergue
    TI__Expert 6346 points

    Julien,

    1. OMAPL138 is in mainline / community support system for a while. As you can see from https://www.ti.com/tool/PROCESSOR-SDK-OMAPL138 that its been many years we had made a SDK full validated release. 

    2. Even from CICD point of view , the reasoning is same for OMAPL138.  The reason i mentioned the link is for the newer devices and release of CICD snapshots based on 2024.04 once the baseline is stable (Ex of new devices are AM62/AM64/AM62A/AM62P etc.. ) 

    3. On "https://git.yoctoproject.org/meta-ti/tree/meta-ti-bsp/conf/machine" >> Not all configs present in community yoctoproject goes thru the SDK release. A subset of those configs specifically legacy platforms are handled at community voluntarily .

    Based on my investigation, i will open up a conversation in uboot and yocto mailing list once the scarthgap and 2024.04 baseline is mature for new devices.

    Hope it clarifies. 

  • 0 in reply to Praneeth Bajjuri
    Prodigy 50 points

    It does, thanks for the follow-up.