FTDI D2XX Driver not working on Windows 11 ARM with M3 Pro Mac

Discussion in 'Parallels Desktop on a Mac with Apple silicon' started by ChristianG22, May 14, 2024.

  1. ChristianG22

    ChristianG22 Bit poster

    Messages:
    4
    Hi,
    I can't connect to a USB device using FTDI hardware on an Apple MacBook Pro with M3 Pro processor.
    This is my scenario:
    • Apple MacBook Pro with M3 Pro chip
    • macOS Sonoma 14.4.1
    • Parallels Desktop 19 for Mac Pro Edition 19.3.1
    • Parallels ARM Virtual Machine Running Windows 11 Pro ARM 23H2
    • FTDI D2XX driver v2.12.36.4A for Windows 11 ARM, manually installed as per instructions
    • ECUMASTER EMU Black client software v2.169
    • ECUMASTER EMU Black USB device
    USB device with FTDI chip shows up in device manager correctly as USB Serial Converter and USB Serial Port (COM3) and in the Bluetooth and devices overview under Other devices as ECUMASTER EMU BLACK but will not connect with client software (see attached screenshot).
    There are users with the same scenario and an Apple M1 host where this works, my M3 does not.
    I used to work with an Intel i9 MacBook Pro and Windows 11 before without any trouble.
    Any ideas?
     

    Attached Files:

  2. TattooTroy

    TattooTroy TattooTroy Bit poster

    Messages:
    5
    I'm having a similar issue trying to get the GM vehicle diagnostic USB interface to connect to Diagnostic software in Windows 11 ARM. It shows up as com port which it not a com port device.
     
  3. LiXmA

    LiXmA

    Messages:
    2
    I have the same Problem on my MacBook Pro M3 and hopefully somebody know a solution
     

    Attached Files:

  4. LiXmA

    LiXmA

    Messages:
    2

    Attached Files:

  5. jose21

    jose21

    Messages:
    3
    I have exactly the same situation. I need to use windows software to program various things from Teensys to motor controllers. All use USB based connections. I have an M3 macbook and parallels 20 running windows 11. I have not been able to get a single USB connection to work. I now see this is a common problem.
     

Share This Page