Monday, December 11th 2017, 10:13am UTC+1

You are not logged in.

  • Login
  • Register

chadkennedy

Beginner

Date of registration: Nov 17th 2017

Posts: 6

1

Wednesday, November 22nd 2017, 5:54pm

[SOLVED] SES v3.30 crashes when Monitor Mode Debugging is enabled _using Segger-provided example

I tried the Segger-provided example given here:
https://www.segger.com/products/debug-pr…ing/#tab-3297-7

After dismissing the "monitor mode missing license" dialog Segger closes and gives the Crash Reporter dialog.

Configuration:
Windows 10
Segger 3.30
nRF52 SDK 14.2.0
J-Link V6.20d S/N 682368144
PCA10040

See for reference this thread: SES v3.30 crashes when Monitor Mode Debugging is enabled

I didn't get a chance to try the Segger-provided example before that thread was closed.

chadkennedy

Beginner

Date of registration: Nov 17th 2017

Posts: 6

2

Wednesday, November 22nd 2017, 5:56pm

One small error in the above post on my part: Since I'm using the Segger-provided example in this case, the nRF SDK is not used at all.

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 434

3

Thursday, November 23rd 2017, 5:23pm

Hello Chad,

Thank you for your inquiry.
I just tried the Example Project with the setup you provided and the application is working as expected.
Did you follow the steps in the ReadMe that is included in the example project?
If yes, could you zip up the project you were using and attach it?

Best regards,
Nino

chadkennedy

Beginner

Date of registration: Nov 17th 2017

Posts: 6

4

Monday, November 27th 2017, 3:18pm

I have zipped up and attached the project file I'm using, as requested.
chadkennedy has attached the following file:

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 434

5

Monday, November 27th 2017, 4:46pm

Hello Chad,

You did not select the correct target device as described in the ReadMe.
That is why the project is not working on your device.
Edit the target device in the Project settings to your particular target device and you should be good to go.
For that go to Project->Edit Options...->Debug->Debugger->Target Device and edit that entry.

Best regards,
Nino

chadkennedy

Beginner

Date of registration: Nov 17th 2017

Posts: 6

6

Monday, November 27th 2017, 4:57pm

I changed from Cortex-M4 to nRF52832_xxAA. Did a rebuild and debug. Same crash occurs. I have attached the updated project.
chadkennedy has attached the following file:

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 434

7

Monday, November 27th 2017, 5:11pm

Hello Chad,

The issue is still not reproducible on our side with the same application and setup.
Could you try updating the J-Link Software to the latest version and give it a try?
Are you using something else than the J-Link OB for target connection with the eval board?

Best regards,
Nino

chadkennedy

Beginner

Date of registration: Nov 17th 2017

Posts: 6

8

Monday, November 27th 2017, 8:42pm

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

Thank you for your help Nino!

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 434

9

Tuesday, November 28th 2017, 8:56am

Hello Chad,

great to hear that you are up and running again.
I will consider this case as closed then.

Best regards,
Nino