No support for the ARM toolchain on... ARM?

[jnorris]

Trying to install the STM32 boards in Arduino on a Raspberry Pi, but no luck: "Tool xpack-arm-none-eabi-gcc is not available for your operating system."

[fpistm]

Hi @jnorris ,
Currently not.
See stm32duino/Arduino_Core_STM32#708

I close this one as an issue is already opened for this.

[odo2063]

actually there is something unofficial...https://github.com/koendv/stm32duino-raspberrypi

[fpistm]

I know @odo2063 but I would like a maintain able solution.

[odo2063]

me too...but sometimes having at least something is better than nothing...

[fpistm]

Right, but If I release this I will have to support it and answer to all related issue...
So user can use this following instructions provided by @koendv

[fpistm]

Currently I'm waiting xpack support for arm then I will considered to add this support as mentionned in stm32duino/Arduino_Core_STM32#708

[koendv]

Hi Frederic,

Right now I am using stm32duino on a Raspberry Pi 4, 4gb ram, running 32-bit raspbian "buster". The Arduino IDE is stable. The built-in IDE editor is sometimes a bit slow. But in general, things work.

The upcoming version of the xpack gnu arm embedded gcc will support 32 and 64 bit arm linux hosts. To run stm32duino on arm linux, the only missing component is STM32CubeProg. Could you consider compiling STM32CubeProg for arm linux?

Since the introduction of the Raspberry Pi 4, these small arm linux systems are quite capable, and I believe that this market will grow rapidly, with more and more use cases, including for STM32 embedded software development, where the Arduino IDE is a major tool.

In the meantime, I don't mind sharing my solution. If you want to try stm32duino on raspberry, go to https://github.com/koendv/stm32duino-raspberrypi, copy the url of the .json file and paste the url in the Arduino IDE, File->Preferences "Additional Board Manager URLS". There are binaries for 32-bit (armv7l) and 64-bit arm (aarch64) linux.

regards,

koen

[ilg-ul]

I confirm, work on the next release of the xPack GNU Arm Embedded GCC (v9.2.1-1.2), which will add support for aarch64 and armhf, is under way.

The target date is end of March; I'll let you know when available.

But, as Koen mentioned, it would probably be useful to start preparing and build the other tools (STM32CubeProg?) for 32/64-bit Arm.

[fpistm]

Could you consider compiling STM32CubeProg for arm linux?

Unfortunately, I could not "compile" it myself. I'm an user like you 😉
You should ask this on ST community.

Target date is end of March. I'll let you know when available.

Thanks @ilg-ul

[ilg-ul]

Unfortunately, I could not "compile" it myself. I'm an user like you 😉
You should ask this on ST community.

This will probably take more time than getting the toolchain run on Arm.

If this is an open source project, perhaps it should not rely entirely on STM tools and also provide open source tools, like the ones used in Koen's solution.

[fpistm]

This will probably take more time than getting the toolchain run on Arm.

Probably...

If this is an open source project, perhaps it should not rely entirely on STM tools and also provide open source tools, like the ones used in Koen's solution.

The main issue is that OSF does not support all STM32 series. Moreover it is only one upload method they are other provided. It is planned to provide the DFU utils for all.

[ilg-ul]

Unfortunately, I could not "compile" it myself. I'm an user like you 😉
You should ask this on ST community.

I'm a bit confused. Are you managing this project as a hobby? According to your GitHub account, you seem to be working for STMicroelectronics, so I expected this to be a project officially supported by STMicroelectronics.

The main issue is that OSF does not support all STM32 series. Moreover it is only one
upload method they are other provided. It is planned to provide the DFU utils for all.

Can you elaborate a bit? What STM32 series are not supported by the OSF tools?

I'm not an Arduino user, so correct me if I'm wrong, but, as for upload methods, I saw in Koen's solution several upload methods, using various bootloaders, in rom or in flash. What else would be needed?

And what do you mean by 'provide the DFU utils for all'?

I'm asking this because I'm trying to understand if I can further help this project.

I have a very elaborated build environment (called the xPack Build Box), which allows me to build binaries for Linux Intel 32/64, Linux Arm 32/64, Windows 32/64, macOS, and maybe we can use this to provide a consistent set of tools for the Duino users, in addition to the STM specific tools.

[fpistm]

I'm a bit confused. Are you managing this project as a hobby? According to your GitHub account, you seem to be working for STMicroelectronics, so I expected this to be a project officially supported by STMicroelectronics.

No it is not a hobby even if several time I'm working at home even the week end... And yes it is supported by STMicroelectronics but it is first a community project. And a I said I'm a user of the STM32CubeProgrammer. Moreover, main ST Software ecosystem mainly support 3 OS as far as I know, that's why I said the bet way is to request on ST community to have STM32cubeProgrammer support for ARM arch.

Can you elaborate a bit? What STM32 series are not supported by the OSF tools?

STM32H7, STM32WB, STM32L5, STM32L4+,... some of the OSF projects start to introduce some of them but not stable yet or does not support all value line.

I'm not an Arduino user, so correct me if I'm wrong, but, as for upload methods, I saw in Koen's solution several upload methods, using various bootloaders, in rom or in flash. What else would be needed?

yes, that's why I said STM32CubeProgrammer is not the only way to upload so for those one this will be OK. I never said I will not add the ARM tooclchain just answered the STM32CubeProgrammer would not be possible while there is not ported on this arch.

And what do you mean by 'provide the DFU utils for all'?

Currently, DFU utils is used only for some target and I would generalize them for all.

I'm asking this because I'm trying to understand if I can further help this project.

Any help are welcome, as said this is a community project. 😉

I have a very elaborated build environment (called the xPack Build Box), which allows me to build binaries for Linux Intel 32/64, Linux Arm 32/64, Windows 32/64, macOS, and maybe we can use this to provide a consistent set of tools for the Duino users, in addition to the STM specific tools.

Thanks, that would be nice. I will get back to you if I need to made some build when I have a time slot to work on this, it will be very appreciated.

[ilg-ul]

... yes it is supported by STMicroelectronics ... the best way is to request on ST
community to have STM32cubeProgrammer support for ARM arch.

Don't you think that, from the internal STM procedures point of view, it is a bit weird (to not say terribly wrong) if, in order to communicate to your colleagues working on the STM32cubeProgrammer you need us to go to the ST community, instead of contacting them directly and getting an estimate when their tool will also be available for Arm 32/64-bit? If it is only a matter of a reasonable time, we'll wait, otherwise we need to consider alternate solutions.

And what exactly do you mean by 'ST Community'? I remember some time ago I reported some issues with compiling the STM packages with more recent GCCs, on a site that looked like a forum, but all that happened was that after several months the moderator mentioned that the issue will be passed to someone to investigate, and since then nothing else happened.