$ ./k5prog -r -v
Quansheng UV-K5 EEPROM programmer v0.9 (c) 2023 Jacek Lipkowski <sq5bpf@lipkowski.org>
k5_prepare: try 0
cmd: 15 05 ok:1
****** Connected to firmware version: [2.01.32]
Successfully read EEPROM
I backupped old fw of my K5.
./k5prog -r -v
[0] - 0 bar value
[1] - 1 bar value
[2] - 2 bar value
[3] - 3 bar value it equals to ADC value for 7.6 V
[4] - 4 bar value
[5] - always 0x2300 ???
[6] - always 0xFFFF ???
[7] - always 0xFFFF ???
The battery voltage can be calculated as V = (760 * ADC) / [3] / 100./k5prog -F -YYY -b firmware.bin
$ k5tool -reboot
Opening /dev/ttyUSB0
Handshake...
Firmware: "2.01.32"
HasCustomAesKey: 0
IsPasswordLocked: 0
Reboot device...
Bootloader: "2.00.06"
Done
$ k5tool -rdee
Opening /dev/ttyUSB0
Handshake...
Firmware: "2.01.32"
HasCustomAesKey: 0
IsPasswordLocked: 0
Read EEPROM offset=0x0000, size=0x2000 to eeprom-0000-2000.raw
Read 0000...0080: OK
Read 0080...0100: OK
Read 0100...0180: OK
...
Read 1f00...1f80: OK
Read 1f80...2000: OK
Done
$ k5tool -wrflash RT590_v2.01.32_publish.bin
Opening /dev/ttyUSB0
Read packed FLASH image from RT590_v2.01.32_publish.bin...
Unpack image...
CRC check passed...
Write FLASH size=0xe5dc
Waiting for bootloader beacon...
Bootloader: 2.00.06
Send version "2.01.32"...
Bootloader: 2.00.06
Write 0000...0100: OK
Write 0100...0200: OK
Write 0200...0300: OK
Write 0300...0400: OK
...
Write e300...e400: OK
Write e400...e500: OK
Write e500...e5dc: OK
Done
Are they USB programmable now, or do they still need a programming cable?
When Chirp saves an ".img" file with your choice of memory channels and frequencies, is that file portable
to other Quansheng UV-K5(radios, or just your specific one?
Should I assume that programs like Chirp are only writing/flashing frequencies and settings into channel memory,
and that their ".img" file does not over-write Radio Calibration and Factory Config data (like the ones we backed up)?
If that is true, then my Chirp .img file can be used for a friends UV-K5(with a different serial#, correct?
./k5tool -rdee 0x1E00 0x0200 eeprom-calib.raw
xxd -c 16 -g 1 eeprom-calib.raw eeprom-calib.hex
...
When Chirp saves an ".img" file with your choice of memory channels and frequencies, is that file portable
to other Quansheng UV-K5(radios, or just your specific one?
...
Should I assume that programs like Chirp are only writing/flashing frequencies and settings into channel memory,
and that their ".img" file does not over-write Radio Calibration and Factory Config data (like the ones we backed up)?
If that is true, then my Chirp .img file can be used for a friends UV-K5(with a different serial#, correct?
$ ./k5tool -port /dev/ttyUSB1 -simula