I think there is a reference project that we can use as base:
https://github.com/tylerwhall/zephyr-rust
It doesn't seem to implement the drivers or anything else in the kernel.
Best Regards,
Alan
On Wed, Mar 13, 2024 at 8:36 PM Tomek CEDRO wrote:
> On Wed, Mar 13, 2024 at 10:03 PM Gregory
Hi Anders,
As I said the RP2040 doesn't have a unique id like others MCUs, then the
solution they found was read from its SPI Flash, more info:
https://github.com/raspberrypi/pico-sdk/pull/12
You need to look how they did it and use it in NuttX.
BR,
Alan
On Thu, Mar 14, 2024 at 4:09 AM
-1 from me for Rust in the kernel, +1 for Rust in apps.
Pierre-Noël Bouteville
Envoyé de mon iPhone
> Le 14 mars 2024 à 09:51, raiden00pl a écrit :
>
> -1 from me for Rust in the kernel, +1 for Rust in apps.
-1 from me for Rust in the kernel, +1 for Rust in apps
Mixing languages in the kernel was never a good idea. Kernel should follow
"as simple as possible" philosophy whenever it could.
My opinion is that although Rust is safer than C, if you know what you are
doing, a C is good enough.
If you
-1 from me for Rust in the kernel, +1 for Rust in apps.
Sebastien and Tomek gave enough arguments to avoid Rust in the kernel.
Not a technical argument from me: Rust has too many arrogant members
in the community with a messianic approach (like `Rust will save embedded,
blah, blah, blah`),
it's
Hello Alan and thanks for the warm welcome.
Yes, the id is in the flash part of the board and the code for extracting the
unique id is in the Pico bootrom. But how to acces and run bootrom code from a
Nuttx application?
The code for other boards seem to access an id in a processor register. And
