Hello, I have a problem with staring "Run" in the "debugger mode" . I used Rigado evaluation board with BMD300 (nrf52) and also work with nrf5 SDK_15.3.0 Examples. Sometimes I have problem with push the button "Run" in the Debugger mode, sometimes it is ok.
I have already read this article https://www.iar.com/support/tech-notes/debugger/application-does-not-run-stand-alone/
Log:
Mon May 13, 2019 15:43:48: IAR Embedded Workbench 8.30.2 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.1\arm\bin\armproc.dll)
Mon May 13, 2019 15:43:48: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.1\arm\config\debugger\NordicSemi\nRF52.dmac
Mon May 13, 2019 15:43:48: JLINK command: ProjectFile = C:\Rigado\BLE_BNO_ver1\nRF5_SDK_15.3.0_59ac345\examples\peripheral\blinky\pca10040\s132\iar\settings\blinky_pca10040_s132_nrf52832_xxaa.jlink, return = 0
Mon May 13, 2019 15:43:48: Device "NRF52832_XXAA" selected.
Mon May 13, 2019 15:43:48: DLL version: V6.44h, compiled May 3 2019 17:37:09
Mon May 13, 2019 15:43:48: Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Mon May 13, 2019 15:43:48: Selecting SWD as current target interface.
Mon May 13, 2019 15:43:48: JTAG speed is initially set to: 1000 kHz
Mon May 13, 2019 15:43:48: Found SW-DP with ID 0x2BA01477
Mon May 13, 2019 15:43:48: Found SW-DP with ID 0x2BA01477
Mon May 13, 2019 15:43:48: Scanning AP map to find all available APs
Mon May 13, 2019 15:43:48: AP[2]: Stopped AP scan as end of AP map has been reached
Mon May 13, 2019 15:43:48: AP[0]: AHB-AP (IDR: 0x24770011)
Mon May 13, 2019 15:43:48: AP[1]: JTAG-AP (IDR: 0x02880000)
Mon May 13, 2019 15:43:48: Iterating through AP map to find AHB-AP to use
Mon May 13, 2019 15:43:48: AP[0]: Core found
Mon May 13, 2019 15:43:48: AP[0]: AHB-AP ROM base: 0xE00FF000
Mon May 13, 2019 15:43:48: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Mon May 13, 2019 15:43:48: Found Cortex-M4 r0p1, Little endian.
Mon May 13, 2019 15:43:48: FPUnit: 6 code (BP) slots and 2 literal slots
Mon May 13, 2019 15:43:48: CoreSight components:
Mon May 13, 2019 15:43:48: ROMTbl[0] @ E00FF000
Mon May 13, 2019 15:43:48: ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
Mon May 13, 2019 15:43:48: ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
Mon May 13, 2019 15:43:48: ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
Mon May 13, 2019 15:43:48: ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
Mon May 13, 2019 15:43:48: ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
Mon May 13, 2019 15:43:48: ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Mon May 13, 2019 15:43:48: Reset: Halt core after reset via DEMCR.VC_CORERESET.
Mon May 13, 2019 15:43:48: Reset: Reset device via AIRCR.SYSRESETREQ.
Mon May 13, 2019 15:43:48: Hardware reset with strategy 0 was performed
Mon May 13, 2019 15:43:48: Initial reset was performed
Mon May 13, 2019 15:43:48: J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (4096 bytes)
Mon May 13, 2019 15:43:48: J-Link: Flash download: Total time needed: 0.103s (Prepare: 0.042s, Compare: 0.002s, Erase: 0.003s, Program: 0.047s, Verify: 0.000s, Restore: 0.005s)
Mon May 13, 2019 15:43:48: 2108 bytes downloaded (13.20 Kbytes/sec)
Mon May 13, 2019 15:43:48: Loaded debugee: C:\Rigado\BLE_BNO_ver1\nRF5_SDK_15.3.0_59ac345\examples\peripheral\blinky\pca10040\s132\iar\_build\blinky_pca10040_s132.out
Mon May 13, 2019 15:43:48: Reset: Halt core after reset via DEMCR.VC_CORERESET.
Mon May 13, 2019 15:43:48: Reset: Reset device via AIRCR.SYSRESETREQ.
Mon May 13, 2019 15:43:49: Hardware reset with strategy 0 was performed
Mon May 13, 2019 15:43:49: Target reset
