AS6 windows7 problems

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

I'm getting this error on AS6 and win7:

[ERROR] Unexpected JTAG ID 0x0960b03f (expected 0x0960d03f)., ModuleName: TCF (TCF command: Device:startSession failed.)

The device connected is an ATmega645A

It works ok on win XP and studio4 so I know the JTAG connection is right.

Tried both on JTAGICE3 and JTAG ICE MKII

Last Edited: Wed. Jul 31, 2013 - 01:30 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

The device connected is an ATmega645A and it's ID is 0x0960d03f

Eh? it's talking about the ID of the JTAGICE not the AVR. You can run two or more JTAGICE on the same machine. The debugger uses their individual ID numbers to know which one to talk to.

How do the ICEs appear in Device Manager? If you use USBDeview.exe have they enumerated OK?

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

I'm using only one ICE. I do not have another ice connected to the computer. It works ok for ISP connection, and JTAG on ATMEGA16A

This from USBDeview:

Port_#0004.Hub_#0001 JTAGICE3 Vendor Specific Yes Yes No No J30200024919 31/07/2013 8:13:52 AM 31/07/2013 8:21:32 AM 03eb 2110 1.01 ff ff ff WinDriver6 windrvr6.sys Jungo Atmel Corp. 100 mA 2.00 JTAGICE3 11.0.0.0 USB\VID_03EB&PID_2110\J30200024919

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

Ah, apologies, I just finished downloading the 645A datasheet (when did Atmel datasheets suddenly grow from 5MB to 60MB?!?!) and I see that as well as a signature identity it does have the JTAG ID 0x960d (manufacturer = 0x1F). (curious that both 645A and 645P have the same ID in fact!).

In fact the device XML shows:

          

which is where the expected number will be coming from. If your system is seeing 0x960b03f instead then:

C:\Program Files\Atmel\Atmel Studio 6.1\devices>grep -i 960b03f *.xml
ATmega649A.xml:          
ATmega649P.xml:          

It would appear that what you are looking at is an ATmega649A or ATmega649P. Someone supplied you the wrong chip.

(I guess a 5 and a 9 might be easily confused).

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

I did not have any problem with the older studio 4 and XP.

The pop out window says:

"Unable to enter programming mode. The read device id indicates that the connected device is an ATmega645A.

Please verify device selection."

And the device signature 0x1E9605 is marked in red.

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

Ok, thank you clawson for all your support. I'll try to modify the file because I have about 200 boards with this chip.

Last Edited: Wed. Jul 31, 2013 - 02:11 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I can only go by what I see. Your initial error was:

 JTAG ID 0x0960b03f (expected 0x0960d03f)

even if this were USB noise or a fault in the USB device driver or something it just seems too coincidental that the ID has been corrupted from that for 645A/645P to something that is still valid and identifies 649A/649P. Either they are 649's or Atmel have made some kind of production error and put a 649 ID in a 645 device. OTOH I suppose the difference is just a couple of swapped/shifted bits B=1011, D=1101 so I suppose if there were noise or something it might be corrupted in this way but how did the rest of ID number remain intact?

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

It's too consistent to be noise. Every time I try it even different boards, I got 0x0960b03f and nothing else.

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

Possible fix is to use JTAGICE3 with win7.

Imagecraft compiler user

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

Solved: I modified ATmega645A.XML file in Atmel Studio 6.1/devices folder. It works OK now.

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

That's a bit of an "iffy" fix. If I were you I'd try to get to the bottom of whatever is wrong here. If you use JTAG to read the signature is it confirmed as 0x1E9605 ?

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

Yes, the signature is confirmed. I know is not the best solution, I have an AVR ticket, but until is "officially" solved I have a fix.