So I tried commenting out some lines in uv5r.py

The following is a work around when I get a Radio did not respond error. I don't know what's wrong why most of the time it doesn't get the expected acknowledge return. So for the work around I assumed that the radio is responding.

#if ack != "\x06":
# if ack:
# LOG.debug(repr(ack))
# raise errors.RadioError("Radio did not respond")

When I was able to read from the radio intermittently, this solves the issue if Chirp can't get the firmware version from the memory block.

#if not any(type in radio_version for type in radio._basetype):

raise errors.RadioError("Incorrect 'Model' selected.")¶

After doing this I was able to download / upload from the radio. Now I do understand that this is dangerous since the checks are there in order to not mess with the radio's memory. Perhaps the developer, who has a deeper understanding on the software and how to program the radios, can shed more light to this.

73

Thanks,
Albert DW1ZEQ

The line

1. raise errors.RadioError("Incorrect 'Model' selected.")

should be

#raise errors.RadioError("Incorrect 'Model' selected.")

Hi Jim,

Thank you for your response. I wonder if you have an idea on what's supposed to be the line 1 and line 2 for the firmware version? I was able to update the value when I uploaded to the radio so I was thinking if I have the version expected I could write it and won't have to do with the hack anymore after that.

Thanks,
Albert

Albert Linga wrote:

Hi Jim,

Thank you for your response. I wonder if you have an idea on what's supposed to be the line 1 and line 2 for the firmware version for baofeng A58? I was able to update the value when I uploaded to the radio so I was thinking if I have the version expected I could write it and won't have to do with the hack anymore after that. I was initially looking at the ident for A58 in the module file but the values in there when converted from hex to ascii doesn't make sense as a version number

Thanks,
Albert

I wouldn't have any idea. And if I did, this region of memory is read only. So you shouldn't be able to write to it even if you knew what should be there.

Jim

Jim,

How are you comparing if the firmware version is supported? Also from what I have experienced, I was able to write on line 1 and line 2 of firmware version block. I was also expecting this block was read only , apparently it was not. I'm guessing since the manufacturer didn't write on that block, the write access restriction wasn't also specified.

Thanks,
Albert

Albert,

To be detected as a BF-F8HP, tone of the following 5 strings must be found anywhere in the 14 byte region of memory that contains the firmware version.

"BFP3V3 F", "N5R-3", "N5R3", "F5R3" or "BFT"

But even if you edited the image to put "N5R3" into this region of memory, CHIRP wouldn't upload the image to the radio because the firmware version of the image must exactly match the firmware version of the radio before an upload will be allowed.

Contact me by way of email and I will see if I can get you going.

Jim