• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 617 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.

CCS/RM41L232: SafeTI:how to do startup code when using SafeTI library

lina zhang
Intellectual 440 points
Part Number: RM41L232
Other Parts Discussed in Thread: HALCOGEN, RM42L432

Tool/software: Code Composer Studio

Hello,

I am starting to integrate SafeTI library 2.3.1 to my system.

By HALCoGen generated startup code that existed in Sys_startup.c,for example _c_int00 function.

Could the startup code  be directly applied in my system?

If there are some boot-time diagnostics, these diagnostics will be manually added into the above _c_int00 function.Is that right?

  • 0
    TI__Guru 59540 points
    Hello Lily,

    In the installed SafeTI Diagnostic directory, there are examples of implementing the library for various devices. In the case of the RM41 device, please reference the RM42 examples. There are two included without an RTOS. One is for use with IAR IDE and the other for CCS.

    The CCS version is located at this path if you have installed to the default directory:
    C:\ti\Hercules\SafeTI Diagnostic Library\2.3.1\demo_app\HALCoGen\RM42L432_NoOS

    The only difference between the RM41 and the RM42 device is the size of Flash so you will need to adjust the linker command file for this difference.

    Also, within Halcogen, there is an option to select a Safe Startup. This options also shows a base level of safety diagnostic functions that are implemented.

    using these two sources, you should be able to get an idea of how to implement the boot time diagnostics. Periodic diagnostics will be based on your application needs and how you setup your task/control loop. Some periodic diagnostics will/can be called less frequently than others and some may need to be called at a higher frequency. Again, it is dependent on your system definition and your FTTI requirements.