ATmega32u4 inf.?

[mies]

hi,

First of all, thanks adafruit, for the quick delivery... Within a week!! (to holland)
I did not know they could fly that fast..

Now the problem..

I,m trying to install the inf. file, from github, for my ATmega32u4, but it is not working..
Tried it on win7, xp, automatic, manual, but windows says its it doesn't install because it can't find the right software.


When i connect it via usb, the green light "breaths", red led is on...
Windows says; Found new hardware, AVR CDC Bootloader, and when it asks for drivers, i click manualy,... go the the folder with the inf file,
and there it end's... It says it's not the right software for this hardware..
Right clicking the inf, and then trying to install it doesn't do anything..
I've tried the lufa CDC bootloader, the bootloader from the adafruit-github-link.. they all do the same.
In despaire i tried the teensy inf, and then it sort of works, in my hardware list, the unknown avr now is a com 3 port..
But then avr dude says 32u4 is not valid...

What can i do to fix it..?

Thanks (in advance)

mies

P.S. In comparison with other adafruit documentation this one is fairly short. Nothing about pinout, or a how-to with an example.. I.E. the usb gamepad on a atmega32u4..

[mies]

Update..

Something happend, just a minute ago..

I tried to instal teensyduino, and it said i needed a driver..
For a change i pressed o.k. Now it shows up on mij hardwarelist as USB Serial..
then i uploaded the newest WinAVR,
The teensy driver is working on my ATm32u4,
when i try AVRdude, it showed up... Same text as i see on the product screen...
...LUFA....Etc, etc......

hurray, for a moment..... although teensyduino doesn't do a thing with it...
Is it normal that the teensyduino-submenu's are "off" ?
When i select teensy, i see a USB/CPU/Keyboard menu, but when i select the AT32u4, they turn grey?


mies

[adafruit]

the 32u4 board is fairly new so there isn't as many examples, but its also meant for people with avr experience, not for 'beginners'
you may have not downloaded the .inf correctly. it definitely works and is nearly identical to the teensy one

the teensyduino code isnt directly supported since its not a teensy, we got it working with v19 but there have been some changes since then. try v19. however, its intended to be used with avrdude

[mies]

thanks

As you guest correctly, i am a beginner...
Did a few things with avr, and avrdude,(if i count my minipov-programming ) but there my experience ends..
(Ah, and a lot of prototyping on boarduino/arduino...)

But for installing software, and downloading it, i'm not to bad (being modest).
First i downloaded it directly via the link from adafruit,
i tried it by downloading the trunk-file from github, i've tried the bootloader-inf directly from LUFA ,
But when i try to use the inf (by directing the hardware-installer to the bootloader.inf file)
it won't work. On different OS's.

Any idea' ?

As for the -level of user- info... I think you could read the productpage any way you want.. the teensyduino-chapter-end quote "this wil get you going" is what made me think "ah, i can do that"

soit, i will learn...
First things first, the driver....

mies

[adafruit]

try clicking on "automatically install" when the driver comes up

[mies]

that's the first thing i've tried....
Right now it installs the PJRC driver automaticaly... and if i try to choose the CDC bootloader, it says there is no valid file.... I keep trying, and pick up some knowledge on my way....

[adafruit]

we use them tons on XP and they work fine so we're really confused. what does it say when it fails? can you post a screenshot?

[larryvc]

Hi,

I'm having the same problem on Win7 with both the Device manager install and the right click install methods as shown in the two following screen shots.

Also please edit the .inf file on a windows machine so that it has CRLFs.

LUFA CDC bootloader.jpg (285.06 KiB) Viewed 4679 times

LUFA CDC bootloader right click install.jpg (246.1 KiB) Viewed 4659 times

[larryvc]

Hi adafruit,

The LUFA CDC bootloader.inf file contained the wrong VID and PID. The VID and PID should be "USB\VID_239A&PID_0001&REV_0001".

The device is now recognized.

Here is the corrected .inf file: [Modified to include the both the old VID/PID and the new VID/PID]

Code: Select all

;************************************************************
; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation


[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%MFGNAME%
LayoutFile=layout.inf
CatalogFile=%MFGFILENAME%.cat
DriverVer=11/15/2007,5.1.2600.0

[Manufacturer]
%MFGNAME%=DeviceList, NTamd64

[DestinationDirs]
DefaultDestDir=12


;------------------------------------------------------------------------------
;  Windows 2000/XP/Vista-32bit Sections
;------------------------------------------------------------------------------

[DriverInstall.nt]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.nt
AddReg=DriverInstall.nt.AddReg

[DriverCopyFiles.nt]
usbser.sys,,,0x20

[DriverInstall.nt.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.nt.Services]
AddService=usbser, 0x00000002, DriverService.nt

[DriverService.nt]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys

;------------------------------------------------------------------------------
;  Vista-64bit Sections
;------------------------------------------------------------------------------

[DriverInstall.NTamd64]
include=mdmcpq.inf
CopyFiles=DriverCopyFiles.NTamd64
AddReg=DriverInstall.NTamd64.AddReg

[DriverCopyFiles.NTamd64]
%DRIVERFILENAME%.sys,,,0x20

[DriverInstall.NTamd64.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,%DRIVERFILENAME%.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.NTamd64.Services]
AddService=usbser, 0x00000002, DriverService.NTamd64

[DriverService.NTamd64]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\%DRIVERFILENAME%.sys


;------------------------------------------------------------------------------
;  Vendor and Product ID Definitions
;------------------------------------------------------------------------------
; When developing your USB device, the VID and PID used in the PC side
; application program and the firmware on the microcontroller must match.
; Modify the below line to use your VID and PID.  Use the format as shown below.
; Note: One INF file can be used for multiple devices with different VID and PIDs.
; For each supported device, append ",USB\VID_xxxx&PID_yyyy" to the end of the line.
;------------------------------------------------------------------------------
[SourceDisksFiles]
[SourceDisksNames]
[DeviceList]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A, USB\VID_239A&PID_0001&REV_0001

[DeviceList.NTamd64]
%DESCRIPTION%=DriverInstall, USB\VID_03EB&PID_204A, USB\VID_239A&PID_0001&REV_0001


;------------------------------------------------------------------------------
;  String Definitions
;------------------------------------------------------------------------------
;Modify these strings to customize your device
;------------------------------------------------------------------------------
[Strings]
MFGFILENAME="CDC_vista"
DRIVERFILENAME ="usbser"
MFGNAME="http://www.fourwalledcubicle.com"
INSTDISK="LUFA CDC Bootloader Driver Installer"
DESCRIPTION="Communications Port"
SERVICE="USB RS-232 Emulation Driver"


[adafruit]

hmm it shouldnt matter but maybe for win7 it does. we'll update it!

[larryvc]

HI adafruit,

I tried the old .inf on a WinXP machine and it didn't install. The fixed .inf worked.

VID and PID must match the device for the driver install to work.

See below: (This on Win7)

ATmega32u4 com port.jpg (248.47 KiB) Viewed 4645 times

[adafruit]

hi, yes, thanks, we got it! if you have already installed a CDC driver, it will 'automatch' even with the wrong VIDPID - most hardware hacking geeks do but you do not which is why it worked for some people.

[larryvc]

Hi adafruit,

I modified the .inf file in my earlier post to reflect both the old and new VID/PID.

EE + CS = Hardware Hacker for a long time!

Cheers from Redmond

[mies]

Larry, thanks a lot..
nice to now somebody else experienced the same...
(thought i was going mad.... nobody else? in the whole world)
i'll give it another try,

Many thanx in advance...

(will be next week before i can post my findings, have to go abroad for work)

Edit////

Couldn't wait, tried it right away.. Right click didn't work.. says the inf doesn't support this methode,
But.... when i tried to update the driver manually, it found the right driver, and now it works...
It finally says, com port, with the adafruit inf..
thanks again..

[EmbeddedCreations]

I was having trouble getting the .inf loaded, and this thread helped me.

I had a different issue, The Rev my bootloader was reporting is 0002 not 0001, and modifying the .inf to use "REV_0002" worked for me:
USB\VID_239A&PID_0001&REV_0002