[SOLVED] J-Trace PRO not accessible Win11

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

  • [SOLVED] J-Trace PRO not accessible Win11

    I upgraded my system and now I cant access to the device. The device isn't connected with the tracer.
    Connect with jlink and JTAG is possible.

    In microchip I want reach the probe with TCP and therefore I added it under "Add Target".

    The device status is "connected".

    If I want to connect, the message is: Unable to connect to tool J-Link over IP (752000846)

    @EDIT
    In microchip under "Device Programming" is a JLink Button and this button appears after selcting Jlink probe but the button is disabled.

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

  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.
    Could you try connecting to J-Trace Pro and your target device with the J-Link Commander via USB first?
    wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander
    Does this work?
    If yes, could you try the same via IP?
    Does this work?

    Could you provide screenshots of both connect sessions?

    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.

  • SEGGER J-Link Commander V7.62c (Compiled Mar 23 2022 16:45:48)
    DLL version V7.62c, compiled Mar 23 2022 16:44:32

    Connecting to J-Link via USB...O.K.
    Firmware: J-Link EDU Mini V1 compiled Mar 3 2022 10:17:12
    Hardware version: V1.00
    S/N: 801011341
    License(s): FlashBP, GDB
    USB speed mode: Full speed (12 MBit/s)
    VTref=3.299V


    Type "connect" to establish a target connection, '?' for help
    J-Link>connect
    Please specify device / core. <Default>: ATSAMD51G19A
    Type '?' for selection dialog
    Device>
    Please specify target interface:
    J) JTAG (Default)
    S) SWD
    T) cJTAG
    TIF>s
    Specify target interface speed [kHz]. <Default>: 4000 kHz
    Speed>
    Device "ATSAMD51G19A" selected.


    Connecting to target via SWD
    InitTarget() start
    InitTarget()
    InitTarget() end
    InitTarget() end
    Found SW-DP with ID 0x2BA01477
    DPIDR: 0x2BA01477
    CoreSight SoC-400 or earlier
    Scanning AP map to find all available APs
    AP[2]: Stopped AP scan as end of AP map seems to be reached
    AP[0]: AHB-AP (IDR: 0x24770011)
    AP[1]: AHB-AP (IDR: 0x74770001)
    Iterating through AP map to find AHB-AP to use
    AP[0]: Core found
    AP[0]: AHB-AP ROM base: 0x41003000
    CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
    Found Cortex-M4 r0p1, Little endian.
    FPUnit: 6 code (BP) slots and 2 literal slots
    CoreSight components:
    ROMTbl[0] @ 41003000
    [0][0]: E00FF000 CID B105100D PID 000BB4C4 ROM Table
    ROMTbl[1] @ E00FF000
    [1][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
    [1][1]: E0001000 CID B105E00D PID 003BB002 DWT
    [1][2]: E0002000 CID B105E00D PID 002BB003 FPB
    [1][3]: E0000000 CID B105E00D PID 003BB001 ITM
    [1][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
    [1][5]: E0041000 CID B105900D PID 000BB925 ETM
    [1][6]: E0042000 CID B105900D PID 003BB907 ETB
    Cortex-M4 identified.
    J-Link>

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

  • Hi,

    why a J-Link EDU Mini now? I thought this is about J-Trace Pro?
    Also you keep editing your posts with widely different information so it becomes very difficult for us to follow what is going on what what is not working.

    So could you please simply answer my question before trying anything else?
    Could you try connecting to J-Trace Pro and your target device with the J-Link Commander via USB first?
    wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander
    Does this work?
    If yes, could you try the same via IP?
    Does this work?


    Could you provide screenshots of both connect sessions?
    And I mean screenshots, not copy pasting strings that you edit all over the place.

    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.

  • Yes, it works. See the atteched output. The probe is not shown in Microchip Studio 7.0.2542

    The subject of this thread is a little bit missleading. I want access the probe from Microchip Studio under Win11.

    Regarding your second test. I dont know how it is possible to attach the probe with Jlink Commander via TCP.
    Images

    • jlink-usb.png

      133.07 kB, 964×1,606, viewed 143 times

  • Hi,

    Microchip Studio is not listed on the “supported IDEs” page and untested.
    Therefore, we cannot guarantee that it works.
    As J-Link Commander is able to detect the J-Link, the USB connection is fine.

    We recommend to contact Microchip regarding this. This is actually the wrong forum at this point.

    We MAY list Microchip Studio in the future though
    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.