Microcontroller in LOCKUP state

Log in or register to post comments
Go To Last Post
5 posts / 0 new
Author
Message
shivasworld
shivasworld's picture
Level: Rookie
Joined: Mon. Jun 17, 2019
Posts: 29 View posts
#1
Posted by shivasworld: Thu. Sep 19, 2019 - 05:14 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello All, 

 

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 ?? 

 

Few of the Build Logs while downloading the code to the controller are as follows:- 

 

INFO: Configuring trace using 'SWO,ETB' setting ... 
Trace: Using detected ETMv3CM at address 0xe0041000 
Trace: ETMv3CM is not powered-up (ETMCR=0x411) 
Trace: ETMv3CM powered-up OK (ETMCR=0xc10) 
Trace: Access to detected ETMv3CM(architecture=3.5) initialized (CONF=0x8c842000, CTRL=0xc10, IDR=0x4114f250) 
NFO: SWO trace mode is not supported by the probe (use I-jet/I-jet-Trace probe) - trace is disabled. 
CPU status - LOCKUP 
HardFault exception. 
The processor has escalated a configurable-priority exception to HardFault. 
A bus fault has occurred on an instruction prefetch (CFSR.IBUSERR, BFAR). 
Exception occured at PC = 0xffffffff, LR = 0x0 
 
Please, help me with this issue. How to solve this error ??

 

Thanks.

Tags:

Atmel SMART ARM-based MCUs and MPUs, Atmel Cortex-M MCUs, #Lockup #ATSAME54P20A #HardFault #BusFault #UsageFault, #ATSAME54P20A
Top
shivasworld
shivasworld's picture
Level: Rookie
Joined: Mon. Jun 17, 2019
Posts: 29 View posts
Posted by shivasworld: Thu. Sep 19, 2019 - 10:17 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello All, 

 

Please help me with the above issue. If anyone have any idea about the issue and have already faced it earlier,  then please come up and respond to the post ??

 

Thanks and Regards.

Last Edited: Thu. Sep 19, 2019 - 10:18 AM
Top
Kartman
Kartman's picture
Level: 10k+ Postman
Joined: Thu. Dec 30, 2004
Posts: 24417 View posts
Location: Melbourne,Australia
Posted by Kartman: Thu. Sep 19, 2019 - 11:18 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What have you done to verify your pcb is correct? Poor pcb layout might be the cause of your problems.

Top
shivasworld
shivasworld's picture
Level: Rookie
Joined: Mon. Jun 17, 2019
Posts: 29 View posts
Posted by shivasworld: Thu. Sep 19, 2019 - 11:55 AM (Reply to #3)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No @Kartman, The PCB is designed according to the various specifications mentioned in the Device Datasheet. The controller is working yesterday, the issue started to appear from tomorrow evening. 

 

 We have only used 32KHz oscillator, the various coupling capacitors and  LDO's to regulate the voltage. Also, we have jumper pins to connect the external LCD (16X2)to the custom PCB to display some data to screen. 

 

The code seems to be compiled fine but when we download the code to the controller it is giving me various BusFaults, Hardfault and Usage fault exception, which can be observed in the Log Window inside IAR embedded workbench. I don't know whether it is fault in the hardware or software currently which may lead to various hardfault exceptions. 

 

The code for LCD display is fine as single character is getting displayed on the screen correctly before, but the debugging the code leads to various Hardfaults. 

 

Note:- What do you suggest, I need to change the controller now or is  it possible to get the controller up and running again ??

Please, help me out with the issue. 

Last Edited: Thu. Sep 19, 2019 - 12:09 PM
Top
Kartman
Kartman's picture
Level: 10k+ Postman
Joined: Thu. Dec 30, 2004
Posts: 24417 View posts
Location: Melbourne,Australia
Posted by Kartman: Thu. Sep 19, 2019 - 09:35 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Sounds like you’re in a panic and any logical sense has gone out the window. Apart from begging for help, you’ve not given much information. From where i sit it could be ANYTHING!
My suggestion is to wind back the code until where it worked - you have version control don’t you? Of course you don’t. Now might be a good time to start. Then have a look at your clock setup. Go back to the internal oscillator and see if that improves things.

I usually would start with a known good piece of hardware THEN do my own pcb. It is not simple things you are playing with here, so you want a fallback when things don’t go to plan.

Top