Koen De Vleeschauwer

There's an arm64 build; what's missing is integrating the arm64 build with the others.

Just FYI: Raspberry already has the following debian packages: - binutils-arm-none-eabi - gcc-arm-none-eabi - libnewlib-arm-none-eabi libnewlib-dev - libstdc++-arm-none-eabi-newlib After installing these packages, you can compile stm32 code on Raspberry. Eg....

Fine. If you provide a STM32 board package that assumes arm-none-eabi-g++, arm-none-eabi-ld, dfu-util, ... are in /usr/bin, I can try to compile some examples ("blink") on raspberry and get the...

OK. odo2063, if I put an arm-none-eabi toolchain up, are you willing to test it?

OK. Your turn. https://github.com/koendv/stm32duino-raspberrypi gcc-arm-none-eabi-9-2019-q4-major, dfu-util 0.9, hid-flash 2.2.1, built for armv7l-linux-gnu (raspberry in 32-bit mode). Build takes 16.5 hours. I could recompile this for aarch64 if needed.

OK. I've got a raspberry, I've already compiled the toolchain, and you can download toolchain and stm32tools for 32-bit raspbian "Buster" from my github. What comes next is installing toolchain...

OK. That is good news. You can download the [gcc-arm-none-eabi 9.2.1 toolchain and STM32Tools](https://github.com/koendv/stm32duino-raspberrypi/releases) for armv7l (raspberry pi in 32-bit mode) and aarch64 (raspberry pi in 64-bit mode). There's also...

OK. Estimate 2.5 days build time. I guess the advantage will be the 32-bit build will be the more general armhf, and not the raspberry-specific armv7l. Does this imply the...

> Yes some binaries will have to be built for the targeted hosts (ex: DFU utils). OK. The latest version of dfu-utils is v0.9. If we have to recompile for...

On Thu, 21 May 2020 04:13:49 -0700 beta-tester wrote: > i just tried to install STM32 Cores 1.9.0 on my Raspberry Pi > (newest Raspbian Buster updated and upgrades and...