AS7 works on one computer, unable to read Device ID on 3 other computers

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

 I have a JTAGICE MKII programmer that shows up in the list of programmers in Atmel Studio 7 (latest version today). I select JTAG and click apply and it seems to be okay at that point, but when I click on the button to read the device ID, I get the error "JTAGID not valid. Debugger command enterProgMode failed." Here is the kicker though, there is no problem programming the board (has an ATMEGA1280) on my co-worker's computer. I did a fresh install on a 3rd computer in the lab, and it too fails to read the device ID. I am using the exact same board, same usb cable, same programmer, and I have not even moved the programmer's connection to the JTAG connector on the board.... so it is not a cable issue, or a board issue, power issue, or a 'plugging in the JTAG connected the wrong way issue'.

 

. I did not mess around with fuse settings at all, so they should be correct considering it is able to be programmed on that one magical (co-worker's) computer.

 

I have even tried installing the same exact version of Atmel studio 7.0.1417 as the computer that is able to program, using the same install exe file that my co-worker used! 

I even have the same model computer as the computer that is able to program, and we are both running windows 10. Same USB cable is being used. I am using the same power supply brick to the power the board that contains the atmega1280.

 

I tried two other computers, and they too have the same problem programming  (No copies of atmel were on those computers so there is no version conflict to speak of).

 

I haven't used Atmel Studio in the past much, but I am NOT impressed.

 

 

 

Johnny Ancich

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

JohnnyAncich wrote:
I have even tried installing the same exact version of Atmel studio 7.0.1417 as the computer that is able to program, using the same install exe file that my co-worker used!

Atmel Studio 7.0 - Release Notes

(page 3)

Atmel Studio 7.0.1931

...

– AVRSV-8001: Tool firmware upgrade instability.

...

via Atmel Studio 7 | Microchip Technology

IIRC, AVRSV-8001 was due to either a USB reset signal and/or USB timing issue.

JohnnyAncich wrote:
I even have the same model computer as the computer that is able to program, and we are both running windows 10.
The build of Windows 10 that's on a PC depends on PC :

  • make
  • model
  • generation
  • serial number (sometimes)

winver for Windows 10 build (version number, period, build number)

Some Windows 10 builds have made Atmel Studio non-functional.

WinUSB is less likely to cause issues than in early versions of Windows 10.​​​​​​​

 


Windows 10 - release information | Microsoft Docs

WinUSB (Winusb.sys) | Microsoft Docs

 

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

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

Still struggling 3 days later.  Good thing this is not project related, or I would be FIRED by now.

 

Here is the version of windows 10, if it matters.

 

I see a lot of conflicting information about the JungoConnectivity driver.  I read somewhere that version 11 is for Studio6 while version 12 is for Studio7.   My device manager shows Jungo as being version 11.5 BUT, my co-worker who is using Version 7 and whose programming is able to WORK is also using version 11.5 of Jungo.

 

I REMOVED Jungo, and then used the 'REPAIR' option when you try to uninstall Studio7.   During repair I could see it was re-installing some USB drivers, and at the end I now no longer have JUNGO, but a separate group called ATMEL with my JTAGICE programmer in that group.  GUESS WHAT?  Still cannot read a device, nor erase a chip!

 

 

 

 

 

Johnny Ancich

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

******
SOLVED
******

 

Since my AVR programming pod is called a JTAG ICE, I naturally thought you set the Device programming window's Interface selection to 'JTAG'.   I demonstrated this to my much more experienced co-worker at least 3 times and he did not pick up on the fact that the I had selected JTAG.   Changed it to "ISP", and BANG... IT WORKED.

 

 

Johnny Ancich

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

But if your chip has JTAG ( ATMEGA1280 )  then JTAG programming as well as debugging should work from the JTAG header. Are you saying that you plugged the ISP connector in and tried to use JTAG for programming?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly