Page 1 of 1
Usb device not found.
Posted: Sat Jan 05, 2008 7:35 pm
by overthere
Hi there,
if i connect to the device, XP says "Gerät nicht erkannt", also Linux says me the same:
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
(I used lsusb for the listing, libusb is installed, avrdude supports programmer)
I checked the these points:
- Crystal (12 MHz works)
- 5 Volt supply voltage
- Z-Diodes are connected
- Mega8-16 is inserted
What may be my error?
Please help me!
Posted: Sat Jan 05, 2008 7:36 pm
by overthere
I need to add: My problem is that AvrDopper USB device is not found.
Posted: Sat Jan 05, 2008 10:12 pm
by christian
Three more things that come to my mind:
(1) Did you compile for the ATMega8 or the ATMega88? They are not binary compatible.
(2) Did you check wiring, especially pin assignments of the USB connector (unless you used a known-to-work PCB, of course)?
(3) Did you try to insert a hub between the host and the device?
Posted: Sun Jan 06, 2008 7:02 pm
by Guest
michael[dev]$ /sbin/lsusb
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 050: ID 16c0:05df
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Okay, if found my error. Gnd of the Atmel was not connected. The _baught_ platine had an error. Sorry for the stupid request, but I have never taught about that stupid problem. Sorry.
But there's the next problem. If I want to connect in the USB HID Mode.
michael[dev]$ avrdude -c stk500v2 -P avrdoper -p t26
avrdude: stk500v2_command(): command failed
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.
avrdude done. Thank you.
The IC (tiny26) is connected, I just checked the "Pads" of the circuit. Have you got an idea. (sorry for being a noob to usb stuff)
Posted: Sun Jan 06, 2008 8:19 pm
by christian
As far as I can see, this is NOT a USB problem, but a problem in the communication between the programmer and the target device. Did you use an 74HC type for the ISP driver?
Posted: Mon Jan 07, 2008 3:50 pm
by overthere
Yes, I used a 74HCT, but this must also worK? Or not?
Posted: Mon Jan 07, 2008 4:19 pm
by christian
Yes, that should work. Probably even better. Only 74LS and 74 standard don't work.
Posted: Mon Jan 07, 2008 6:10 pm
by Guest
Thanks for your help.
(1) The USB UID works perfekt now, but only if the device supply jumper is deactivated. If I activate device supply, and I still supply the device by a battery, it doesn't work. Also if I disconnect the battery. What could that be?
(2) The red diode I put in, is never on. When is this diode normally on?
(3) If I try to write to the flash by avrdudes terminal mode, it refuses. Is that "normal"?
Posted: Mon Jan 07, 2008 6:20 pm
by Guest
(2): I always looked at the screen. It lights up when I'm programming. Sorry.
Posted: Mon Jan 07, 2008 6:52 pm
by christian
You MUST NOT set the jumper for device supply if you have an external supply connected! This may even damage your computer (although computers have a self-resetting fuse in the USB supply these days).
If you disconnect the battery, the device CAN be supplied by the programmer if the device's ISP connector is wired accordingly.
Regarding terminal mode: As far as I know, terminal mode does not support page-wise writing. If the device requires page mode, you probably can't program it from terminal mode.
Posted: Sun Feb 24, 2008 12:02 am
by vibrex
"Three more things that come to my mind:
(1) Did you compile for the ATMega8 or the ATMega88? They are not binary compatible.
(2) Did you check wiring, especially pin assignments of the USB connector (unless you used a known-to-work PCB, of course)?
(3) Did you try to insert a hub between the host and the device?"
I would like to know what is the problem to connect a hub? My notebook has 4 USB ROOT HUB indicated in hardware properties of my computer.
May I have some help?
Thanks a lot.
Carlos. (Rio de Janeiro - Brasil)
Posted: Sun Feb 24, 2008 6:01 pm
by christian
A hub, especially a USB 2.0 hub, may have a different timing in the low speed USB communication. Timing dependent bugs may therefore occur or not occur if a hub is inserted.