-
Notifications
You must be signed in to change notification settings - Fork 136
FAQ
https://github.com/avrdudes/avrdude/wiki/Known-limitations-of-avrdude
https://avrdudes.github.io/avrdude/
- Create a separate issue for each problem
- Tell us what exactly the problem is and how you came to experience it
- OS
- Programmer
- Part
- How host, programmer and part are connected/rigged up
- AVRDUDE binary version used (in bash
avrdude -v 2>&1 | grep -i version) - Full command line including all options
- Output of the command
- Please try to use the latest released version
- You may be requested to try out git main as well
- Sometimes it also helps us if you upload a file with the
-vvor-vvvvoutput - Sometimes it also helps us if you post the hex file used (if you are okay to share the hex file)
- What you would have expected to happen
Latest binary snapshots are linked here, for Linux, macOS and Windows. https://github.com/avrdudes/avrdude/wiki/Getting-Nightly-Builds-for-AVRDUDE
I am new to avrdude and I do not have a programmer, what are the recommended programmers to be used with avrdude?
avrdude supports many programmers. Here are some examples of low cost and well-supported programmers.
- usbasp, usbtinyisp, stk500v2 clones, AVRISPmkII clones, etc, for classic AVRs
- AVRISP mkII clones also support xMega AVRs
- serialupdi for new UPDI parts; jtag2updi can be used as well but it does not support newer UPDI parts.
- If you prefer official tools from Microchip, then SNAP is also well supported. PICKit 4 is also well supported but it is more expensive and considered EOL by Microchip.
I have got the programmer working. Now I want to try using bootloader. Which bootloader should I use?
Survey of AVR bootloaders:
We recommend urboot for classic AVR chips.
For xmega, you may want to try xboot (AVR109 based)
For UPDI parts, you may want to try optiboot_x and optiboot_dx.
If you use USB AVRs, you may want to try Caterina (AVR109 based) or FLIP1/FLIP2 (Atmel extension to USB DFU).
As long as your USB to Serial chips are supported by the OS, they should work with avrdude. Typically the default baud rate for most programmers is 115200. 500K baud or lower are typically a good one to use if you want to go with high speed if the programmer or bootloader supports it. 1M baud or 2M baud may work as well for some programmers/bootloaders.
Notes:
- FTDI FT232RL -- you may want to change the latency timer from the default 16ms to 1ms. The chip supports up to 3M baud.
- FTDI FT232H/FT2232H -- you may want to the latency timer from the default 16ms to 1ms. The chip supports up to 12M baud.
- Silabs CP2102 or similar -- the max supported baud rate is 921600.
- Silabs CP2102N -- the max supported baud rate is 3M baud.
- WCH CH340 -- the max supported baud rate recommended by WCH is 500k dual direction. 1M baud will usually work but 2M baud has been known to not work reliably.
- WCH CH343 -- the max supported baud rate recommended by WCH is 3Mbps and HW flow control is required.
- Holtek HT42B534 -- the chip supports up to 3M baud
- Prolific PL2303TA/HXD/GS/GC/GE -- the chip supports up to 12M baud. Older version of PL2303 chip like PL2303HXA/XA are obsoleted and may not work under Windows, so it is better to avoid them.
- Microchip MCP2200 -- the max supported baud rate is 1M baud
- Maxlinear XR21B1420 -- the max supported baud rate is 3M baud
- Infineon (Cypress) CY7C65213/213A1 CY7C65223/D -- the max supported baud rate is 3M baud
It is also good to get USB to TTL adapters which have DTR and/or RTS pin if you work with bootloaders like urboot, Optiboot or Wiring.
How to change the latency timer of FTDI USB to Serial chips (eg: FT232RL, FT232H, FT2232H) from the default 16ms to 1ms?
Under Windows, go to Device Manager "Ports (COM & LPT)" and find the corresponding USB to Serial Port, in the "Advance Settings", change the latency timer value from 16ms to 1ms.
More details with screenshots. https://github.com/avrdudes/avrdude/discussions/1022#discussioncomment-8576777
For Linux, run with the root permission.
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
Note: .Replace ttyUSB0 with the right port for your system).
If you want to do more, try "terminal mode" (-t). You can browse around interactively through your device, including the fuse values. Non-interactively, it would need -U options, like:
avrdude … -U lfuse:r:-:h -U hfuse:r:-:h -U efuse:r:-:h
You can use piping.
echo "dump eeprom 0 0x10" | .\avrdude_pr1121v1 -c arduino -P COM4 -b 115200 -t
Please refer to the above issue for the ways to write all ELF sections at once. Step 1: to check the unique memory sections.
avrdude `avrdude -pATmega328p/At | grep ^.ptmm.A | cut -f3 | uniq | sed "s/.*/-U &:w:blink.elf:a/"`
Or
$ avrdude -pm32u4/ot|grep write|cut -f3|uniq
eeprom
flash
lfuse
hfuse
efuse
lock
Step 2: to write the avrdude command based on the output of Step 1.
avrdude -v -pm32u4 -cusbasp -U{eeprom,flash,{l,h,e}fuse,lock}:w:"$1":e "${@:2}"
Please refer to the following discussion for the tips under different OS.
PR #1507 has been merged to address this issue. It has been included in avrdude 7.3 release. Take note you need to use MSYS2 mingw binaries with libserialport support under Windows.
Please refer to the following issue. It has the driver attached as well.
CH340 based serialupdi programmers does not work under FreeBSD due to the driver limitation (Still an issue in FreeBSD 14).
The following is a good example for jtag2updi.
It is strongly recommended that you upgrade to V2 FW. Some of the classic AVR chips may not be supported by V1 FW (eg: ATmega32U4).