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

TMS570LC4357: TMS570LC4357 CCM Test

AxelanderS
Prodigy 60 points
Part Number: TMS570LC4357

Hey,

I am currently conducting a few tests aimed at the lockstep monitoring feature of the Cortex-R5F and its Core Compare Module. I have already set up and used all of the self tests and also the CPU Input Inversion Diagnostic is working perfectly fine. I would just like to know if there are any other ways than the Input Inversion to force a Lockstep Error so that I can verify the functionality of this feature even more? I have played around with different CPU Voltages and Temperatures but nothing has ever triggered an Error and out of curiosity I would like to force one. Is there anything else I could do?

Cheers, Alex

  • 0
    TI__Guru**** 196776 points

    Hi Alex,

    To intentionally trigger a CCM-R5F error, you can use either "Error forcing" or "input inversion" mentioned in technical reference manual. I don't know other method.

    The MCU general registers (R, R1, ...R14, etc) don't have fixed values upon reset. To avoid an erroneous CCM compare error, the application software needs to initialize those registers to zero before the registers are used:     _coreInitRegisters_(); in HL_sys_startup.c

    If those registers are not initialized, you might get CCM compare error.