M1-Pro, PD-18, Non-Functional USB Cable, CHIRP (Resolved)

[GaryM21]

My older MacBook Pro failed recently and so I just purchased a new 14" MacBook Pro. As it is Non-Intel based (ie no Bootcamp) I purchased the recently released Parallels 18 and "upgraded" from Win10 to Win11.

I use CHIRP to program different hand held HAM radios and that applicatIon uses USB to communicate with the various radios. There is a USB cable that is used to do this. It's USB-A based so I use a USB-A to USB-C adaptor. Under my previous set up I would plug in the USB cable and WIN10 would recognize the device and load the appropriate drivers, and everything worked just fine. When I try that now using PD18 and Win11 nothing happens and the radios are not recognized. More problematically PD18 sometime hangs completely and I have to use Terminal to kill the Win11 processing thread.

Has anyone had success using USB connected devices to Win11 in a PD18 VM? Are there known issues with USB devices and PD18?

Any info would be helpful, as I've searched using a variety of keywords and haven't found any usable information.

 

[GaryM21]

I resolved my issue. First, I bought a genuine FTDI based cable. Second, I downloaded the FTDI ARM based drivers from FTDI that are listed as being compatible with the M1, M1 Pro, etc Apple chip set. Then I manually installed the drivers for the cable. BUT, and this is the key, it failed to load. The issue is that downloads in the Windows/Parallel contain DO NOT go to the C: drive. You need to manually move (or copy) the downloaded drivers to the C: drive partition or WinDoze bitches about the drivers and fails. Simply moving the driver package to C: and reinstalling, the rebooting (of course) resolved the issue and my USB device is now working...