Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

Upgrading SES to latest version (5.70a) does not work properly with nRF52832 DK and nFR52840 DK

Hello,

I have a firmware working perfect with nRF52832 DK and nRF52840 DK, using SES 5.40a.

Now I just upgraded SES to version 5.70a. With new SES version, each time I flash my DK board I should turn it OFF and ON to get the firmware start running. Even the RESET button does not work.

I see that SES 5.40a uses JLink_x64.dll version 6.94d, and SES 5.70a uses JLink_x64.dll version 7.60c.

I just tried to overwrite JLink_x64.dll from old SES (5.40a) to new SES (5.70a) and EVERYTHING STARTS TO WORK PROPERLY.

Even when it solves my SES upgrade problem, it seems to me to be an artifact that should be fixed some other way.

  • HI Alberto,

    Are there any errors before you perform OFF/ON sequence? Can you provide more information about the error?

    Best regards,
    Dejan

  • Hi Alberto,

    Could you please try to do the same with several different versions of SES (JLink_x64.dll) between your starting version and the last one?
    Please test as many versions as you can between the two you mentioned and provide the results.

    Best regards,
    Dejan

  • Here you have extended information:

    It has nothing to do with my firmware, it happens the same with all sdk Bluetooth examples.

    Taking as reference ble_peripheral\ble_app_blinky, I can say it hangs exactly right after log_init();

    It is able to run first call to NRF_LOG_INFO() but second call never runs, firmware hangs.

    All examples\peripheral run properly, even when using log_init(); and NRF_LOG_INFO().

    Regard to give a try to some prev SES versions, I will give it a try, but I am afraid they are going to work properly.

  • Regard to extended information, please find my post above.
    Regard to multiple SES versions testing requested, here you have a full report:
    SES v5.40a (JLink dll v. 6.94d) OK
    SES v5.40c (JLink dll v. 6.96) OK
    SES v5.42a (JLink dll v. 6.98e) OK
    SES v5.44 (JLink dll v. 7.20) OK
    SES v5.50 (JLink dll v. 7.20b) FAIL
    SES v5.50a (JLink dll v. 7.22d) FAIL
    SES v5.70a (JLink dll v. 7.60) FAIL
    As can be seen, problem seems to start with SES v5.50 and/or its JLink dll v.7.20b.
    Remember that all failing versions work properly if overwriting latest working JLink dll (v7.20).
    Also remember you can see the problem with any SDK ble example (tested with ble_peripheral\ble_app_blinky).
    While this problem is sorted out, I will keep using latest SES v5.70a with JLink dll v.7.20 (from SES 5.44).

  • Hi Alberto,

    Thank you for all provided information.
    I'll get back to you when I get more information for you.

    Best regards,
    Dejan

Related