#FIRMWARE BIN FILE HEX EDIT INSTALL#
#FIRMWARE BIN FILE HEX EDIT SERIAL#
#FIRMWARE BIN FILE HEX EDIT SOFTWARE#

If the cable works with the OEM software and radios then I'd guess it's the former. Most of the programming cables are interchangeable but a few are not. I've annotated which region corresponds to what offset in the OEM software data file as best as I can guess.Īs far as I know all you need to reproduce my work is Python 3.8+ and the pyserial package from pypi. I'm attaching an updated script that implements the writing portion of the protocol although I haven't tested it yet. I ran the software, read a factory radio, filled in as many fields as I could with unique values, and cross referenced the captures I have to narrow down which regions are which. Well like I mentioned when the OEM software reads from and writes to the radio it seems to basically write to or read from it's data file. I am willing to brick my radio but I am confident that it will not come to that. I can make a Linux machine available (Linux Mint 20.3), but as I mentioned above, I have been doing all of my CHIRP development using Windows. I don't have a 'Radioddity' programming cable, but as I mentioned above, I have many appropriate programming cables. I have 2 GM-30 radios (1 still in its factory state and 1 that was donated by someone and I don't know how they have used it). I also have appropriate PC03 style programming cables with Prolific, FTDI, Silicon Labs and WCH Serial-to-UART chips.

#FIRMWARE BIN FILE HEX EDIT SERIAL#

I use the Eltima Serial Port Monitor software to do my serial port capture work. I have been using Windows 7 32-bit for all of my development work. I can create additional serial port captures as required. I made serial port capture back when I installed it. I have had the OEM software installed on my PC for quite some time.

You have a Radioddity GM-30 radio, a Radioddity programming cable, a Linux machine, and are willing to risk bricking the radio.

You have knowledge of the CH340 USB to Serial adpater USB protocol and can help me write a Wireshark dissector for it.

The data files map pretty closely to the representation of channel settings in the radio's memory.

#FIRMWARE BIN FILE HEX EDIT INSTALL#

You're willing to install the shady OEM software on your PC and work on reverse engineering the data file format.If anyone else reading this wants to help please reach out to me especially if: By comparing the regions with the data files saved by the OEM programming software I can already roughly see where channel settings, names, and flags are stored. I'm attaching a WIP script to this message which can be used to read the radio's memory to local files. When I have it figured out I'll post the relevant details here in case someone else wants to write a CHIRP plugin. I have several of these radios and am working on reverse engineering the programming protocol the stock firmware uses. Oem-data-file.txt (3.36 KB) oem-data-file.txt Radio-memory.txt (3.59 KB) radio-memory.txt Serial port capture from Radioddity GM-30

Firmware bin file hex edit