FTDI driver problem

[LisaH9]

I'm attempting to install a USB device for a ColoradoTime Dolphin timing system for swimming on my M1 Mac running Windows ARM.
Ive looked thru the FTDI threads and downloaded the drivers,unzipped the folder and copied it to the C: drive . I attempted to update the device drivers from there. The version numbers match that from the download file.
I also copied the drivers into the Dolphin installation file. When I attached the USB timing controller I see the device is recognized by Parallels.

The installation folder for Dolphin is in C: Program Files (x86)
Here's the two errors I'm getting.

Any thoughts on if/how I can get this to work?
It works fine on my old intel Mac with Parallels.

 

[Avinash Bundhoo]

Hello,
Please follow the steps below and let us know if this resolves your issue

1. Run the virtual machine.

2. Download the driver here: https://ftdichip.com/wp-content/uploads/2022/02/CDM-v2.12.36.4-for-ARM64-Signed-Distributable.zip
2.1. Locate the unpacked folder of CDM-v2.12.36.4-for-ARM64-Signed-Distributable -> right-click -> "Copy".
2.2. Open "File Explorer" -> navigate to the C:\ drive -> right-click -> "Paste".
2.3. Folder should appear in your C:\ drive and have a path: C:\CDM-v2.12.36.4-for-ARM64-Signed-Distributable

3. Open Windows Device Manager: click Win R, type devmgmt.msc and click OK. Locate the device
4. Right-click on the device > Update drivers > Browse my computer for drivers > Let me pick from a list... > Show All Devices > Next > Have Disk > Browse and navigate to the C:\CDM-v2.12.36.4-for-ARM64-Signed-Distributable folder (make sure "Include Subfolders" is checked) -> click "Next".
Note: If it cannot locate the required .inf file on its own, try pointing it to FTDIBUS.inf in the ARM64 subfolder manually (if it doesn't work, try FTDIPORT.inf).
5. Device manager should locate the driver and install it.

Following is according to the FTDI driver installation manual, according to it, after installing a bus layer driver, also a COM port layer may need to be installed:

6. Right-click in device manager -> select "Scan for hardware changes".
Note: you may need to replug your device for it to have effect.
7. Locate a new device with ?
8. Right-click on the device > Update drivers > Browse my computer for drivers > Let me pick from a list... > Show All Devices > Next > Have Disk > Browse and navigate to the C:\CDM-v2.12.36.4-for-ARM64-Signed-Distributable folder (make sure "Include Subfolders" is checked) -> click "Next".
Note: If it cannot locate the required .inf file on its own, try pointing it to FTDIBUS.inf in the ARM64 subfolder manually (if it doesn't work, try FTDIPORT.inf).

For additional information, please check section 3.3 of the FTDI driver installation manual: https://ftdichip.com/wp-content/upl...vers-Installation-Guide-for-Windows-10_11.pdf

 

[LisaH9]

I believe I'm following this - but I have two difficulties.
1. I can't tell exactly the device that is installed.
The way this works, I install a receiver using a serial (printer type) USB cable. Under the PORTS(COM & LPT) I have a lot of OEMx.inf(frdiport.inf) and PR-PL011.inf) devices, I'm not sure if/what is associated with my device.

But the way that my Dolphin program works, I'm to connect the receiver, THEN start the app. When I do that, I get 2 windows:
a. Attempting to load FTD2xxx.dll from:C\programfiles (x86)\Calorado Time Systems\Dolphin5.
bFailed to load FTD2xx.dll. Are the FTDI Drivers Installed?

Do you have any suggestions?
Thank you.

 

[LisaH9]

So I think I got it to work. I can't fully test, but the program opens.
The solution was to copy the two files from the downloaded CDR under folder X86 (there's only two files) to the directory mentioned in the loading message.

 

[LisaH9]

So I think I got it to work. I can't fully test, but the program opens.
The solution was to copy the two files from the downloaded CDR under folder X86 (there's only two files) to the directory mentioned in the loading message.

note: I previously tried this but copied from the ARM folder. This time I copied from the x86 folder. I didn't think to do that before, but it occurred to me that if the CDM ARM library had an x86 folder, and since the program files were in x86, maybe that was the problem.