Atmel ICE won't debug with AS 6.2

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

That's probably expected but I wanted to mention it.  In case there is some magic I can use to make it work.

 

It may do the Device Programming, but it makes a real mess in the chip when I use it for debugging.  It gets the chip so screwed up, it won't work right until I reflash it.

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

I use the Atmel ICE with 6_2 all the time with no problems.  Doing so right now. What is happening in your debug session?

 

Jim

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

Please Read: Code-of-Conduct

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

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

Hi steve. Does it look like my issue http://www.avrfreaks.net/forum/s...???

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

Thanks for the responses.   Do you use Windows 10 or Windows 7.  I see problems with both, but they may be different.

 

@nvl1109 No, I haven't seen that.

 

First of all, I don't believe Studio ever wanted to update the firmware.   Is that normal?

 

I just took a look with AS Device Programming.  It says Firmware Version 1.16, Hardware Version 0.

 

Version 0.  Maybe this explains why they were selling them for $80 to clueless suckers.   Apparently they aren't smart enough to employ the old trick of calling the first ones version 3.  wink

 

One of the things I noticed when I was using Win7, and maybe Win10, was that breakpoints would get stuck.  The software would continue to stop at the same spot even when I got rid of the breakpoint.

 

 

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

steve17 wrote:
Thanks for the responses. Do you use Windows 10 or Windows 7. I see problems with both, but they may be different.

 

I am using both.  Predominantly Win7PRO/64.

 

IF you have a copy of AS7 on a machine can you connect to that and see if it will update?  If it does, then after the update connect it to AS6_2 and see if it does it again.  If it does then try debugging.

 

JIm

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

Please Read: Code-of-Conduct

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

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

jgmdesign wrote:

IF you have a copy of AS7 on a machine can you connect to that and see if it will update?  If it does, then after the update connect it to AS6_2 and see if it does it again.  If it does then try debugging.

JIm

Yeah, I could do that and it would probably work.  I need to use 6_2 though until AS7 gets fixed, and if this thing gets stuck updating or downdating,  I'd be worse off.  There may be a button I can push to force an update attempt but I don't know where to look.

 

Maybe someone using 6.2 could see what they have.  It's Tools > Device Programming > Apply > Tool information.

 

 

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

Here is what I have:

 

Studio 6_2 About screen:

 

 

Jim

 

This ICE works on both my 6_2 and AS7 suites without any issue....just change firmware as needed.

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

Please Read: Code-of-Conduct

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

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

I've done some testing today.  I see at least one problem when running on Win7, but so far it is not a show stopper.  I get a phantom breakpoint.  I set 3 breakpoints I'll call a b and c.  They worked.  I removed all three and that worked too.  No more breakpoints.  Then I re-added  breakpoint b and that causes the program to stop where breakpoint a had been set.  If I remove breakpoint b, that removes the now phantom breakpoint a.

 

Things were much worse when using Windows 10.  I saw the same inexplicable things I saw yesterday.  I'm serious when I say I can't explain what I see without resorting to the supernatural.  When the chip goes wacky, breakpoints no longer work so all I can do is speculate what the heck is happening.  The chip still works in some ways and in other ways does things that are too bizarre for words.

 

 

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

Show a screenshot of where you put the breakpoints and what the screen looks like when it eats itself.

 

Jim

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

Please Read: Code-of-Conduct

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

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

Thanks for the info Jim.  I didn't see your post while I was working on my previous post. 

 

I see you have a later firmware than I have.  I guess I'll do the AS7 and then AS6 trick.

 

My Studio on this Win7 machine is older than yours (SP1).  I do have SP2 laying around here and I think that's what I'm running on my Win10 installation.

 

I'll try updating stuff tomorrow.

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

jgmdesign wrote:

Show a screenshot of where you put the breakpoints and what the screen looks like when it eats itself.

 

Jim

I can certainly do that if you want to see strange things.  wink  But would it make sense to upgrade the firmware first?

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

I would try updating your version of AS6_2 to make sure it's the latest, then try upgrading the ICE.  If that does not work, then you could try shifting gears between AS7 and AS6 but I only mention that trick just to see that the ICE takes an update in both directions.  If there is indeed something wrong with the ICE it should fail the upgrade...risky I admit, but at this point it may be worth the risk.

 

Just my opinion, YMMV

 

Jim

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

Please Read: Code-of-Conduct

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

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

jgmdesign wrote:

I would try updating your version of AS6_2 to make sure it's the latest, then try upgrading the ICE. 

I will do that, but I don't think that is the answer.  I'm now on Win10 and my AS6.2 here is the latest, just like yours.  It's on Win10 that my Xmega becomes possessed by demons.  I'm pinning my hopes on getting the firmware upgrade.

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

I updated 6.2 to SP2 on Win7 so it is like yours.  6.2 on Win10 was already SP2.

 

I plugged the ICE into AS7, which happens to be on a Win10 installation.  The firmware update went smoothly to version 1.26.

 

Then I plugged it into 6.2 SP2 and the firmware never downdated.  It's still 1.26.  It seems to be working the same or better than it did before the update.

 

It seems to work okay on Win7.  I think I can explain the phantom breakpoint. It's a minor but confusing glitch in the debugger which can easily be overcome.  I set a breakpoint in a function call.  The function being called was in another source file.  I placed a breakpoint at the beginning of the function.  They showed up as 2 breakpoints.  Each was shown in the breakpoint window.  I guess deep down in the hardware there was only one breakpoint but it was seen as 2.   When I removed both breakpoints, the code still stopped where the first one had been.  I fixed it by putting a breakpoint there and removing it. 

 

So the bottom line is, the Atmel Ice seems to be working okay on Win7.   Win10 is another story.  Using it on Win10 still causes my Xmega to be possessed by demons.  I'll try to tell you about the unexplainable bizarre behavior in another post.

 

 

 

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

Well thats a bit of good news!  Good to read it's working.

 

Jim

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

Please Read: Code-of-Conduct

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

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

steve17 wrote:
... and if this thing gets stuck updating or downdating,  I'd be worse off.  There may be a button I can push to force an update attempt but I don't know where to look.
No button that I can recall; maybe atfw.exe will power cycle the Atmel-ICE.

In Windows 10 there's a way to power cycle a USB hub; for Windows 7 maybe it's DevCon.

 


Atmel Studio

Firmware Upgrade

http://www.atmel.com/webdoc/GUID-ECD8A826-B1DA-44FC-BE0B-5A53418A47BD/index.html?GUID-4E9E3579-4F39-414D-A20A-BCD92AACF964

(atfw.exe in Manual Upgrade)

Microsoft

Microsoft

MSDN

IOCTL_USB_HUB_CYCLE_PORT control code

https://msdn.microsoft.com/en-us/library/windows/hardware/ff537340(v=vs.85).aspx

https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/devcon-restart

 

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

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

Thanks for the help guys.  It looks like everything is working okay now on Win7 and Win10.