* Fix writing BOOTROW for Curiosity Nano by @askn37
* Terminal writes to bootrow will do a read/CE/write cycle if needed by @stefanrueger
Co-authored-by: Stefan Rueger <stefan.rueger@urclocks.com>
On -x random dyrun will use only (random) opcodes that
- The AVR architecture actually has
- Are benign, ie, not reading/writing I/O or SRAM
- Stay within the boundaries of the application
This transfers the information from the CMakeLists.txt
libavrdude VERSION and SOVERSION into the autotools
configure script and (partly) uses the information to
build the libavrdude.la libtool library.
At this time, VERSION must always be SOVERSION.0.0 for
this to work (and that is checked).
As libtool is supposed to be able to build libraries for every
target system, we delegate library building to libtool and stop
building our own static libavrdude.a library.
You can control whether the static/dynamic library is built by
using the --(disable|enable)-(static|dynamic) configure flags.
As no-dist-built-files was only introduced in Automake 1.16.4,
we cannot rely on that feature being present and need to continue
using our own workaround.
This hooks the dist-hook in a more robust fashion in the face
of multiple dist-hook targets (and versioninfo.mk already uses
one).
Guard m4 macro calls with m4_pattern_forbid for all
macros which do not come with Autoconf/Automake.
All other macros might not be present on the system,
and it is better to m4_pattern_forbid them and have
autoreconf fail, than to have autoreconf generate a
malformed broken configure script which then always
fails with a weird error message.
Elaborate a bit more on the VERSIONINFO_* and versioninfo_*
m4 macros. This should help me get back into things when I
come back to this in a year or so and have forgotten most
of the details.
Different parts read unused fuse bits back with different bit default
values, the ATDF files don't necessarily document this correctly.
Rather than showing a warning that is ignored make this a debug message.
