HardFault Handler for LPC54608

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

HardFault Handler for LPC54608

964 Views
Zhaozhiling
Contributor I

Hello! Our machine master uses LPC54608, the screen is stuck after starting up, JLink locates the PC pointer and finds that the software has entered the hardware abnormal interrupt function, which is in a dead loop state. After testing, it is found that in void BOARD_BootClockPLL180M(void), when the MCU frequency is 180MHz and there is no re-burning program, if the value of FlashTIM is set to 0x8, the system will crash immediately, and if it is switched to 0x7, the system will crash after 24 hours. Then it was found that turning off flash acceleration also had an impact on the crash time, in addition, re-burning the program will also make the system return to normal, what is the reason for this? What can be done to avoid this problem?微信图片_20240822190(08-27-10-19-44).png微信图片_20240822190(08-27-10-19-44).jpg580ce42fb475acc5(08-27-10-19-44).png微信图片_20240827185159.png

Labels (1)
0 Kudos
Reply
3 Replies

937 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, my name is Pavel, and I will be supporting your case, could you let me know how you replay the same behavior to do a report? could you replay on an example SDK?

Best regards,
Pavel

0 Kudos
Reply

910 Views
Zhaozhiling
Contributor I

After repeated press several times, the machine will be stuck randomly, but it can be restored by re-burning the program or replacing the chip. By connecting J-LINK to the crashed machine and changing the FLASHTIM and Flash acceleration enable register values in the Flash configuration register, the frozen state can be removed. But a day later, this happened again. Is it related to the Flash configuration register? Our sample SDK is not available in its entirety, which part of the source code do you want to see?微信图片_20240830170348.jpg

0 Kudos
Reply

864 Views
Pavel_Hernandez
NXP TechSupport
NXP TechSupport

Hello, my apologize for the delayed response, if you want, I could open an internal case, because if you upload here, this is a community channel.

Could you replay this issue on an EVK? could you isolate the part that is having this behavior? to don't share us the whole project, could help us to get more details about this behavior. 

Best regards,
Pavel

0 Kudos
Reply