Re: [chirp_devel] Wouxun KG-UV6D memory map available

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.