Has anyone used the Zephyr RTOS on a Pi Pico or any other smallish system?

I'm writing something relatively simple for a Pico in C using the SDK.
It doesn't need an RTOS, the old classic cyclic executive paradigm will
work fine.
At one time I'd have used an 8bit CPU but why faff about when you can
get something like a Pico for hardly any cost even if 2x Cortex M0+
seems overkill.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 12/24/24 12:47, mm0fmf wrote:

Has anyone used the Zephyr RTOS on a Pi Pico or any other smallish system?

I'm writing something relatively simple for a Pico in C using the SDK.
It doesn't need an RTOS, the old classic cyclic executive paradigm will
work fine.
At one time I'd have used an 8bit CPU but why faff about when you can
get something like a Pico for hardly any cost even if 2x Cortex M0+
seems overkill.

Well, you can have two threads, kinda, with the Pico without an
RTOS...just split your work between the two cores. I just did a simple
project using one core to do a com link to a pc for command/response,
and the other core to do a real-time hardware controller chore. Made it painless...

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 25/12/2024 00:30, wmartin wrote:

On 12/24/24 12:47, mm0fmf wrote:

Has anyone used the Zephyr RTOS on a Pi Pico or any other smallish
system?

I'm writing something relatively simple for a Pico in C using the SDK.
It doesn't need an RTOS, the old classic cyclic executive paradigm
will work fine.
At one time I'd have used an 8bit CPU but why faff about when you can
get something like a Pico for hardly any cost even if 2x Cortex M0+
seems overkill.

Well, you can have two threads, kinda, with the Pico without an
RTOS...just split your work between the two cores. I just did a simple project using one core to do a com link to a pc for command/response,
and the other core to do a real-time hardware controller chore. Made it painless...

That was my plan. The project has to do simple things like scan a 4x4
keyboard, light assorted LEDs and send strings over the UART at 38k4 to
control something. I'd already decided that I would run all the UART send/receive on one core and run the control on the other core. That way
the control core remains non-blocking and the UART core can block if needed.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)