The MCU on our board starts at SAFE-Mode, on the Eva-board the Code switches the current mode from DRUN to RUN1 without problems. The Code previously worked on our board. Which functions can we test? Can the voltage supply be the problem? Programming over the JTAG-interface is possible and the it looks like the Debugging is working. The FCCU seems to switch the MCU in SAVE-Mode. Should the xosc switch by the code be possible in SAVE-Mode? Witch procedure is recommended for an error-analysis. Where can I find detailed informations.
Hi Nils.,
[Peter] – Yes, it can be problem. If you are using for example BIST self-test after power on than Leopard can cause the safe mode. So first of all make sure you are in Leopard datasheet spec and also make sure your power supply is strong enough to deliver the requested current in proper time.
To exclude the weak power supply issue you can apply external power supply to your board.
[Peter] – The first thing to do is to check the RGM registers DES and FES in order to identify the root cause of SAFE mode.
Are you in safe mode directly after reset? Place breakpoint or while(1) loop at the start of your code to make sure no other code is executed after reset and check the Mode entry for Mode.
Share with me the concept of RGM[FES], RGM[DES], and FCCU[CFSx], FCCU[NCFSx] registers.
Do not forget that you need to read FCCU via OPx bit set.
All the informations required for SAFE mode analyses are in MPC5643L reference manual. However this require wide experiences with this micro to fully understand how to find the issue.