[ABANDONED] SAMC21 and SAM-ICE

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

  • [ABANDONED] SAMC21 and SAM-ICE

    Hello,

    I am trying to connect to my SAMC21E18 with the SAM-ICE debugger (SWD) but I'm having difficulties: target voltage is read correctly but Atmel Studio 7 is then incapable of programming as it fails with "Error: InitTarget(): PCode returned with error code -1"

    This is Jlink commander output:

    Source Code

    1. SEGGER J-Link Commander V6.20i (Compiled Nov 17 2017 17:47:07)
    2. DLL version V6.20i, compiled Nov 17 2017 17:46:22
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link ARM V8 compiled Aug 26 2015 15:08:21
    6. Hardware version: V8.00
    7. S/N: 28023442
    8. License(s): RDI, GDB
    9. OEM: SAM-ICE
    10. VTref = 3.287V
    12. Type "connect" to establish a target connection, '?' for help
    13. J-Link>connect
    14. Please specify device / core. <Default>: ATSAMC21E18
    15. Type '?' for selection dialog
    16. Device>
    17. Please specify target interface:
    18. J) JTAG (Default)
    19. S) SWD
    20. TIF>s
    21. Specify target interface speed [kHz]. <Default>: 4000 kHz
    22. Speed>
    23. Device "ATSAMC21E18" selected.
    25. Connecting to target via SWD
    26. InitTarget()
    27. Secured Atmel SAMD device detected.
    28. For debugger connection the device needs to be unsecured.
    29. Note: Unsecuring will trigger a mass erase of the internal flash.
    30. Executing default behavior previously saved in the registry.
    31. Device will be unsecured now.
    32. InitTarget()
    33. Secured Atmel SAMD device detected.
    34. For debugger connection the device needs to be unsecured.
    35. Note: Unsecuring will trigger a mass erase of the internal flash.
    36. Executing default behavior previously saved in the registry.
    37. Device will be unsecured now.
    39. ****** Error: InitTarget(): PCode returned with error code -1
    Display All


    What do you think is wrong? I think connections are fine, the MCU gets 3.3V and the SWD cable should be ok.
    Thanks

  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.
    SAM-ICE support is provided through Atmel and not SEGGER so I am not allowed to spend much time on your question.
    So I suggest contacting Atmel about that issue.

    Is the issue reproducible with a evalboard?
    Did you program a application that might have set flash read/write protections?

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

    Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.
    SAM-ICE support is provided through Atmel and not SEGGER so I am not allowed to spend much time on your question.
    So I suggest contacting Atmel about that issue.

    Is the issue reproducible with a evalboard?
    Did you program a application that might have set flash read/write protections?

    Best regards,
    Nino
    Thanks, I already ordered an evaluation board and will try to see what's wrong. Meanwhile I already asked on Atmel forums.
    The problem happens even just by reading the processor ID, what is weird is that reset signal happens after some data is sent through SWDIO, not sure this is the correct behaviour.

    Thanks