[SOLVED] Abnormal function of Linux JlinkConfigExe

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

  • [SOLVED] Abnormal function of Linux JlinkConfigExe

    It was successful to change the Jlink startup mode to CMSIS_DAP using JlinkConfigExe, but it was inoperable to change the Jlink startup mode of CMSIS_DAP mode to Jlink.
    In the Arch Linux environment.

    Linux archlinux 5.10.27-1-lts #1 SMP Tue, 30 Mar 2021 13:22:29 +0000 x86_64 GNU/Linux

  • Hi,

    We need some add. information to be able to help here.
    1. What does "unsuccessful" mean? (J-Link not listed in configurator anymore once switched to CMSIS-DAP mode? Listed but re-configure throws an error? If there is an error message, can you send a screenshot?)
    2. Does it work under ArchLinux if JLinkConfigExe is started with superuser access rights?
    3. Does it work under Windows?
    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.

  • Right-click-> Configure.
    No configuration dialog box is displayed.
    There is no error message.

    But using JLinkConfigExe in linux.
    Right-click-> Configure.
    Can display the configuration dialog box correctly.
    CMSISM-DAP mode can be selected normally, but Jink mode cannot be selected.


    But using sudo JLinkConfigExe in linux.
    Right-click-> Configure.
    Can display the configuration dialog box correctly.

    Can choose Jlink mode to start normally

    Windows right-click-> Configure.
    Can display the configuration dialog box correctly.
    Can choose Jlink mode to start normally

    The post was edited 1 time, last by taotieren ().

  • SEGGER - Alex wrote:

    Hi,

    We need some add. information to be able to help here.
    1. What does "unsuccessful" mean? (J-Link not listed in configurator anymore once switched to CMSIS-DAP mode? Listed but re-configure throws an error? If there is an error message, can you send a screenshot?)
    2. Does it work under ArchLinux if JLinkConfigExe is started with superuser access rights?
    3. Does it work under Windows?


    The test found that the udev rules of cmsis-dap need to be configured. After configuration, the jlink and CMSIS-DAP modes can be switched normally through JlinkConfigExe.

    Shell-Script: 99-cmsis-dap.rules

    1. sudo cat > /etc/udev/rule.d/99-cmsis-dap.rules << EOF
    2. # Copy this file to /etc/udev/rules.d/
    3. # If rules fail to reload automatically, you can refresh udev rules
    4. # with the command "udevadm control --reload"
    6. # This rules are based on the udev rules from the OpenOCD project, with unsupported probes removed.
    7. # See http://openocd.org/ for more details.
    8. #
    9. # This file is available under the GNU General Public License v2.0
    11. ACTION!="add|change", GOTO="cmsis_dap_rules_end"
    13. SUBSYSTEM=="gpio", MODE="0660", GROUP="plugdev", TAG+="uaccess"
    15. SUBSYSTEM!="usb|tty|hidraw", GOTO="cmsis_dap_rules_end"
    17. # CMSIS-DAP compatible adapters
    18. ATTRS{product}=="*CMSIS-DAP*", MODE="666", GROUP="plugdev", TAG+="uaccess"
    20. LABEL="cmsis_dap_rules_end"
    21. EOF
    Display All

  • That’s why I asked for additional info....
    I already suspected that it is the rules file but now we know it.

    We will fix this in one of the next versions.
    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.