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.

TMS320f28031 Self tests / Fail safety

Other Parts Discussed in Thread: TMS320F28031

Hi everyone,

I am using a tms320f28031 micro controller for my project. Its an high voltage, high current project and my reviewers are going to see how fail safe the system is.

The project uses pretty much all the peripherals the micro controller has. My question is- what are the self tests the peripherals can have. - like for ADC , CAN and other critical peripherals. The micro controller should be able to self test the peripherals and respond appropriately to make sure the system is safe upon failure of any components/ peripherals.

In addition to this, I also want to know about how to tackle micro electronic faults, registers / PC getting stuck and memory faults etc. In other words, how do I give deliberately memory faults and make the system immune to such faults.

I understand the questions are kind of vague but if you guys can give some direction, it ll be very helpful. Basically I need to just know I can  ensure the fail-safety of the system. Thanks in advance

-Binesh

  • Binesh

    Your need for fail safe systems relates to functional safety in any one the application spaces,  appliances, industrial or automotive.

    TMS320F03x Piccolo C2000 MCUs are widely used in many appliance safety application. This device comes with  a list of software test library (STL) developed for IEC60730/UL1998 safety standards. SafeTI web site gives a good summary of these standards. SafeTI 60730 URL below, has an active link to download the STL libraries for this family of MCUs. It has SW/HW documentation that explains the use and applicability. You can use these libraries and expand according to your application/fail safe needs.

    http://www.ti.com/ww/en/functional_safety/safeti/SafeTI-60730.html

    thanks

    Sam

  • Hi Sam,

    Thank you very much for your prompt reply. I ve gone through the STL libraries. I was challenged in implementing the libraries. Is there any help regarding that anywhere?

    Also, I would like to know specific to memory faults - How do I give memory faults intentionally and see how the system responds and to check any means of hacking into my system like buffer overflow etc.

    Im just trying to see all safety aspects of the system in terms of hacking , failure etc . Thanks

    -Binesh
  • Binesh
    The examples comes with a Simple App example including all the required STL libraries. Memory errors are generally destructive tests and soft errors cannot be easily induced at the memory structure level.

    Force/store a word/segment of memory with bit errors either in RAM or Flash prior to calling this range of memory that has this false error locations. This will force the SW to exit the error conditions.

    Hope this helps
    thanks
    Sam