-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to flash Firmware with AIOC #56
Comments
I had the same problem with a board I just had made with JLCPCB (running 1.2.0 firmware), using the uvtools website and Brave web browser on Ubuntu Linux (with web serial enabled). It would fail at random times all throughout the download from 2% to 85%, so I swapped to a dedicated cable I had for the baofengs and it was fine. FWIW, I noticed the blue light came on with the dedicated cable, but not with the AIOC adapter. |
Interesting.. I have a few suspects on what the problem could be.. I think I will put out some testing firmware for you to narrow down the problem and fix it for good |
I switched course and I have bought a Quansheng UV-K5 myself, so I can debug this much more easily :-) They are so cheap.. |
Hi Simon, |
Thanks for the report Patric! I just programmed the egzumer firmware to my new Quansheng UV K5-8 using the browser flasher without any issues.. I am running on Linux so I am currently thinking that it must be an OS problem. Do (all of) you guys use Windows per chance? In order to narrow down the issue, I have attached a few test firmwares that you can try. Let me know if you have success with one of the firmwares. I tried changing a few settings and also increasing serial buffer size. |
In my case it was KUbuntu Linux, using Brave web browerser with webserial turned on. I flashed first 1.3.0-rc1 (as had been using 1.2.0), then each test firmware in turn. All but the last would fail at varying percentages from 3% all the way through to 90% This one however was able to flash three times in a row:
It is not perfect, as I tried a few more flashes, jumping back between |
Thank you for your investigations but the initial problem for me was not an interrupted flash but a flash impossible to start because the Chrome browser under Kubuntu 22.04 systematically returns this error:
So should I try one of the three firmware to solve my problem, and if so, which one? |
Did you put the radio in firmware flashing mode (PTT key during power up)? |
Of course I put the radio in firmware flashing mode. I'm flashing my Quansheng with a new firmware every week at this time (the one of F4HWN based on egzumer, updated once a week) . I have no problem with the original flashing cable but only with AIOC. That's not a problem for me since I have both devices but I would like to talk about AIOC on my website and tell people that they don't have to buy the original cable to flash the quansheng but buy an AIOC instead so they can do all with it. |
Can you try the group thing? The AIOC is a CDC device, which can by default only be accessed by the root user. |
I don't think it matters and don't know how to manage that. |
Do a edit: Apologies, yes, ttyACM - probably had DFU on the brain when I typed that. 🤣 |
Given that I had the same issues, I think it matters a lot. Thanks @pfeerick for the instructions
It should be If you don't want to, you can alternatively create a udev rule for the AIOC device that allows anyone on the system to use it. Put See here for more information: If you don't want to do this either, I am sorry that I cannot help you. |
Finally I got my an AIOC and start testing ... I am using latest v1.3.0-rc.1 Now testing Online flash-tool of Egzumer with using Windows-11 and Google Chrome.. But when Flashing is NO Suc6,
Flashed radio now with CH340 interface and UVtools correctly and than next test ... Also No suc6 with K5Prog-Win V1.27
I will test the releases mentioned on 18-Feb later ... |
Yeah, can you try the firmware aioc-fw-1.3.0-rc.1-serialbuf.zip from above? |
As you can see above... I works a litte bit and than fault. As the AIOC is already programmed, I do not need the wire and can use the command ... I got an error
Here I found the tip, to use ZADIG again and install Libusb-WinUSB And now
So now I can test loading firmware agaian.... My findings .... Indeed now it works BUT only with little volume Just switch on radio and Here my logging:
So bigger buffer works, but programming is still very sensitive to volume of radio |
Thanks a lot for the detailed testing! Yeah, windows is very picky with the DFU util stuff. For some people it just works, others have to use weird tricks. I don't know why it's all over the place. Unless someone can tell me a specific problem, I am leaving it as is, because there is not much that is more painful than debugging Windows issues and also because I don't have any Windows machine anymore at home. The volume thing is odd. Can you or anyone confirm that this is only a problem with the AIOC and not with an official cable? What if you have the volume at minimum? |
v1.3.0-rc.2 now has the doubled buffer size fix included. I will close this issue for now, just reopen if you need more help. |
Hello,
First many thanks for this very useful device !
All is working perfectly with my Qaunsheng UV K5-6 : Chirp reading and writing, audio card... except firmware flashing.
I'm using google Chrome to flash with this link (working with official programming cable) :
https://egzumer.github.io/uvtools/
But with AIOC, It does nopt work. The browser return this :
Thanks for working on it if you can and have time for.
David (F4BPP).
The text was updated successfully, but these errors were encountered: