LPC5516 crach when running faster than 100Mhz

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

LPC5516 crach when running faster than 100Mhz

1,407 Views
jeroenbussink
Contributor II

We have 2 batches of PCB's with different date codes on the CPU the one with sSD21480A  (week 48 2021) works without any problems the new batch has a date code sSD21490A  (week 49 2021) in this version the programs craches after the init.

To debug I have created a new default project with only a clock setup and this has the same problem it runs when I set the ferqeuency < 100Mhz and it crashes when its set > 100Mhz.

Any sugestions what can be done to solve this?

Labels (1)
0 Kudos
11 Replies

1,377 Views
frank_m
Senior Contributor III

I suspect you Flash settings are incorrect. If the number of wait cycles is too small, the core will hardfault.

The datasheet guarantees proper function at certain clock frequencies with a defined number of wait cycles, and at a given temperature. Each shipped part is guaranteed to meet this requirement, but many do exceed this guaranted values. How much depends on intrinsic parameters (batch), and on temperature.

0 Kudos

1,382 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello,

I need more information about your MUCs, Could you give me a picture of both MCUs? Where did you buy the last lot?

Best regards,
Pavel

0 Kudos

1,373 Views
jeroenbussink
Contributor II

Hello,

I have attached a picture of a working and a not working CPU, both CPU are bought from AVNET.

jeroenbussink_0-1657691917158.png

 

jeroenbussink_1-1657691962419.png

 

0 Kudos

1,401 Views
jsoccerd
Contributor II

I know with the LPC5536 that the default flash memory speed is determined by the FMC register in SYSCON so if you don't change that it causes a hard fault on that processor. Check for similar registers and see if you can change the flash speed.

0 Kudos

1,390 Views
jeroenbussink
Contributor II

I have checked the FCM register but its set by the libary to the correct value (10)

0 Kudos

1,368 Views
jsoccerd
Contributor II

The value in the FLASHTIM should be 0xB or 11, not 10 if you want 150MHZ.

0 Kudos

1,353 Views
jeroenbussink
Contributor II

The system is running at 144Mhz, and then 10 should be ok according to the data sheet and the SDK functions. 

jeroenbussink_0-1657778717673.png

 

0 Kudos

1,352 Views
jeroenbussink
Contributor II

To test I increased the wait states to 11 and now the boards that are running at 144Mhz are working. Strange thing is that this value is other than calculated by the SDK and shown in the manual.

jeroenbussink_0-1657779975371.png

 

In a second test I put the sampels to a speed 150Mhz so the wait states are calculated at 11 now some of the boards still work and some of them stopped working again.

0 Kudos

1,342 Views
jsoccerd
Contributor II

That's probably because quartz oscillators have some inherent error in them, and the PLL also has some error, so I would suggest to go a little bit below a desired frequency to account for tolerances.

0 Kudos

1,313 Views
jeroenbussink
Contributor II

For now we have choosen a number of wait states one higher then stated in the manual

0 Kudos

1,305 Views
frank_m
Senior Contributor III

If you think that products do no satisfy guaranteed requirements as described in the datasheet, you might contact the supplier (NXP) directly or via official distributor, not via a public forum.

I know of no vendor that discusses quality issues, unreleased products, or future portfolios on public fora.

0 Kudos