As Joerg Wunsch wrote: > Instead of trying to figure out the file offset from the first > record of the file, pass it on to the read routine, based on > the device and memory configuration. If the device is an > AVR32, the memory offset (which has already been present in > avrdude.conf anyway) is expected to be present in the file > itself. > > This is now also implemented in the S-record routine (which > completely lacked a similar logic before), as well as in the > routines to write back Intel hex or S-record files.
To everyone on the list: please test this to ensure I did not introduce any regressions with that. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ avrdude-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avrdude-dev
