Post Go back to editing

ADuCM360 HardFault

Category: Software

We are Producing a device based on ADuCM360 Microcontroller. We have bought 200 PCs of ADuCM360 from China distributors and mount all of them on PCBs. After programming them I discovered that none of the boards work. after debugging I found out that ADuCM360 stuck in Hardfault exception after reset.

We have been using ADuCM360 for a long time and we haven't had any issue with them until now. Last year we purchased 100 PCs of ADuCM360 and all of them are working correctly.


I will describe the problem in detail so you can give me a hint to solve this problem.


I use j-link debugger

Keil uVision

and ADuCM360 Evaluation board


I programmed the evaluation Board with simple blinker example code.

I start debugging mode and the program execution is stopped at hardfault Handler as shown in picture below.





when I searched for caller code of hartfault the device is stopped at address @0x0001FFFC as shown below



I discovered that on the healthy ADuCM360 this block of flash is not readable by debugger (Address from @ 0x00020000 to @0x00020800). But in the faulty ADuCM360 these addresses have access to write and read.


I hope that you can help me find out the reason and solution for this problem.




Parents Reply Children
  • Hi Raquel,

    the marking on the newly bought chips is:



    D30    #1406



    the marking on the chips we were using so far is:



    D30    #1503



    So, it is clear that the only differences between them are the year of production and the country they were made in.

    There has been no design or software change in production. The configuration for debugger is perfectly ok and J-link debugger recognizes the chip and even downloads the program on the chip but after running the program it gives hard fault.

    when i replace the faulty chip (Malaysia) with the one we had from past (China) everything works normally and there is no hard fault anymore. So, I assume that there is something wrong in ADuCM360 chip from Malaysia.

  • Hi,

    It seems that the parts are not working as we would expect, considering as well that you can access addresses from 0x00020000 to 0x00020800 which are reserved for the Kernel.

    Who was the distributor you bought this parts from?

    I recommend you contact the distributor so you can bring the parts back to Analog Devices for Failure Analysis.



  • Hi,

    Thank you for your response.

    we bought these chips from a distributor in China. we will contact them to bring chips back to Analog Devices.