[SOLVED] J-Link Software and Documentation pack versions

  • Hi everyone,

    question for J-Link BASE Classic in combination with J-Link Software and Documentation pack versions (currently the latest version is V8.34).

    Is a J-Link Software and Documentation pack version somehow connected with the end of support period for one year after the purchase?
    I've noticed, that from V8.24 on, at least the "PCode_DevPro_ST_STM32U5.pex" script is not working ... but using V8.24 and older versions without any problem.

    I can dig dipper, for now just have to clarify the end of support period and J-Link Software and Documentation pack versions.

    Br,

  • Hello,


    Please note that the support period is not tied to the J-Link Software and Documentation Pack itself. Once your support period ends, you simply no longer have entitlement to direct technical support.

    Regarding your issue:
    Could you try specifying the full path to the .pex file and see if that resolves the problem?

    I'll also follow up internally to investigate why the changelog hasn't been updated on our website.

    Best regards,
    Simon

    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: https://www.segger.com/ticket/

    Or you can contact us via e-mail.

  • Simon hi,

    yes, it seems that full path approach has a working results ... results attached (V8.24 and V8.34).
    Used full path command:
    DevPro.exe -operation ReadOptionBytes -if SWD -speed 4000 -SetConfigVal "OptionName=FLASH_OPTR" -ScriptFile "C:\Program Files\SEGGER\JLink\Script\PCode_DevPro_ST_STM32U5.pex"

    It would be appreciated, if backward compatibility using just -ScriptFile PCode_DevPro_ST_STM32U5.pex is preserved.

    Br,

  • Hi,

    question for a possible workaround (also for other future users) ... Would it help if we just make a clean installation?
    In my case, I've always performed the "Upgrade existing installation" and have "C:\Program Files\SEGGER\JLink" path in Windows user variables.

    In addition, for ST STM32U5, SEGGER Wiki page does not mention a full path approach for -ScriptFile command:
    ST STM32U5 Option Bytes Programming - SEGGER Knowledge Base

    If it's purely a Device Provisioner thing, could SEGGER team let us know in which J-Link Software and Documentation pack version this limitation will be resolved?

    Br,

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!