Objective Development Forums

USB with atmega 32

2008-01-05T16:50:22+02:00

christian wrote:This can be almost anything. That's why I recommended to start with a working example and change only one thing at a time.

Oke thanks for everything

Statistics: Posted by Phoenix — Sat Jan 05, 2008 4:50 pm

USB with atmega 32

2008-01-05T16:39:48+02:00

This can be almost anything. That's why I recommended to start with a working example and change only one thing at a time.

Statistics: Posted by christian — Sat Jan 05, 2008 4:39 pm

USB with atmega 32

2008-01-05T16:33:56+02:00

completely unknown

Code:

Device Descriptor:
bcdUSB:             0x0000
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x00 (0)
idVendor:           0x0000
idProduct:          0x0000
bcdDevice:          0x0000
iManufacturer:        0x00
iProduct:             0x00
iSerialNumber:        0x00
bNumConfigurations:   0x00

ConnectionStatus: DeviceFailedEnumeration
Current Config Value: 0x00
Device Bus Speed:      Low
Device Address:       0x00
Open Pipes:              0

Statistics: Posted by Phoenix — Sat Jan 05, 2008 4:33 pm

USB with atmega 32

2008-01-05T16:12:08+02:00

Does it report the device name for the unknown device? If it knows the device name and vendor name, then the USB driver works. In this case you need to associate libusb with the device. This is usually done with a .inf file.

If the device is completely unknown, there's probably a more fundamental error (such as wrong clock speed, wiring problem, logic level problem, I/O pins not configured correctly or something similar).

Statistics: Posted by christian — Sat Jan 05, 2008 4:12 pm

USB with atmega 32

2008-01-05T15:34:39+02:00

Oke thanks I have no error now.

So I went back to the firmware and I doesn't work and my computer didn't find a device so I made some hardware asjust ments and now I finds a unknown device

So is this a firmware error ?

Statistics: Posted by Phoenix — Sat Jan 05, 2008 3:34 pm

USB with atmega 32

2008-01-04T19:59:49+02:00

This is a different problem than what you reported before. -lusb is libusb-win32. You should install it at a path where it can be found by the compiler (or add -L and -I flags to extend the search path). See http://libusb-win32.sourceforge.net/.

Statistics: Posted by christian — Fri Jan 04, 2008 7:59 pm

USB with atmega 32

2008-01-05T15:47:34+02:00

Oke I will do that but I think I already have firmware running on my atmega32.
But the host software doesn't work because when I compile he doesn't find -lusb and I don't know what it is or where I can find it.

Statistics: Posted by Phoenix — Fri Jan 04, 2008 3:38 pm

USB with atmega 32

2008-01-03T22:44:23+02:00

I would recommend that you start analytically: Use one of the reference projects on an ATMega8 and get it running. Then move this same project over to the ATMega32, updating the usbconfig.h and other pin assignments as well as fuse values accordingly. Then bring in your firmware code, taking care that you don't break anything.

That's the procedure I would recommend for the firmware. Once you have a working example, change only one thing at a time.

When you have the firmware running, we can talk about the host software.

Statistics: Posted by christian — Thu Jan 03, 2008 10:44 pm

USB with atmega 32

2008-01-03T19:30:34+02:00

Oke
Compiler works!
But I can't compile the commandline software.

And the device is NOT recognized by my computer.

Statistics: Posted by Phoenix — Thu Jan 03, 2008 7:30 pm

USB with atmega 32

2008-01-03T18:55:24+02:00

OK. One thing after the other. Please make sure that the device is recognized by Windows. I don't know how you can distinguish a broken device from a device without drivers on Windows, but there should be a way to do that.

Regarding the host application: Please make sure you can compile a simple "Hello World!" example. If that does not work, something is wrong with your compiler installation and you should fix that first.

Statistics: Posted by christian — Thu Jan 03, 2008 6:55 pm