• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 84 subscribers
  • Views 421 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.

TMS320F28335: MCU abnormity process

Frank Lee96
Intellectual 830 points
Part Number: TMS320F28335


Hi TI,

We add abnormity check procedure in our software such as checking broken RAM,broken ROM and so on.So we should add some extra procedure to do abnormity process when there is abnormity to make the MCU be on controllable state reducing dangerous output.Can you give me some advisable suggestion to solve this problem that what the MCU should execute ?

Best regards,

Frank

  • 0
    TI__Mastermind 32995 points
    Hi Frank,

    There is a IEC 60730 Diagnostic Library available for the F2833x device. There is a March13n algorithm in the software package which tests for RAM failures.

    www.ti.com/.../iec60730swpackages

    Regards,
    sal
  • 0 in reply to Sal Pezzino
    TI__Mastermind 32995 points
    If a failure is identified and it is a dangerous fault, it is up to you to handle the failure and either repair it if possible or go to a safe state.

    sal
  • 0 in reply to Sal Pezzino
    Intellectual 830 points
    Hi Sal,
    Thanks.It is said there is a way that MCU calls the function 'assert()' when there is a error ,I don't know which state the MCU be on after call the function,is that in debug mode or other?By the way,if there is a watchdog used in the application,what we should do when errors occur?MCU should fed the watchdog not to call assert() rather than?
    Best regards,
    Frank
  • 0 in reply to Frank Lee96
    TI__Mastermind 32995 points
    The asserts should only be compiled in a debug build configuration. You are free to use it and supply the function which is called if the assert fails.

    The assert is likely only for software systematic errors. For example passing the wrong parameter to a function. I do not believe the assert function is called on a hardware error. You can confirm.

    If you detect a fault, it is up to you to feed the watchdog while you take the system to a safe state, or you can not feed the watchdog and cause a watchdog reset as long as you can ensure that the reset will not create a dangerous state in the system.

    Regards,
    sal