[ABANDONED] Can connect to the chip (SAMD21) but can't erase or program it

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

  • [ABANDONED] Can connect to the chip (SAMD21) but can't erase or program it

    SEGGER: J-Link EDU Mini V1 compiled Dec 7 2021 08:38:51
    SHIP: ATSAMD21E18A

    J-Link Commander was able(!) to connect to the chip (see below), but I can't erase or program it.
    and the support is useless since it's EDU version (unbelievable support model)

    Source Code

    1. SEGGER J-Link Commander V7.60h (Compiled Feb 9 2022 14:16:26)
    2. DLL version V7.60h, compiled Feb 9 2022 14:15:10
    4. Connecting to J-Link via USB...O.K.
    5. Firmware: J-Link EDU Mini V1 compiled Dec 7 2021 08:38:51
    6. Hardware version: V1.00
    7. S/N: 801041448
    8. License(s): FlashBP, GDB
    9. USB speed mode: Full speed (12 MBit/s)
    10. VTref=3.298V
    13. Type "connect" to establish a target connection, '?' for help
    14. J-Link>connect
    15. Please specify device / core. <Default>: ATSAMD21E18A
    16. Type '?' for selection dialog
    17. Device>
    18. Please specify target interface:
    19. J) JTAG (Default)
    20. S) SWD
    21. T) cJTAG
    22. TIF>s
    23. Specify target interface speed [kHz]. <Default>: 4000 kHz
    24. Speed>
    25. Device "ATSAMD21E18A" selected.
    28. Connecting to target via SWD
    29. InitTarget() start
    30. InitTarget()
    31. InitTarget() end
    32. Found SW-DP with ID 0x0BC11477
    33. DPIDR: 0x0BC11477
    34. CoreSight SoC-400 or earlier
    35. Scanning AP map to find all available APs
    36. AP[1]: Stopped AP scan as end of AP map has been reached
    37. AP[0]: AHB-AP (IDR: 0x04770031)
    38. Iterating through AP map to find AHB-AP to use
    39. AP[0]: Core found
    40. AP[0]: AHB-AP ROM base: 0x41003000
    41. CPUID register: 0x410CC601. Implementer code: 0x41 (ARM)
    42. Found Cortex-M0 r0p1, Little endian.
    43. FPUnit: 4 code (BP) slots and 0 literal slots
    44. CoreSight components:
    45. ROMTbl[0] @ 41003000
    46. [0][0]: E00FF000 CID B105100D PID 000BB4C0 ROM Table
    47. ROMTbl[1] @ E00FF000
    48. [1][0]: E000E000 CID B105E00D PID 000BB008 SCS
    49. [1][1]: E0001000 CID B105E00D PID 000BB00A DWT
    50. [1][2]: E0002000 CID B105E00D PID 000BB00B FPB
    51. [0][1]: 41006000 CID B105900D PID 001BB932 MTB-M0+
    52. Cortex-M0 identified.
    53. J-Link>
    Display All
    Images

    • segger.jpg

      75.2 kB, 464×555, viewed 244 times

    • atmel.jpg

      258.13 kB, 1,098×1,009, viewed 216 times

    The post was edited 4 times, last by mikkadim ().

  • Hi,

    <rant>
    What exactly is unbelievable to you when it comes to the support model?
    That for a $15 educational debug probe (J-Link EDU Mini), that has professional quality, we cannot invest hundreds of hours of specialized J-Link engineers into support?
    How dare you SEGGER of being a company that needs to pay salaries and plan with resources
    </rant>

    Back to the topic:
    If you can connect, the J-Link and wiring is electrically OK.
    Failure in flash programming can have multiple reasons.

    What do you mean with “was able to connect”?

    Did it work once but not anymore?

    Can you erase + program the same MCU with another tool than J-Flash Lite?
    For example with the tool in your last screenshot?

    Do you work with an eval board or custom hardware?
    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.

  • A suggestion:

    Since J-Link Commander connects, use it to erase and flash the ATSAMD21E18A. If jlink.exe has problems it might give better info about what is going wrong.

    The J-Link Commander command to erase is: "erase" (with no arguments it'll erase the whole flash)

    The J-Link Commander command to flash a .hex file is: "loadfile filename.hex"

  • SEGGER - Alex wrote:

    Hi,

    <rant>
    What exactly is unbelievable to you when it comes to the support model?
    That for a $15 educational debug probe (J-Link EDU Mini), that has professional quality, we cannot invest hundreds of hours of specialized J-Link engineers into support?
    How dare you SEGGER of being a company that needs to pay salaries and plan with resources
    </rant>
    Not standing behind your product is not the best support model. Even if it cost $15.
    Rise the price, if that is the issue, instead of a rant.



    Back to the topic:

    If you can connect, the J-Link and wiring is electrically OK.
    Failure in flash programming can have multiple reasons.

    What do you mean with “was able to connect”?
    Was able to connect to the Segger device and SEGGER J-Link Commander shows that chip ID was detected.



    Did it work once but not anymore?
    Did not work at the beginning.







    Can you erase + program the same MCU with another tool than J-Flash Lite?
    For example with the tool in your last screenshot?
    No, Atmel Studio 7.0.1931 (not the latest, since the latest does not support Segger J-link EDU) is unable to erase to program it.



    Do you work with an eval board or custom hardware?
    Custom one.

  • mwb1100 wrote:

    A suggestion:

    Since J-Link Commander connects, use it to erase and flash the ATSAMD21E18A. If jlink.exe has problems it might give better info about what is going wrong.

    The J-Link Commander command to erase is: "erase" (with no arguments it'll erase the whole flash)

    The J-Link Commander command to flash a .hex file is: "loadfile filename.hex"
    Thank you, yes I tried that too, no luck.

    Also tried on a different chip ATSAMD21E17A (all CRYSTALLESS) - same.

  • mikkadim wrote:

    Not standing behind your product is not the best support model. Even if it cost $15.
    Rise the price, if that is the issue, instead of a rant.
    This statement does not really make sense...
    The fact that you still get responses + hints from SEGGER staff via the forum (where there is no claim for) shows that we (SEGGER) actually *are* behind our products, even if they only cost $15.
    If the price is no issue for you and you demand technical support from engineers etc., then why didn't you go for the J-Link BASE that actually comes with support?

    Do you actually also see the problem with an eval board?
    If yes and you can provide some reproducer (for the eval board), we will have a look if it is a generic issue in the J-Link software.


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