ATSAMB11ZR Xplained Pro - No device detected

1 post / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi, I just bought the ATSAMB11ZR Xplained Pro and the first thing I wanted to do, was to run an example application. So I installed the latest Atmel Studio 7 Verison and followed the instructions of Chapter 3 and 4 in the  Example Profiles Application User's Guide. After updating the EDBG firmware successfully, I was able to apply the Device in the Device Programming Window (Chapter 4.2.1 Step 8.2). But when I tried to read the Device ID I got this Error:

 

 

Some further Information:

  • I'm using Windows 10 Pro and Atmel Studio 7.0 (build 1931) 
  • The status LED is on permanently as soon as the device is applied
  • Here's the ApplicationStatus-Log when I hit Read (maybe it helps):
    18:44:59.686: 06 44 59 686: msg recv(e8):C 185 Tool setProperties "AT_13" {"InterfaceProperties":{"SwdClock":2000000},"InterfaceName":"SWD","DeviceName":"ATSAMB11ZR","PackPath":"C:/Program Files (x86)/Atmel/Studio/7.0/Packs/Atmel/SAMB11_DFP/2.3.190/Atmel.SAMB11_DFP.pdsc"}
    18:44:59.687: 06 44 59 687: msg send(e8):E Tool contextChanged [{"ID":"AT_13","Name":"com.atmel.avrdbg.tool.edbg","DeviceId":"ArmDev_9","InterfaceName":"SWD","InterfaceProperties":{"SwdClock":2000000},"HardwareRevision":240,"MajorFirmwareVersion":3,"MinorFirmwareVersion":37,"FirmwareBuildNumber":438,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":3,"MinorFirmwareVersionOnDisk":37,"CanEraseXmegaPages":1}]
    18:44:59.687: 06 44 59 687: msg send(e8):R 185
    18:44:59.687: Got Tool::contextChanged([{"ID":"AT_13","Name":"com.atmel.avrdbg.tool.edbg","DeviceId":"ArmDev_9","InterfaceName":"SWD","InterfaceProperties":{"SwdClock":2000000},"HardwareRevision":240,"MajorFirmwareVersion":3,"MinorFirmwareVersion":37,"FirmwareBuildNumber":438,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":3,"MinorFirmwareVersionOnDisk":37,"CanEraseXmegaPages":1}] ) event, notifying listeners
    18:44:59.687: Tool:setProperties 8,9758 msecs
    18:44:59.688: 06 44 59 688: msg recv(e8):C 186 Tool getContext "AT_13"
    18:44:59.688: 06 44 59 688: msg send(e8):R 186  {"ID":"AT_13","Name":"com.atmel.avrdbg.tool.edbg","DeviceId":"ArmDev_9","InterfaceName":"SWD","InterfaceProperties":{"SwdClock":2000000},"HardwareRevision":240,"MajorFirmwareVersion":3,"MinorFirmwareVersion":37,"FirmwareBuildNumber":438,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":3,"MinorFirmwareVersionOnDisk":37,"CanEraseXmegaPages":1}
    18:44:59.689: Tool:getContext 1,9948 msecs
    18:44:59.690: 06 44 59 690: msg recv(e8):C 187 Device getContext "ArmDev_9"
    18:44:59.690: 06 44 59 690: msg send(e8):R 187  {"ID":"ArmDev_9","Name":"ATSAMB11ZR","Session":0,"MemoryIDs":[],"RunControlID":""}
    18:44:59.690: Device:getContext 0,9974 msecs
    18:44:59.693: 06 44 59 693: msg recv(e8):C 188 Device startSession "ArmDev_9" "ProgrammingSession"
    18:44:59.693: 06 44 59 693: prg Connect to the device OCD
    18:44:59.724: 06 44 59 724: dap Error reading adr 0xe000edf0 , Error=0x2028
    18:44:59.724: 06 44 59 724: dap RDDI_DAP_WriteD32 e000edf0 a05f0003
    18:44:59.725: 06 44 59 725: dap Error writing adr 0xe000edf0 , Error=0x2028
    18:44:59.725: 06 44 59 725: dap Failed to write to DHCSR to Halt the core
    18:44:59.725: 06 44 59 725: dap RDDI_DAP_WriteD32 4000f040 00000000
    18:44:59.726: 06 44 59 726: dap Error writing adr 0x4000f040 , Error=0x2028
    18:44:59.726: 06 44 59 726:  Cannot write at memory address 4000f040
    18:44:59.726: 06 44 59 726: dap RDDI_DAP_WriteD32 4000f044 00000078
    18:44:59.727: 06 44 59 727: dap Error writing adr 0x4000f044 , Error=0x2028
    18:44:59.727: 06 44 59 727:  Cannot write at memory address 4000f044
    18:44:59.727: 06 44 59 727: dap RDDI_DAP_WriteD32 4000b008 00000000
    18:44:59.728: 06 44 59 728: dap Error writing adr 0x4000b008 , Error=0x2028
    18:44:59.728: 06 44 59 728:  Cannot write at memory address 4000b008
    18:44:59.728: 06 44 59 728: dap RDDI_DAP_WriteD32 4000e010 00000200
    18:44:59.729: 06 44 59 729: dap Error writing adr 0x4000e010 , Error=0x2028
    18:44:59.729: 06 44 59 729:  Cannot write at memory address 4000e010
    18:44:59.730: 06 44 59 730: dap Error reading adr 0x4000b190 , Error=0x2028
    18:44:59.730: 06 44 59 730: dap RDDI_DAP_WriteD32 4000b190 04262e60
    18:44:59.731: 06 44 59 731: dap Error writing adr 0x4000b190 , Error=0x2028
    18:44:59.731: 06 44 59 731:  Cannot write at memory address 4000b190
    18:44:59.731: 06 44 59 731: dap RDDI_DAP_WriteD32 4000b190 04272e60
    18:44:59.732: Watchdog thread was started.
    18:44:59.732: Converting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP errorConverting 4109 to generic DAP erro06 44 59 732: dap Error writing adr 0x4000b190 , Error=0x2028
    18:44:59.732: 06 44 59 732:  Cannot write at memory address 4000b190
    18:44:59.732: 06 44 59 732: dap RDDI_DAP_WriteD32 4000b190 04262e60
    18:44:59.733: 06 44 59 733: dap Error writing adr 0x4000b190 , Error=0x2028
    18:44:59.733: 06 44 59 733:  Cannot write at memory address 4000b190
    18:44:59.733: 06 44 59 733: dap RDDI_DAP_WriteD32 4000a000 00000000
    18:44:59.733: 06 44 59 733: dap Error writing adr 0x4000a000 , Error=0x2028
    18:44:59.734: 06 44 59 733:  Cannot write at memory address 4000a000
    18:44:59.734: 06 44 59 733: dap RDDI_DAP_WriteD32 4000f408 00008005
    18:44:59.734: 06 44 59 734: dap Error writing adr 0x4000f408 , Error=0x2028
    18:44:59.734: 06 44 59 734:  Cannot write at memory address 4000f408
    18:44:59.734: 06 44 59 734: dap RDDI_DAP_WriteD32 4000f010 00000000
    18:44:59.735: 06 44 59 735: dap Error writing adr 0x4000f010 , Error=0x2028
    18:44:59.735: 06 44 59 735:  Cannot write at memory address 4000f010
    18:44:59.735: 06 44 59 735: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=85 03 03 03 80 80 00 80 00 00
    18:44:59.738: 06 44 59 738: dap DAP_Commands replySize0=512 msg=85 00 07 02 42 ...
    18:44:59.738: 06 44 59 738:  No device detected. Error 4109
    18:44:59.738: 06 44 59 738: msg send(e8):R 188 {"Code":1,"Service":"Device","Format":"No device detected. Error 4109"}
    18:44:59.738: Device:startSession 47,8719 msecs
    18:44:59.738: 18:44:59: [ERROR] No device detected. Error 4109, ModuleName: TCF (TCF command: Device:startSession failed.)
    18:44:59.741: 06 44 59 741: msg recv(e8):C 189 Device getContext "ArmDev_9"
    18:44:59.742: 06 44 59 742: msg send(e8):R 189  {"ID":"ArmDev_9","Name":"ATSAMB11ZR","Session":0,"MemoryIDs":[],"RunControlID":""}
    18:44:59.742: Device:getContext 2,9919 msecs
    18:44:59.742: 18:44:59: [ERROR] No device detected. Error 4109, ModuleName: TCF (TCF command: Device:startSession failed.)
    18:44:59.745: 06 44 59 745: msg recv(e8):C 190 Tool getTargetVoltage "AT_13"
    18:44:59.745: 06 44 59 745: pro Mk3Protocol::get()
    18:44:59.745: 06 44 59 745: pro JtagIce3 <<< 02 00 01 00 02
    18:44:59.745: 06 44 59 745: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 0A 00 01 02 00 01 00 02
    18:44:59.745: 06 44 59 745: dap DAP_Commands replySize0=512 msg=80 01 07 02 42 ...
    18:44:59.745: 06 44 59 745: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81
    18:44:59.746: 06 44 59 746: dap DAP_Commands replySize0=512 msg=81 11 00 09 0E ...
    18:44:59.746: 06 44 59 746: pro JtagIce3 >>> 84 01 F4 0C 00
    18:44:59.746: 06 44 59 746: msg send(e8):R 190  3.3159999999999998
    18:44:59.746: Tool:getTargetVoltage 3,9885 msecs
    18:44:59.746: 18:44:59: [ERROR] No device detected. Error 4109, ModuleName: TCF (TCF command: Device:startSession failed.)

     

I know there are other Posts about this Error, but the solutions do not fit my problem. It seems that the Error is often caused by a buggy Atmel Studio installation or version, so I reinstalled Atmel Studio, installed an older Version and installed it on a different computer. But I couldn't get it working. Another solution was to erase the firmware with a Jumper, but my board doesn't have this possibility.

 

I hope someone has another idea how to fix this. Please let me know if you need any further information.

 

Thanks in Advance

 

Last Edited: Wed. Dec 5, 2018 - 05:57 PM