New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple Silicon / ARM #87
Comments
Yikes. Thanks for the heads up. |
Stay awesome! |
I had the same problem on M1 Mac Mini but found a solution and wanted to share. It works with Windows 10 ARM64 (Build 21327) under Parallels 16.3.2 Technical Preview using FTDI FT232R USB UART using the beta ARM64 drivers from FTDI. The beta drivers (CDM v2.12.32.B3 for ARM64.zip) can be downloaded from ftp://ftp.ftdichip.com (user: u45902898-ide, pass: Ftd1$erv). I used the following steps: There are 2 items of the drivers that needs to be installed, first the bridge, and after the serial to usb driver, both updated with inf from package from FTDI.
Thanks to ZoltanMarosan on Microsoft Community for the instruction. I used Tasmotizer 1.2.exe and worked great. |
Thanks for sharing! (It's really incredible how complex we humankind have made the process of flashing a few hundred kbs to a chip. Its in the same category as sending a large file over the internet without any hurdles.) |
Any update on plans for a native version of Tasmotizer for M1 Macs? |
@mbspears I have zero experience with native Mac apps, so most likely no. |
Thanks for the update. I completely understand. Would have been nice if Apple made a backward compatible mode or something. |
The additional issue is that I have no one nearby who has the M1 version, so I can't even properly debug where the issue is. |
Has anyone got a good link to the (CDM v2.12.32.B3 for ARM64.zip) file? The server seems to have changed its password |
Hello .I need driver ftdi .please send me to mail alexandtr1@mail.ru. |
Hello. |
I lost driver for arm. please send the driver. Thank you. |
Hi, i need the driver please. santir.1098@gmail.com |
I also need the drivers. please that's more than 4 people who've requested the driver... someone reupload it to dropbox or one drive..... we would all really appreciate it. @haakonstorm please help us out @jziolkowski @mbspears @cwilmo |
Hi guys @smokescreen42 @Noenemy88 @Alexandtr1 @M1LLZR . The Support of FTDI sent me the .zip with drivers for ARM64. Best regards! |
thank you so freakin much !!!!! I use VAG CAN PRO for my Audi diagnostic software and after buying an M1 MacBook Pro I havn't been able to check Audi codes and this should solve my problem because the VCP dongle is an FT232R serial. |
Hope u can resolve it! @smokescreen42 |
this is me reporting back that it works and I was just able to get K Line synced under the com port and erase my codes ! |
Hey @smokescreen42, How did you set it up on your M1? I've got a MacBook Air M1 with a FT232R running WIn10 on Parallels 17. I've tried installing the drivers using Test Mode but I keep getting this error: |
Using with Apple Silicon. Just install PyQt5 via Homebrew and it just works |
With everything installed and up-to-date regarding brew, pip3, python3… when I try to install from PyPI using pip on my iMac M1 with: I get the error:
|
Can not reproduce. M1 Air (2020) with latest Ventura
|
I was able to solve the problem by installing latest python (currently version 3.11.3) with HomeBrew, making it the default one (instead of Python 3.9 that comes with Xcode) by adding it to my PATH. It works. |
Just to add another data point - seems to be working fine for me (M1 Pro, Ventura) with just a |
Tasmotizer has issues on the new ARM architecture Apple has switched to. This is on a MBA 13" M1. I first tried installing via
pipx
but that failed, so downloaded the release instead and that resulted in the above. Switched back to my macOS Catalina MBP (Intel) and Tasmotizer worked instantly, flashing a couple Sonoff Basic R2's. I just wanted to start this thread to follow up on status on (eventual?) ARM64 ("Apple Silicon") support for the 'tizer. Thank you all for your awesome work.The text was updated successfully, but these errors were encountered: