Project

General

Profile

Actions

Bug #2053

closed

Crash during upload Yaesu Vx-3R on Mac OS Yosemite

Added by Tim Kerby about 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
11/14/2014
Due date:
% Done:

0%

Estimated time:
Chirp Version:
0.4.0
Model affected:
Yaesu Vx-3R
Platform:
MacOS
Debug Log:
I read the instructions above:

Description

Hardware?

  • Ebay prolific interface. Prolific tool reports chip as genuine and normal drivers work
  • Macbook Air 13 inch Late 2011

Software?

  • Chirp 0.4.1

What works?

  • Other radios (e.g. Yaesu FT817)
  • Download from the Vx-3R
  • The same upload using the Windows version on a Windows 7 machine with the same cable
  • The same upload using the Windows version on a Windows XP virtual machine in Parallels on the same Mac with the same cable

What goes wrong?

  • The upload starts and the radio switches from Wait to Rx
  • About 25% of the way through the radio reports 'Error'
  • Chirp appears to hang and 50% of the time the entire Mac is unresponsive and needs reboot. Other times a force quit of Chirp works
  • The radio has been blanked of all memories

What have I changed that didnt fix it?

  • Uploading a different file to the radio
  • Changing Chirp version. I was using 0.4.1 but 0.4.0 fails in the same way
  • Retrying. Same effect on multiple attempts although whether the whole Mac hung varied between them

Files

vx3_large.img (31.8 KB) vx3_large.img Image file I was trying to upload Tim Kerby, 11/14/2014 02:15 AM
debug.log (10.5 KB) debug.log Tim Kerby, 11/14/2014 01:49 PM
Actions #1

Updated by Tim Kerby about 10 years ago

Here is the .img file. I'll get the debug log tonight

Actions #2

Updated by Tim Kerby about 10 years ago

Debug log attached - doesn't reveal much

Actions #3

Updated by Jens Jensen about 10 years ago

please try the opensource pl2303 driver:

http://1drv.ms/Nl68Ru
At this web page you may need to right-click or control-click to link to get it to download. After downloading, you may need to control-right click, then open in order to bypass Mac Gatekeeper.

Actions #4

Updated by Tim Kerby about 10 years ago

Tried to use that driver but it wont load in Yosemite as the kext is incorrectly signed.

Actions #5

Updated by Srini Sankaran about 10 years ago

Tim Kerby wrote:

Tried to use that driver but it wont load in Yosemite as the kext is incorrectly signed.

I had similar freeze issues with a "genuine" Prolific cable as well, when using Chirp on my Mac OS X (and also on Windows 8) with my Wouxun KG-UV8D, although there was no problem with the same cable with Kenwood TM-V71A or Baofeng UV82. I tried different drivers, prayed to different deities and demigods :-), and finally just broke down and bought an FTDI cable at amazon.com http://amzn.com/B0097E2I2S

Everything has been perfect with the FTDI cable. I wish I had spent this $20 earlier, rather than trying to save a couple of bucks on a cheap prolific cable.

Actions #6

Updated by Jens Jensen about 10 years ago

unfortunately with yosemite, drivers (i.e., kexts) have to be signed.
This is a problem affecting much more than just Chirp and serial chipset drivers.
If you want to sign your drivers, you have to pay apple 100 bucks to get a developer cert - and this is not going to happen for most open-source, hobby-grade projects.

The other option is to disable kext signature checking system wide (which is a very big hammer for such a small nail).
which is using boot-args kext-dev-mode=1 as seen http://www.cindori.org/trim-enabler-and-yosemite/

This is obviously not a desired solution from a security standpoint, but appears to be the only workaround.

Hoping that Apple will get lots of flak for this and implement an easier way, such as allowing user to selectively whitelist specific modules.

Unfortunately, with recent stunts that FTDI has pulled, it has become obvious that there are probably alot of fake FTDI chips out there (similar situation to prolific).
So your cable might work for now on Mac (at least until FTDI convinces Apple to use their "we-disabled-your-counterfeit-ftdi-chip-for-you" code in future apple ftdi drivers). But you will still be out-of-luck on windows.
One would be hopeful that this forces cable manufacturers to use genuine chipsets, however if anyone is in tune with the reality of global supply chain and fabrication situations (i.e., follow eevblog, etc) you will probably not be so hopeful. Especially so for cable market absolutely dominated by chinese clones.

Actions #7

Updated by Jens Jensen over 9 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF