Re: Where Is The AVRISP USB Programmer When I Plug It In?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Robert L Cochran wrote:
> I have an AVRISP programmer bought from an Ebay merchant. It is a USB
> device and connects to my FC5 machine's USB ports on one end and the
> Atmel device I wish to program at the other end (using a 10-pin IDC
> cable intended for in-system programming.) I'm using avrdude to move my
> code to the AVR device. The problem seems to be avrdude can't find the
> programmer. I could be wrong about this. Here are the /var/log/messages
> output I get when I plug the AVRISP into a USB port:
> 
> Jan  5 17:01:29 bobcp4 kernel: usb 1-1: new full speed USB device using
> ohci_hcd and address 4
> Jan  5 17:01:29 bobcp4 kernel: usb 1-1: configuration #1 chosen from 1
> choice
> Jan  5 17:01:29 bobcp4 kernel: usbcore: registered new driver usbserial
> Jan  5 17:01:29 bobcp4 kernel: drivers/usb/serial/usb-serial.c: USB
> Serial support registered for generic
> Jan  5 17:01:29 bobcp4 kernel: usbcore: registered new driver
> usbserial_generic
> Jan  5 17:01:29 bobcp4 kernel: drivers/usb/serial/usb-serial.c: USB
> Serial Driver core
> Jan  5 17:01:29 bobcp4 kernel: drivers/usb/serial/usb-serial.c: USB
> Serial support registered for cp2101
> Jan  5 17:01:29 bobcp4 kernel: cp2101 1-1:1.0: cp2101 converter detected
> Jan  5 17:01:29 bobcp4 kernel: usb 1-1: reset full speed USB device
> using ohci_hcd and address 4
> Jan  5 17:01:29 bobcp4 kernel: usb 1-1: cp2101 converter now attached to
> ttyUSB0
> Jan  5 17:01:29 bobcp4 kernel: usbcore: registered new driver cp2101
> Jan  5 17:01:29 bobcp4 kernel: drivers/usb/serial/cp2101.c: Silicon Labs
> CP2101/CP2102 RS232 serial adaptor driver v0.07
> 
If this is showing up just after you plug the device in, then the
device is showing up as a USB to serial device. It is probably
/dev/ttyUSB0 from looking at the modules loaded.
> 
> Here is what avrdude tells me when I try to program my AVR chip:
> 
> [rlc@bobcp4 hw]$ avrdude -c avrisp -P /dev/ttyUSB0 -p m128 -U
> flash:w:hw.hex -v -v -v -v
> 
> avrdude: Version 5.2, compiled on Dec 15 2006 at 11:30:09
>         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
> 
>         System wide configuration file is "/usr/local/etc/avrdude.conf"
>         User configuration file is "/home/rlc/.avrduderc"
>         User configuration file does not exist or is not a regular file,
> skipping
> 
>         Using Port            : /dev/ttyUSB0
>         Using Programmer      : avrisp
> avrdude: Send: 0 [30]   [20]
> avrdude: Send: 0 [30]   [20]
> avrdude: Send: 0 [30]   [20]
> avrdude: ser_recv(): programmer is not responding
> avrdude: stk500_recv(): programmer is not responding
> avrdude: Send: Q [51]   [20]
> avrdude: ser_recv(): programmer is not responding
> avrdude: stk500_recv(): programmer is not responding
> 
> 
> The output of mount is
> 
<---------------[ SNIP ]------------------->
> 
> 
> Can anyone offer suggestions that would let avrdude find the programmer?
> I can provide photographs of the programmer on request. I have turned
> off iptables and stopped it to test this issue. Also, /dev/ttyUSB0 has
> been made world writable, again for testing purposes. No luck. I've
> checked the avr-chat mailing list and I saw one suggestion that I change
> how udev treats the device, but I'm not sure it applies here. Clearly I
> seem to be missing something -- a device driver?
> 
> 
Stopping IPtables is not going to help. This is not a network
problem. IPtables will only affect a USB NIC, and not other USB
devices on the local machine.

If the problem were that the program could not write to the serial
port, you should see that is the dialog from avrdude. It looks like
the program is able to read and write the port.

Now, I have a couple of questions:
Does the programmer plug directly into the USB bus, or is the a USB
to serial adapter that is then plugged into a serial port on the
programmer?

Is the programmer a USB to serial device with TTL level outputs? If
so, are you doing this with the cable plugged into something you are
trying to program?

Do you have any other USB serial devices? (ls /dev/ttyUSB*) If so,
are you sure you are using the correct one?

Are you sure the programmer works?

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux