Is it possible to use the Arduino IDE on an ARM64 Linux system to compile and upload code to an STM32-based board? Are the STM32 tools and CMSIS dependencies also available for this architecture?
Would STM32CubeProgrammer now make the above tools and dependencies redundant?
Hello @hajtas ,
I can confirm that it does work on ARM64 MacOS, we havent tested it on linux, but its support is included in the board definition. If you try it out and it doesnt work we can debug it and have a new release for you in a matter of days. You are also welcome to upload it using the STM32CubeProgrammer by passing the .elf files to it and it should work without a problem
Thank you tips — I can confirm that it works on ARM64 Linux/Raspberry Pi as well. I was able to compile, upload, and run a sketch successfully using arduino-cli.
Arduino IDE 2 does not currently provide an ARM64 Linux build, so I used arduino-cli & Arduino IDE 1.8.19 instead.
The board definition JSON also required some modifications, in addition to a few Linux-specific issues in the upload scripts. Some .sh scripts appear to be Bash-only, and there are occasional problems with paths or command names.
For now, I worked around these with aliases and symlinks, but I can collect the affected JSON entries, script lines, and verbose logs if that would help you debug and prepare a fixed release.
I only tested uploading with the STM32CubeProgrammer CLI (STM32_Programmer_CLI), and it worked without any problem.
I am very glad you got it working! It would be of much help if you can provide the diffs you’ve made, we can then update the scripts as needed. Thank you!
I’ve made two changes:
-
STM32Tools: I removed the STM32Tools dependency from the
toolsDependenciessection. I’m not familiar with its purpose, and it didn’t seem to be necessary for getting the setup working. -
CMSIS: The existing
allhost entry didn’t match my ARM64 Linux environment, so I added an explicitaarch64-linux-gnuentry, pointing to the same archive. I wonder if Arduino IDE 2.0 might handle theallentry differently.
I’ve attached the patch file based on the current Inkplate board definitions:
--- package_Inkplate_Boards_index.json.orig 2026-10-30 08:12:54.763288375 +0100
+++ package_Inkplate_Boards_index.json 2026-10-30 20:04:41.006654806 +0100
@@ -2376,11 +2376,6 @@
},
{
"packager": "Inkplate_Motion",
- "name": "STM32Tools",
- "version": "2.2.1-0"
- },
- {
- "packager": "Inkplate_Motion",
"name": "CMSIS",
"version": "5.7.0"
}
@@ -2625,6 +2620,13 @@
"url": "https://github.com/SolderedElectronics/Dasduino-Board-Definitions-for-Arduino-IDE/raw/master/STM32_Tools/CMSIS-5.7.0.tar.bz2",
"archiveFileName": "CMSIS-5.7.0.tar.bz2",
"checksum": "SHA-256:0b04b0f214e483bcc360cda985cddc0de8031714019ceabcda4770d510b82bfe",
+ "size": "26151901"
+ },
+ {
+ "host": "aarch64-linux-gnu",
+ "url": "https://github.com/SolderedElectronics/Dasduino-Board-Definitions-for-Arduino-IDE/raw/master/STM32_Tools/CMSIS-5.7.0.tar.bz2",
+ "archiveFileName": "CMSIS-5.7.0.tar.bz2",
+ "checksum": "SHA-256:0b04b0f214e483bcc360cda985cddc0de8031714019ceabcda4770d510b82bfe",
"size": "26151901"
},
{
Hope this helps!
This is just the first step. My next task will involve modifications to the pre-build and post-build scripts, which is a separate part of the process. I’ll share those changes as well once I get to that point.
A few findings regarding STM32Tools:
The only file actually needed from STM32Tools is stm32CubeProg.sh. The dfu-prefix, dfu-suffix, dfu-util, hid-flash and upload_reset ELF binaries are not required. STM32Tools is only needed to provide the wrapper script that prepares the parameters for the STM32_Programmer_CLI command.
The stm32CubeProg.sh script can be placed directly in the board package at ~/.arduino15/packages/Inkplate_Motion/hardware/stm32/1.0.2/stm32CubeProg.sh.
In platform.txt, tools.stm32CubeProg.path={runtime.platform.path} can then be used instead of relying on the separately installed STM32Tools package.
There is also an incorrect executable reference in stm32CubeProg.sh: it uses STM32_Programmer.sh, whereas on Linux the correct command is STM32_Programmer_CLI. This is provided by the stm32cubeprogrammer_2.23.0_arm64.deb package.
For example, would it make sense to use a newer release of the official STM32duino Arduino_Tools package instead? The 2.4.0 release already includes ARM64 support:
Alternatively, would keeping only the required shell script in the board package be a reasonable approach?