[SOLVED] J-Link unable to get ATSAML10E out of secure mode.

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

  • [SOLVED] J-Link unable to get ATSAML10E out of secure mode.

    When attempting to enumerate or program an ATSAML10E processsor, the J-link driver reports that "Debug Access Level is 0 (secured). For debugger connection the device needs to be unsecured". Clicking 'yes' to unsecure the device however never succeeds and the window pops up again until eventually it gives up. We have successfully flashed this processor using the J-Link programmer before without issues so we are unsure what might be different this time. Haven't had much success looking through the ATSAML10 manual either.

    Below is the full output when trying to program the device through Keil uVision.



    Brainfuck Source Code

    1. JLink info:
    2. ------------
    3. DLL: V6.54 , compiled Oct 28 2019 10:33:23
    4. Firmware: J-Link V10 compiled Oct 22 2019 16:28:15
    5. Hardware: V10.10
    6. S/N : 600107114
    7. Feature(s) : RDI, FlashBP, FlashDL, JFlash, GDB
    8. * JLink Info: InitTarget()
    9. * JLink Info: BootROM Phase Extension detected, trying to start application...
    10. * JLink Info: Timeout while waiting for application boot.
    11. * JLink Info: Device will be unsecured now.
    12. * JLink Info: InitTarget: Unsecuring device...
    13. * JLink Info: Found SW-DP with ID 0x0BF11477
    14. * JLink Info: Scanning AP map to find all available APs
    15. * JLink Info: AP[1]: Stopped AP scan as end of AP map has been reached
    16. * JLink Info: AP[0]: AHB-AP (IDR: 0x04770025)
    17. * JLink Info: Iterating through AP map to find AHB-AP to use
    18. * JLink Info: AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
    19. * JLink Info: InitTarget()
    20. * JLink Info: BootROM Phase Extension detected, trying to start application...
    21. * JLink Info: Timeout while waiting for application boot.
    22. * JLink Info: Device will be unsecured now.
    23. * JLink Info: InitTarget: Unsecuring device...
    24. * JLink Info: Found SW-DP with ID 0x0BF11477
    25. * JLink Info: Scanning AP map to find all available APs
    26. * JLink Info: AP[1]: Stopped AP scan as end of AP map has been reached
    27. * JLink Info: AP[0]: AHB-AP (IDR: 0x04770025)
    28. * JLink Info: Iterating through AP map to find AHB-AP to use
    29. * JLink Info: AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
    30. ***JLink Error: Could not find core in Coresight setup
    31. Error: Flash Download failed - Target DLL has been cancelled
    32. Flash Load finished at 16:27:41
    Display All
  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us. If you did not change your setup and your application everything should still be working.
    For the unlock to work the reset pin must be connected to J-Link. Could you check if the reset line is correctly wired?

    Should that still not work could you provide a J-Link log file for investigation?
    wiki.segger.com/Enable_J-Link_log_file

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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.
  • Checked the reset line and it is still in place. The j-link is still able to program other boards, it is just one that is behaving this way.

    If it isn't the result of a setting being changed accidentally then I think the processor got damaged somehow to be honest. We thought it might just be some mode triggered by incorrect settings since usually the j-link just reports it can't find anything if the processor is damaged. We might just replace this one and try to figure out how it got damaged rather than figure out exactly what is damaged.