unable to download firmware on Linux about uvk5-chirp-driver HOT 9 CLOSED

strange, your radio should respond to the hello request with the firmware NAME and it reply with the hello request instead .. weird...
the radio is in normal state ??? mean power up normaly.

here is my communication.. but under windows..

[2024-01-18 07:40:37,238] chirp.loaded.uvk5_egzumer - DEBUG: Sending hello packet
[2024-01-18 07:40:37,238] chirp.loaded.uvk5_egzumer - DEBUG: Sending command (unobfuscated) len=0x0008:
000: 14 05 04 00 6a 39 57 64 ....j9Wd

[2024-01-18 07:40:37,265] chirp.loaded.uvk5_egzumer - DEBUG: Received reply (unobfuscated) len=0x0028:
000: 15 05 24 00 45 47 5a 55 ..$.EGZU
008: 4d 45 52 20 76 30 2e 32 MER.v0.2
016: 31 00 00 00 00 00 00 20 1......
024: 00 00 00 00 00 00 00 00 ........
032: 00 00 00 00 00 00 00 00 ........

and your :

[2024-01-17 16:46:37,481] chirp.loaded.uvk5_egzumer - DEBUG: Sending hello packet
[2024-01-17 16:46:37,481] chirp.loaded.uvk5_egzumer - DEBUG: Sending command (unobfuscated) len=0x0008:
000: 14 05 04 00 6a 39 57 64 ....j9Wd

[2024-01-17 16:46:37,488] chirp.loaded.uvk5_egzumer - DEBUG: Received reply (unobfuscated) len=0x0008:
000: 14 05 04 00 6a 39 57 64 ....j9Wd

from uvk5-chirp-driver.

Yes, powered up normally, NOT in programming mode, with radio ON before plugging in.

from uvk5-chirp-driver.

ok,
try to read the radio with the driver in the original driver uv-k5

if it's the same error, that mean it's not egzumer driver in chirp that make this.
then try to reflash the radio with the egzumer-21

i dont have linux here to try it...

from uvk5-chirp-driver.

same error with a few more traceback points in the debug output.
chirp_debug-original_ uv-k5.txt

I'm somewhat reluctant to re-flash just now. I spent a bit of time saving a few channels.
I suppose I could write them all down. The paste from the flash process follows.

CRC check passed...
Detected firmware version: *EGZUMER v0.21
Firmware uses 99.04% of available memory (60852/61439 bytes).
Connecting to the serial port...
Radio in flash mode detected.
Bootloader version: 2.00.06
Version check passed.
Flashing firmware...
Flashing... 100%
Successfully flashed firmware.

from uvk5-chirp-driver.

This is a communication issue. The radio echoes back what it receives, looks like a short between TX and RX lines. This not a driver or chirp problem.

from uvk5-chirp-driver.

I wonder ... serial ports are enumerated starting at zero on Linux and at 1 on Windows.
Could the "short" be in the code? I haven't read the entire driver.

I encountered this impasse configuring dial-up to work for both dual booting Windows and Linux.
It confounded me memorably.

from uvk5-chirp-driver.

This has nothing to do with the driver or chirp. You can see in the log what is being sent to UART and what is being received. Serial port mirrors whatever it receives.

from uvk5-chirp-driver.

I can avail a stock UV-K6. I'll see if I can copy that with the original driver.
I can share results early next week.

from uvk5-chirp-driver.

Sorry to have suggested the possibility of a coding error.
I hope you'll accept my apology.

The truth is, the cable has to be plugged in ALL the way!
When the microphone plug is fully seated, it works like a charm.

https://ham.stackexchange.com/a/22056

from uvk5-chirp-driver.