ooo looks like the #Zephyr SDK is getting caught up (mostly) on GCC and others. New version (in alpha) is GCC 14.3-based, which was released less than a month ago.
#zephyr
0 posts0 participants0 posts today
:･*Fweeblies*:･
Thursday...and that means a new #Zephyr video 
I cover using LCD drivers and LVGL to make basic GUIs. Check it out!
https://youtu.be/Kfgln6RdoYc
It's taken a while, but I think I've finally gotten the hang of some of the #Zephyr project/workspace patterns, specifically manifests and "shared libraries”.
Continued thread
Wait, why does IntelliJ Serial Connection plugin not set DTR any more? It definitely used to set it. Down another rabbit hole. #zephyr
OK, somehow this code now blocks forever... what? It should just wait until you connect to the serial console. #zephyr
```c
while (!dtr) {
uart_line_ctrl_get(dev, UART_LINE_CTRL_DTR, &dtr);
k_sleep(K_MSEC(250));
}
```
Olympus Chrome Six
New #Zephyr video! 
One big benefit of using an #RTOS is the ability to run multiple threads, and that's exactly what I cover. Check out the full video!
https://www.youtube.com/watch?v=3OSKV2jrAHM
Tomorrow is the day! Come hang out and learn about writing device drivers in #Zephyr. Even if you don't have hardware, you can still follow along. And yes, the webinar will be recorded.
https://event.on24.com/wcc/r/4870160/B0654D058D6BC12D5A08B9607370682A?partnerref=sh3
Oooo #zephyr doesn't want to compile with the GCC 14.2 build... so many -Wincompatible-pointer-types warnings... so many.
Am I wanting to stab the computer while trying to deal with debugging threads and #zephyr? Yes. I'm gonna have to go get my JLink debugger.
Dare I tippytoe back into Rust on #zephyr? Maybe.
Updated a few projects to #Zephyr 4.1 from 4.0, and so far no major concerns. I did trip over a devicetree thing where, I think, some things got changes from properties to strings. OK, that's just a weird choice. I need to go read the commits to understand why.
I think tonight I'm going to see just what it would take to get C++ modules to work with #Zephyr.
Continued thread
And, miracle of miracles, it works correctly. FWIW, using uv to manage the west dependencies. #Zephyr
Wow, I sure hope I got all the manifests set up right with #Zephyr because I just accidentally blew away everything. Fortunately, I had just done a git commit/push.
One thing in #Zephyr I really struggle with is the best way to create some shared code. In this case, I have a bunch of protocol-related code that should be common to multiple projects. Should that be its own project in the manifest? If so, not sure how it gets into the whole list of includes/etc? There's a lot of docs, but... they all seem focused on adding new upstream dependencies, and really not with how you might do this for your own projects.
Adding more stupid things to my Enterprise Blinky. Added reboot tracking and random blinking. Mostly this is an excuse to poke at random bits of #Zephyr and understand the minimum possible use.
GitHubGitHub - petrilli/enterprise-blinky: An overcomplicated version of the embedded test script leveraging Zephyr.An overcomplicated version of the embedded test script leveraging Zephyr. - petrilli/enterprise-blinky
Why don’t they make every car on the train an observation car? #Amtrak #Zephyr #TrainThoughts