Bug #4611

Chirp wont finish clone

Added by Shawn Loucks over 5 years ago. Updated almost 2 years ago.

Status:Closed Start date:03/12/2017
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Platform:Windows
Model affected:Baofeng UV-5R


I can clone from my radio to chirp, but I can not clone from chirp to the radio.

After entering the data, and I try the clone process, the clone freezes half way. I have tried to leave it for an hour, and it doesn't move. I downloaded the most recent chirp, the cord is plugged in all the way into the radio, radio is on.

Radio is a UV-5R
I am using windows 10
64 bit

debug.log - Debug log from #4649 (31.5 kB) Bernhard Hailer, 04/08/2020 12:38 pm

Related issues

related to Bug #4649: Chirp stalls when cloning Closed 03/19/2017


Updated by Jim Unroe over 5 years ago

  • Status changed from New to Feedback

Is it programming cable with a Prolific chip? If yes, then have you downgraded the device driver to v3.2.0.0 (the auto installed device driver is incompatible with counterfeit chips)?

Drivers & USB Cables


Updated by Shawn Loucks over 5 years ago

Unsure how to check to see if it has a Prolific chip. Assuming it didn't I follow the instructions on downgrading the driver device yesterday. It gets about 1/2 and just pauses. After letting it pause for a hour or so. I unplugged the cable, looked at the radio and the programmed frequency's and names were in the there without the clone finishing.

Updated by Jim Unroe over 5 years ago

Step 11 in the link above shows you how to find the Driver tab in Device Manager which shows you the chip vendor and installed driver version.


Updated by Jim Unroe over 5 years ago

Confirm that you have a Prolific chip and if you do confirm that you have the v3.2.0.0 device driver installed. If confirmed and the failed upload still happens, then attach a debug log of the failed upload.


Updated by Shawn Loucks over 5 years ago

After looking at step 11 on the site, it is a prolific. In the driver tap is says its driver version I did have to change the driver to v3.2.0.0 to read on chip, and that's what I was using when the clone pauses.

Updated by Jim Unroe over 5 years ago

Start CHIRP, do an upload that fails, close CHIRP and attach the debug.log here.

Detail for locating the debug.log file are on the How to report issues page.


Updated by Shawn Loucks over 5 years ago

I added debug.log file in the issue page

Updated by Jim Unroe over 5 years ago

Where is it?


Updated by Bernhard Hailer over 2 years ago

  • File debug.log added
  • Target version set to chirp-daily
  • Chirp Version changed from 0.4.0 to daily

I closed #4649 and copied the debug log here.

Updated by Bernhard Hailer about 2 years ago

  • Model affected changed from UV-5R to Baofeng UV-5R

Has this been resolved?
The log does not say much, it probably should be collected again in a fresh attempt.

Updated by Bernhard Hailer almost 2 years ago

  • Status changed from Feedback to Closed

No more feedback.

Also available in: Atom PDF