Zephyr Integration

Question

Zephyr Integration

scholzi100 opened this issue 3 years ago · comments

Paul Scholz commented 3 years ago

Zephyr is a RTOS, targeting some what IoT systems, it supports a lot of boards and is included in the Linux foundation.

Website: https://www.zephyrproject.org/

Code Examples:
https://docs.zephyrproject.org/latest/samples/index.html#samples-and-demos

Are there any plans to integrate with Zephyr or any other RTOS for better hardware support?

Dominik Westner · Answer 1 · Sat Apr 10 2021 05:23:55 GMT+0800 (China Standard Time)

I started a port. Initial port is not difficult, but in order to take advantage of zephyr features you'd need to make significant changes. Also having to use C++ makes the binary pretty large. I had to disable some features to fit it into 128kB for a stm32 g0. Didn't proceed further as I also wanted to wait for the 256kB version of the g0.

nanosonde · Answer 2 · Sat Apr 10 2021 16:39:39 GMT+0800 (China Standard Time)

Concerning the large binary:
Have you disabled RTTI, exception handling and the stdlib while compiling the C++ code?

C++ in this project is not using the STL and does not make use of RTTI and exceptions.
Dynamic memory allocations are used with new, but in a very "controlled" manner.
Also not STL containers (std::vector, etc.) are used.

I can recommend reading this: https://arobenko.github.io/bare_metal_cpp/#_know_your_compiler_output

Basically it boils down to the following compiler flags for C++:
-fno-exceptions -fno-unwind-tables -fno-rtti

In the CC1310 port I am additionally using; -std=c++11 -fno-threadsafe-statics .

Dominik Westner · Answer 3 · Sat Apr 10 2021 21:17:04 GMT+0800 (China Standard Time)

Ah, didn’t know this. C++ is the one language I always tried to avoid :) Will check. Thank you that’s very helpful.

…

Sent from my phone

On 10. Apr 2021, at 04:39, nanosonde ***@***.***> wrote: Concerning the large binary: Have you disabled RTTI, exception handling and the stdlib? C++ in this project is not using the STL and does not make use of RTTI and exceptions. Dynamic memory allocations are used with new, but in a very "controlled" manner. I can recommend reading this: https://arobenko.github.io/bare_metal_cpp/#_know_your_compiler_output Basically it boils down to the following compiler flags for C++: -fno-exceptions -fno-unwind-tables -fno-rtti In the CC1310 port I am additionally using; -std=c++11 -fno-threadsafe-statics . — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

thelsing · Answer 4 · Sun Apr 11 2021 19:28:29 GMT+0800 (China Standard Time)

If somebody wants to further reduze the footprint of the lib with further tweaks from the article. Feel free to submit a pull request.

Regarding the topic: I have no plans to port the lib to other OSs. But pull requests are welcome.

Paul Scholz · Answer 5 · Tue Apr 13 2021 00:33:25 GMT+0800 (China Standard Time)

I started a port. Initial port is not difficult, but in order to take advantage of zephyr features you'd need to make significant changes. Also having to use C++ makes the binary pretty large. I had to disable some features to fit it into 128kB for a stm32 g0. Didn't proceed further as I also wanted to wait for the 256kB version of the g0.

Well, lead times are endless long because of the "chip shortage". I am also waiting on a ST G0B1RE board for testing with NCN5130. Thankfully async uart for stm32 got merged into zephyr back in January. One less thing to worried about.