Bug #11165
closedUnable to program the Quansheng UV-5R Plus using UV-K5 Model in Chirp
0%
Description
Accoording to the documentation for CHIRP, specifically "Home and Compatability List" the instructions indicate to use the UV-K5 option for the model number. Doing so renders an error " ERROR: Radio serial detection failed: Firmware '4.00.06' not supported". This is a brand new radio I have just recieved 2/11/2024 and the manufacturer has it labeled as a "2024" version. I am assuming this "New" versio has an updated firmware resulting in the error I am recieving.
Files
Updated by Dan Smith 10 months ago
Yep, that firmware version is much newer than what the driver was developed with. Can you try the attached version (instructions at LoadingTestModules) and report back please? Assuming it downloads, please save and attach the very first .img you get before you make any changes so we can have a look at it.
Thanks!
Updated by Herbert Davis 10 months ago
Dan Smith wrote in #note-1:
Yep, that firmware version is much newer than what the driver was developed with. Can you try the attached version (instructions at LoadingTestModules) and report back please? Assuming it downloads, please save and attach the very first .img you get before you make any changes so we can have a look at it.
Thanks!
Hi Dan, Applying this module fix just returnes another error stating that there is an "Internal driver error". And because of that I am also unable to grab the stock image to send to you as requested.
Thanks,
Herbert
Updated by Dan Smith 10 months ago
Please grab and attach a fresh debug log per How_To_Report_Issues after you have loaded the module and made the attempt so I can see what's going on.
Thanks!
Updated by Herbert Davis 10 months ago
Dan Smith wrote in #note-3:
Please grab and attach a fresh debug log per How_To_Report_Issues after you have loaded the module and made the attempt so I can see what's going on.
Thanks!
As requested lofg file is attached.
Thank you!
Updated by Dan Smith 10 months ago
Okay, try this new module please.
This is actually a bug in some (newish) detection code that this driver uses and which gets confused when modules are loaded. So, thanks for finding that, I'll fix that separately. The new module has a sort of hack in it which should fix the problem for you to test.
Again, thanks much for your help and patience!
Updated by Dan Smith 10 months ago
- Related to Bug #11166: Reloading detected drivers can fail with "Unable to concatenate none to list" added
Updated by Herbert Davis 10 months ago
Dan Smith wrote in #note-6:
Okay, try this new module please.
This is actually a bug in some (newish) detection code that this driver uses and which gets confused when modules are loaded. So, thanks for finding that, I'll fix that separately. The new module has a sort of hack in it which should fix the problem for you to test.
Again, thanks much for your help and patience!
Hi Dan, that fixed the issue I was having. All appears to be working fine now. As requested I have attached the immage file.
73's
Herebert
Updated by Dan Smith 10 months ago
- Status changed from New to Resolved
- Assignee set to Dan Smith
- Target version set to chirp-py3
Okay, great to hear, thanks.
I won't merge this for a day or two (for other reasons) so if you get a chance to put it through its paces a bit to make sure all the knobs and dials work with your newer-firmware radio, I'd sure appreciate it. Just comment back here if/when you find anything (or confirm everything is good). Just note that loading that module only "sticks" until you close chirp, so each time you open it you'll need to re-load it until the next build comes out with this integrated.
Updated by Frank Huber 10 months ago
Hi,
I experience the same error.
"Load module from issue" -> I key in 11165 -> leads to error message "unable to load modules from that issue"