-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Updated STLink-v1 driver for macOS #964
Conversation
I really hope that this rework is mainly functional. We definitely need either old hardware or at least one person to test.
|
edc5e44
to
b023959
Compare
- Updated xcode project settings v11.3.1 - Removed support for 10.6-10.12 - Compiled new kexts for macOS 10.13-10.15 - Moved instructions to separate README - Updated installation instructions
b023959
to
230497c
Compare
We have a STM32VL DISCOVERY (STM32F100RB) board now which contains an onboard ST-Link/V1 module (I shot an original one (2010) on ebay for cheap). I have found some additional time to test the kext on a macOS 10.13 and 10.14 machine. They install as expected with |
@dot4qu: Can you test something for us here on Catalina? |
Yes absolutely! Don't have a V1 though, just an ST-LINK/V2 usb stick |
@dot4qu: Thx for raising your hand. That does not really matter for what I intend to ask for. In fact you should not need any hardware at all apart from a Mac with Catalina itself. The intention is to see if the driver for the legacy STLink-v1 installs correctly on macOS. The task would be to:
Note: You are able to roll back all changes to the original state later on (I may give some additional advice), so don't be afraid to loose track of any temporary changes to your system settings. I've gone through this on a 10.14 (Mojave) test system and would just like to see if we get the same results on the newer version. |
You want me to checkout Running
|
My request solely targeted the |
This is the verification that an STLink-v1 (real HW) is recognised correctly on macOS 10.13 now:
However there still is an issue with
... but that seems to be a non-related problem to me, as I have experienced this with this specific board on Debian as well. I'll open a new ticket for this to allow for further investigation. |
@dot4qu: The reason for the failures at your side is the read-only filesystem introduced for the system partition with Catalina. You can try |
yep, looks like it's all good |
Kinda busy recently, sorry for the late response. If the kext works well under |
@chenguokai: That's ok. Yes, I have been thinking about to try that yesterday as I read about this option recently. I'll give it a try. It may also solve the read-only filesystem issue in Catalina. The /S/L/E setting still derives from the old kext version. Looks like we can conclude testing soon then... 🎉 |
@dot4qu: Thx for your feedback. Now you can do a first clean-up on your system:
This will cleanly remove the kext in /S/L/E again. I'll let you know as soon as we can continue. |
This is the verification that an STLink-v1 is recognised correctly on macOS 10.13 & 10.14:
Note: This is with the kext installed to |
@dot4qu: After rebooting your system, you may now retry |
@chenguokai: The observed problem #964 (comment) vanishes again when the board is connected under reset (Reset button pressed). It does not seem to be a general problem (thus not necessary every time the board is connected), but recovers the onboard STM32F100RB, if it has run into this kind of frozen state. |
Thx @chenguokai. So let's wait for @dot4qu 's feedback. |
Yep, you're correct. Still the kext loading error as expected with SIP back enabled, but no read-only problems now.
|
@dot4qu: That's good news. Thank you very much for testing. Here are the instructions for rolling back everything on your macOS:
That should ensure there are no leftovers on your local machine. |
Special thanks to @dot4qu for testing on macOS Catalina!
(Closes #735)