[SOLVED] JTag Communication Error: SAM3U-EK and SAM-ICE

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

  • [SOLVED] JTag Communication Error: SAM3U-EK and SAM-ICE

    Hi everyone!

    I've been working with an Atmel SAM3U-EK (evaluation board) and SAM-ICE. I've been trying to troubleshoot my problem but there's not too much documentation on SAM-ICE and I've finally hit a wall after a week. I am new to these products so hopefully what I'm doing wrong is something really simple.

    So anyways, when I connect the jtag cable between the mcu and sam-ice, most of the time I get the error in the picture attached. However, sometimes it decides to work and communication is successful. Is the problem the JTag cable or something with the debugger and/or evaluation board? I should be getting another jtag cable soon to further test if the cable is the problem.

    Thanks and hopefully this is not a complicated fix.

    EDIT: If someone could just point me in the right direction as well that would be great. I'm trying my best to learn more about these products ya
    Images

    • Jtag_Communication_error.jpg

      183.15 kB, 669×1,030, viewed 813 times

    The post was edited 2 times, last by euphoricnoise ().

  • Hi,

    So anyways, when I connect the jtag cable between the mcu and sam-ice, most of the time I get the error in the picture attached. However, sometimes it decides to work and communication is successful.


    Yeah, sounds like a connection issue due to bad signal quality or similar.
    Trying with another cable is definitely a good idea.
    If the problem persists: Please check the SAM-ICE with another board, to make sure the SAM-ICE is not the problem here.


    - Alex
    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 - Alex wrote:

    Yeah, sounds like a connection issue due to bad signal quality or similar.
    Trying with another cable is definitely a good idea.
    If the problem persists: Please check the SAM-ICE with another board, to make sure the SAM-ICE is not the problem here.


    - Alex
    It looks like there's something in my code that makes the uC go to sleep and not able to respond with the debugger. Looks like it was a user error. Thanks Alex!

  • Hi,

    Alright. So you had it running before and after flashing a particular application, it stopped working.
    From your post, I got the impression that it was not working at all, from the beginning.

    Good to hear that you have found the problem.
    Low power modes are always tricky since there are different levels of low-power modes which
    all have different effects on the debug side, and some of them do not allow debugging.
    In addition, on the SAM3U it is difficult for the debug probe to gain control over the device again,
    since it does not provide a real concept for cases where debugger connection shall be performed and the device is already in a low-power mode.


    - Alex
    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.