topic Re: MPC5777C Problem with NCF 42, using debugger in MPC5xxx

MPC5777C Problem with NCF 42, using debugger

mauriziogreco — Tue, 18 Sep 2018 13:13:32 GMT

Hi,

has someone an idea about FCCU reaction using TRACE32 ,when the NCF_42 is active?

In the MPC5777C there is the NCF 42: "Lockstep mode Indication of disabled Checker Core or RCCUs. Fault is cleared by clearing the FCCU channel status,FCCU_NCF_Sn[NCFSm]"

I'm working with FCCU active to react to NCF_42.

My SIU_LOCKSTEP.LSE is 1.

When i work on my ECU without TRACE32 (Lauterbach) I don't see any reset action by FCCU.

When i work with TRACE32 (Lauterbach), all is working well until I don't ask "break" on Trace32.

In this case I see the reset action driven by EOUT port of FCCU.

But if I build a new S19 using same code (but in this case keeping disabled NCF 42), all works fine with Lauterbach and also "asking" break on TRACE32.

Where I missing ?

Thanks in advance to all

Re: MPC5777C Problem with NCF 42, using debugger

mauriziogreco — Wed, 19 Sep 2018 07:12:59 GMT

Hi, I'm thinking that using debugger the RCCU will be stopped and FCCU start its reaction?

Someone agree with me?

Re: MPC5777C Problem with NCF 42, using debugger

petervlna — Fri, 21 Sep 2018 06:23:18 GMT

Hi,

In debug mode the RCCUs are disabled, therefore you will see this fault.

Make decision block in your SW for disabling NCF42 when debug mode is active, if you want to use lockstep in debug mode.

Peter

Re: MPC5777C Problem with NCF 42, using debugger

mauriziogreco — Fri, 21 Sep 2018 10:12:17 GMT

Hi Peter, I was only supposing about that.

But now with your confirmation , I feel more certain of solution to be adopted.

Many thanks.

Maurizio