[chirp_devel] [PATCH] [th_uv3r] Add support for newer 2.5kHz TYT TH-UV3R

[ag6ie at wolak.net]

I've inherited as much of the functionality as possible from the older
firmware, but it appears that the memory layout is quite different. The
older firmware uses frequency + offset, whereas the new one uses
independent TX and RX frequencies (there's some evidence online that it
supports cross-band splits...need to test that). The symptom when using
the existing CHIRP support on new radios is that the memory gets blanked
out on upload, because there's more memory on the newer units and the
layout of individual memories is different.

I think I have access to an older UV3R, so I may be able to find the
model number indication somewhere in memory. Without a few more images
from the wild, though, I'd be concerned about hitting the right spot.

On Sat, Jan 31, 2015, at 08:09 AM, Dan Smith wrote:
> > # HG changeset patch
> > # User Eric Allen <eric at hackerengineer.net <mailto:eric at hackerengineer.net>>
> > # Date 1422595106 28800
> > #      Thu Jan 29 21:18:26 2015 -0800
> > # Node ID fd4bb2f6fd60680f6f811b7573f6fef1132fa9d3
> > # Parent  bd1d2bac911911051c0a7b7f345cb6a0eba58ea7
> > Add support for new firmware in TYT TH-UV3R that supports 2.5kHz steps.
> 
> What is the actual bit that needs changing? Duplicating the driver like
> this really complicates support going forward. Can we modify the
> existing driver to support both? Normally the way we do this is look at
> something in the memory image that indicates which model it is (see, for
> example, the UV5R driver).
> 
> --Dan
> 
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)