All,<br><br>CHIRP checks the radio and image to make sure they are the from the same firmware. For example<br><br>Image is ' Ver BFB231 '<br>Radio is ' Ver BFB231 '<br><br>CHIRP also verifies that "Ver BFB" is in the radio_verison<br>
<br>Here's the problem with a few Baofeng UV-5R radios with BFB297 firmware. There are apparently 2 versions with BFB297 floating around.<br><br>1. Image is ' Ver BFB297 ' (works OK)<br>2. Image is 'BFB299 BFB297 ' (upload failure)<br>
<br>The upload failure is caused by the 'Ver BFB' check failure. There is no 'Ver "<br><br>A possible solution is to narrow the requirements of the check<br><br>- if "Ver BFB" not in radio_version:<br>
+ if "BFB" not in radio_version:<br><br>There would still be an issue of one type of BFB297 radio not being able to load the 'aux block' of the other type. I believe that is could be overcome by limiting the part of the string that is matched<br>
<br>- image_version = _firmware_version_from_image(radio)<br>- radio_version = _get_radio_firmware_version(radio)<br>+ image_version = _firmware_version_from_image(radio)[7:]<br>+ radio_version = _get_radio_firmware_version(radio)[7:]<br>
<br>Which should make the comparison like this<br><br>Image is 'BFB297 '<br>Radio is 'BFB297 '<br><br>Is it safe to swap the 'aux blocks' of this two similar firmware versions? I don't know. Maybe. Every other part of the 'aux block' is identical between the two images. But that is at the 'factory' delivered state.<br>
<br>Anyone else have any thoughts about this issue?<br><br>Jim<br><br>