I would find usefull having a way to inspect full _memobj content, I mean see how the full MEM_FORMAT apply to actual memory contents.
my two cents ...
73 de IZ3GME Marco
On 01/11/2012 17:19, Dan Smith wrote:
The "show raw memory" feature tells me two things that hexdump doesn't:
- the I'm seeking to the right position
- that I have correctly defined the structure in Chirp's bitwise syntax
It's more of a Chirp integration test than an exploration tool.
Sorry, I misinterpreted. You mean something to take an existing setting and dump the raw memory for it? I thought you were talking about just replacing hexdump functionality for whole-image diff'ing.
Settings are not directly mapped to a chunk of memory in the same way, so I don't think there's any reasonable path to go from the abstract setting object to the memory chunk it represents. If you can figure out a way (or a reasonable change) then that might be doable.
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel