How to install STM32CubeMX on Windows 10 ARM64 on Raspberry Pi 4

[JBreu.1]

As in the FYI note STM32CubeMX on Raspberry Pi 4 the Oracle Java is needed. But seems that Oracle java 1.8.x is only operative for Windows x64 or x86, not for ARM. Any alternatives? Thanks

[Houda GHABRI]

Hi @JBreu.1​ ,

Can you please tell which version of CubeMX are you using?

Since version 6.2.0 STM32CubeMX embeds the JRE, no need to install Orcale Java.

To be sure to use the embedded java version you can use this command to launch CubeMX:

<CubeMX installer folder >\STMicroelectronics\STM32Cube\STM32CubeMX-6-2-0\jre\bin\java -jar STM32CubeMX.exe

Hope this helps you.

Houda

[CPop.1]

I found that the STLink driver doesn't work on arm64. Even after installing everything else, the device is not discovered. (I can see the mass storage portion of the composite device but the debugger device is listed in device manager as not having a driver).

(https://community.st.com/s/question/0D53W000011vaXZSAY/stlink-stcubeprogrammer-support-on-windows-arm64).

[Pavel A.]

> but the debugger device is listed in device manager as not having a driver).

It should be served with a standard in-box winusb driver.

ST, make a small fix in the INF file for the ST-LINK . Add .NTARM64 section:

[Standard.NTarm64]

... copy here content of [Standard.NTx86] or [Standard.NTamd64] section ...

Add this to [Version] section:

CatalogFile.NTARM64 = STLinkDbgWinUSB_A64.cat

Get the signature from Miscrosoft as usual ...

[Nawres GHARBI]

Hi @Pavel A.​ 

could you share the obtained drivers please

[Pavel A.]

Hi Nawres, I have not signed the driver. The INF with changes is attached.

Not tested on ARM, I don't have an arm64 machine yet.

[CPop.1]

Just an observation (completely different from the original problem): I've diffed yours and mine and found two devices appear only in the x86 section but not in the amd64 (so because I've duplicated the amd64 one, I have not included them). ST should review if amd64 is complete or why these devices are only detectable on x86 machines:

%DeviceName% =USB_Install, USB\VID_0483&PID_3752&MI_00

%DeviceName% =USB_Install, USB\VID_0483&PID_3753&MI_00

[CPop.1]

Workaround with unsigned drivers here :https://community.st.com/s/feed/0D53W000011vaXZSAY