This document describes how to use On-line BISTs on MPC5777C.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STCU2 On-line BIST (MBIST+ LBIST) execution time on NXP Evaluation board ( X-MPC5777C-561DS) is 25.8ms.
This measured time is valid for:
System clock PLL = 200MHz
STCU module clock = System clock / 4
MBIST = 50MHz
LBIST = 25MHz
Result after testing MBIST+LBIST = 0 faults latched in ERR_STAT register and all LBISTs was successfully executed.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STCU2 On-line LBIST only execution time on NXP Evaluation board ( X-MPC5777C-561DS) is 37.4ms.
This measured time is valid for:
System clock PLL = 200MHz
STCU module clock = System clock / 4
LBIST = 25MHz
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LBIST on 50MHz
I do not recommend to run LBIST at 50MHz as it was failing in my setup.
I've tried to test code that you have attached, including that in my code. I'm not able to verify registers (as you have showed in this document) because as soon as the code enter in function STCU2_Online_BIST there is a reset. I'm using a JTAG connection with Lauterbach. Have you any suggestion?
Hi,
Please do not spam my example codes with comments.
Create new thread with reference to my example codes, but if you do not found any issue in my code do not post it here.
I have verified these example codes on 3 samples and all were running fine.
Besides I see you do not fully understand tests mechanism.
If test is started it takes cca 10-20ms to finish of execution. Then reset is generated after last LBIST. After reset you can attach debugger and read registers.
Peter
PS: I will delete those posts in a day.