RE: SEGGER Embedded Studio and Monitor Mode Debugging

Michael Dietz — Mon, 08 Aug 2016 10:01:32 GMT

arm_startup_nrf52.s and iar_startup_nrf52.s are the startup files for the Keil and IAR IDEs respectively, and will not work with Embedded Studio.

Use the nRF Package in Embedded Studio like you already are. You don't need to modify nrf_startup.s as this is not where the exceptions/interrupts are defined in Embedded Studio. You need to modify $(DeviceVectorsFile) which is in the same System Files/ folder as nRF_Startup.s. Basically all you need to do is make sure DebugMon_Handler is defined as the other ISRs. But here is my file, you can check against it or just use it: nrf52_Vectors.s

-Mike

RE: SEGGER Embedded Studio and Monitor Mode Debugging

leonwj — Sun, 07 Aug 2016 23:25:31 GMT

Hello,

In order to get MMD up and running under Segger Embedded Studio (SES), you will need the following files (in addition to your main application code):

JLINK_MONITOR.c - contains the definitions of the mmd routines (in file JLink_Monitor_Code.zip of the original blog post that you referenced & nRF5x-MMD-led-btn-example.zip in the Part 2 blog)

JLINK_MONITOR.h - contains the declarations of the mmd routines (in file JLink_Monitor_Code.zip of the original blog post that you referenced & nRF5x-MMD-led-btn-example.zip in the Part 2 blog)

JLINK_MONITOR_ISR_SES.s - contains the SES specific asm code which drive the mmd routines referenced in the above files when the Debugmon interrupt is triggered (in file JLink_Monitor_Code.zip of the original blog post that you referenced & nRF5x-MMD-led-btn-example.zip in the Part 2 blog)

ses_nrf52_startup.s - contains the SES specific definition for the vector table with DebugMon_Handler entry (in file nRF5x-MMD-led-btn-example.zip in the Part 2 blog)

Please respond back if you experience any issue(s) with the above or getting MMD working correctly.

Regards