BIST example in document AN11993

[JC2]

I can't find the BIST example provided by AN11993 on the official website, where can I find it？

“The application note also provides examples for offline and online self-test configurations can be directly implemented by the
user. The examples are provided in the software package accompanying this document and is also explained in detail.”

[petervlna]

Hello,

You can find the example here:

https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/Example-MPC5744P-BIST-On-line-GHS614/ta-p/111439...

Not sure why it is not anymore on the web. Probably some migration issues.

Best regards,

Peter

[JC2]

Hi, Peter. Is this a green hills project? How do I open and debug it? I have not used similar projects before. Do you have S32 version demo? Thank you very much!

[petervlna]

Hello,

Yes, the project is in GreenHills MULTI.

I do not have S32DS version. You can simply port it. it should be not much effort as S32DS already supports this device.

The GHS project is precompiled, so you simply load elf into device and execute.

Best regards,

Peter

[JC2]

Hi, Peter. This is an online BIST project. When I run it, I find that the values of the Shutdown BIST Registers: STCU_LBSSW, STCU_LBESW, STCU_MBSLSW, STCU_MBELSW, did not change, they are all 0. However, after the program runs, the Startup BIST Registers: STCU_LBS, STCU_LBE, STCU_MBSL, STCU_MBEL changed. The code is configured as online BIST. Why does this happen?

[petervlna]

Hello,

Ok, such behaviour has only 2 explanations:

1. You did not start Online BIST at all.

2. Your results of online BIST are cleared by SW before you read them.

I suspect the second case. Set endless loop at first instruction in statup, and skip it. Execute the BIST and then attach with debugger. Or by very quick when attaching after reset.

If you do "up" with debugger instead of attach, you will perform external reset and loose the results.

Best regards,

Peter

[JC2]

I don't really understand. Can you explain it in more detail? Does "first instruction in startup" mean after the BIST is configured and before the "STCU.RUNSW.R = 0x00000301" is executed? Can the steps you mentioned be implemented using the debug function of the S32DS? Thank you very much.

[petervlna]

Hello,

Simply either make SW not to execute after BIST triggers reset.

By some dummy while(1); loop in your main lets say, or in startup.

Or by some SW branching based on Online BIST results (usually used in real applications).

Can the steps you mentioned be implemented using the debug function of the S32DS?

No, As debugger wont stop on breakpoint after reset. You need to manually attach it and the code would already be in progress.

Best regards,

Peter