rp2040_hal VS picostdlib

You can go bare metal for the raspberry pico. Maybe it's also interesting to you: https://pico-doc.synack.me/

In this release we improved Alire integration. Now you don't need the compiler to be in the PATH (only alr) when you are working with a crate, because Alire will configure it for you. Suppose you setup a crate for Rasperry Pico, if you open it in VS Code, then navigation should work out of the box. Also any Alire configuration is skipped altogether if the VSCode was launched with alr edit or alr exec.

If you want a more modern processor, pick the RPI Nano. You find extensive doc here: https://pico-doc.synack.me/

Ada on Raspberry Pi Pico website ( https://pico-doc.synack.me/)

AdaCore's docs are fantastic for understanding why things are done the way they are. However, when I'm learning a new platform or language I prefer to see a lot of practical examples first. That's what I tried to do with my "Ada on the Raspberry Pi Pico" project:

https://pico-doc.synack.me/

Heres the rp2040 wrapper someone else did: https://github.com/EmbeddedNim/picostdlib

As a workaround, you might be able to just get Nim to output the c sources (nim cc), and set up your own build system (make or whatever) to build and link it. This is the approach taken in https://github.com/EmbeddedNim/picostdlib. If you do this, you might want to pass in --cpu:m68k or some other supported 8-bit arch, though I'm not sure that --cpu is used for anything else than selection the C compiler exec and flags.

C++ has decent industry acceptance in embedded nowadays, or at least that has been my impression.

After C++, rust is likely the most popular, quite a lot of effort has been put into running rust on embedded, see eg https://github.com/rust-embedded. However, once again to my understanding, industry acceptance is still highly marginal.

After that, there's a bunch of toy-ish efforts to run other languages. Zig, nim, python and javascript variants, etc. Usually anything that has C ABI compatibility should be possible to get up and running (without writing a compiler backend from scratch). I've had fun with some toy projects using nim for ARM cortex-M targets (https://github.com/EmbeddedNim/svd2nim, https://github.com/auxym/nim-on-samd21, https://github.com/EmbeddedNim/picostdlib).

Using Nim (and eg svd2nim to generate the equivalent of CMSIS headers for register access in pure nim), it would be entirely possible to write even the low level stuff (SPI drivers and whatnot) in 100% nim, with the same performance as C and better safety (better static type system and compile-time checks, etc). Runtime (eg overflow) checks and garbage collection are available (at the cost of some performance) but optional. See eg. a pretty basic higher-level API for GPIO access, that provides native performance, since the abstraction is implemented as macros (compile-time abstraction): https://github.com/auxym/nim-on-samd21/blob/master/src/port....

To be clear: Ratel isn't my project, just something I'm following due to interest.

In the interest of shameless self promotion :), my own experimentations are :

https://github.com/EmbeddedNim/svd2nim

https://github.com/auxym/nim-on-samd21

And I've used and contributed to picostdlib (https://github.com/beef331/picostdlib), the rp2040 support library.

All just as a hobby, but it's interesting to learn that some companies are actually looking into Nim for firmware! Embedded seems like such a slow moving industry. I believe the author of Nesper and Nephyr also developed them for professional work.