[chirp_devel] [PATCH] [UV-5R] Prevent image upload when "special block" doesn't match

[Jim Unroe]

On Fri, Jul 18, 2014 at 5:18 PM, Dan Smith <dsmith at danplanet.com> wrote:

> > [UV-5R] Prevent image upload when "special block" doesn't match
> >
> > add code to compare the data image "special block" to the radio
> > image "special block" and abort the upload if they don't match
>
> How would we ever change the special block if we can't upload it if it's
> different?
>
> --Dan
>

Nothing in is area of memory has ever been mapped to any settings. I have
no idea what this area is used for. We've never had to change any of it for
anything before.

All I know for sure is if you copy these 7 bytes from a KT-980HP or BF-F8HP
CHIRP image to any other UV-5R variant radio, the receiver is disabled. It
is actually 4 bytes (2 sets of 2 separated by 3 bytes) that cause the
issue. I could check each pair independently and abort if either pair
doesn't match. That would minimize the number of bytes affected.

Uploads of images could be prevented when the firmware versions don't
match. But that would prevent some 16 (and growing) firmware versions that
can currently share a common .img file to no longer be able to do it.

I'm definitely open to doing this some other way. Have you got any ideas or
suggestions?

Thanks,
Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20140718/750400ee/attachment-0001.html