AVRDUDE 6.0 released

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

More than two years after the previous release (5.11.1), AVRDUDE 6.0
finally made it to go public.

I'd like to thank everyone who has been involved into that release,
both active developers with SVN access as well as numerous users who
contributed bugfixes, improvements and suggestions.

The primary reason for the major version number bump was a changed
syntax of the configuration file (programmer types are now strings
rather than keywords), but that version number change has certainly
also "raised the bar" about many other things that should have been
done before releasing it. Among those are:

  • direct reading of ELF files (provided libelf with its header files is around when ./configure runs)

  • keep track of input file contents; when programming just a bootloader only, nothing else but the bootloader area is touched

  • config file can refer to a "parent" device; this dramatically simplifies the config file as only those things that have been
    changed compared to the parent must be specified anew

As an experiment, I'm trying to provide an "official" Win32 binary
release for the first time. It has been compiled using a MinGW32
cross-compilation environment on my FreeBSD host system. If this
turns out to be a complete failure, please tell me, so I can stop this
experiment, and leave Windows binaries to those who know more about
the matter than me. If it works, you might want to tell me
nevertheless, so I might continue that service in future.

Here are the complete release notes for 6.0 (from the NEWS file):

  * Major changes compared to the previous version:

    - Programmer types in configuration file are no longer keywords but
      specified as string.

      So you need to change 'type = XYZ;' to 'type = "XYZ";' in own
      config files.  (internal: The parser does not need to know all
      programmer types now, new programmers will update only the table
      in pgm_type.c.)

    - The erase cycle counter (formerly options -y / -Y) has been
      removed.

    - Specifying a -U option without a memory type (short form of
      option argument list) now defaults to "application" memory for
      Xmega devices, and "flash" for everything else.  This ensures
      the Xmega bootloader is not accidentally touched.

    - For programmers that support it, the default erase method is a
      page erase now, rather than a chip erase (Xmega only).

    - Keep track of input file contents
      Memory segments are being tracked to remember whether they've
      been actually read from a file.  Only segments that came from a
      file are being programmed into the device, or considered for
      verification.  This drastically improves handling speed for
      sparse files (e.g. files that have a second bootloader segment),
      and it ensures the device contents is actually compared for
      everything mentioned in the file (even in case the file has
      large 0xFF blocks).

    - The -U option now accepts ELF files as input files, and extracts
      the appropriate section contents that matches the requested memory
      region.  To enable this feature, the host system used for the
      compilation must have a libelf around, including the respective
      header files (i.e., package "libelf-devel" on many Linux systems).

    - Programmers and parts lists

      They are now sorted at output with '-c ?'/'-p ?'. (patch #7671:
      Sorting programmers and parts lists for console output)

      Programmers and parts lists in documentation generated from lists
      mentioned above. (patch #7687: Autogenerating programmers and
      parts lists for docs)

      Output list of programmer types with '-c ?type', add list to
      documentation

    - Configuration files now accepts parent parts/programmers, parts
      starting with '.' (eg. .xmega) are not included in output parts
      list and can be used as abstract parents

      (bug #34302: Feature request : device configuration with parent classes)
      (patch #7688: Implement parent programmers feature)

    - Additional config files which are read after default can be
      specified on command line using '-C +filename'

      (patch #7699 Read additional config files)

    - "Safemode" can now be turned off by default from within a
      configuration file (like ~/.avrduderc).

    - The new option -l logfile allows to redirect diagnostic messages
      to a logfile rather than stderr.  Useful to record debugging
      traces, in particular in environments which do not offer
      shell-style redirection functionality for standard streams.

    - When leaving debugWIRE mode, immediately retry with ISP rather
      than bailing out completely.

    - The USBasp programmer implementation now supports detailed traces
      with -vvv, and device communication traces with -vvvv.

    - The "verbose" terminal mode command allows to query or modify the
      verbosity level.

  * New devices supported:
    - ATmega48P (patch #7629 add support for atmega48p)
    - AT90PWM316 (bug #21797: AT90PWM316: New part description)
    - ATxmega16D4, ATxmega32D4, ATxmega64D4, ATxmega128D4
    - ATmega256RFR2, ATmega128RFR2, ATmega64RFR2, ATmega2564RFR2,
      ATmega1284RFR2, ATmega644RFR2
    - ATtiny1634
    - ATxmega128A1U, ATxmega128A3U, ATxmega128A4U, ATxmega128B1,
      ATxmega128B3, ATxmega128C3, ATxmega128D3, ATxmega16A4U,
      ATxmega16C4, ATxmega192A3U, ATxmega192C3, ATxmega192D3,
      ATxmega256A3BU, ATxmega256A3U, ATxmega256C3, ATxmega256D3,
      ATxmega32A4U, ATxmega32C4, ATxmega384C3, ATxmega384D3,
      ATxmega64A1U, ATxmega64A3U, ATxmega64A4U, ATxmega64B1,
      ATxmega64B3, ATxmega64C3, ATxmega64D3
    - ATtiny43U
    - ATmega406
    - ATxmega8E5, ATxmega16E5, ATxmega32E5
    - ATtiny20, ATtiny40

  * New programmers supported:
    - linuxgpio
      + any (embedded) Linux system with 4 GPIOs available can be used
        as a programmer with little or no additional hardware.

    - avrftdi
      + o-link (patch #7672 adding support for O-Link (FTDI based
        JTAG) as programmer)
      + 4232h (patch #7715 FT4232H support)
    - TPI support
      + openmoko (bug #37977 Support for Openmoko Debug Board)

    - usbasp
      + nibobee (previously specified as '-c usbasp -P nibobee)
      + usbasp-clone (same as usbasp but ignores vendor and product
        string, checks only vid/pid)

    - ftdi_syncbb (new type for synchronous bitbanging with ft232r/ft245r)
      + ft245r (FT245R Synchronous BitBang, miso = D1, sck = D0, mosi
        = D2, reset = D4)
      + ft232r (FT232R Synchronous BitBang, miso = RxD, sck = RTS,
        mosi = TxD, reset = DTR)
      + bwmega (BitWizard ftdi_atmega builtin programmer, miso = DSR,
        sck = DCD, mosi = CTS, reset = RI)
      + arduino-ft232r (Arduino: FT232R connected to ISP, miso = CTS
        X3(1), sck = DSR X3(2), mosi = DCD X3(3), reset = RI X3(4))
      + diecimila (alias for arduino-ft232r)

    - pickit2

    - Atmel JTAGICE3

    - buspirate_bb (TPI programming using the BusPirate in bitbang mode)

  * Bugfixes
      - bug #34027: avrdude AT90S1200 Problem
      - bug #34518: loading intel hex files > 64k using record-type 4
      - patch #7667: Minor memory handling fixes
      - patch #7680: Fixing timeout problem in ser_recv in ser_win32.c
      - patch #7693: Fix config file atmel URLs (+ URLs in
        avrdude.texi and avrpart.h)
      - bug #21663: AT90PWM efuse incorrect, bug #30438: efuse bits
        written as 0 on at90pwmxx parts
      - bug #35261: avrftdi uses wrong interface in avrftdi_paged_(write|load)
      - patch #7437 modifications to Bus Pirate module
      - patch #7686 Updating buspirate ascii mode to current firmware,
        use AUX as clock generator, and setting of serial receive
        timeout
      - bug #34768 Proposition: Change the name of the AVR32 devices
      - patch #7718: Merge global data of avrftdi in a private data
        structure
      - bug #35208: avrdude 5.11 on freebsd 8.2-STABLE does not reset
        Arduino Uno properly
      - bug #34518: loading intel hex files > 64k using record-type 4
        (Extended Linear Address Record)
      - bug #34027: avrdude AT90S1200 Problem
      - bug #30451: Accessing some Xmega memory sections gives not
        supported error
      - bug #28744: Can't load bootloader to xmega128a1
      - bug #29019: pagel/bs2 warning when uploading using stk500 to xmega
      - bug #30756: When setting SUT to 64ms on XMEGA, avrdude doesn't
        read device signature
      - bug #37265: wrong page sizes for XMega64xx in avrdude.conf
      - bug #37942: Latest SVN can't program in dragon_jtag mode
      - patch #7876 JTAGICE mkII fails to connect to attiny if debugwire
        is enabled AND target has a very slow clock
      - bug #39893: Verification failure with AVRISPmkII and Xmega
      - bug #38713: Compilation of the documentation breaks with texinfo-5
      - bug #38023: avrdude doesn't return an error code when attempting
        to upload an invalid Intel HEX file
      - bug #39794: warnings when building avrdude 6.0rc1 under CentOS 6.4
      - bug #35800: Compilation error on certain systems if parport is disabled
      - bug #38307: Can't write usersig of an xmega256a3
      - bug #38580: Current svn head, xmega and fuses, all fuses tied to fuse0
      - bug #39691: Buffer overrun when reading EEPROM byte with JTAGICE3
      - bug #38951: AVR109 use byte offset instead of word offset
      - patch #7769: Write flash fails for AVR910 programmers
      - bug #38732: Support for ATtiny1634
      - bug #36901: flashing Atmega32U4 EEPROM produces garbage on chip
      - bug #28344: chip_erase_delay too short for ATmega324P, 644, 644P, and 1284P
      - bug #34277: avrdude reads wrong byte order if using avr911 (aka butterfly)
      - bug #35456: The progress bar for STK500V2 programmer is "wrong".
      - patch #5708: avrdude should make 10 synchronization attempts instead of just one
      - patch #7606: ATtiny43u support
      - patch #7657: Add ATmega406 support for avrdude using DRAGON + JTAG
      - bug #35474: Feature request: print fuse values in safemode output.
      - patch #7710: usb_libusb: Check VID/PID before opening device
      - [no-id]: Fix SCK period adjustment for STK500v2
      - bug #40040: Support for ATtiny20 and ATtiny40

  * Internals:

    - Restructuring and compacting programmer definition part of
      grammar for config file.
    - Cleanup of parser code, removing unused definitions/
      functions. Using yylex_destroy if available.
    - Fixed some more memory leaks, added cleanup code at program exit
      (to minimize the number of non-freed memory blocks reported by
      valgrind)
    - Fixed some findings reported by cppcheck.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

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

Sorry, there's been a really stupid bug, so I re-rolled the relase as 6.0.1.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

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

Nice one Jörg.

Quote:

* New programmers supported:
- linuxgpio
+ any (embedded) Linux system with 4 GPIOs available can be used
as a programmer with little or no additional hardware.

I smell RasPI .... :-)

/Bingo

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

The .nl mirror still haven't gotten 6.0.1.

Other Savannah mirrors can be found here
http://download-mirror.savannah....

I chose a .no mirror ,and got the 6.0.1 from there

/Bingo

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

Just build it :-)
And remembered to install "libelf-devel"

Configuration summary:
----------------------
DO HAVE    libelf
DO HAVE    libusb
DO HAVE    libusb_1_0
DON'T HAVE libftdi1
DO HAVE    libftdi
DON'T HAVE libhid
DO HAVE    pthread
DISABLED   doc
ENABLED    parport
DISABLED   linuxgpio

..
..
..
make[2]: Leaving directory `/usr/local/avr/build/avrdude-6.0.1'
make[1]: Leaving directory `/usr/local/avr/build/avrdude-6.0.1'
make  install-recursive
make[1]: Entering directory `/usr/local/avr/build/avrdude-6.0.1'
Making install in .
make[2]: Entering directory `/usr/local/avr/build/avrdude-6.0.1'
make[3]: Entering directory `/usr/local/avr/build/avrdude-6.0.1'
 /bin/mkdir -p '/usr/local/avr/bin'
  /usr/bin/install -c avrdude '/usr/local/avr/bin'
Backing up avrdude.conf in /usr/local/avr/etc
 /bin/mkdir -p '/usr/local/avr/etc'
 /usr/bin/install -c -m 644 avrdude.conf '/usr/local/avr/etc'
 /bin/mkdir -p '/usr/local/avr/share/man/man1'
 /usr/bin/install -c -m 644 ../../source/avrdude-6.0.1/avrdude.1 '/usr/local/avr/share/man/man1'
make[3]: Leaving directory `/usr/local/avr/build/avrdude-6.0.1'
make[2]: Leaving directory `/usr/local/avr/build/avrdude-6.0.1'
make[1]: Leaving directory `/usr/local/avr/build/avrdude-6.0.1'
Making clean in .
make[1]: Entering directory `/usr/local/avr/build/avrdude-6.0.1'
test -z "avrdude" || rm -f avrdude
test -z "config_gram.c config_gram.h lexer.c" || rm -f config_gram.c config_gram.h lexer.c
test -z "libavrdude.a" || rm -f libavrdude.a
rm -f *.o
make[1]: Leaving directory `/usr/local/avr/build/avrdude-6.0.1'
 $ avrdude -v

avrdude: Version 6.0.1, compiled on Sep 18 2013 at 18:50:17
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "/usr/local/avr/etc/avrdude.conf"
         User configuration file is "/home/cfo/.avrduderc"
         User configuration file does not exist or is not a regular file, skipping


avrdude: no programmer has been specified on the command line or the config file
         Specify a programmer using the -c option and try again

/Bingo

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

Hi Jörg,

good job.

tf

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

> I smell RasPI .

That's the most prominent one, but there are more of these.
I've seen one board with a MIPS processor as well.

I've got no idea how good/bad this is doing, the linux-gpio
stuff has been contributed by users.

> The .nl mirror still haven't gotten 6.0.1.

Meanwhile, they caught up.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

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

dl8dtl wrote:
> I smell RasPI .

That's the most prominent one, but there are more of these.
I've seen one board with a MIPS processor as well.

I've got no idea how good/bad this is doing, the linux-gpio
stuff has been contributed by users.

> The .nl mirror still haven't gotten 6.0.1.

Meanwhile, they caught up.

Jörg how do i enable the Linux-gpio ...
Is it on the ./configure ?

Im lazy (blush) ...

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
$ ./configure --help | grep gpio
  --enable-linuxgpio      Enable the Linux sysfs GPIO interface programmer
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

He..He

Clever & lazy :-)

Thnx

/Bingo

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

I am having some issues with the new windows version and programing an xmega128a1u with a 911 compatible bootloader. I am using the following syntax on the command line:

avrdude -V -v -c avr911 -p x128a1u -P com24 -b 19200 -U flash:w:b1.hex

I get this command line output:

avrdude: Version 6.0.1, compiled on Sep 18 2013 at 08:20:41
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "C:\avrdude\601\avrdude.conf"

         Using Port                    : com24
         Using Programmer              : avr911
         Overriding Baud Rate          : 19200
         AVR Part                      : ATxmega128A1U
         Chip Erase delay              : 0 us
         PAGEL                         : P00
         BS2                           : P00
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 0
         StabDelay                     : 0
         CmdexeDelay                   : 0
         SyncLoops                     : 0
         ByteDelay                     : 0
         PollIndex                     : 0
         PollValue                     : 0x00
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
           prodsig        0     0     0    0 no         50   50      0     0     0 0x00 0x00
           fuse1          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse2          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse4          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse5          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           lock           0     0     0    0 no          1    0      0     0     0 0x00 0x00
           data           0     0     0    0 no          0    0      0     0     0 0x00 0x00
           eeprom         0     0     0    0 no       2048   32      0     0     0 0x00 0x00
           application    0     0     0    0 no     131072  512      0     0     0 0x00 0x00
           apptable       0     0     0    0 no       8192  512      0     0     0 0x00 0x00
           boot           0     0     0    0 no       8192  512      0     0     0 0x00 0x00
           flash          0     0     0    0 no     139264  512      0     0     0 0x00 0x00
           usersig        0     0     0    0 no        512  512      0     0     0 0x00 0x00
           fuse0          0     0     0    0 no          1    0      0     0     0 0x00 0x00

         Programmer Type : butterfly
         Description     : Atmel AppNote AVR911 AVROSP

Connecting to programmer: .
Found programmer: Id = "BtLdr"; type = S
    Software Version = 1.0; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=512 bytes.

Programmer supports the following devices:
    Device code: 0x7b

avrdude: devcode selected: 0x7b
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude: Device signature = 0x1e974c
avrdude: NOTE: Programmer supports page erase for Xmega devices.
         Each page will be erased before programming it, but no chip erase is performed.
         To disable page erases, specify the -D option; for a chip-erase, use the -e option.
avrdude: reading input file "b1.hex"
avrdude: input file b1.hex auto detected as Intel Hex
avrdude: writing flash (798 bytes):

Writing | #########################                          | 50% 0.00s ***failed;
 ***failed;
 ***failed;
"A bunch of the same failed messages here"
 ***failed;
 ***failed;
Writing | ################################################## | 100% 0.33s

avrdude: 798 bytes of flash written

avrdude done.  Thank you.

This is my serial spy output of the avrdude transaction:

WRITE--1b-------"."
WRITE--53-------"S"
READ---42 74 4c 64 72-"BtLdr"
WRITE--56-------"V"
READ---31 30----"10"
WRITE--76-------"v"
READ---3f-------"?"
WRITE--70-------"p"
READ---53-------"S"
WRITE--61-------"a"
READ---59-------"Y"
WRITE--62-------"b"
READ---59-------"Y"
READ---02-------"."
READ---00-------"."
WRITE--74-------"t"
READ---7b-------"{"
READ---00-------"."
WRITE--54 7b----"T{"
READ---0d-------"."
WRITE--50-------"P"
READ---0d-------"."
WRITE--73-------"s"   <-Signature check
READ---4c 97 1e-"L—." <-Signature reply
WRITE--4c-------"L"   <-Exiting Program mode..why?!
READ---0d-------"."
WRITE--45-------"E"
READ---0d-------"."

It seems like avrdude is just giving up after the checking the device signature. It doesn't even attempt to address or block write to the device.

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

Just to see if this was a windows problem I spent the day installing virtualbox and a Ubuntu 12.04.3 guest OS. I then compiled the latest avrdude tar and ran it in Ubuntu.

I get the same exact error. I even have my FTDI TTL-232RG-VIP-WE usb to serial converter attached to Ubuntu now although I also tried just passing the serial port through the windows host OS.

Note that I have a windows compiled avrdude 5.11 that works fine on the same setup.

Can anyone confirm or deny if serial programing is broken in this version? Do I have some unknown gremlins mucking up just my setup?

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

I am trying to put as much information out there as I can. Sorry if I am coming off as talking to myself here...

I ran some avrdude internal logs and attached them. Note the command line I used was:

avrdude -vvvv -V -c avr911 -p x128a1 -P com7 -b 19200 -l log01.txt -U flash:w:b1.hex

I just learned about the -vvvv option in my searching around for answers or I would have included it earlier. These seem to mirror my software serial spy data from earlier exactly. In both cases there is no attempt to even write data after the signature is acquired.

Attachment(s): 

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

Please open a bug tracker item on savannah, and attach your data there.

Thanks!

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

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

Relevant to the use of Eclipse AVR Plugin with avrdude 6.0.1
keestux has provided an updated AVR Plugin.

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

Where can I download avrdude 6? All I can find are sites that have endless "Download" buttons that lead to more "Download" buttons and advertisements.

Thanks

Don't Let the smoke out!

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

Jassper wrote:
Where can I download avrdude 6? All I can find are sites that have endless "Download" buttons that lead to more "Download" buttons and advertisements.

Thanks


At this link you can click on Download at the top of the page and then choose the version you want:

http://savannah.nongnu.org/forum...

Or you can get the latest, as of this post date, windows avrdude.exe and avrdude.conf, at this link:

http://download.savannah.gnu.org...

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

larryvc wrote:
Jassper wrote:
Where can I download avrdude 6? All I can find are sites that have endless "Download" buttons that lead to more "Download" buttons and advertisements.

Thanks


At this link you can click on Download at the top of the page and then choose the version you want:

http://savannah.nongnu.org/forum...

Or you can get the latest, as of this post date, windows avrdude.exe and avrdude.conf, at this link:

http://download.savannah.gnu.org...

Ahh ok, I just over looked it then. I did find that site too, but all I saw was the files at the very bottom and those are just documentation. Didn't see the avrdude-6.1-svn-20131205-mingw32.zip file further up the list.

Thanks!!!

Don't Let the smoke out!

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

Jassper wrote:
Didn't see the avrdude-6.1-svn-20131205-mingw32.zip file further up the list.
CTRL-F is always your friend on long directory listings, and any page for that matter.

"Experience is what enables you to recognise a mistake the second time you make it."

"Good judgement comes from experience.  Experience comes from bad judgement."

"Wisdom is always wont to arrive late, and to be a little approximate on first possession."

"When you hear hoofbeats, think horses, not unicorns."

"Fast.  Cheap.  Good.  Pick two."

"We see a lot of arses on handlebars around here." - [J Ekdahl]

 

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

Hi,

I'm trying to install avrdude 6.0.1 but I can'd resolve the following items:
Configuration summary:
----------------------
DO HAVE libelf
DO HAVE libusb
DO HAVE libusb_1_0
DON'T HAVE libftdi1 <<<<
DO HAVE libftdi
DON'T HAVE libhid <<<<
DO HAVE pthread
DISABLED doc
ENABLED parport
DISABLED linuxgpio

libftdi1 is installed but is version 0.20
libhid doesn't appear to be supported on debian wheezy so it seems.

if I attempt make install I get:
$make install
/bin/bash ./ylwrap config_gram.y y.tab.c config_gram.c y.tab.h `echo config_gram.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output config_gram.output -- yacc -d
./ylwrap: line 176: yacc: command not found
make: *** [config_gram.c] Error 127

Can anyone point me the right direction?

Regards,
BarkingHatstand

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

Quote:

yacc: command not found

You do not have YACC installed?

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

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

Have a look at the top of this forum and a sticky thread about building avr-gcc 4.5.1. In the three attachments one mentions avrdude 6.01. I haven't tried it but I think Bingo's scripts start by pulling in all the dependencies you need.

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

Great work and i made a decide to try it...
I download windows version and try to use. First of all - it's incompatible with old config file. It's ok. I solve it. After that i tried to get answer from mcu throw the my ft232rl programmer which i used with old version (5.11).
And i got error that: no pthread support installed...

>avrdude -t -c B248 -p atmega168p -P ft0 -vvv

avrdude: Version 6.1-svn-20131205, compiled on Dec  5 2013 at 17:34:22
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "D:\#Project\avrdude.conf"

         Using Port                    : ft0
         Using Programmer              : B248
avrdude: error: no pthread support. Please compile again with pthread installed. See http://sourceware.org/pthreads-win32/.
avrdude: programmer operation not supported

avrdude done.  Thank you.

What can i do with it?

my programmer section in config looks like:

programmer
  id    = "B248";
  desc  = "FT232R based programmer";
  type  = "ftdi_syncbb";
  connection_type = usb;
  miso  = 4;
  sck   = 2;
  mosi  = 6;
  reset = 5;
  buff = 3;
;
Last Edited: Sun. Mar 2, 2014 - 02:53 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yesterday i tried to build avrdude 6.0rc1 with Cygwin. I made it after 10 hours... but only with libftdi1 and libusb1 support. After start avrdude says that need libftdi support (not libftdi1)...
:(

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

VRomanM wrote:
Yesterday i tried to build avrdude 6.0rc1 with Cygwin. I made it after 10 hours... but only with libftdi1 and libusb1 support. After start avrdude says that need libftdi support (not libftdi1)...
:(

Try minGW. I had a few bumps along the way, but ultimately got a good build of 6.0.1.
http://nerdralph.blogspot.ca/201...

I have no special talents.  I am only passionately curious. - Albert Einstein

 

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

ralphd wrote:
VRomanM wrote:
Yesterday i tried to build avrdude 6.0rc1 with Cygwin. I made it after 10 hours... but only with libftdi1 and libusb1 support. After start avrdude says that need libftdi support (not libftdi1)...
:(

Try minGW. I had a few bumps along the way, but ultimately got a good build of 6.0.1.
http://nerdralph.blogspot.ca/201...

Hello, thank you for your answer.
I already made it with mingw but not in static linking. And also send infor to maintainers. It's working now but some thing with ft232r looking not good. )))

Your output of ./configure says that pthread support not installed. Am i right?
What exactly compiler installed in your mingw?

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

VRomanM wrote:
ralphd wrote:

Try minGW. I had a few bumps along the way, but ultimately got a good build of 6.0.1.
http://nerdralph.blogspot.ca/201...

Hello, thank you for your answer.
I already made it with mingw but not in static linking. And also send infor to maintainers. It's working now but some thing with ft232r looking not good. )))

Your output of ./configure says that pthread support not installed. Am i right?
What exactly compiler installed in your mingw?

You're probably right about pthread. Avrdude doesn't use it, so it shouldn't matter.

The mingw install included gcc 4.8.1:

$ gcc --version
gcc.exe (GCC) 4.8.1

I have no special talents.  I am only passionately curious. - Albert Einstein

 

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

> You're probably right about pthread. Avrdude doesn't use it, so it shouldn't matter.

The FT245 implementation requires it. That's what Roman wants to use.

Jörg Wunsch

Please don't send me PMs, use email if you want to approach me personally.

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

Since it seems you need pthread, pretty much every linux distro has libpthread, so it might be easier to do a linux build.
I did a recent avrdude build on CentOS, and it has libpthread:

Quote:
#define HAVE_PTHREAD_H 1
[root@centos64 picoboot-avrdude]# uname -a
Linux centos64 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP Fri Dec 13 13:06:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@centos64 picoboot-avrdude]# gcc --version
gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4)

I'd refer you to the x86_64 build I did, but I didn't include libftdi, so it wouldn't be any help to you.

I have no special talents.  I am only passionately curious. - Albert Einstein

 

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

Thanks evevrybody :)