Studio 7 - device programmers

Log in or register to post comments
Go To Last Post
11 posts / 0 new
Author
Message
erg144
erg144's picture
Level: Hangaround
Joined: Thu. Dec 29, 2011
Posts: 145 View posts
Location: Pittsburgh, PA
#1
Posted by erg144: Sun. Sep 27, 2015 - 09:10 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

 

Windows 10

New install of Studio - thought I would see if it fixed a few issues.  Not sure it fixed any yet, but know it has caused a few.

 

Does not see AVR ISP MKII programmer.  Already a thread on that one.

JTAGICE 3 - needs to upgrade the firmware.  - problem, can not upgrade the firmware.  So the tool can see it, you just can't use it.

  Details:

 firmware version on tool  3.25.  On Disk 3.2a   (not sure "a" comes after 5 but these firmware developers are usually smarter than me)

While trying to upgrade get the message

 

firmware upgrade failed, toggle power on tool and retry upgrade. 

Tags:

Tools, Atmel Studio (AVR-related)
Top
meolsen
meolsen's picture
Level: Site Admin
Joined: Wed. Jul 27, 2011
Posts: 3601 View posts
Location: Microchip, Arizona
Posted by meolsen: Sun. Sep 27, 2015 - 09:24 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Try to do a fw upgrade from the command line. See here (exchange 6.2 for 7.0).

 

If it still fails, add '-v 8' to the command line to turn up the log level and attach it here...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Top
erg144
erg144's picture
Level: Hangaround
Joined: Thu. Dec 29, 2011
Posts: 145 View posts
Location: Pittsburgh, PA
Posted by erg144: Sun. Sep 27, 2015 - 11:37 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

C:\Program Files (x86)\Atmel\Studio\7.0\atbackend>atfw -t jtagice3 -a "c:\Program Files (x86)\Atmel\Studio\7.0\tools\JTAGICE3\jtagice3_fw.zip" -v 8
23:32:25: [init] Initializing logging subsystem
23:32:25: [init] Logging to file: C:\Users\edross\AppData\Local\Temp\atfw.9946-5a28-d5ef-dbd4.log
23:32:25: [init] Finished initializing logging subsystem
23:32:25: [cli] Starting execute stage
23:32:25: [cli] Enumerating connected tools and serial numbers:
23:32:25: [usb] WDU_INIT failed: No valid license (0x20000009).
23:32:27: [cli] No serial number given
23:32:27: [cli] No tool found based on serial
23:32:27: [cli] No Tool is found

 

 

The log file contains the same data as the console output

Top
meolsen
meolsen's picture
Level: Site Admin
Joined: Wed. Jul 27, 2011
Posts: 3601 View posts
Location: Microchip, Arizona
Posted by meolsen: Mon. Sep 28, 2015 - 01:04 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You are seeing the same Jungo on Windows 10 issue as reported in the Atmel Studio forum. Check those threads out...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Top
erg144
erg144's picture
Level: Hangaround
Joined: Thu. Dec 29, 2011
Posts: 145 View posts
Location: Pittsburgh, PA
Posted by erg144: Tue. Sep 29, 2015 - 01:17 AM (Reply to #4)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Someone suggested on one of the other threads that a windows 10 reset would fix all problems.  Out of desperation I tried it.  Seemed to fix all problems.

 

Able to upgrade my avr jtagice3 to the latest release  (by the way, going from 3.5 to 3.a does not seem like it is an upgrade.  are the numbers in hex?)

 

Also, able to see and use my avrisp MKII programmer.   

 

I wish I had noticed the driver version before the reset - but the Jungo version after the upgrade is 11.1.0.0 dated 1/5/2013

 

This was/is painful.  hope I don't have to do that again.

 

 

Top
grgsaliba
grgsaliba's picture
Level: New Member
Joined: Thu. Oct 26, 2006
Posts: 11 View posts
Posted by grgsaliba: Sat. Oct 3, 2015 - 05:06 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm getting a different log when trying command line upgrade but still doesn't work:

 

C:\Program Files (x86)\Atmel\Studio\7.0\atbackend>atfw -t jtagice3 -a "c:\Program Files (x86)\Atmel\Studio\7.0\tools\JTAGICE3\jtagice3_fw.zip" -v 8
17:04:43: [init] Initializing logging subsystem
17:04:43: [init] Logging to file: C:\Users\grgsa\AppData\Local\Temp\atfw.c06b-5883-27d8-8be6.log
17:04:44: [init] Finished initializing logging subsystem
17:04:44: [cli] Starting execute stage
17:04:44: [cli] Enumerating connected tools and serial numbers:
17:04:44: [usb] WDU_INIT failed: No valid license (0x20000009).
17:04:44: [cli] J30200026855
17:04:46: [cli] No serial number given
17:04:46: [cli] Choosing first serial
17:04:46: [cli] Found
17:04:46: [cli] jtagice3
17:04:46: [cli] :
17:04:46: [cli] J30200026855
17:04:46: [cli] Creating upgrader for jtagice3(J30200026855)
17:04:46: [cli] Have upgrader, continue
17:04:46: [cli] Start reading firmware from archive c:\Program Files (x86)\Atmel\Studio\7.0\tools\JTAGICE3\jtagice3_fw.zip
17:04:46: [archive] Temporary firmware directory: C:\Users\grgsa\AppData\Local\Temp\4c9f-860b-23de-9e5e
17:04:46: [archive] Parsing firmware manifest
17:04:46: [cli] Finished reading firmware from archive
17:04:46: [cli] Upgrading jtagice3:J30200026855
17:04:46: [cli] Connect; Application
17:04:46: [cli] Connect; Switch to upgrade mode
17:04:46: [cli] Connect; Upgrade Mode
17:04:47: [cli] GenericError thrown during firmware upgrade
17:04:47: [cli] USB driver initialization failed: No valid license (0x20000009).
17:04:47: [archive] Deleting directory: C:\Users\grgsa\AppData\Local\Temp\4c9f-860b-23de-9e5e

Top
grgsaliba
grgsaliba's picture
Level: New Member
Joined: Thu. Oct 26, 2006
Posts: 11 View posts
Posted by grgsaliba: Sat. Oct 3, 2015 - 05:07 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm getting a different log when trying command line upgrade but still doesn't work:

 

C:\Program Files (x86)\Atmel\Studio\7.0\atbackend>atfw -t jtagice3 -a "c:\Program Files (x86)\Atmel\Studio\7.0\tools\JTAGICE3\jtagice3_fw.zip" -v 8
17:04:43: [init] Initializing logging subsystem
17:04:43: [init] Logging to file: C:\Users\grgsa\AppData\Local\Temp\atfw.c06b-5883-27d8-8be6.log
17:04:44: [init] Finished initializing logging subsystem
17:04:44: [cli] Starting execute stage
17:04:44: [cli] Enumerating connected tools and serial numbers:
17:04:44: [usb] WDU_INIT failed: No valid license (0x20000009).
17:04:44: [cli] J30200026855
17:04:46: [cli] No serial number given
17:04:46: [cli] Choosing first serial
17:04:46: [cli] Found
17:04:46: [cli] jtagice3
17:04:46: [cli] :
17:04:46: [cli] J30200026855
17:04:46: [cli] Creating upgrader for jtagice3(J30200026855)
17:04:46: [cli] Have upgrader, continue
17:04:46: [cli] Start reading firmware from archive c:\Program Files (x86)\Atmel\Studio\7.0\tools\JTAGICE3\jtagice3_fw.zip
17:04:46: [archive] Temporary firmware directory: C:\Users\grgsa\AppData\Local\Temp\4c9f-860b-23de-9e5e
17:04:46: [archive] Parsing firmware manifest
17:04:46: [cli] Finished reading firmware from archive
17:04:46: [cli] Upgrading jtagice3:J30200026855
17:04:46: [cli] Connect; Application
17:04:46: [cli] Connect; Switch to upgrade mode
17:04:46: [cli] Connect; Upgrade Mode
17:04:47: [cli] GenericError thrown during firmware upgrade
17:04:47: [cli] USB driver initialization failed: No valid license (0x20000009).
17:04:47: [archive] Deleting directory: C:\Users\grgsa\AppData\Local\Temp\4c9f-860b-23de-9e5e

Top
meolsen
meolsen's picture
Level: Site Admin
Joined: Wed. Jul 27, 2011
Posts: 3601 View posts
Location: Microchip, Arizona
Posted by meolsen: Sat. Oct 3, 2015 - 07:27 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

17:04:47: [cli] USB driver initialization failed: No valid license (0x20000009).

Same error, see my response above

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Top
grgsaliba
grgsaliba's picture
Level: New Member
Joined: Thu. Oct 26, 2006
Posts: 11 View posts
Posted by grgsaliba: Sat. Oct 3, 2015 - 07:35 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

yes I know ...so is the only solution to reset Windows ??

Top
meolsen
meolsen's picture
Level: Site Admin
Joined: Wed. Jul 27, 2011
Posts: 3601 View posts
Location: Microchip, Arizona
Posted by meolsen: Sat. Oct 3, 2015 - 07:42 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Or, in the other thread, try to replace the Jungo driver with a libusb one. There are some caveats with this that I have listed there.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

Top
TyraMisoux
TyraMisoux's picture
Level: New Member
Joined: Thu. Apr 18, 2013
Posts: 9 View posts
Location: 27200 Savalia - Ilia
Posted by TyraMisoux: Thu. Nov 5, 2015 - 05:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No luck! I tried all usb-drivers.

jtagice3 goes to Download-mode - LED flashes and bldr driver loaded (also replaced this using zadig)

still "license error)

 

17:11:24: [cli] Start reading firmware from archive C:\Program Files (x86)\Atmel\Studio\7.0\tools\JTAGICE3\jtagice3_fw.zip
17:11:24: [archive] Temporary firmware directory: d:\temp\e196-a95f-e3b8-936e
17:11:24: [archive] Parsing firmware manifest
17:11:24: [cli] Finished reading firmware from archive
17:11:24: [cli] Connect; Application
17:11:24: [cli] Connect; Switch to upgrade mode
17:11:24: [cli] Connect; Upgrade Mode
17:11:24: [cli] GenericError thrown during firmware upgrade
17:11:24: [cli] USB driver initialization failed: No valid license (0x20000009).
17:11:24: [archive] Deleting directory: d:\temp\e196-a95f-e3b8-936e
 

edit ... hours later...

I made it work with a "from scratch installation" with my notebook. After fw-upgrade I compared the drivers: They are all the same!
Threre is the "atmel signed" winusb Data-Gateway driver used after powerup to connect the interface.
After change to bootloader-Mode the jungo-driver (windrvr6.sys) is used. This is also the same version on both devices.
I have no idea why upgrade fails on my desktop system.

 

Last Edited: Fri. Nov 6, 2015 - 09:44 AM
Top