avrdude 5.10 give syntax error for

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have compiled avrdude 5.10 because I want to use ftdi. So I went by the instruction from http://doswa.com/2010/08/24/avrdude-5-10-with-ftdi-bitbang.html

 

and tried to run this script:

sudo ./avrdude -v -c avrftdi -C avrdude.conf +atmega328p.conf -P /dev/ttyUSB0 -p m328p 

and I get a syntax error at the line for:

type = "wiring";
#
# PROGRAMMER DEFINITIONS
#

# http://wiring.org.co/
# Basically STK500v2 protocol, with some glue to trigger the
# bootloader.

programmer
  id    = "wiring";
  desc  = "Wiring";
  type  = "wiring";
  connection_type = serial;
;

 

I've tried it without the quotes and it doesn't recognize to 'w';

 

The avrdude.conf file works fine for avrdude-6.1

 

Is there an older version of the avrdude.conf I'm supposed to use with 5.1?

 

- Dan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK, so I did the same process for avrdude-6.1, copied the avrdude file to my working directory and tried the same script file:

sudo ./avrdude -v -v -v -v  -c avrftdi -C avrdude.conf +atmega328p.conf -P /dev/ttyUSB0 -p m328p $1 $2 $3

and got this error:

avrdude: Version 6.1, compiled on Mar 14 2017 at 13:20:17
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

         System wide configuration file is "avrdude.conf"
         User configuration file is "/home/dan/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping

         Using Port                    : /dev/ttyUSB0
         Using Programmer              : avrftdi
avrdude: Warning: using PID 0x6001, ignoring remaining PIDs in list
I avrftdi_open(717): Using device VID:PID 0403:6001 and SN '(null)' on interface A.
D write_flush(481): Setting pin direction (0x0000) and value (0x0000)
T write_flush(493): Set pins command: 80 00 00 82 00 00

I think it might have something to do with how my pins are set:

programmer
  id         = "avrftdi";
  desc       = "FT2232D based generic programmer";
  type       = "avrftdi";
  connection_type = usb;
  usbvid     = 0x0403;
  usbpid     = 0x6001;
  usbvendor  = "";
  usbproduct = "";
  usbdev     = "A";
  usbsn      = "";
#ISP-signals - lower ADBUS-Nibble (default)
  reset  = 3;
  sck    = 0;
  mosi   = 1;
  miso   = 2;
udevadm info --attribute-walk -n /dev/ttyUSB0 | sed -n '/FTDI/,/serial/p'
    ATTRS{manufacturer}=="FTDI"
    ATTRS{removable}=="unknown"
    ATTRS{idProduct}=="6001"
    ATTRS{bDeviceClass}=="00"
    ATTRS{product}=="FT232R USB UART"

  looking at parent device '/devices/pci0000:00/0000:00:1d.1/usb7':
    KERNELS=="usb7"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{devpath}=="0"
    ATTRS{idVendor}=="1d6b"
    ATTRS{speed}=="12"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{authorized_default}=="1"
    ATTRS{busnum}=="7"
    ATTRS{devnum}=="1"
    ATTRS{configuration}==""
    ATTRS{bMaxPower}=="0mA"
    ATTRS{authorized}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{maxchild}=="2"
    ATTRS{bcdDevice}=="0313"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{quirks}=="0x0"
    ATTRS{serial}=="0000:00:1d.1"

 

- Dan

Last Edited: Wed. Mar 15, 2017 - 04:36 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My old conf files define programmer.type without quotes.
Add quotes and the conf file works with modern avrdude.
.
If you have an old avrdude, try it with and without quotes and see if it is happy.
.
David.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

as you can see from my 2nd post, that's not the problem anymore. Going to start a new thread. smiley

- Dan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

DO NOT START A NEW THREAD!!!!

 

Moderator

 

Ross McKenzie ValuSoft Melbourne Australia

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

whoops, sorry boss - already did.

- Dan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

... and so the inevitable happened. Lesson learned hopefully. There is nothing quite as annoying as having to chase threads all over the site to try and get the context of a poster's story.

 

Ross McKenzie ValuSoft Melbourne Australia