TMS570LC4357: Forcing an ESM 1.92 error to test signaling a change of (CCM-R5F) operating state

Stephan HERMANNS

Part Number: TMS570LC4357

Dear Team supporting the Hercules MCUs,

As i read sections 5.3.6, 5.3.7 and 5.4.13 as well as 13.3.2, 13.3.4, 13.3.6 and 13.3.9 of the TRM spnu536a
there is no way to force an ESM 1.92 error without executing one of the (CCM-R5F)'s selftests.

(Q1) Is there a way to stimulate an ESM 1.29 error without starting a sefltest of the (CCM-R5F)?

Thank you - enjoy the day!

Stephan

over 5 years ago

0 QJ Wang over 5 years ago

TI__Guru**** 197036 points

Hi Stephan,

Datasheet says that ESM 1.92 can only be generated by CCM-R5F in self-test mode.

0 Stephan HERMANNS over 5 years ago in reply to QJ Wang

Intellectual 590 points

Good morning, QJ,

Thanks for your quick response.

I guess, you are talking about section 6.5.4.1.1 and table 6-46 of the DS.

(Q1) Your answer gave me an idea.
Is it possible to leave a lockstep mode (PMM1, CPU1, VIM14, inactivity monitor) intentionally without starting a self test?

Thanks again!

Stephan

0 QJ Wang over 5 years ago in reply to Stephan HERMANNS

TI__Guru**** 197036 points

Hi Stephan,

1. The CPU1 and CPU2 are in lockstep. They can not be used as two independent processors.

2. The default mode on start-up is active compare lockstep mode. Self-test mode can only be started by writing 0x6 to CCMKEYR1/2.

0 Stephan HERMANNS over 5 years ago in reply to QJ Wang

Intellectual 590 points

Hi, QJ,

Then we have to force self test modes to test the signaling when the CCM-R5F leaves one of its four lock step modes.

Thanks!

Stephan

Arm-based microcontrollers

Arm-based microcontrollers forum

TMS570LC4357: Forcing an ESM 1.92 error to test signaling a change of (CCM-R5F) operating state