Zephyr 3.0.0 released recently, but there doesn’t seem to be an entry in the registry for it. I understand that with semver this would possibly introduce many breaking changes, but is there a general plan of when and how Zephyr 3.0.0 would be available?
It’s added support for many boards, and I would like it if RP2040 boards, which were added in this release, would have an RTOS available for install on PlatformIO. Thanks!
Actually I started adding Zephyr 3.1.0 support in GitHub - maxgerhardt/platform-raspberrypi at zephyr, but the compiled firmware doesn’t run yet – they changed the build process two a 3-stage linking (pre0, pre1, final elf) and that is… giving me a slight headache.
Yeah, FreeRTOS also has support for the RP2040, but neither is that currently a framework in PlatformIO. I’m particularly interested in Zephyr because it provides many HALs that are used by libraries in its ecosystem, allowing for some more hardware-agnostic development, which I’m interested in.
Oh that’s brilliant, I understand that these things take time. I’ll keep an eye on it, thanks for telling me.
But I’m getting closer with Zephyr, at least I corrected some critical linking errors yesterday, but it still does not run… Feels like something tiny is missing.
I have the verbose reference build log from Zephyr and PlatformIO on my computer, can send this evening. My gut feeling is that I’ll see pretty quickly what’s missing when comparing them. The current behavior is that after drag-and-dropping the UF2 file on the device, it immediately reappears as a UF2 drive. If the firmware were bad, then it would just do nothing usefull, but the fact that it reappers may point to the UF2 file being bad or the bootloader (boot2_some_flash_chip.S) missing and thus immediately triggering the “oh no I have no firmware, please flash me” behavior.