Bug #5207
closedBaofeng UV-5R Programming write error different blocks
0%
Description
What happens is when you try to write it gives a random unable to write to block error
CHIRP daily-20170714 on Linux - Ubuntu 17.04 (Python 2.7.13)
Have tried both of the programming cables that I have used for multiple radios with the same result.
I purchased a 5 pack from amazon. I am having the same issue with one of the 5 radios. The radio that has the issue has the following:
FW message 1 = HN5RV01
FW message 2 = 1
Power on firmware message is: BFB297
All of the other radios in that pack have:
FW message 1 = HN5RV01
FW message 2 = 1FB297
Power on firmware message is: BFB297
Updated by Will Chirp over 7 years ago
I am not sure if http://chirp.danplanet.com/issues/5107 is related.
Updated by Bernhard Hailer over 5 years ago
- Subject changed from Programming write error different blocks to Baofeng UV-5R Programming write error different blocks
- Model affected changed from UV5R to Baofeng UV-5R
Updated by Bernhard Hailer about 5 years ago
- Status changed from New to Incomplete
Have you been able to resolve this on your own since you submitted this?
Chirp will not allow you to write an image created with one firmware version to a radio with another firmware version.
That's for a good reason: some changes in the firmware might cause values to be written into places which might now be invalid - you'd brick your radio.
What you can do is to download from your radio, then import the other image and upload that back.
Updated by Bernhard Hailer almost 5 years ago
This could also be a cable / driver / connector issue. Please refer to these Wiki articles:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]
If there's no solution to be found in any of them, please read: How To Report Issues and provide a debug log. Thank you!
Windows notes: If you are using a generic cable with a Prolific chip, you will very likely need to downgrade your driver to version 3.2.0.0.
It can be found at http://www.miklor.com/COM/UV_Drivers.php
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
You must have the KK7DS Python runtime for Mac OSX installed.
Also see MacOS Tips!
Linux notes: Linux generally is quite good with USB to Serial converter drivers. The most likely cause for grief is a connector which doesn't provide good electrical contact.
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.
Updated by Bernhard Hailer almost 5 years ago
- Status changed from Incomplete to Closed
No more feedback by submitter.