OpenGD77

KB8YKF wrote: ↑

Wed Jan 24, 2024 9:49 pm

I checked and I still see $110 but I noticed it says "Exclusive Prime price" - which I've not noticed before. Do you know anyone with prime?

I just tried it out for you - two displays works great! One on the full size Displayport port, one on full size HDMI.

I had Prime for years, until last week. Placing ads in the streaming service was the final straw, I cancelled.

Thanks for testing it out, much appreciated!

First post on the forum! I signed up in part because I am a heavy Mac user and am interested in the solution to this one. Unfortunately, I did not have success with user CPop.1's solution, here:

W8SCL wrote: ↑

Tue Jan 23, 2024 3:59 pm

You may want to give this driver a try if you're feeling adventurous. I haven't tried it yet so YMMV.

https://community.st.com/t5/stm32-mcus- ... d-p/224127

However, I did a diff on terminal and found that the only real differences between amd64 and arm64 folders are the .inf files. I may try to implement these kind of changes in the official drivers; see below. Thoughts?


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



diff -r ARM64/stlink_VCP.inf STSW2/stlink_VCP.inf
11c11,13
< DriverVer=06/08/2017,2.01
---
> CatalogFile.NTx86 = STLinkVCP_x86.cat
> CatalogFile.NTAMD64 = STLinkVCP_x64.cat
> DriverVer=04/01/2021,2.02
16c18
< %ManufacturerName% = Standard,NTx86,NTarm64
---
> %ManufacturerName% = Standard,NTx86,NTamd64
26a29,31
> %DeviceNameVCP% =USB_InstallVCP, USB\VID_0483&PID_3754&MI_01
> %DeviceNameVCP% =USB_InstallVCP, USB\VID_0483&PID_3757&MI_01
> %DeviceNameVCP_PWR% =USB_InstallVCP, USB\VID_0483&PID_3757&MI_04
28c33
< [Standard.NTarm64]
---
> [Standard.NTamd64]
35a41,43
> %DeviceNameVCP% =USB_InstallVCP, USB\VID_0483&PID_3754&MI_01
> %DeviceNameVCP% =USB_InstallVCP, USB\VID_0483&PID_3757&MI_01
> %DeviceNameVCP_PWR% =USB_InstallVCP, USB\VID_0483&PID_3757&MI_04
69a78
> DeviceNameVCP_PWR="STMicroelectronics STLink Virtual COM Port PWR"

Here's my progress so far:


1. Download stsw-link009_v3_ARM64_UNSIGNED.zip from the ST Forum (see link above)


2. In Parallels, do [shift] + restart -> Troubleshoot -> Advanced Options -> Startup Settings -> restart -> Option 7) Disable driver signature enforcement


3. After startup, run the Command Prompt as Administrator (the small pnputil command, if you can read it)

4. Next, plug in the radio and power on; select USB to Windows 11 when prompted


5. Run Device Manager and select “Digital Radio in USB mode Properties”


6. Do the usual update driver routine, choose the driver from my computer and then choose from a list of the installed drivers on my computer.


7. Looks like everything works, but I don't see a COM port when I run the CPS software. I think that I'm close, but who knows

Have not given up yet on an end-to-end solution. After some testing, the driver installation looks okay. However, the missing COM port may be related to this issue, here:

https://kb.parallels.com/6318?_gl=1*1x1 ... 1708100496

Who knows, I will fight with this a little longer before asking to borrow my wife's Intel-based computer.

I think that's the end of it, it won't work mates. I hacked the official driver files as much as I could to even get this far.

Been reading about the same issues in one form or another all over the internet with ST Link drivers and arm64 architecture. The other driver "STMicroelectronics STLink Bridge" looked promising, but it could not let me flash the radio. Probably nothing to do with the COM port issues, just an unsupported driver that the CPS and radio cannot work with.

Awesome work digging into it, shame it wasn't a magic bullet but very grateful to see all the work you put into it regardless!

73,
W8SCL

W8SCL wrote: ↑

Mon Feb 26, 2024 8:42 pm

Awesome work digging into it, shame it wasn't a magic bullet but very grateful to see all the work you put into it regardless!

73,
W8SCL

And thank you for the suggestion, I learned a lot in the process! An arm-based computer is not ready to be my sole machine, especially for hobbies. If anyone wants to keep going down this thread, this is where I would go next.

1. WinUSB (Winusb.sys) installation for developers, here:

https://learn.microsoft.com/en-us/windo ... vice-class


2. INF ControlFlags section info, here:

https://learn.microsoft.com/en-us/windo ... gs-section


The reason why I failed is covered on the ST Forum by the user CPop.1 in an earlier post, where they say:

"...Again, Pavel's solution is really something that must be done by ST and cannot be worked-around by the community."

and

"Not ideal but if you could supply us with unsigned drivers we could, in theory, temporarily work around this issue. The existence of an invalid signature triggers the Windows policy."



So what did I do? Presidents' Day Sale at OWC. I will be running Parallels on an i5 chipset

My next attempt I think is to try to use Zadig (https://zadig.akeo.ie/) to see if it will insert the WinUSB driver under Arm. Wish me luck! lol

Watching this thread closely, good luck!