Bob Chiodini wrote:
I get the impression from the /var/log/messages output when I plug
the programmer in to the USB port that this driver is already present
in the 2.6.18-1.2257.fc5 kernel, and ttyUSB0 is a serial port, isn't
it? I'm still not sure how to get avrdude to speak to the programmer.
Perhaps the firmware upgrade done to it by AVRStudio will help.
Bob
Bob,
I did some poking on the bdmicro website and there is a later verion
of avrdude.
http://download.savannah.gnu.org/releases/avrdude/
You could try talking to the programmer via mincom. Maybe there is a
baud rate or handshake issue.
Bob...
I can report a happy ending to the story now. AVRStudio4 did a firmware
upgrade to the programmer itself. When I retried avrdude using
/dev/ttyUSB0, it worked like magic. Here is the output:
[rlc@bobcp4 bbot]$ avrdude -p m128 -P /dev/ttyUSB0 -c stk500
avrdude: stk500_recv(): programmer is not responding
avrdude: successfully opened stk500v2 device -- please use -c stk500v2
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e9702
avrdude: safemode: Fuses OK
avrdude done. Thank you.
[rlc@bobcp4 bbot]$ avrdude -p m128 -P /dev/ttyUSB0 -c stk500v2
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e9702
avrdude: safemode: Fuses OK
avrdude done. Thank you.
--------------------------------------------------------------------------------------
As you can see, avrdude is quite intelligent and will try different
programmer devices as needed. I guess it was definitely worthwhile to
check the programmer out on Microsoft Windows. There isn't a Linux
version of AVRStudio, and I wouldn't have gotten the all-important
firmware upgrade without it.
Bob
