AVRDUDE 8.0 released

[stefanrueger]

I just released version 8.0 of AVRDUDE, a new major release after 7.0 in 2022.

Since the last release 7.3 AVRDUDE has gained

• Support of multi-memory .hex/.srec files and memory lists including terminal backup and restore commands for all memories
• New terminal disasm command for disassembling code
• Strengthened libavrude library (which will probably settle over the next few releases)
• GUI implementation of AVRDUDE to demonstrate use of the libavrdude library
• New testing scripts allowing AVRDUDE to test combinations of programmer-chip pairs for all memories
• Improved infrastructure for cmake and autotools
• Support for new parts
  • AVR16DU14, AVR16DU20, AVR16DU28, AVR16DU32
  • AVR32DU14, AVR32DU20, AVR32DU28, AVR32DU32
• Support for new programmers
  • serprog
  • pickit5_updi
• Support for new serial adapters
  • ch342, ch344, ch347, ch9103

It's been a tremendous effort and particular thanks go to @dl8dtl, @MCUdude, @ndim, @mcuee, @askn37, @funkeleinhorn, @MX682X and countless others for contributions and advice.

Enjoy :)

[funkeleinhorn]

Nixpkgs Update: NixOS/nixpkgs#337100

[dl8dtl]

Congratulations to the team, and a big "Dankeschön!" to Stefan!

[mcuee]

Indeed this is great!
@stefanrueger and @MCUdude contributed most to the avrdude 8.0 release. Thanks!

[mcuee]

Good thing is that the following two github actions work nicely.
https://github.com/avrdudes/avrdude/actions/runs/10541592535 (Deploy)
https://github.com/avrdudes/avrdude/actions/runs/10541592513 (avrdude_packing_release).

@umbynos
Thanks for the help with avrdude_packing_release github action.

• Adding arduino_packing_release github action #1690

[mcuee]

Remaining issues -- mainly missing libserialport support for MSVC binaries and avrdude_packing_release build (Static linking build).

• github actions improvement #1679
• To add libserialport support to Windows MSVC build #1552

[mcuee]

Related issue:

• Avrdude 7.3 arduino/avrdude-packing#31
• Add libserialport for future avrdude release arduino/crossbuild#13

@umbynos @MCUdude @ndim

We may want to revisit the above issues now that avrdude 8.0 release has been done.

[mcuee]

@stefanrueger @MCUdude and @dl8dtl

I have added the other binaries generated by the above-mentioned github actions in the release.
https://github.com/avrdudes/avrdude/releases/tag/v8.0

[mcuee]

My build of avrdude 8.0 using the crossbuild container.
arduino/avrdude-packing#31

1. with libserialport support
   avrdude-v8.0_cross_mingw32.zip
   avrdude-v8.0_cross_linux_x64.zip
   avrdude-v8.0_cross_linux_x86.zip
   avrdude-v8.0_cross_linux_arm64.zip
   avrdude-v8.0_cross_linux_arm32.zip

[mcuee]

@MCUdude
Homebrew formula updated -- no support of libserialport and SWIG/Python though.
https://github.com/Homebrew/homebrew-core/blob/c456f8468c12f3b180610b4c78a8f09fd079867d/Formula/a/avrdude.rb

[gdkadem]

Autodetect does not work in version 8. When I point the chip manually, it reads and writes without any problems. However, when we want to use automatic detection, it cannot find the chip.

[mcuee]

Autodetect does not work in version 8. When I point the chip manually, it reads and writes without any problems. However, when we want to use automatic detection, it cannot find the chip.

Please help to provide more details. It is better that you create a new issue and provide the details. Thanks.

[gdkadem]

When I type "avrdude.exe -c pickit2 -B 4.00 -p m8" without doing anything,
it returns the result "WARNING: Unable to detect MCU".
But when I manually select the processor and select read/write/verify, the process goes smoothly.
"avrdude.exe -c pickit2 -p m8 -B 4.00 -U flash:v:"C:\Users\acer.acer-Computer\Downloads\usbasp.atmega8.2018-06-25.hex":i Verifying 4646 bytes of flash against input file usbasp.atmega8.2018-06-25.hex Reading | ###################################### | 100% 2.12s 4646 bytes of flash verified"

VID_20240928_100753.mp4

I tried the same thing with USBASP. Same problems occur again.

[mcuee]

Please use the command line and not the GUI avrdudess. I think this is a known problem of arvduess.

• Improve MCU auto-detect ZakKemble/AVRDUDESS#26

[MCUdude]

@mcuee I'm thinking about bunding the statically built Avrdude binaries to a new version of my Arduino cores. However, I can't execute the macOS binary, because it has been released by an unauthorized developer. What to do? And how did @umbynos get around this when building "Arduino flavored" Avrdude binaries?

[mcuee]

@mcuee I'm thinking about bunding the statically built Avrdude binaries to a new version of my Arduino cores. However, I can't execute the macOS binary, because it has been released by an unauthorized developer. What to do? And how did @umbynos get around this when building "Arduino flavored" Avrdude binaries?

@MCUdude

You have to sign up with Apple Developer program and then you can sign the binaries with the Code-Signing Certificate.

Reference:
https://github.com/arduino/avrdude-packing/blob/main/.github/workflows/release.yml

The annual fee is US$99.
https://developer.apple.com/support/enrollment/

Maybe it is not worth the trouble and we may still ask @umbynos for help to release newer version of avrdude binary in the Arduini avrdude-packing git repo.

[mcuee]

@MCUdude and @umbynos

I have added to the comment here about the issue with Code-Signing Certificate for macOS.

• Avrdude 7.3 arduino/avrdude-packing#31

[umbynos]

Hey, yeah, is because of code-signing. We got a certificate from Apple Dev program and we use that to sign binaries (CLI/IDE)..

[MCUdude]

@mcuee libserialport 0.1.2 has just been released, and is available though macOS Brew. Currently, Avrdude is built without libserialport support when using brew. What would it take to fix this?

https://github.com/sigrokproject/libserialport/releases

[mcuee]

Technically we can build libserialport under the crossbuild container but I have tried it and it does not work.

This was part of the discussion here.

• Avrdude 7.3 arduino/avrdude-packing#31

[MCUdude]

But a lot of users just use their package manager to install Avrdude. How can we ensure it is built with all necessary dependencies, with libserialport being the latest one?

[mcuee]

@MCUdude

For macOS users, the main package manager is probably Homebrew. There is no issue to ask Homebrew maintinaer to upgrade the formula to include libserialport dependency. You may need to raise a ticket.
https://github.com/Homebrew/homebrew-core/blob/2c65c99efc0565df5972e11d07b175ad7a9d4e18/Formula/a/avrdude.rb

The other thing is to ask Homebrew maintainer to update libserialport version (maybe they will upgrade soon). You can raise a ticket as well to speed up the adoption.
https://github.com/Homebrew/homebrew-core/blob/2c65c99efc0565df5972e11d07b175ad7a9d4e18/Formula/lib/libserialport.rb

[mcuee]

@MCUdude
You can also raise a PR towards Homebrew project to update the formula.
https://github.com/Homebrew/homebrew-core/pulls

[mcuee]

I am not using macPorts but it does include libserialport dependency. But the version is only at avrdude 7.3. And the page mentioned that there is no maintainer.
https://ports.macports.org/port/avrdude/details/