Bug #10613
open[ERROR Firmware version does not match] Programming Baofeng UV82 over writes memory offset holding read only firmware version to blank
0%
Description
[ERROR Firmware version does not match] Programming Baofeng UV82 over writes memory offset holding read only firmware version to blank.
version CHRIP next-20230601 on Python 3.10.8 wxPython 4.2.0 msw (phoenix) wxWidgets 3.2.0
Steps to reproduce
- read in factory default radio programming using Chirp Next; note in "Settings" under "Other Settings" the line "Firmware Message 1" shows version "N82-33"
- add a new channel
- save file for later use
- write back file, programming is successful
- read back again from radio, note in "Settings" under "Other Settings" the line "Firmware Message 1" is now blank
- update/add channel to saved file in step 3 and then use this file to update radio - Firmware error message is shown and radio not updated (see attached file for screen shot)
Full log file also attached
Files
Updated by Jeff Breazile 11 months ago
- File Baofeng_UV-82HP_20230601.img Baofeng_UV-82HP_20230601.img added
- File Test1.2_Baofeng_UV-82HP_20230530.img Test1.2_Baofeng_UV-82HP_20230530.img added
attaching image files, where you can see the version read back after first programming "Baofeng_UV-82HP_20230601.img" the firmware message in settings memory offset is blank. In file "test1.2_Baofeng_UV-82_20230530.img" which is the original download of factory new radio, yes I know the file name has "0530" that was my mistake when creating the new .img, it was created with 0601 CHIRP next. Anyway this second file shows the firmware message at memory offset with "N82-33".
If you use the fist file, it works on a factory new or already programmed radio.
If you try to use file 2 on a factory new radio it works, on a radio that has already been programmed it fails with firmware mismatch error
This behavior is also seen on CHIRP next version 20230530
Updated by Jeff Breazile 11 months ago
One more detail for clarity, the file attached "test1.2_Baofeng_UV-82_20230530.img" this is the file described in step 3 in instructions to reproduce failure, it is the original read from the factory new radio, with new channels added, and showing the firmware version.
Updated by Jeff Breazile 11 months ago
I think I see the issue, I will post screen shots of the binary dump of all .img files when my other system comes back online. It appears that CHIRP-next is over writing the memory location of the firmware version in byte 0x1829. If I diff the two .img files I attached you can see after programing and reading back the radio, this byte is now empty, but on the original read/clone of a factory new radio this byte (0x1829) contains the firmware version string.
If I modify in "Settings" "Welcome Message 1" this value appears and over writes the byte location 0x1829 where the firmware string originally was.
If I leave the default "Welcome Message 1" blank and just add a new channel, you see this byte location where the firmware version string was is now blank.
Sorry I don't think I have time to clone your repo and submit a patch, hopefully this is enough to quickly fix the issue.
Updated by Jeff Breazile 11 months ago
tested this flow on Baofeng BF-F8HP and it works as expected, no issues. Tested on Linux: Ubuntu 22.04.2 LTS
Also tested the UV-82HP on Linux: Ubuntu 22.04.2 LTS, same behavior, complains about Firmware mismatch and over writes memory location for firmware string with the value of "Power-On Message 1" in settings under "Other Settings"
for all Linux testing used Chirp next-20230601 on Python 3.10.6 wxPython 4.0.7 gtk3 (phoenix) wxWidgets 3.0.5