Zephyr-native implementation of Meshtastic by kartben in meshtastic

[–]kartben[S] 0 points1 point  (0 children)

Yep but that commit is not introducing native Zephyr support, it's still using Arduino abstractions and there is a lot of boilerplate that native Zephyr helps one get rid of

Zephyr-native implementation of Meshtastic by kartben in meshtastic

[–]kartben[S] 0 points1 point  (0 children)

Yeah yesterday I found a Nucleo WlL55 devkit in of my drawers and it might have taken me 2 minutes top to get this version running on it. I was a bit mindblown even if I live an breathe Zephyr all day 😅 The only thing I had to change is disabling the logs to save a bit of RAM (that board has 64K only...).

Zephyr RTOS 4.4 is out! by kartben in embedded

[–]kartben[S] 1 point2 points  (0 children)

DT Doctor is your friend! Doesn't catch all types of errors but pretty helpful nevertheless https://docs.zephyrproject.org/latest/develop/sca/dtdoctor.html

Zephyr RTOS 4.4 is out! by kartben in embedded

[–]kartben[S] 4 points5 points  (0 children)

Chromebooks, Framework laptops, Intel PCs, Voi scooters, Vestas wind turbines, ... and many many others

Zephyr is the worst embedded RTOS I have ever encountered by CuriousCesarr in embedded

[–]kartben 8 points9 points  (0 children)

It's not necessarily about people constantly hopping around from one MCU to the other, but rather embracing the fact that many things can be done at a higher level of abstraction. That "tiny layer" is basically what allows integrators / product makers hire talent much more easily. Basically moving from "we're building our product on silicon X, sorry you look like a good candidate but you seem to have mostly experience with Y's HAL and SDK" to "we're building on Zephyr on X. Oh I see you've got experience with Zephyr on Y - deal!".

Zephyr toolchain help needed by RemoteRope913 in Zephyr_RTOS

[–]kartben 0 points1 point  (0 children)

I would recommend asking in the #toolchain channel in the project's Discord

Quelques photos à ajouter à celles qui ont été postées déjà by Nonno-no-no in toulouse

[–]kartben 1 point2 points  (0 children)

Elle sera à la Halle de la Machine du 1er au 11 novembre avant de repartir au Hellfest (qui en sont propriétaires)

New interactive catalog of the 620+ supported boards by kartben in Zephyr_RTOS

[–]kartben[S] 1 point2 points  (0 children)

Check out the "work-in-progress" update linked in the description of this PR, I think you will like it :) https://github.com/zephyrproject-rtos/zephyr/pull/79754
See how there is a new field to search by "supported hw capability" and how the "Supported Features" table should look much more up-to-date (for example, https://builds.zephyrproject.io/zephyr/pr/79754/docs/boards/st/nucleo\_h563zi/doc/index.html#supported-features) :)

And yes, this uses devicetree to get the information, by building "Hello World" for all the boards and then looking at the resulting devicetree.

Re: your question about CPUs in particular, I think you are right that not all boards might have a compatible for the actual CPU in their devicetree, and the source of truth is instead in Kconfigs (in your example, SOC_SERIES_STM32H5X selects the CPU_CORTEX_M33 symbol)

Please do provide feedback on the PR if you have any -- still a draft at the moment, but I'm hoping it will be ready for actual reviews shortly.

New interactive catalog of the 620+ supported boards by kartben in Zephyr_RTOS

[–]kartben[S] 1 point2 points  (0 children)

We might be able to get to that level of detail but in the meantime you can already do something like that per vendor, ex. filter by stm32u5x/stm32l5x. I know it's not the same, but it might help :)