Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

SEGGER - Johannes — Wed, 29 Nov 2017 14:40:51 GMT

For completeness:

J-Link V6.22 fixes the crash that happens after the missing license dialog.

Monitor Mode in general works on all platforms.

Monitor Mode Debugging is an additional feature of J-Link that requires a "higher end" J-Link model (J-Link PLUS, J-Link ULTRA+, J-Link PRO) and may be used only for evaluation on other J-Link models, including the J-Link OBs.

Evaluation of Monitor Mode can currently only be accepted through the dialog on Windows. On Linux and macOS, Monitor Mode can therefore currently not be evaluated/used.

The free Nordic license covers Embedded Studio only, but no additional features (Monitor Mode, Flash Breakpoints, J-Flash) of J-Link.

Regards, Johannes

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Don Schoppe — Wed, 29 Nov 2017 13:15:43 GMT

Hi Johannes, I just wanted to let you know that I tested the J-link Ultra+ under Ubuntu. MMD does indeed work in this case. Thanks, Don

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Don Schoppe — Wed, 29 Nov 2017 12:45:33 GMT

Sure thing and thanks!

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Don Schoppe — Wed, 29 Nov 2017 12:31:32 GMT

Hi Johannes, regarding the SES crash on Windows, installing J-Link V6.22 as Chad suggested solved the issue for me. Regarding SES on Linux, I think one of my co-workers has an Ultra+ I can try but it's more convenient when working with the nRF52840 PVK to just use the on-board support. I didn't realize that MMD is truly for evaluation only. I assumed it was covered as part of the free Nordic license when developing on Nordic hardware. Thanks, Don

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Joakim Jakobsen — Wed, 29 Nov 2017 12:25:34 GMT

I'm glad the update fixed it.
Maybe you could accept Chad's answer as correct, so that others with the same problem can see that the issue is resolved?
Best regards.

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Don Schoppe — Wed, 29 Nov 2017 12:20:43 GMT

Chad, thank you! The J-Link V6.22 fixed my SES crash on Windows as well. Best, Don

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Joakim Jakobsen — Tue, 28 Nov 2017 09:11:00 GMT

Thanks for sharing your solution.
I'm glad you were able to solve it.

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Joakim Jakobsen — Tue, 28 Nov 2017 09:09:56 GMT

Thank you very much for the input Johannes.

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Chad Kennedy — Mon, 27 Nov 2017 19:41:22 GMT

Upgrading to the latest J-Link drivers resolved the issue for me. Segger Embedded Studio V3.30 comes packaged with J-Link V6.20d. I downloaded version J-Link V6.22 from here: www.segger.com/.../jlink

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

SEGGER - Johannes — Mon, 27 Nov 2017 15:31:49 GMT

Hi Don,

Monitor Mode and Flash Breakpoints can currently only be evaluated on Windows. We might add an option to enable evaluation on Linux, too. Otherwise you will need a J-Link PLUS or higher, which is required for non-evaluation use of monitor mode anyhow.

As Joakim we were not able to reproduce the crash on Windows when clicking on Yes nor No in the dialog, yet. Did you send the crash reports with a comment that mentions MMD? Then we will check what went wrong.

@chadkennedy: If you compile a project for a Nordic device and the network adapter the license is locked to is present, you should not get the No installed activation popup. If that still comes up, can you provide your project file and the contents / screenshot of the License Manager -> Manage Activations and Licnese Manager -> Diagnose Problems

Regards Johannes

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Chad Kennedy — Mon, 27 Nov 2017 14:25:47 GMT

Hi Joakim, Thanks for your response. I'm running into the same problem even with the sample MMD app from Segger. I've confirmed that I added the free SES license from Nordic (although SES regularly re-prompts me to go get a license, and shows "No installed activation" in the License Manager window, but does show my license under "Manage Activations). Please let us know if you get any feedback from Segger. Without MMD, debugging on Nordic will be somewhat painful.

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Joakim Jakobsen — Thu, 23 Nov 2017 08:13:56 GMT

I'm afraid I'm not able to reproduce the crash problem, so it's hard to say what's causing the problem.
I'll make a request for some support from SEGGER. Maybe they can provide some useful input.
I don't know if it's related, but did you add the free SES license provided by Nordic? (I have the license installed).
Also, I couldn't find anyone using MMD on Ubuntu.

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Chad Kennedy — Tue, 21 Nov 2017 22:14:52 GMT

Hi Don, I don't have any further insights unfortunately, but I can confirm I'm seeing the same thing. I'm using the PCA10040 (nRF52 DK) with the S132 SoftDevice and the "ble_app_hrs_pca10040_s132" example. I'm on Windows and after dismissing the "monitor mode missing license" dialog Segger closes and gives the Crash Reporter dialog.

Windows 10 Segger 3.30 nRF52 SDK 14.2.0 SoftDevice S132 5.0.0 J-Link V6.20d PCA10040

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Don Schoppe — Tue, 21 Nov 2017 14:03:06 GMT

Thanks. I have restarted the PC a few times and uninstalled/reinstalled SES 3.30 x64. I've also tried to debug a different example (ble blinky) but experience the same crash. In addition I moved the SDK closer to the root, thinking perhaps the paths were getting too long. SES still crashes. I would really like to get this working under Ubuntu (my primary dev environment). SES doesn't crash under Ubuntu, but it doesn't enter debug monitor mode either. I suspect the MMD license will actually be required there or one may have to use the J-Link PLUS, ULTRA+ or PRO which includes the license. Is anyone at Nordic using DMM with SES 3.30 under Ubuntu? Thanks!

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Joakim Jakobsen — Tue, 21 Nov 2017 08:49:01 GMT

I'm using Win10x64, SES 3.30, SDK v14.1, Softdevice S140 and the nRF52840 PDK.
I actually don't know what the problem might be. You could try restarting your computer or maybe reinstalling the SDK/SES?
Best regards.

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Don Schoppe — Mon, 20 Nov 2017 17:02:51 GMT

Hi Joakim, Thanks! I put the files in the same location as ble template example's main.c and the code is building fine so I don't think it's a path problem. BTW, are you on Windows or Linux? Which versions of SES, SDK, and softdevice are you using? Thanks, Don

RE: Monitor mode debug w/ nRF52840, SES 3.3, SDK14.1.0, BLE S140

Joakim Jakobsen — Mon, 20 Nov 2017 13:07:01 GMT

Hi Don Schoppe!
I've tried reproducing the problem you have having, but I'm not facing any problems.
I can see that you added the JLINK_MONITOR.h to your project explorer, but did you remember to add the path definition to your preprocessor definitions?
Best regards.