IAR exporter: extended debugger settings template with modifiable options needed for Nordic targets

[anangl]

Description

The default CMSIS-DAP interface speed (Auto) is causing troubles in debug communication (at least on Nordic's DKs). It was changed to 2 MHz for Nordic targets. An extra option "--drv_vector_table_base=0x0" was also added for these, so the debug session is not started with a jump to the application's reset handler, but to the SoftDevice's one instead.

Status

READY

Migrations

NO

TODO

• /morph export-bulid

[anangl]

@theotherjimmy Could you have a look?
cc @nvlsianpu @pan-

[pan-]

@anangl does it work with the existing CMSIS DAP firmware from Nordic ?

[anangl]

Yes. I've tested it with version 0221 on both, NRF51_DK and NRF52_DK.

[pan-]

@anangl I'm able to start a debug session now but I still can't flash the flash the application from IAR.
What version of IAR do you use ?

[anangl]

7.60.2

[theotherjimmy]

/morph export-build

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 133

All exports and builds passed!

[0xc0170]

@anangl Please can you update to 7.8 and verify that it works?

[0xc0170]

@anangl Any update with IAR 7.8 ?

[anangl]

@0xc0170 Not yet. I'm in the process of upgrading IAR to 7.8. Unfortunately, my current license does not allow to use version newer than 7.6, so it takes a bit more time (I need license renewal), but it should be finished soon, hopefully.

[anangl]

I finally checked it with 7.80.4. The behavior is the same (to be exact, almost the same, 7.60.2 reported an unknown option CADI_ID used in the project). The only problem I encounter is that when I plug the board to a USB 3.0 port I get some (probably) communication errors - IAR reports either a memory verification error:

Fri Mar 31, 2017 09:29:11: CPU status - IN RESET 
Fri Mar 31, 2017 09:29:11: CPU status OK 
Fri Mar 31, 2017 09:29:11: Downloading nrf52xxx flash loader 
Fri Mar 31, 2017 09:29:11: Loaded debugee: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\flashloader\NordicSemi\nrf52xxx.out 
Fri Mar 31, 2017 09:29:12: Target reset 
Fri Mar 31, 2017 09:29:17: Unloaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\flashloader\NordicSemi\nrf52xxx.mac 
Fri Mar 31, 2017 09:29:17: Flash memory checksum verification failed for range 0x1C000-0x2493A. 
Fri Mar 31, 2017 09:29:58: IAR Embedded Workbench 7.80.4 (armproc.dll) 
Fri Mar 31, 2017 09:29:58: Loading the CMSIS-DAP driver 

or a problem with loading the flash loader:

Fri Mar 31, 2017 09:30:42: CPU status - IN RESET 
Fri Mar 31, 2017 09:30:43: CPU status OK 
Fri Mar 31, 2017 09:30:43: Downloading nrf52xxx flash loader 
Fri Mar 31, 2017 09:30:43: Failed to load flash loader: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\flashloader\NordicSemi\nrf52xxx.out 
Fri Mar 31, 2017 09:30:43: Unloaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\flashloader\NordicSemi\nrf52xxx.mac 
Fri Mar 31, 2017 09:30:43: Failed to load flash loader: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\flashloader\NordicSemi\nrf52xxx_xxaa.flash 
Fri Mar 31, 2017 09:31:09: IAR Embedded Workbench 7.80.4 (armproc.dll) 
Fri Mar 31, 2017 09:31:10: Loading the CMSIS-DAP driver 

When I use a USB 2.0 port instead, the flashing and debugging goes without any problems. Maybe @pan- is encountering a similar problem? But I think it's not related to the exporter, rather to the USB driver used by IAR - when I try to debug with Keil uVision or pyOCD (via plug-in in eclipse), everything works well no matter if I use USB 2.0 or 3.0.

[0xc0170]

@anangl Thanks