Bug #9972


Chirp doesn't work with Retevis RT24

Added by Geoff Wiggins almost 2 years ago. Updated over 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Chirp Version:
next (py3)
Model affected:
Debug Log:
I read the instructions above:


Just bought a pair of these radios and tried using Chirp. I receive the cannot download block 0008 error message. Prolific drivers ok and Retevis's own software works ok, just wondering why Chirp doesn't.

Ideas please.

Using Win 11 in case this may be an issue.

Debug file and 2 pics attached.

Regards, Geoff.


P1010493.JPG (2.55 MB) P1010493.JPG Geoff Wiggins, 08/03/2022 03:31 PM
debug.log (34.7 KB) debug.log Geoff Wiggins, 08/03/2022 08:42 PM
Actions #1

Updated by Jim Unroe almost 2 years ago

  • Status changed from New to Feedback

I only see 1 picture and there is no debug.log file.


Actions #2

Updated by Geoff Wiggins almost 2 years ago

Hi Jim.
Try again.
Debug.log attached

Actions #3

Updated by Jim Unroe almost 2 years ago

Thank you for adding the debug.log file. Unfortunately it doesn't provide any more information that you already explained in your original description of the problem.

The RT24 was never directly reversed engineered by a CHIRP developer. Someone opened a ticket about 2 years ago saying the the Radioddity R2 Vendor/Model selection worked as-is for the RT24 so the RT24 was added to CHIRP as an alias or the Radioddity R2. I have sent a note to Retevis to see if they would donate an RT24, RT24V or its close cousin the H777S in a hope that having the radio would help with diagnosing the problem.

So you do have already have the older Prolific v3.2.0.0 driver installed in your Windows 11 computer? The latest driver provided to Microsoft and automatically installed when a Prolific chip is detected by Win11 now refuses to work with the more recent PL2303TA chip like it has been doing for the last decade with older PL2303XA chip. It has become so stubborn that it won't even assign a COM port any more. It now takes a driver version or older to work properly (v3.2.0.0 recommended).


Actions #4

Updated by Geoff Wiggins almost 2 years ago

Thanks for the reply. I know about the Prolific issues and have 3.8.39 installed, previously .25 and they work fine with my Yaesu FTM-100. Windows did update to 3.9.3 which of course doesn't work. This is a well known issue due to Chinese knock offs of the chipset.

I tried Radioddity R2, doesn't work.

I hope you receive a response from Retevis.

73 Geoff G4XMJ

Actions #5

Updated by Jim Unroe almost 2 years ago

Yes, the v3.8.39.0 driver works with the newer PL232TA chip but not the PL232XA chip that has been end-of-life (EOL) for over 10 years. But recently the PL232TA chip also went EOL. So the v3.8.40.0 and newer drivers have dropped support for the PL232TA as well. I just use the v3.2.0.0 driver because it works with both versions of the EOL Prolific chips. If I only used CHIRP I could use the v3.3.2.102 or v3.3.2.105 drivers, but they have issues with some of the OEM programming software from around 10 years ago.

I did get a reply from Retevis. We are still negotiating the details, but it looks like I will be getting the RT24 (PMR), RT24V (FreeNet) and H777S (FRS) radio models to use for troubleshooting this issue.


Actions #6

Updated by Geoff Wiggins almost 2 years ago

Glad they seem to be helpful. Please do let me know the outcome in due course.

73 Geoff.

Actions #7

Updated by Jim Unroe over 1 year ago

  • Chirp Version changed from daily to next (py3)

The Retevis RT24 has updated support on the CHIRP Next (Py3) build.


Actions #8

Updated by Dan Smith over 1 year ago

  • Status changed from Feedback to Closed
  • Assignee set to Jim Unroe
  • Target version changed from chirp-legacy to chirp-py3

Also available in: Atom PDF