AnsweredAssumed Answered

AduCM4050 CMSIS-DAP debugger stopped working

Question asked by DOSulli2 Employee on Jan 25, 2018
Latest reply on Mar 6, 2018 by Narsimh

Hi there

I have been using the ADuCM4050 COG board for a week or 2, with IAR EWB v8.2, and using the CMSIS-DAP USB debugger. I'm just using the CMSIS pack examples and playing with them.

 

All worked fine till today, when Download and Debug wont work anymore. Following the wiki guidelines I erased flash with the Cross Core Serial Flash tool (using the ADuCM302x selection....assume this OK). This registered a successful erase. Then I dropped a bin file using DAPLINK and I was able to use download and debug successfully once. Since then, I have not been able to use it, despite erasing flash etc. I also used Maintenance mode to drag and drop the interface file. I'm running out of ideas now. The IAR debug log is copied below....

 

The error pop-up is a CMSIS-DAP window that says Fatal error: failed to connect to CPU.

 

The other odd thing is that in Windows Device Manager I don't explicitly see any mBed or CMSIS-DAP devices.

 

Any help appreciated

Thanks
Dara

 

Thu Jan 25, 2018 13:44:24: IAR Embedded Workbench 8.20.1 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0_2\arm\bin\armproc.dll)
Thu Jan 25, 2018 13:44:24: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0_2\arm\config\flashloader\AnalogDevices\FlashADuCM4050.mac
Thu Jan 25, 2018 13:44:24: Loading the CMSIS-DAP driver
Thu Jan 25, 2018 13:44:24: Probe: CMSIS-DAP probe SW module ver 1.12
Thu Jan 25, 2018 13:44:24: Probe: CMSIS-DAP S/N '0603000041114e4500263003b60f0001a6e1000097969900' mapped to a number 97969900.
Thu Jan 25, 2018 13:44:24: Emulation layer version 4.26
Thu Jan 25, 2018 13:44:25: Notification to init-after-power-up hookup.
Thu Jan 25, 2018 13:44:25: Notification to core-connect hookup.
Thu Jan 25, 2018 13:44:25: Probe: ConnectSpec='CMSIS-DAP:0603000041114e4500263003b60f0001a6e1000097969900:7-1BF7082F-0-0000'.
Thu Jan 25, 2018 13:44:25: Connecting to TAP#0 DAP AHB-AP-CM port 0 (IDR=0x24770011).
Thu Jan 25, 2018 13:44:25: Recognized CPUID=0x410fc241 Cortex-M4 r0p1 arch ARMv7-M
Thu Jan 25, 2018 13:44:25: Debug resources: 6 instruction comparators, 4 data watchpoints.
Thu Jan 25, 2018 13:44:25: CPU status OK
Thu Jan 25, 2018 13:44:25: MultiCore: Asynchronous core execution FORCED.
Thu Jan 25, 2018 13:44:25: MultiCore: Synchronous core execution DISABLED.
Thu Jan 25, 2018 13:44:25: LowLevelReset(hardware, delay 200)
Thu Jan 25, 2018 13:44:26: -I- execUserFlashInit!
Thu Jan 25, 2018 13:44:26: Loaded debugee: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0_2\arm\config\flashloader\AnalogDevices\FlashADuCM4050.out
Thu Jan 25, 2018 13:44:26: Target reset
Thu Jan 25, 2018 13:44:28: Unloaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0_2\arm\config\flashloader\AnalogDevices\FlashADuCM4050.mac
Thu Jan 25, 2018 13:44:28: Downloaded C:\Users\dosulli2\Documents\SVN\Project CbM\ADuCM4050 Testing\EV-COG-AD4050LZ\EV-COG-AD4050LZ\EV-COG-AD4050LZ\iar\Debug\Exe\blinky_example.out to flash memory.
Thu Jan 25, 2018 13:44:29: Loaded debugee: C:\Users\dosulli2\Documents\SVN\Project CbM\ADuCM4050 Testing\EV-COG-AD4050LZ\EV-COG-AD4050LZ\EV-COG-AD4050LZ\iar\Debug\Exe\blinky_example.out
Thu Jan 25, 2018 13:44:29: The downloaded program doesn't seem to match the expected memory layout of the target system:
Thu Jan 25, 2018 13:44:29: There are linked memory segments outside known memory areas.
Thu Jan 25, 2018 13:44:29: Memory is specified as follows:
Thu Jan 25, 2018 13:44:29:   0x00000000 - 0x0007FFFF  ROM/Flash
Thu Jan 25, 2018 13:44:29:   0x10000000 - 0x10007FFF  RAM
Thu Jan 25, 2018 13:44:29:   0x20000000 - 0x20003FFF  RAM
Thu Jan 25, 2018 13:44:29:   0x20040000 - 0x20053FFF  RAM
Thu Jan 25, 2018 13:44:29:   0x22000000 - 0x2207FFFF  RAM
Thu Jan 25, 2018 13:44:29:   0x40000000 - 0x4004CFFF  Uncached/SFR
Thu Jan 25, 2018 13:44:29:   0x42000000 - 0x43FFFFFF  Uncached/SFR
Thu Jan 25, 2018 13:44:29:   0xE0000000 - 0xFFFFFFFF  Uncached/SFR
Thu Jan 25, 2018 13:44:29: Segments are linked as follows:
Thu Jan 25, 2018 13:44:29:   0x00000000 - 0x0000015F  ROM/Flash
Thu Jan 25, 2018 13:44:29:   0x00000180 - 0x0000019F  ROM/Flash
Thu Jan 25, 2018 13:44:29:   0x000007FC - 0x000007FF  RAM
Thu Jan 25, 2018 13:44:29:   0x00000800 - 0x00003B0C  ROM/Flash
Thu Jan 25, 2018 13:44:29:   0x20000000 - 0x20000333  RAM
Thu Jan 25, 2018 13:44:29:   0x20003800 - 0x20003FFF  RAM
Thu Jan 25, 2018 13:44:29:   0x20040000 - 0x20053FFF  RAM
Thu Jan 25, 2018 13:44:29: LowLevelReset(software, delay 200)
Thu Jan 25, 2018 13:44:29: LowLevelReset(hardware, delay 200)
Thu Jan 25, 2018 13:44:29: The processor cannot be debugged.
Thu Jan 25, 2018 13:44:29: The debug registers are not accessible or
Thu Jan 25, 2018 13:44:29: the CPU clock is stalled by the memory controller.
Thu Jan 25, 2018 13:44:29: CPU status FAILED
Thu Jan 25, 2018 13:44:29: Reading memory at 0x00000000 failed while verifying download.
Thu Jan 25, 2018 13:44:31: Reset or power cycle the board.Cannot initialize DAP access
Thu Jan 25, 2018 13:44:31: IAR Embedded Workbench 8.20.1 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0_2\arm\bin\armproc.dll)
Thu Jan 25, 2018 13:44:31: Loading the CMSIS-DAP driver

Outcomes