Replies: 5 comments
-
From here: We may even be able to read the Flash and EEPROM into single hex file (currently not supported), this should be easier than ELF file.
|
Beta Was this translation helpful? Give feedback.
-
Even better, looking at
(*) The mapping of the respective fuse bytes to offset locations follows historic name convention as in This means we can, indeed, transform our .hex files to act as container files for how a part has been prepared. Above is only valid for classic parts. More modern parts have their own, different mapping into a linear address space, so clearly that mapping needs to be per part family (or is worse comes to worst) per part. Useful applications would be to make a backup of all (writeable) memories of a part in a single .hex file. And, extending the Comments welcome from those who are more AVR-literate than me: @MCUdude, @SpenceKonde, @WestfW, @dl8dtl, ... |
Beta Was this translation helpful? Give feedback.
-
The comments in PR #1206 should help as well. Comment by @stefanrueger.
(*) Not available in all parts |
Beta Was this translation helpful? Give feedback.
-
I think this feature request does not gain much traction and I will close this for now as not planned. We can always revisit this in the future if someone is interested and prepare a PR for this. |
Beta Was this translation helpful? Give feedback.
-
Close this discussion for now. |
Beta Was this translation helpful? Give feedback.
-
#1195 (comment)
@MCUdude @stefanrueger @McMCCRU @dl8dtl
PR #1195 adds a convenient way to write all the memory sections using a single elf file. (Edit --> elf may be difficult as avrdude needs to learn to write a valid ELF file).
What about memory reading?
I am thinking of a new memory name called
all
and I think it is nice to have the following command to be able to read the chip and write toan ELF filea hex file. Any comments? This can be in a new enhancement.Beta Was this translation helpful? Give feedback.
All reactions