SES v3.30 crashes when Monitor Mode Debugging is enabled

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • SES v3.30 crashes when Monitor Mode Debugging is enabled

    Hi,

    I have just updated my Segger Embedded Studio from v3.26a to v3.30.
    My license have also been updated from evaluation to licensed for Nordic.

    My setup:
    a) OS: Windows 10 Pro
    b) SES version: v3.30

    Previously, I am running Monitor Mode Debugging in v3.26a and it was working.
    After upgrade and running Monitor Mode Debugging in v3.30, IDE stops working and error report has been requested.
    Even if I re-use SES v3.26a, similar problem occurs.

    Please advise on what can be done.

    Many thanks!
    Images

    • SES_v3.30_Crash.png

      20.04 kB, 491×323, viewed 614 times

  • Hello,

    Thank you for you inquiry.

    I just tried to reproduce your behaviour but could not reproduce any crash in monitor mode.
    What target device are you using?
    Is it an eval board or custom hardware?
    Which J-Link are you using?
    What is its serial number?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Nino,

    Thank you for your response.

    I'm using the following:
    Target device: nRF52832 eval board
    J-link: nRF52 DK board
    Serial number: Segger 682474296

    Many thanks in advance.

    p.s. I'm puzzled too, the Monitor Mode Debugging was working previously.

  • Hello,

    i tired monitor mode debugging with that exact board and had no issues doing so.

    Did you use the example project from our website as a baseline?
    segger.com/products/debug-prob…ode-debugging/#tab-3297-7
    What are the differences between your project and the example project?
    Could you provide your example project or a project where the issue is reproducible?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • I am seeing the same crash. 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.

    I followed the directions here: devzone.nordicsemi.com/blogs/8…olutionize-the-way-you-d/

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

  • Hello,

    As this issue is not reproducible with the examples we provide this thread will be closed now.
    Please contact Nordic in regards of issues with their examples.
    The blog post you linked is outdated and might not work with current ES and Nordic SDK examples.
    For reference use the example that i linked in my previous post.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.