[SOLVED] j-ling debuging in MCUXpresso IDE v10.1.1_606

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

  • [SOLVED] j-ling debuging in MCUXpresso IDE v10.1.1_606

    Hello,

    I tried do run the j-link debugger with our customer board and the MCUXpresso IDE v10.1.1_606. Unfortunately I get always an error.
    I use an j-link Ultra+ connect to the board with an J-Link 10-pin Needle Adapter (8.06.04).

    The attached picture “J-Link, GDB Server error.PNG”, “J-Link, Launching error.PNG” and “J-Link, GDB Server error screenshot.PNG” are screen shoots of the error.
    The attached file “detail J-Link, GDB Server error.txt” is the error log of j-link.

    Do you have a hint for my?

    best regards
    Dominik Fallmann
    Images
    • J-Link, GDB Server error.PNG

      59.81 kB, 552×400, viewed 547 times
    • J-Link, Launching error.PNG

      39.79 kB, 447×318, viewed 501 times
    • J-Link, GDB Server error screenshot.PNG

      386.71 kB, 1,913×1,011, viewed 557 times
    Files
  • Hello Dominik,

    Thank you for your inquiry.
    Are you trying to debug eval or custom hardware?
    If eval which one?
    Can you connect to the chip using the J-Link commander?
    wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander

    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.
  • Hello Nino,
    thank you for your swift response.

    Are you trying to debug eval or custom hardware?
    We use a custom Hardware. Please, see the attached picture "customer_hardware.png".

    Can you connect to the chip using the J-Link commander?
    I can use J-Link commander. With my first try a get also an error. Please, see the attached picture "J-Link_Commander1.png".
    Images
    • customer_hardware.png

      40.01 kB, 1,108×629, viewed 382 times
    • J-Link_Commander1.png

      47.74 kB, 670×659, viewed 415 times
  • Hello,

    From the screenshots the target voltage VTref is suspicously low.
    Are you running the target device in some low power mode?
    For this particular device 3.3 V are usually expected.
    If you run it in low power mode keep in mind that some modes disable debug interfaces so J-Link can't access the device anymore.
    We recommend driving the device at 3.3 V for debugging.

    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.
  • Hello Nino,

    thank you for your effort.
    I have found the fault, Pin3 have to connect to GND and at our customer hardware was the Pin3 not connected.
    At the attachment “customer_hardware_Pin3.png” you can find a cut-out of tag-connect datasheet (tag-connect.com/Materials/TC2050-ARM2010.pdf) vs a cut-out from JTAG connector of our hardware.
    best regards
    Dominik
    Images
    • customer_hardware_Pin3.png

      60.27 kB, 1,186×628, viewed 530 times
  • Hi Dominik,

    Great to hear that you are up and running again.
    We will consider this thread as solved now.

    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.