Bug #10975
closedHiroyasu HI-8811 can't be read with firmwareV2.00
100%
Description
Hi,
I received today an Hiroyasu HI-8811 with firmware V2.00 and hardware 11-V02.
when I tried to download the configuration from the radio I got the following error:
Radio returned unknown identification string
The fingerprint of this radio seems to be: 00 00 00 28 00 20 d4 04 that is not part of RT470LRadio fingerprints in driver.
I added the fingerprint in array to be able to download the img (stock configuration) but I didn't dare rewrite the image on the radio...
The automatic backup image is not same as the one I got by saving the tab opened in Chirp after read, I don't know if it's normal ?
Many thanks !
Files
| chirp-error.png (15.3 KB) chirp-error.png | Error message when downloading from radio | ||
| Hiroyasu_HI-8811_20231129T124202.img (44.9 KB) Hiroyasu_HI-8811_20231129T124202.img | Auto-backup img | ||
| Hiroyasu_HI-8811_20231129.img (44.9 KB) Hiroyasu_HI-8811_20231129.img | img saved from chirp tab | ||
| HI-8811 Menu List (00-56).txt (3.47 KB) HI-8811 Menu List (00-56).txt | |||
| HI-8811 Menu List (00-56) - FW V2.00.txt (3.47 KB) HI-8811 Menu List (00-56) - FW V2.00.txt | |||
| mml_jc8810 - hi8811_v2.py (48.8 KB) mml_jc8810 - hi8811_v2.py | |||
| mml_jc8810 - hi8811_v2.py (49.2 KB) mml_jc8810 - hi8811_v2.py |
Updated by Jim Unroe 12 months ago
Reppad NG wrote in #note-2:
There are very few changes, just a few default values (probably related to predefined channels) and a new read-only menu in position 54.
The file is attached.
Thanks. I will take a look at it and try to come up with something for you to test.
Updated by Jim Unroe 12 months ago
Give this test driver module a spin. This is how you use it: LoadingTestModules
My experience with this type of radio (RT-470, RT-470L, RT-470X, HI-8811, etc) is that it appears that some areas of the radios are always changing as the radio is used. This certainly made it more of a challenge to reverse engineer.
CHIRP-next downloads the full memory range (at least the same range that the OEM software does), but has been programmed to skip several memory areas to match the behavior of the OEM software during the upload process. There is always some risk, but CHIRP developers do their best to make it as low as possible.
If you want, start out your testing by making all of your changes using the OEM software and then download to CHIRP to see if the changes match.
Updated by Reppad NG 12 months ago
Thanks for these explanations, these radios don't look like a piece of cake...
The module you sent has no modification compared to the one already in chirp, not even the new identification string?
Do you know where I can find the OEM software ? I got no response from the seller.
The only things I found now is on radtel website :
- The old RT-470X Program Software v1.0.3.2 software seems to read the configuration and channels properly, maybe it not check the radio identifier and the memory layout is same (there is no software for RT-470L on the site)...
- They say radios with V2.00 software have a new PCB and are not firmware compatible with older models (but they kept the same HW revision number: 11-V2.0)
Updated by Jim Unroe 12 months ago
The file that I attached was absolutely identical to the current driver. The only explanation that I have is that I made the changes but neglected to save them.
I have recreated the changes, made sure to save them and have quickly tested them to verify that it still works with my v1.17 radio.
Updated by Reppad NG 12 months ago
Don't worry, it can happen!
In the end, it's pretty much the same modification I made to download the image the first time, I just didn't dare write to the radio because I was afraid there'd be changes in the data mapping.
As I couldn't find any OEM software explicitly compatible with this radio, I made some changes to the radio by hand to test the driver in read mode, all went well so I made my configuration in Chirp, uploaded it to the radio and everything seems OK.
Many thanks !
Updated by Jim Unroe 12 months ago
Reppad NG wrote in #note-8:
Don't worry, it can happen!
In the end, it's pretty much the same modification I made to download the image the first time, I just didn't dare write to the radio because I was afraid there'd be changes in the data mapping.
As I couldn't find any OEM software explicitly compatible with this radio, I made some changes to the radio by hand to test the driver in read mode, all went well so I made my configuration in Chirp, uploaded it to the radio and everything seems OK.Many thanks !
The software provided Anysecu, Radtel and Talkpod radios don't really match the radios that they provide it for. I first used the software to map the memory and soon found out that it does not match the radio. That is when I resorted using the radios menus to do the engineering and created the menu lists. Most of the 1.xx firmware updates have added menus and/or change the choices available in the menus. The Talkpod firmware update also expanded their radio variant to 512 channels. So that is why I ask you edit the menu list to match your radio's list.
Being that the HH-8811 radios with firmware v2.00 doesn't seem to have made any important menu difference between my v1.17 radio, I am pretty confident that I can go ahead and submit a patch to add the v2.00 firmware support. If you discover anything that does need further attention, a new ticket can be opened to address it.
Updated by Reppad NG 12 months ago
Jim Unroe wrote in #note-9:
The software provided Anysecu, Radtel and Talkpod radios don't really match the radios that they provide it for. I first used the software to map the memory and soon found out that it does not match the radio. That is when I resorted using the radios menus to do the engineering and created the menu lists. Most of the 1.xx firmware updates have added menus and/or change the choices available in the menus. The Talkpod firmware update also expanded their radio variant to 512 channels. So that is why I ask you edit the menu list to match your radio's list.
Being that the HH-8811 radios with firmware v2.00 doesn't seem to have made any important menu difference between my v1.17 radio, I am pretty confident that I can go ahead and submit a patch to add the v2.00 firmware support. If you discover anything that does need further attention, a new ticket can be opened to address it.
Quite a game of chase!
Indeed, everything suggests that the firmware is compatible, and this update is probably aimed more at supporting the new PCB than adding new features.
I'll be sure to let you know if there's any problem, thanks again for your responsiveness.
Updated by Anonymous 12 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|6668dae920c4c409697baf0330c199abf04bdfb5.