• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 1362 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.

RTOS/PROCESSOR-SDK-AM57X: PDK component header files

Matthew McKee
Intellectual 926 points

Part Number: PROCESSOR-SDK-AM57X

Tool/software: TI-RTOS

Hello,

I am looking at the possibility of packaging a customized PDK together for customers of our AM572x-based boards. I noticed that many of the PDK components include files, such as Settings.h, that are not tracked on TI's Gitorious repos for said PDK components. How do I generate these files manually? I would like to be able to clone a component's repo, modify the source to fully support our boards, and generate all files necessary to be a drop-in replacement in a Processor SDK RTOS install.

Thanks,

Matt McKee

  • 0
    TI__Guru**** 393215 points
    The RTOS team have been notified. They will respond here.
  • 0 in reply to Biser Gatchev-XID
    Intellectual 926 points
    Additionally, is there any way to automatically generate the eclipse metadata found in many of the Processor SDK RTOS components? Thanks.
  • 0 in reply to Matthew McKee
    TI__Guru** 116780 points

    Matthew,

    I have confirmed that the Settings.h file is not in the TI external GIT and I am checking with the team internally why this is not checked into external GIT. I have also reached out to the software team to provide details on generating exlipse metadata but you may also want to check on the code composer studio forums as that metadata is added to the components so that CCS is able to discover the products from the SDK.

    Regards,
    Rahul

  • 0 in reply to Rahul Prabhu
    Intellectual 926 points

    I know that part of why Settings.h isn't included is that it's generated with "xdc release" builds which must be performed before a Processor SDK release. But, I feel that some parts of the release build system aren't included or updated. For example, performing "xdc release" in an osal directory checked out from TI's Gitorious at the commit that matches what is included in the latest Processor SDK RTOS release errors out due to a bug in osal/build/buildlib.xs. Since TI makes sure everything builds before they package Processor SDK RTOS releases, I must be missing some additional configuration files or environment variables that are not obvious from the documentation and/or source.

  • 0 in reply to Matthew McKee
    TI__Guru** 116780 points
    This is being looked at by the development team. At the moment, the recommendation is to download from GIT and run XDC release as that is the only file that doesn`t seem to be checked in into the GIT.