Clock configuration is not working - CLOCK_SYS_ConfigureMcMe

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Clock configuration is not working - CLOCK_SYS_ConfigureMcMe

863 Views
karma_JC
Contributor I

Hi...

I was tempering around MPC5748G LCEVB board to erase flashing area(0x00F8C000) for booting.  I downloaded PE tool PKGPPCNEXUS  trial version to do some using PE Multilink Universal JTAG.  Due to reset issue, PKGPPCNEXUS can not work with LCEVB.   After this, my LCEVB is not working correctly.  It seems to reset during clock configuration. I traced the to LPU_SetClockSourcesInLpuStandbyMode in CLOCK_SYS_ConfigureMcMe.  The operation seems to have exception, and resetting itself.  From now on, any my test application calling for clock setting has this issue. Do you know how to recover this back????

Thanks

James

0 Kudos
Reply
2 Replies

807 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi James,

first, my recommendation is to skip block at 0xF8_C000. This block is used by HSM when enabled. There's a security feature - if there's an ECC error at beginning of this block, the device will stuck in reset forever. And it's not recoverable.

https://www.nxp.com/docs/en/engineering-bulletin/EB00875.pdf

When you create a project in S32DS, this block is not used and it's usually also not touched by debuggers.

You can use other blocks for boot header:

lukaszadrapa_0-1653052434284.png

This is not the root cause of your problem, you would not be able to establish the connection ever. I'm just mentioning this, so you do not accidentally brick your board - typically when erase operation on that block is terminated by unexpected reset.

It's not very clear what happened on your board. If you didn't play with DCF records, there's nothing to "recover". Just erase the flash and start over. If it doesn't help, there's either some issue in your software or the board was damaged somehow. If you load some SDK example, is it working?

Regards,

Lukas

 

0 Kudos
Reply

847 Views
karma_JC
Contributor I

Hi:

After some effort for recover, the debug console showed SIGTRAP -> 0x00404100.  Is there something wrong with this?

Thanks

James

0 Kudos
Reply