Post Go back to editing

Firmware update failure on the ADUCM3029 MCU using Analog Devices - SensorPal interface

Category: Software
Product Number: ADuCM3029
Software Version: Analog Devices - SensorPal version 2.5.3.1
Hello to everyone,
 
I wanted to test the EVAL-ADICUP3029 evaluation board for research purposes using the Analog Devices - Sensor Pal interface, but I am encountering problems updating the firmware on the MCU due to the following failure: ‘The interface firmware FAILED to reset/halt the target MCU’. I have tried different options detailed in the EVAL-ADICUP3029 User Guide, but the problem persists. Here is a brief description of the considerations I have taken into account:
  • Firstly, I have checked that switches S2 and S5 are in the correct positions, i.e., S2 in the USB position and S5 in Wall/USB, as I am powering the board by connecting the cable micro-USB to USB to the laptop.

Secondly, I have tried to program the ADuCM3029 MCU by following the steps below:

1. I dragged and dropped the file 'adi_mbed_interface.hex' into the mass storage device, named 'DAPLINK'. Then two text files were generated ('ASSERT.txt' and 'FAIL.TXT'). In the 'FAIL.TXT' it appears the following text message: 'An internal error has occurred'.

2. I also tried to erase the flash by using the software CrossCore Serial Flash Programmer, but this option didn't work, as it can observe in the screenshot that I show below:



To do the previous step I powered cycle the ADICUP3029 board while holding down the boot switch (S3). The USB was selected on switch S2. I tried different baud rates, but the same problem persisted.

  • Finally, I tried to put the device in 'Maintenance mode' and dragged and copied the file 'ADICUP3029_maintenance_drive_revC_1_0.hex' into the flash. After that, the mass storage device changes its name to "DAPLINK". I procceded to unplug and plug the board to the computer, and repeated the step 2 described above, but the same failure occurs, i.e., "The interface firmware FAILED to reset/halt the target MCU".
Please, could anyone tell me how I can proceed to solve this problem? The board was working properly a week ago. I have tried to use this board in other compueters, but the problem persist.
 
Thank you very much for your attention.
 
Best regards.