[chirp_devel] Baofeng UV-5R Variants and CHIRP v0.4.1

[Jim Unroe]

> Perhaps the upload sequence needs to have some additional safety, i.e., query target radio and compare/match some ident string on candidate image - and fail upload if they match - of course with an informative message (link to kb article, etc).

The daily build has been doing this for quite some time. It is the
v0.4.1 stable that doesn't. It was driving me nuts that people were
having trouble with their radios and it shouldn't have been happening.

>
> I think in general certain radio drivers should always do this as we have had this problem before (different radio images with similar/same radio models).

Agreed.

>
> Does anyone know if oem software does this? I think I recall seeing that the oem software only queries and stores certain portions of the radio image (not special blocks) - while certain functions that interact with special block are done in sort of a real-time fashion.

Yes. You remember correctly. The OEM software has been immune the the
memory layout changes (since the changed introduced with BFB291
firmware.

Jim