----- Original Message -----
From: "raoul.palma" <raoul.palma@yahoo.com>
To: AVR-Chat@yahoogroups.com
Sent: Monday, October 1, 2012 12:14:49 PM
Subject: [AVR-Chat] Re: Using Jungo driver to talk to AVRISP
--- In AVR-Chat@yahoogroups.com, Philippe Habib <phabib@...> wrote:
>
> I'm looking at App Note AVR069, which mentions licensing and using the
Jungo driver to talk to the AVRISP. Has anyone done this? Is there any
sample code available? From the Jungo web site, it seems like
WindDriver is what you would use to create a driver and DriverCore might
be what to use to talk to the existing driver that Atmel has already
developed for the AVRISP. I'd appreciate a nudge in the right direction
to get started if anyone has already dealt with this.
>
> Thanks.
>
Having just gone thru a hair-graying experience getting my two USB
programmer to work in Window 7, here's a summary of my findings:
-) The Jungo driver is used exclusively by Atmel Studio. As far as I can
tell, Atmel is licensing it (for $) and end users are not allowed to
directly use it. That's probably why you can't find much info about it.
-) If you are using a toolchain other than Studio 6, use avrdude for all
programming tasks. Avrdude requires, for Windows 7, only, the libusb
driver called the "usblib filter driver". It is included with the
WinAVR command-line toolchain . You can also download the latest
"Windows 7 signed driver" from the Sourceforge site.
You do not need a signed driver to get avrdude to work properly. I think
the usblib version that comes from WinAVR is an unsigned version. Using
the signed driver merely eliminates a totally useless warning message
from Windows that's trying to scare people into thinking their PC will
catch fire and explode if they install unsigned drivers. So, the MS
warning may safely be ignored.
Following is the full procedure to install the libusb filter driver on
Windows 7. I've never seen this procedure explained anywhere else.
The Latest libusb from Sourceforge (libusb-win32-bin-1.2.6.0 as of
2012-09-30)
<http://sourceforge.net/projects/libusb-win32/files/libusb-win32-release\
s/>
http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases\
/
INSTALLATION INSTRUCTIONS (not explained in the libusb documentation or
anywhere else)
- Plug in the USB cable between your programmer and your PC.
- Run the libusb driver generator utility [ inf-wizard.exe ] and select
your programmer from the list of all the USB devices detected on your
system.
- Choose to let the utility install the drivers onto your system.
- Exit the installer utility. You will find new .INF and .CAT files in
the folder of the utility. The program [ inf-wizard ] will have named
these files appropriately according to the type of programmer you have
connected at the time .
- Go into Device Manager. You should see your programmer listed under
the group named "LibUSB-Win32 Devices". It should have an exclamation
mark, [ ! ], on its icon indicating that the programmer has not yet been
associated with the libusb driver.
NOTE: If there is no exclamation mark on the programmer icon this means
that an older libusb driver is already installed. Windows 7 need a
libusb driver version of 1.2 or greater for some USB programmers to work
with avrdude.My AVRIsp MKII needed a newer libusb version to work with
avrdude, but my USBTinyISP did not. Any older libusb driver needs to be
removed:
- Right-click on the usbasp device entry in Device Manager and
choose "Uninstall". Also choose the option to "Delete the driver
software for this device". Clock button [ OK ]. A confirmation message
will appear.
- Right-click on your programmer's entry under LibUSB-Win32 Devices
and left-click on "Update Driver Software". Click "Browse my computer
for driver software". Browse to your folder where the .INF file was
created. Click [ Next ]. You should then get a message that the device
was installed correctly. Try to program your AVR MCU using avrdude. As
far as I can tell, only the AVRIsp mkII USB programmer needs the "-P
usb" command line option in to avrdude. So, try the command line both
ways to see which one works.
Example command lines to confirm that avrdude is communicating with your
programmer:
>$ avrdude -p m168 -c usbasp
>$ avrdude -p m168 -c usbtiny
>$ avrdude -p m168 -c avrispmkii -P usb
A successful avrdude response:
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100%
0.05s
avrdude: Device signature = 0x1e9403 {your signature value will
be different}
avrdude.exe: current erase-rewrite cycle count is 971 (if being tracked)
avrdude.exe: safemode: Fuses OK
avrdude done. Thank you.
[Non-text portions of this message have been removed]
------------------------------------
Yahoo! Groups Links