AnsweredAssumed Answered

Program fleet if add sEI and CLI in case of protecting read&write process

Question asked by Kim Chan on Aug 15, 2018
Latest reply on Sep 4, 2018 by Radek Sestak



I have many interfaces, for example 

ebStatus = APP_InterruptDisable ();

*****read or write process****


to protect process when reading or writing.

Now I add "__asm SEI;" in APP_InterruptDisable () and "__asm CLI" in APP_InterruptEnable(ebStatus).

Then I power on the board and it can send and receive frames.

But, if I send a NM frame to ECU, it will cause program fleeting.

It's sure that __asm SEI and __asm CLI will have effect on this because it's all normal it I don't add them.

But I can't figure out why it will have effect on it.

So I want to know, why it has problem when add them in case of sending NM frame to ECU.

I have fleeting problem before in other case and I solved by enlarging stack size.

But it doesn't work here.


ECU: S12G128