Atmel ice known good Computer and OS

Go To Last Post
21 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

I am hoping to get some known good computer and operating systems configurations listed here for the Atmel ice and studio 7.

I can not for the life of me get the Ice to enter programming mode. The infamous 0xc0 error. I have not entered debug so I know I don't need to "exit" that correctly. This is on fresh windows 7 SP1 and windows 10 installs, all drivers appear correct and the ice did a firmware upgrade the first time I started studio 7 on widows 10.

I have tested with known good boards also an explained 328pb mini and have done continuity testing from the ice PCB to my atmega pins.

I feel the issue may be that I am running Windows under boot camp on a MacBook Pro.

So I am now thinking about picking up a used Thinkpad T510 to test with. Other alternative is to RMA the ice.

What successful setups are you running?

Adam

Last Edited: Sat. Sep 17, 2016 - 05:26 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you for requesting this for you're starting a service to others.

amitchell wrote:
... and operating systems configurations ...
Via 'winver' for the Windows version AND build.

That's enough for Windows 10 due to cumulative updates since its RTM (Windows 10 version 1507).

Windows 7 and 8.1 - it's possible to have a Windows Update set that's a subset of a complete set; cumulative updates for these start 2016-October but will be by security-only or all.

amitchell wrote:
This is on fresh windows 7 SP1 ...
There's a LOT of updates post-SP1; there's a 2016-April cumulative then further updates to now.

One Windows 7 SP1 sequence of install and update consumes several hours.

Very unlikely there will be a Windows 7 SP2.

amitchell wrote:
... and windows 10 installs, ...
If that was Windows 10 version 1607 (Anniversary Update, early Aug 2016) then I wish you luck; it's not in Current Branch for Business (CBB) (that's version 1511).

amitchell wrote:
I feel the issue may be that I am running Windows under boot camp on a MacBook Pro.
fyi, these are the only Windows I could find for Parallels :

https://atlas.hashicorp.com/scorebig/boxes/windows-2012R2-SC

https://atlas.hashicorp.com/daas/boxes/windows-2012R2

https://atlas.hashicorp.com/daas/boxes/windows-2012R2-core

Those are Windows Server 2012 R2 which is in the release notes for Atmel Studio 7.0.1006

amitchell wrote:
So I am now thinking about picking up a used Thinkpad T510 to test with.
fyi, one ThinkPad has a serious defect on Windows 10 version 1607 :

https://www.askwoody.com/2016/whats-been-fixed-and-whats-still-broken-in-windows-10/#comment-98890

There are relatively inexpensive new Windows 10 notebook PC.

For a bit more get Windows 10 Pro for Pro can :

  • be on CBB (a quick configuration)
  • go up to Enterprise via CSP (or your local MSP) which then can go LTSB in addition to CBB

Windows 10 Enterprise is available via CSP (Cloud Solution Provider; min quantity of 1) or VL (Volume Licensing; min quantity of 5); there's a 90 day trial via multiple sources.

Windows 10 Home is only on Current Branch.

If the notebook PC has Windows 10 Home then lock down Windows 10 Home (iow disable automatic updates for "a while").

There's an amazing number of Windows 10 ISO in the wild such that a Windows 10 All In One (AIO) (dimensions : 32b or 64b; home, pro, enterprise, education) is by version AND build; possibly one way to back out a hosed, BSOD, or won't boot Windows 10 Home if the Windows 10 Home install DVD or USB is missing or misplaced or there's no install partition.


https://technet.microsoft.com/en-us/windows/mt679505.aspx (Windows 10 release information)

http://www.parallels.com/

https://www.vagrantup.com/

https://www.askwoody.com/automatic-updates/

 

"Dare to be naïve." - Buckminster Fuller

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Windows 10 Home 1511

AS7 1006

Atmel Ice

Arduino Due Sam3x

connect via JTAG

programming and debug seem to work normally

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

No luck on the Lenovo T510 running windows 10 build 1511 fully updated and oatmeal studio 7 1006. Sending Atmel/Mouser an RMA request. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Don't you love autocorrect!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Oatmel it's a good name as any for Studio. devil

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

jstampfl wrote:

Windows 10 Home 1511

AS7 1006

...

Has the house of cards that Microsoft and Atmel created gone so fragile that it collapses if you do not use certain combinations of versions (with 4 digit version numbers !) ?

Is new owner Microchip putting some pressure on to get rid of this Microsoft dependency (that is costing them business)?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hugo_habicht wrote:

Is new owner Microchip putting some pressure on to get rid of this Microsoft dependency (that is costing them business)?

OH $DEITY... I hope so!

 

Ross McKenzie ValuSoft Melbourne Australia

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Question to people with the ICE does it show up as a COM port in windows device manager? Mine does not.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Anything younger than about 10 years old will not show up as  com port.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

amitchell wrote:

Question to people with the ICE does it show up as a COM port in windows device manager? Mine does not.

No on both Windows7 and Windows 10

 

By chance on these machines do you have Studio 6_2 installed?  If the answer is yes, then you have to manually change the driver the ICE will use.  The Jungo driver for AS7 is different than the one for AS6_2.

 

It's  a pain in the a$$, but I have learned to live with it.

 

https://www.avrfreaks.net/forum/i...

 

JIm

 

EDIT:

Each time you change the driver, you may have to update/downgrade the Firmware in the ICE.  Studio will take care of this.

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user

Last Edited: Tue. Sep 27, 2016 - 03:33 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I was trying the different O/S and studio combinations on both laptops and couldn't get anything to work. Even got a 2nd ice.

I am now sticking with Windows 10 and studio 7.

 

Here is an error log from Studio 7.

 

17:30:45.683: Constructing a new instance of Status Report Service
17:30:45.683:  
17:30:45.683: Providing a new reference to the instance of Status Report Service
17:30:45.695: Entering constructor for: Atmel.VsIde.AvrStudio.Services.BackendService.BackendServicePackage
17:30:45.695: Entering Initialize() of: Atmel.VsIde.AvrStudio.Services.BackendService.BackendServicePackage
17:30:45.725: 17:30:45: [INFO] Starting local Backend Agent atbackend.exe 127.0.0.1:0
17:30:45.734: 17:30:45: [INFO] Process: C:\Program Files (x86)\Atmel\Studio\7.0\atbackend\atbackend.exe /connection-port=64539 
17:30:45.786: Entering constructor for: Atmel.VsIde.AvrStudio.Debugging.DataBreakpoint.DataBreakpointPackage
17:30:45.790: Entering Initialize() of: Atmel.VsIde.AvrStudio.Debugging.DataBreakpoint.DataBreakpointPackage
17:30:45.873: Entering constructor for: Atmel.VsIde.AvrStudio.Debugging.DebugCommands.DebugCommandsPackage
17:30:45.880: Entering constructor for: Atmel.VsIde.AvrStudio.Services.DeviceService.DeviceServicePackage
17:30:45.880: Entering Initialize() of: Atmel.VsIde.AvrStudio.Services.DeviceService.DeviceServicePackage
17:30:45.884: Entering constructor for help about Atmel.VsIde.AvrStudio.Branding.HelpAbout.HelpAboutPackage
17:30:45.885: 17:30:45: [INFO] Initializing help package Atmel.VsIde.AvrStudio.Branding.HelpAbout.HelpAboutPackage
17:30:45.896: Entering constructor for: Atmel.VsIde.AvrStudio.LanguageServices.Packages.ServiceProviderImplementations
17:30:45.897: Entering Initialize() of: Atmel.VsIde.AvrStudio.LanguageServices.Packages.ServiceProviderImplementations
17:30:46.949: Entering constructor for: Atmel.VsIde.AvrStudio.Services.TargetService.TargetManagerPackage
17:30:46.950: Entering Initialize() of: Atmel.VsIde.AvrStudio.Services.TargetService.TargetManagerPackage
17:30:46.993: Entering Initialize() of: Atmel.VsIde.AvrStudio.AsfPackage.AsfPackage
17:30:47.087: Entering constructor for: Atmel.VsIde.AvrStudio.Asf.Service.AsfServicePackage
17:30:47.088: Entering Initialize() of: Atmel.VsIde.AvrStudio.Asf.Service.AsfServicePackage
17:30:47.092: Entering constructor for: Atmel.FDK.FDKPackage
17:30:47.099: Entering Initialize() of: Atmel.FDK.FDKPackage
17:30:47.120: Entering constructor for: Atmel.AtmelKits.AtmelKitsPackage
17:30:47.121: Entering Initialize() of: Atmel.AtmelKits.AtmelKitsPackage
17:30:47.125: Entering constructor for: ToolchainProvider.AvrStudioToolchainExtensionPackage
17:30:47.125: Entering Initialize() of: ToolchainProvider.AvrStudioToolchainExtensionPackage
17:30:47.131: Entering constructor for: Atmel.VsIde.AvrStudio.Extensions.AvrAssembler.AvrAssemblerToolchainPackage
17:30:47.131: Entering Initialize() of: Atmel.VsIde.AvrStudio.Extensions.AvrAssembler.AvrAssemblerToolchainPackage
17:30:54.738: Entering constructor for: Atmel.VsIde.AvrStudio.Services.ToolService.ToolServicePackage
17:30:54.739: Initializing Atmel.VsIde.AvrStudio.Services.ToolService.ToolServicePackage
17:30:54.867: 17:30:54: [INFO] Added ToolInfo: Atmel-ICE
17:30:54.868: 17:30:54: [INFO] Added ToolInfo: AVR Dragon
17:30:54.868: 17:30:54: [INFO] Added ToolInfo: AVRISP mkII
17:30:54.869: 17:30:54: [INFO] Added ToolInfo: AVR ONE!
17:30:54.871: 17:30:54: [INFO] Added ToolInfo: EDBG
17:30:54.873: 17:30:54: [INFO] Added ToolInfo: EDBG MSD
17:30:54.874: 17:30:54: [INFO] Added ToolInfo: EDBG
17:30:54.875: 17:30:54: [INFO] Added ToolInfo: Atmel FLIP
17:30:54.877: 17:30:54: [INFO] Added ToolInfo: J-Link
17:30:54.878: 17:30:54: [INFO] Added ToolInfo: J-Link over IP
17:30:54.879: 17:30:54: [INFO] Added ToolInfo: J-Link ARM-Pro
17:30:54.880: 17:30:54: [INFO] Added ToolInfo: J-Link Ultra
17:30:54.881: 17:30:54: [INFO] Added ToolInfo: JTAGICE3
17:30:54.881: 17:30:54: [INFO] Added ToolInfo: JTAGICE3
17:30:54.881: 17:30:54: [INFO] Added ToolInfo: JTAGICE mkII
17:30:54.885: 17:30:54: [INFO] Added ToolInfo: mEDBG
17:30:54.886: 17:30:54: [INFO] Added ToolInfo: Atmel Mega DFU
17:30:54.887: 17:30:54: [INFO] Added ToolInfo: Power Debugger
17:30:54.888: 17:30:54: [INFO] Added ToolInfo: QT600
17:30:54.888: 17:30:54: [INFO] Added ToolInfo: SAM-ICE
17:30:54.888: 17:30:54: [INFO] Added ToolInfo: Simulator
17:30:54.888: 17:30:54: [INFO] Added ToolInfo: STK500
17:30:54.889: 17:30:54: [INFO] Added ToolInfo: STK600
17:30:55.459: 17:30:55: [INFO] Connecting to backend agent atbackend.exe(pid:6312) 127.0.0.1:64539
17:30:55.554: 17:30:55: [INFO] Connected to backend at 127.0.0.1:64539
17:30:55.944: Tool:getAttachedTools 385.3459 msecs
17:30:55.979: Stream:setLogBits 5.0049 msecs
17:30:55.979: 05 30 55 979: msg send(60):R 1
17:30:55.987: 05 30 55 987: msg recv(60):E Locator peerAdded {"Port":"64539","Host":"127.0.0.1","ID":"LocalHIL0","Name":"Local HIL","OSName":"Windows","TransportName":"TCP"}
17:32:45.974: Entering constructor for: Atmel.VsIde.AvrStudio.Debugging.Programming.ProgrammingPackage
17:32:45.975: Entering Initialize() of: Atmel.VsIde.AvrStudio.Debugging.Programming.ProgrammingPackage
17:32:49.450: 05 32 49 450: msg recv(60):C 2 Tool setupTool "com.atmel.avrdbg.tool.atmelice" "com.atmel.avrdbg.connection.cmsis-dap" {"Type":"com.atmel.avrdbg.connection.cmsis-dap","SerialNumber":"J41800060199","DapProduct":"Atmel-ICE CMSIS-DAP","UsbVendorId":1003,"UsbProductId":8513}
17:32:49.530: Got Tool::contextAdded(< INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"","MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] > ) event, notifying listeners
17:32:49.532: Tool:setupTool 85.078 msecs
17:32:49.698: 05 32 49 527: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\48e1-b52e-ca71-fbfe
17:32:49.707: Tool:getContext 12.0123 msecs
17:32:49.712: 05 32 49 528: archive Parsing firmware manifest
17:32:49.715: 05 32 49 528: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\48e1-b52e-ca71-fbfe
17:32:49.717: 05 32 49 529: msg send(60):E Tool contextAdded < INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"","MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] >
17:32:49.721: 05 32 49 529: msg send(60):R 2  "AT_1"
17:32:49.724: 05 32 49 695: msg recv(60):C 3 Tool getContext "AT_1"
17:32:49.728: 05 32 49 705: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\dd26-9718-0e03-3e08
17:32:49.733: 05 32 49 705: archive Parsing firmware manifest
17:32:49.737: 05 32 49 705: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\dd26-9718-0e03-3e08
17:32:49.742: 05 32 49 706: msg send(60):R 3  {"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"","MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}
17:32:49.746: 05 32 49 709: msg recv(60):C 4 Tool connect "AT_1"
17:32:49.750: 05 32 49 714: pro Mk3HouseKeepingProtocol::startSession()
17:32:49.754: 05 32 49 714: pro JtagIce3 <<< 10 00
17:32:49.759: 05 32 49 714: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=2 msg=00 FF 
17:32:49.764: 05 32 49 715: dap DAP_Commands replySize0=512 msg=00 02 00 02 6D ...
17:32:49.768: 05 32 49 715: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.772: 05 32 49 715: dap DAP_Commands replySize0=512 msg=81 00 00 02 6D ...
17:32:49.777: 05 32 49 715: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=11 msg=80 11 00 07 0E 00 00 00 01 10 00 
17:32:49.781: 05 32 49 716: dap DAP_Commands replySize0=512 msg=80 01 00 02 6D ...
17:32:49.783: Tool:connect 75.0777 msecs
17:32:49.786: 05 32 49 716: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.788: 05 32 49 717: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:49.789: 05 32 49 717: pro JtagIce3 >>> 80 00
17:32:49.790: 05 32 49 717: prg Event listener object is destroyed while listener thread is running
17:32:49.792: 05 32 49 717: pro Mk3Protocol::get()
17:32:49.793: 05 32 49 717: pro JtagIce3 <<< 02 00 00 00 01
17:32:49.795: 05 32 49 717: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 01 00 01 02 00 00 00 01 
17:32:49.796: 05 32 49 717: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:49.797: Tool:checkFirmware 12.0111 msecs
17:32:49.799: 05 32 49 718: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.837: 05 32 49 719: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:49.839: 05 32 49 719: pro JtagIce3 >>> 84 01 00 00
17:32:49.842: 05 32 49 719: pro Mk3Protocol::get()
17:32:49.847: 05 32 49 719: pro JtagIce3 <<< 02 00 00 01 01
17:32:49.851: 05 32 49 719: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 02 00 01 02 00 00 01 01 
17:32:49.855: 05 32 49 719: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:49.860: 05 32 49 719: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.861: 05 32 49 720: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:49.863: 05 32 49 720: pro JtagIce3 >>> 84 01 01 00
17:32:49.864: 05 32 49 720: pro Mk3Protocol::get()
17:32:49.866: 05 32 49 720: pro JtagIce3 <<< 02 00 00 02 01
17:32:49.867: 05 32 49 720: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 03 00 01 02 00 00 02 01 
17:32:49.868: 05 32 49 720: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:49.870: 05 32 49 721: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.871: 05 32 49 721: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:49.872: 05 32 49 721: pro JtagIce3 >>> 84 01 21 00
17:32:49.873: 05 32 49 721: pro Mk3Protocol::get()
17:32:49.875: 05 32 49 721: pro JtagIce3 <<< 02 00 00 03 02
17:32:49.876: 05 32 49 721: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 04 00 01 02 00 00 03 02 
17:32:49.877: 05 32 49 722: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:49.878: 05 32 49 722: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.880: 05 32 49 722: dap DAP_Commands replySize0=512 msg=81 11 00 09 0E ...
17:32:49.881: 05 32 49 722: pro JtagIce3 >>> 84 01 76 00 00
17:32:49.882: 05 32 49 722: pro Mk3Protocol::get()
17:32:49.884: 05 32 49 722: pro JtagIce3 <<< 02 00 00 05 01
17:32:49.885: 05 32 49 722: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 05 00 01 02 00 00 05 01 
17:32:49.886: 05 32 49 723: dap DAP_Commands replySize0=512 msg=80 01 00 09 0E ...
17:32:49.887: 05 32 49 723: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.889: 05 32 49 724: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:49.890: 05 32 49 724: pro JtagIce3 >>> 84 01 01 00
17:32:49.892: 05 32 49 724: pro Mk3Protocol::get()
17:32:49.893: 05 32 49 724: pro JtagIce3 <<< 02 00 00 09 01
17:32:49.894: 05 32 49 724: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 06 00 01 02 00 00 09 01 
17:32:49.896: 05 32 49 724: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:49.897: 05 32 49 724: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.898: 05 32 49 725: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:49.900: 05 32 49 725: pro JtagIce3 >>> 84 01 00 11
17:32:49.901: 05 32 49 725: pro Trailing status (0x11) received from the debugger: 'The requested command is not supported.'.
17:32:49.903: 05 32 49 728: pro Failed reading HOUSEKEEPING_CONFIG_FIRMWARE_IMAGE, this is a single-firmware board, continue
17:32:49.904: 05 32 49 728: pro Mk3DiscoveryProtocol::query()
17:32:49.905: 05 32 49 728: pro Mk3Protocol::query()
17:32:49.907: 05 32 49 728: pro JtagIce3 <<< 00 00 00
17:32:49.908: 05 32 49 728: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 07 00 00 00 00 00 
17:32:49.909: 05 32 49 729: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:49.911: 05 32 49 729: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.912: 05 32 49 730: dap DAP_Commands replySize0=512 msg=81 11 00 0C 0E ...
17:32:49.913: 05 32 49 730: pro JtagIce3 >>> 81 00 00 01 11 12 13 14
17:32:49.915: 05 32 49 730: pro Mk3Protocol::query()
17:32:49.916: 05 32 49 730: pro JtagIce3 <<< 00 00 02
17:32:49.918: 05 32 49 730: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 08 00 01 00 00 02 
17:32:49.919: 05 32 49 731: dap DAP_Commands replySize0=512 msg=80 01 00 0C 0E ...
17:32:49.920: 05 32 49 731: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.922: 05 32 49 731: dap DAP_Commands replySize0=512 msg=81 11 00 07 0E ...
17:32:49.923: 05 32 49 781: pro JtagIce3 >>> 81 00 00
17:32:49.925: 05 32 49 781: pro Mk3Protocol::query()
17:32:49.926: 05 32 49 781: pro JtagIce3 <<< 00 00 02
17:32:49.927: 05 32 49 782: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 09 00 01 00 00 02 
17:32:49.929: 05 32 49 782: dap DAP_Commands replySize0=512 msg=80 01 00 07 0E ...
17:32:49.930: 05 32 49 782: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.931: 05 32 49 783: dap DAP_Commands replySize0=512 msg=81 11 00 07 0E ...
17:32:49.933: 05 32 49 783: pro JtagIce3 >>> 81 00 00
17:32:49.934: 05 32 49 783: msg send(60):R 4
17:32:49.935: 05 32 49 786: msg recv(60):C 5 Tool checkFirmware "AT_1"
17:32:49.936: 05 32 49 795: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\28e7-1fc0-95c3-3112
17:32:49.938: 05 32 49 795: archive Parsing firmware manifest
17:32:49.939: 05 32 49 795: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\28e7-1fc0-95c3-3112
17:32:49.940: 05 32 49 796: msg send(60):R 5
17:32:49.942: 05 32 49 839: msg recv(60):C 6 Tool setProperties "AT_1" {"InterfaceProperties":{"IspClock":125000},"InterfaceName":"ISP","DeviceName":"ATmega328PB","PackPath":"C:/Program Files (x86)/Atmel/Studio/7.0/Packs/atmel/ATmega_DFP/1.0.106/Atmel.ATmega_DFP.pdsc"}
17:32:49.943: 05 32 49 931: tcf Using device file C:/Program Files (x86)\Atmel\Studio\7.0\Packs\atmel\ATmega_DFP\1.0.106\atdf\ATmega328PB.atdf
17:32:49.944: 05 32 49 931: dbg AvrToolsDeviceFileReader::parseFiles(ATmega328PB) - start processing xml file
17:32:49.946: 05 32 49 941: dbg AvrToolsDeviceFileReader::parseFiles(ATmega328PB) - done
17:32:49.948: 05 32 49 941: dbg Using flash page size 128.
17:32:49.949: 05 32 49 941: msg send(60):E Device contextAdded [{"ID":"Dev_1","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}]
17:32:49.950: 05 32 49 941: pro JtagIce3 <<< 1D 7D 00
17:32:49.952: 05 32 49 942: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 0A 00 11 1D 7D 00 
17:32:49.953: 05 32 49 942: dap DAP_Commands replySize0=512 msg=80 01 00 07 0E ...
17:32:49.955: 05 32 49 942: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.955: Got Tool::contextChanged(< INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_1","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] > ) event, notifying listeners
17:32:49.955: Tool:setProperties 119.1081 msecs
17:32:49.956: 05 32 49 943: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:49.958: 05 32 49 943: pro JtagIce3 >>> 1D 00
17:32:49.959: 05 32 49 943: pro JtagIce3 <<< 1E
17:32:49.961: 05 32 49 943: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 0B 00 11 1E 
17:32:49.962: 05 32 49 943: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:49.963: 05 32 49 943: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.965: 05 32 49 944: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:49.966: 05 32 49 944: pro JtagIce3 >>> 1E 7D 00 00
17:32:49.968: 05 32 49 953: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\1368-4116-ef7d-822c
17:32:49.968: Tool:getContext 13.0128 msecs
17:32:49.970: Device:getContext 1.0013 msecs
17:32:49.977: 05 32 49 953: archive Parsing firmware manifest
17:32:49.979: 05 32 49 953: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\1368-4116-ef7d-822c
17:32:49.980: 05 32 49 954: msg send(60):E Tool contextChanged < INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_1","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] >
17:32:49.982: 05 32 49 954: msg send(60):R 6
17:32:49.983: 05 32 49 956: msg recv(60):C 7 Tool getContext "AT_1"
17:32:49.984: 05 32 49 956: pro JtagIce3 <<< 1E
17:32:49.986: 05 32 49 956: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 0C 00 11 1E 
17:32:49.987: 05 32 49 957: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:49.989: 05 32 49 957: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.989: Tool:getContext 13.0117 msecs
17:32:49.990: Device:getContext 1.0009 msecs
17:32:50.191: 05 32 49 957: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:50.207: 05 32 49 957: pro JtagIce3 >>> 1E 7D 00 00
17:32:50.212: 05 32 49 966: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\1ec9-7157-f1d3-1c16
17:32:50.216: 05 32 49 966: archive Parsing firmware manifest
17:32:50.220: 05 32 49 967: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\1ec9-7157-f1d3-1c16
17:32:50.225: 05 32 49 968: msg send(60):R 7  {"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_1","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}
17:32:50.229: 05 32 49 969: msg recv(60):C 8 Device getContext "Dev_1"
17:32:50.233: 05 32 49 969: msg send(60):R 8  {"ID":"Dev_1","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}
17:32:50.238: 05 32 49 977: msg recv(60):C 9 Tool getContext "AT_1"
17:32:50.243: 05 32 49 977: pro JtagIce3 <<< 1E
17:32:50.248: 05 32 49 977: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 0D 00 11 1E 
17:32:50.252: 05 32 49 978: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:50.257: 05 32 49 978: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:50.262: 05 32 49 979: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:50.266: 05 32 49 979: pro JtagIce3 >>> 1E 7D 00 00
17:32:50.270: 05 32 49 987: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\68ed-7afc-caf0-0437
17:32:50.275: 05 32 49 987: archive Parsing firmware manifest
17:32:50.279: 05 32 49 988: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\68ed-7afc-caf0-0437
17:32:50.283: 05 32 49 989: msg send(60):R 9  {"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_1","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}
17:32:50.287: 05 32 49 990: msg recv(60):C 10 Device getContext "Dev_1"
17:32:50.290: 05 32 49 990: msg send(60):R 10  {"ID":"Dev_1","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}
17:32:50.945: 05 32 50 944: msg recv(60):C 11 Tool setProperties "AT_1" {"InterfaceProperties":{"IspClock":125000},"InterfaceName":"ISP","DeviceName":"ATmega328PB","PackPath":"C:/Program Files (x86)/Atmel/Studio/7.0/Packs/atmel/ATmega_DFP/1.0.106/Atmel.ATmega_DFP.pdsc"}
17:32:50.947: 05 32 50 945: msg send(60):E Device contextRemoved ["Dev_1"]
17:32:50.949: 05 32 50 945: dbg Using flash page size 128.
17:32:50.951: 05 32 50 945: msg send(60):E Device contextAdded [{"ID":"Dev_2","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}]
17:32:50.953: 05 32 50 945: pro JtagIce3 <<< 1D 7D 00
17:32:50.954: 05 32 50 946: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 0E 00 11 1D 7D 00 
17:32:50.956: 05 32 50 946: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:50.957: 05 32 50 946: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:50.959: 05 32 50 947: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:50.961: 05 32 50 947: pro JtagIce3 >>> 1D 00
17:32:50.961: Got Tool::contextChanged(< INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_2","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] > ) event, notifying listeners
17:32:50.961: Tool:setProperties 19.0186 msecs
17:32:50.962: 05 32 50 947: pro JtagIce3 <<< 1E
17:32:50.964: 05 32 50 947: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 0F 00 11 1E 
17:32:50.966: 05 32 50 947: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:50.968: 05 32 50 947: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:50.969: 05 32 50 948: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:50.971: 05 32 50 948: pro JtagIce3 >>> 1E 7D 00 00
17:32:50.973: 05 32 50 959: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\7e99-6a2e-bd2b-ae8d
17:32:50.974: 05 32 50 959: archive Parsing firmware manifest
17:32:50.976: Tool:getContext 13.9957 msecs
17:32:50.976: 05 32 50 959: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\7e99-6a2e-bd2b-ae8d
17:32:50.986: Device:getContext 10.0093 msecs
17:32:50.994: Tool:getTargetVoltage 3.0046 msecs
17:32:51.008: 05 32 50 961: msg send(60):E Tool contextChanged < INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_2","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] >
17:32:51.010: 05 32 50 961: msg send(60):R 11
17:32:51.011: 05 32 50 962: msg recv(60):C 12 Tool getContext "AT_1"
17:32:51.013: 05 32 50 962: pro JtagIce3 <<< 1E
17:32:51.018: 05 32 50 963: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 10 00 11 1E 
17:32:51.020: 05 32 50 963: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:51.025: 05 32 50 963: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.029: 05 32 50 964: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:51.033: 05 32 50 964: pro JtagIce3 >>> 1E 7D 00 00
17:32:51.037: 05 32 50 974: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\60fc-f39a-515e-b675
17:32:51.042: 05 32 50 974: archive Parsing firmware manifest
17:32:51.046: 05 32 50 974: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\60fc-f39a-515e-b675
17:32:51.051: 05 32 50 975: msg send(60):R 12  {"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_2","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}
17:32:51.054: 05 32 50 986: msg recv(60):C 13 Device getContext "Dev_2"
17:32:51.059: 05 32 50 986: msg send(60):R 13  {"ID":"Dev_2","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}
17:32:51.063: 05 32 50 992: msg recv(60):C 14 Tool getTargetVoltage "AT_1"
17:32:51.068: 05 32 50 992: pro Mk3Protocol::get()
17:32:51.072: 05 32 50 992: pro JtagIce3 <<< 02 00 01 00 02
17:32:51.076: 05 32 50 992: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 11 00 01 02 00 01 00 02 
17:32:51.080: 05 32 50 993: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:51.085: 05 32 50 993: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.088: 05 32 50 993: dap DAP_Commands replySize0=512 msg=81 11 00 09 0E ...
17:32:51.092: 05 32 50 993: pro JtagIce3 >>> 84 01 70 13 00
17:32:51.096: 05 32 50 993: msg send(60):R 14  4.9760000000000000
17:32:51.809: 05 32 51 809: msg recv(60):C 15 Tool setProperties "AT_1" {"InterfaceProperties":{"IspClock":125000},"InterfaceName":"ISP","DeviceName":"ATmega328PB","PackPath":"C:/Program Files (x86)/Atmel/Studio/7.0/Packs/atmel/ATmega_DFP/1.0.106/Atmel.ATmega_DFP.pdsc"}
17:32:51.812: 05 32 51 809: msg send(60):E Device contextRemoved ["Dev_2"]
17:32:51.814: 05 32 51 809: dbg Using flash page size 128.
17:32:51.816: 05 32 51 809: msg send(60):E Device contextAdded [{"ID":"Dev_3","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}]
17:32:51.817: 05 32 51 809: pro JtagIce3 <<< 1D 7D 00
17:32:51.819: 05 32 51 809: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 12 00 11 1D 7D 00 
17:32:51.820: 05 32 51 810: dap DAP_Commands replySize0=512 msg=80 01 00 09 0E ...
17:32:51.822: 05 32 51 810: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.824: 05 32 51 811: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:51.824: Got Tool::contextChanged(< INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_3","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] > ) event, notifying listeners
17:32:51.824: Tool:setProperties 18.9894 msecs
17:32:51.826: 05 32 51 811: pro JtagIce3 >>> 1D 00
17:32:51.828: 05 32 51 811: pro JtagIce3 <<< 1E
17:32:51.829: 05 32 51 811: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 13 00 11 1E 
17:32:51.831: 05 32 51 812: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:51.832: 05 32 51 812: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.833: 05 32 51 812: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:51.835: 05 32 51 812: pro JtagIce3 >>> 1E 7D 00 00
17:32:51.837: 05 32 51 822: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\ba49-1aa9-0a59-e5c3
17:32:51.838: Tool:getContext 14.0126 msecs
17:32:51.839: 05 32 51 822: archive Parsing firmware manifest
17:32:51.839: Device:getContext 1.0001 msecs
17:32:51.842: 05 32 51 822: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\ba49-1aa9-0a59-e5c3
17:32:51.845: 05 32 51 824: msg send(60):E Tool contextChanged < INVALID TOKEN [{"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_3","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}] >
17:32:51.849: 05 32 51 824: msg send(60):R 15
17:32:51.854: 05 32 51 825: msg recv(60):C 16 Tool getContext "AT_1"
17:32:51.858: 05 32 51 825: pro JtagIce3 <<< 1E
17:32:51.862: 05 32 51 825: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 14 00 11 1E 
17:32:51.867: 05 32 51 826: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:51.871: 05 32 51 826: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.876: 05 32 51 826: dap DAP_Commands replySize0=512 msg=81 11 00 08 0E ...
17:32:51.878: 05 32 51 826: pro JtagIce3 >>> 1E 7D 00 00
17:32:51.883: 05 32 51 836: archive Temporary firmware directory: C:\Users\Family\AppData\Local\Temp\35e5-eb95-34a1-27c4
17:32:51.887: 05 32 51 836: archive Parsing firmware manifest
17:32:51.892: 05 32 51 836: archive Deleting directory: C:\Users\Family\AppData\Local\Temp\35e5-eb95-34a1-27c4
17:32:51.896: 05 32 51 837: msg send(60):R 16  {"ID":"AT_1","Name":"com.atmel.avrdbg.tool.atmelice","DeviceId":"Dev_3","InterfaceName":"ISP","InterfaceProperties":{"IspClock":125000},"HardwareRevision":0,"MajorFirmwareVersion":1,"MinorFirmwareVersion":33,"FirmwareBuildNumber":118,"Chipset":1,"CanDo12VUpdiActivation":false,"MajorFirmwareVersionOnDisk":1,"MinorFirmwareVersionOnDisk":33,"CanEraseXmegaPages":1}
17:32:51.901: 05 32 51 839: msg recv(60):C 17 Device getContext "Dev_3"
17:32:51.905: 05 32 51 839: msg send(60):R 17  {"ID":"Dev_3","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}
17:32:51.909: 05 32 51 841: msg recv(60):C 18 Device startSession "Dev_3" "ProgrammingSession"
17:32:51.914: 05 32 51 841: pro JtagIce3IspInterface::activate()
17:32:51.919: 05 32 51 841: pro Mk3Protocol::set()
17:32:51.923: 05 32 51 841: pro JtagIce3 <<< 01 00 00 00 01 01
17:32:51.928: 05 32 51 841: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=15 msg=80 11 00 0B 0E 00 15 00 12 01 00 00 00 01 01 
17:32:51.932: 05 32 51 842: dap DAP_Commands replySize0=512 msg=80 01 00 08 0E ...
17:32:51.937: 05 32 51 842: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.941: 05 32 51 842: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:51.945: 05 32 51 842: pro JtagIce3 >>> 80 00
17:32:51.950: 05 32 51 842: pro Mk3Protocol::set()
17:32:51.954: 05 32 51 842: pro JtagIce3 <<< 01 00 00 01 01 01
17:32:51.957: 05 32 51 842: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=15 msg=80 11 00 0B 0E 00 16 00 12 01 00 00 01 01 01 
17:32:51.960: 05 32 51 843: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:51.965: 05 32 51 843: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.969: 05 32 51 844: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:51.972: 05 32 51 844: pro JtagIce3 >>> 80 00
17:32:51.976: 05 32 51 844: pro Mk3Protocol::set()
17:32:51.981: 05 32 51 844: pro JtagIce3 <<< 01 00 01 00 01 01
17:32:51.985: 05 32 51 844: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=15 msg=80 11 00 0B 0E 00 17 00 12 01 00 01 00 01 01 
17:32:51.990: 05 32 51 844: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:51.995: 05 32 51 844: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:51.999: 05 32 51 845: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:52.004: 05 32 51 845: pro JtagIce3 >>> 80 00
17:32:52.008: 05 32 51 845: pro JtagIce3 <<< 10 C8 64 19 20 00 53 03 AC 53 00 00
17:32:52.012: 05 32 51 845: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=21 msg=80 11 00 11 0E 00 18 00 11 10 C8 64 19 20 00 53 03 AC 53 00 00 
17:32:52.017: 05 32 51 846: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:52.022: 05 32 51 846: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:52.398: 05 32 52 398: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:52.403: 05 32 52 398: pro JtagIce3 >>> 10 C0
17:32:52.405: Device:startSession 564.5099 msecs
17:32:52.407: 17:32:52: [ERROR] Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool), ModuleName: TCF (TCF command: Device:startSession failed.)
17:32:52.418: 05 32 52 398: pro JtagIce3 <<< 0D
17:32:52.418: Device:getContext 1.9868 msecs
17:32:52.419: 17:32:52: [ERROR] Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool), ModuleName: TCF (TCF command: Device:startSession failed.)
17:32:52.424: 05 32 52 399: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=10 msg=80 11 00 06 0E 00 19 00 11 0D 
17:32:52.434: Tool:getTargetVoltage 12.9505 msecs
17:32:52.450: 17:32:52: [INFO] Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool)

Unable to enter programming mode. Verify device selection, interface settings, target power, security bit, and connections to the target device.
17:32:52.523: 05 32 52 399: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:52.526: 05 32 52 399: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:52.530: 05 32 52 400: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:52.535: 05 32 52 400: pro JtagIce3 >>> 0D C9
17:32:52.539: 05 32 52 400: pro JtagIce3 <<< 03 A1
17:32:52.543: 05 32 52 400: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=11 msg=80 11 00 07 0E 00 1A 00 11 03 A1 
17:32:52.548: 05 32 52 401: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:52.552: 05 32 52 401: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:52.556: 05 32 52 401: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:52.560: 05 32 52 402: pro JtagIce3 >>> 03 C9
17:32:52.562: 05 32 52 402: pro JtagIce3 <<< 11 01 01
17:32:52.566: 05 32 52 402: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 1B 00 11 11 01 01 
17:32:52.570: 05 32 52 402: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:52.574: 05 32 52 402: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:52.578: 05 32 52 403: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:52.582: 05 32 52 403: pro JtagIce3 >>> 11 00
17:32:52.586: 05 32 52 403: pro JtagIce3IspInterface::deactivate()
17:32:52.590: 05 32 52 403: msg send(60):R 18 {"Code":1,"Time":0,"Format":"Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool)","Severity":4,"AltOrg":"Atmel"} {}
17:32:52.594: 05 32 52 418: msg recv(60):C 19 Device getContext "Dev_3"
17:32:52.597: 05 32 52 418: msg send(60):R 19  {"ID":"Dev_3","Name":"ATmega328PB","Session":0,"MemoryIDs":[]}
17:32:52.601: 05 32 52 422: msg recv(60):C 20 Tool getTargetVoltage "AT_1"
17:32:52.605: 05 32 52 422: pro Mk3Protocol::get()
17:32:52.609: 05 32 52 422: pro JtagIce3 <<< 02 00 01 00 02
17:32:52.612: 05 32 52 423: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=14 msg=80 11 00 0A 0E 00 1C 00 01 02 00 01 00 02 
17:32:52.617: 05 32 52 423: dap DAP_Commands replySize0=512 msg=80 01 00 06 0E ...
17:32:52.621: 05 32 52 423: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:52.625: 05 32 52 424: dap DAP_Commands replySize0=512 msg=81 11 00 09 0E ...
17:32:52.628: 05 32 52 424: pro JtagIce3 >>> 84 01 73 13 00
17:32:52.632: 05 32 52 424: msg send(60):R 20  4.9790000000000001
17:32:57.683: 05 32 57 683: msg recv(60):C 21 Tool tearDownTool "AT_1"
17:32:57.705: 05 32 57 705: pro Mk3HouseKeepingProtocol::endSession()
17:32:57.709: 05 32 57 705: pro JtagIce3 <<< 11 00 00
17:32:57.709: Tool:tearDownTool 26.9692 msecs
17:32:57.728: 05 32 57 705: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=12 msg=80 11 00 08 0E 00 1D 00 01 11 00 00 
17:32:57.733: 05 32 57 706: dap DAP_Commands replySize0=512 msg=80 01 00 09 0E ...
17:32:57.738: 05 32 57 706: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:57.742: 05 32 57 707: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:57.746: 05 32 57 707: pro JtagIce3 >>> 80 00
17:32:57.750: 05 32 57 708: msg send(60):E Device contextRemoved ["Dev_3"]
17:32:57.754: 05 32 57 708: msg send(60):R 21

 

Last Edited: Tue. Sep 27, 2016 - 03:56 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This section of Atmel's documentation looks interesting:

 

http://www.atmel.com/webdoc/prot...

 

In particular this bit:

 

http://www.atmel.com/webdoc/prot...

 

YOu can see some of those commands in, for example:

17:32:49.768: 05 32 49 715: dap rddi_CMSIS_DAP_Commands nCmds=1 cmdSize0=1 msg=81 
17:32:49.772: 05 32 49 715: dap DAP_Commands replySize0=512 msg=81 00 00 02 6D ...

The table tells us 0x81 is and AVR Protocol response. What isn't clear is what the protocol is - I guess it means "JTAGICE3" protocol. The curious thing is that earlier in the conversation you see things like:

17:32:51.969: 05 32 51 844: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:51.972: 05 32 51 844: pro JtagIce3 >>> 80 00

which appears to be an "OK" response. But at the point of failure this happens:

17:32:52.398: 05 32 52 398: dap DAP_Commands replySize0=512 msg=81 11 00 06 0E ...
17:32:52.403: 05 32 52 398: pro JtagIce3 >>> 10 C0

I guess the key is in the "..." after the 06 0E there? Wonder what changed in the command that got the non-OK response?

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

interesting I did send that log to Morten via PM hoping he can shed some light.

I did get a successful device read and program with an attiny84a board.

However I still am unable to find success with the atmega328pb. I have an atmega328pb explained mini board that I added an isp header too and the ice cannot read that device ID either...

Maybe an issue with the newer 328pb?

Last Edited: Wed. Sep 28, 2016 - 06:13 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Update:

I have soldered connections directly from the ice to the chip using SPI channel 0 pins. Success!

My PCB connectors are wired through SPI channel 1 pins. Now to test directly soldering the connections from the ICE to SPI channel 1.

Kind of begs the question can we in serial program using SPI channel 1?

Last Edited: Thu. Sep 29, 2016 - 02:22 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Kind of begs the question can we in serial program using SPI channel 1?

What does the datasheet for your chip say?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Datasheet for the most part just says two SPI channels.

 

However

 

According to the 328PB Datasheet section 33.9.1 

 

Serial Programming Pin Mapping
Table 33-14 Pin Mapping Serial Programming
Symbol Pins I/O Description
MOSI PB3 I Serial Data in
MISO PB4 O Serial Data out
SCK PB5 I Serial Clock
Note:  The pin mapping for SPI programming is listed. Not all parts use the SPI pins dedicated for the
internal SPI interface.

 

Those pins correspond to SPI Channel 0... which I am currently using as Capacitive touch channels because that layout was really sweet. 

I hope I just didn't blow a few hundred bucks for that... no 

 

Trap for young players, I.e. me.

 

 

I officially feel like a tool, and I am contemplating not telling my wife that this has happened. 

Last Edited: Thu. Sep 29, 2016 - 03:21 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I hope I just didn't blow a few hundred bucks for that...

Sorry but you did, should have read the data sheet earlier. wink All AVR datasheets shows you the pins reserved for programming. You can of course use them for other things if you follow some precaution which are also shown on the datasheet.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Reporting good:

 

Windows 10 Pro (Version 1607)

Atmel Studio 7.0.1188

 

My computer is not a name brand computer. Primary components:

* Motherboard: Gigabyte GA-Z97M-D3H

* Processor: Intel Xeon E3-1231v3 (overclocked, @ 3.51GHz)

* Graphics card: AMD R9 380

* There are a few USB Hubs between computer and Atmel ICE.

 

Devices:

* JTAG to ATSAM3X8E (Arduino Due,) ATmega32, ATmega32U4 (Arduino Leonardo,) ATmega162, ATmega2560 (Arduino Mega 2560)

* debugWIRE to ATmega328P (Arduino Uno)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Known good from me.

Atmel Studio 7.0.1188

Windows 10 Pro build 1607

Running on my late 2012 retina MacBook Pro under Bootcamp.

Atmel ICE and atmega328PB hooked up correctly!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Known to work for me.
Win10 Pro, whatever is the current build all at the date of this post.
AS7 newest build(and all older builds)

Custom build pc:
I7-4770k
Gigabyte z87-D3H(old)/asus maximus vii hero(new).
16gb Ram

Atmel Ice and the older blue(mk2(?)) Programming tool in use.

Last Edited: Wed. Oct 5, 2016 - 08:27 AM