[chirp_devel] Wouxun KG-UV6D memory map available

[Tom Hayward]

On Thu, Nov 1, 2012 at 9:26 AM, Johan Adler <johan.adler at gmail.com> wrote:
> I would love to participate. I am not all familiar with the existing
> codebase and conventions, byt I know a bit or two about programming
> (major hobby of mine for more than 30 years).
>
> Is there som git/cvs system set up for cooperative coding, or am I
> supposed to check out a newish version, transplant my patches, run a
> new diff and post the result?

http://chirp.danplanet.com/projects/chirp/wiki/Developers

You pull code from the Mercurial reposititory, and submit new code as
patches to this list. Mercurial's mq extension makes managing your
patches simple, then you can send them with the Patchbomb extension.

> I started a new project, mapping the areas that are still unknown to
> me for different models/firmware for a chance to spot differences.
> Basically I make a hexdump using xxd for the unknown areas, making it
> easier to run a diff without being confused by any known setting being
> different. The files are uploaded to the issue section, I guess, so
> look for the there.

I use hexdump+diff for initial analysis, then move to Chirp's "show
raw memory" as soon as possible. This doesn't really apply to
settings--Dan, is there a show raw memory equivalent useful for
settings?

> I may not find it a bit useful myself, but it would be a nice hack to
> implement (at least) read support for Wouxun proprietary .wx format.
> The KG-UV Commander has it. there is some information available in
> Yahoo groups.

I found the format used by the VX-* Commander programs is identical to
Chirp's .img format (clone dump) for the corresponding radios. This
made it very easy to support in Chirp. Maybe .wx is the same?

Tom KD7LXL