• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 89 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.

F29H85X-SDK: SDL dependencies onto the SDK

Francois Charlot
Mastermind 29922 points

Part Number: F29H85X-SDK

Hello,

Is the F29 SDK actually independent from the F29 SDK? The concern here is that the SDL will be safety qualified when the SDK will not, so if the SDL depends on the SDK, this would break the safety qualification.

For example, I see in the ADC example sdl_adc_os_detect_example.c calls to ADC_setINLTrim(), which is an SDK function. So it looks like customers have to provide their own SDL support functions similar to the SDK functions... Am I missing anything?


Best regards,
François.

  • 0
    TI__Expert 4075 points

    Hi Francois,

    Let me check with F29 SDK team and get back to you.

    Thanks,

    Ira

  • +1 in reply to Ira Thete
    TI__Expert 4075 points

    The SDL library itself doesn't call any SDK functions, so in that sense it's independent.  You are right that users are responsible for some configurations before running the SDL functions though--configuring SYSCLK, GPIOs, ADC trims, Interrupts, etc... In our examples, we use the driverlib functions which aren't FSQ, so customers will either have to qualify those for safety themselves or use an MCAL equivalent (since MCAL will be FSQ).