Monitor Mode Debugging with J-Link and GDB/Eclipse

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

Srinivas — Fri, 14 Dec 2018 09:56:47 GMT

i was all the setting give in the tutorial, still i am getting new problem like after break point now the code is moving Hardfault handler in startup file . Can any one help on this

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

awneil — Wed, 12 Sep 2018 17:07:24 GMT

"NOTE: The J-Link OB that is included on Nordic development kits does not include a license for monitor mode debugging. On Windows machines, the J-Link driver will allow evaluation of the monitor mode debugging feature if the user accepts a license pop-up."

Like this:

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

Alaa — Tue, 10 Apr 2018 14:03:46 GMT

I got errors in JLINK_MONITOR_ISR_SES.s file:

make: *** [_build/nrf52832_xxaa_JLINK_MONITOR_ISR_SES.s.o.o] Error 1
recipe for target '_build/nrf52832_xxaa_JLINK_MONITOR_ISR_SES.s.o.o' failed
symbol `_HandleReadRegDone_Veneer' is already defined
undefined symbol _APP_SP_OFF_S0 used as an immediate value
undefined symbol _APP_SP_OFF_S0 used as an immediate value
undefined symbol _MON_VERSION used as an immediate value
undefined symbol _NUM_BYTES_BASIC_STACKFRAME used as an immediate value
undefined symbol _NUM_BYTES_EXTENDED_STACKFRAME used as an immediate value

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

Tis — Thu, 12 Oct 2017 13:43:23 GMT

Hi Daniel,

I figured out that reading your Blog “Getting More Out of Make” is helpful since it mentions the otherwise empty GDB_PORT and DBG_BUILD_DIR. (Please, add a link to it) Nevertheless I don’t succeed in MMD working. Therefore, I asked for the exact things to do. Now in my Debug Configuration the 2 commands are: mon exec SetMonModeDebug=1 mon exec SetMonModeVTableAddr=0x22000

It is unclear why in your screenshot there is the 3rd command mon reset 0 So, I thought the others from the created file of 8 commands are also needed in Eclipse.

A debug session of ble_app_blinky can be started and keeps running in the busy/wait loop as long as no breakpoints are hit. However, when e.g. the breakpoint at the source code bsp_board_led_on(LEDBUTTON_LED) should be hit, then the smartphone app says after 20 seonds that the BLE connection is disconnected. And the intended breakpoint is not hit at all. (No connection is possible anymore: so, reset)

Although I follow all the instructions, I do not manage to have MMD working. Please, any help is welcome!

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

Daniel Veilleux — Wed, 11 Oct 2017 20:53:45 GMT

Hello Tis,

Those two commands (SetMonMode...) are either appended to your existing JLink settings inside eclipse or need to be executed when starting GDB from the command line. If you look at the Makefile that I reference you can see that the "PHONY: gdb_cmd_file" section is the part of the Makefile that creates a text file for use when invoking GDB from the command line.

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

Tis — Wed, 11 Oct 2017 18:45:59 GMT

It is not fully clear to me what commands to add to enable monitor mode debugging. Firstly, 2 commands are mentioned. Then, in the box of “PHONY: gdb_cmd_file” 8 commands are echoed. Finally, in the Debug Configuration 3 commands are shown, although other commands (of 8?) might not be visible. Please, could you clarify what commands are exactly needed?

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

Daniel Veilleux — Wed, 10 May 2017 15:20:34 GMT

Hello Garret,

I wasted an entire evening trying to get it to work with my Linux machine as well before I sent an email to Segger support. It works fine on Linux if you purchase a professional J-Link.

RE: Monitor Mode Debugging with J-Link and GDB/Eclipse

Garret — Wed, 10 May 2017 11:55:01 GMT

Under prerequisites you have this sentence.

On Linux and OSX machines, the J-Link driver will accept the commands to enable monitor mode debugging but will silently fail to enable it.

I have spent literally hours trying to get the Monitor mode running on Segger IDE on a Linux machine. I was starting to lose my mind and gave up.

Is there anyway to get it working??

Garret