We have custom PCB having ATSAME54P20A microcontroller. Suddenly today I started getting CPU Status - LOCKUP error and I am unable to download the code to the microcontroller. Before, that I am able to download the code to controller but it is giving me various BusFault and HardFault handler errors.
I am using IAR Embedded workbench environment and ATMEL ICE debugger to download the code to controller.
How can I download the code to controller again ?? How to remove the LOCKUP state of Cortex M4 device ATMSAME54P20A ?? What steps I need to take to resolve this issue ??
ShivasWorld said:I am using IAR Embedded workbench environment and ATMEL ICE debugger
So why have you posted in the ARM Development Studio forum ?
You'd be better on Microchip's dedicated SAM forum:
Hi Andy Neil , Because the problem is related to Atmel ATSAME54P20A device, which uses ARM Cortex M4 architecture and the given problem is related to the LOCKUP state of controller which is mentioned in the link below:-
So, that's why I posted it over here.
The article in the link given above doesn't provide in detail how to solve this error. If you know how to solve this behaviour of controller please help me out.
But you have posted in a forum specifically for the ARM Development Studio - and you are not using the ARM Development Studio
OK I will move it from here. Anyways, do you have any idea about the above issue then please help.
I have moved it to Community help forum. Can you help me with above issue if you have any idea ??
Admin here: I have moved this to the Cortex-M forum, as it relates to Cortex-M4. Community Help is for helping using the website.
Did you try another chip? Sounds you bricked it. Anyway, better try in the SAM forum as the likelyhood is larger someone there had the same problem. It does not sound like a general Cortex-M but more as a SoC problem.
No, I haven't tried another chip yet. But, I am wondering there must be some way to get the controller up and running as other features are working correctly like reading Device ID , voltage settings, and the fuse bits are also according to the device datasheet.
I think there might be some way to get out of the LOCKUP state of controller.
What do you suggest in this case ??
A Reset should get you out of the LOCKUP state.
ShivasWorld said:What do you suggest in this case ?
Again, the SAM forum is the place to go for specific advice about capabilities of the particular chip, and the particular debug probe.
Including whether a LOCKUP can actually prevent programming the that chip with that probe.
Or if there's an option to use a built-in ROM bootloader to bypass problematic user code.
I have tried Reset but it doesn't get me out of the LOCKUP state. I just need to find other solution to this problem.
Are you sure that it doesn't get you out - or is it that it just goes straight back into the state again?
If you have code which is doing something to cause the LOCKUP state, then it will keep doing that until you change the code.
View all questions in Cortex-M / M-Profile forum