🔬👾Add an example for a real embedded system

[lukevalenty]

There should be an example that can be built and experimented with on a real embedded board. Arduino might be nice due to its popularity.

https://github.com/a9183756-gh/Arduino-CMake-Toolchain

[Jasinsky]

@lukevalenty -

What do you think about https://platformio.org/?

There are many more popular low-cost embedded boards (mostly targetting hobbyists - but not only). PlatformIO has a coherent library management system - is able to set up toolchain automatically, etc.

Many thanks for such a great concept and library!

Regards,
Daniel

[lukevalenty]

I haven't used platformio myself, but it looks intriguing. Could be a good learning opportunity for myself. 🙂

[antonysigma]

Me too! I wish to see a more hardware oriented example of cib.hpp. Something like a Arduino LED blinker controlled by a push button.

Examples:
https://godbolt.org/z/Y983h4
https://github.com/boost-ext/sml

[mhanuel26]

@lukevalenty ,

Hi Luke, I recently saw your presentation and example using Atiny device for this (excellent btw), it might be a good start and example for a real embedded platform, but I was looking for it under this repo and could not find it. Is this something you can share or help to setup for us mere mortals?

Thanks,

[lukevalenty]

Hi @mhanuel26! We have been tossing around the idea of making a separate repo that pulls together all of our C++ baremetal libraries/framework into a dev kit that can be used for various microcontrollers. Stay tuned!

[antonysigma]

@lukevalenty Given the dependency on C++20 standard and the most recent gcc toolchain, what is the strategy of unifying the gcc build environments in the dev kit? Just curious.

@mhanuel26 Same here. I am also hoping to see the real world, end to end example of CIB as demonstrated in the ATTiny seminar. While we are waiting, have you tried the modm framework? They have a pretty good tutorial on setting up GCC compiler for ATTiny MCUs. The one on the Microchip website is outdated and not suitable for CIB.

[lukevalenty]

@antonysigma: We are planning on using cmake and setup cmake toolchains for each of the targets. AVR, ARM, RISCV, and ARCv2 all have compatible toolchains.

[antonysigma]

Re: CMake. @lukevalenty Great! I am looking forward to it.

I hit roadblocks with CMake in the past with the Canadian cross compilation pattern. CMake needed a separate build folders for the generated executables, in order to generate headers/cpp like what we do in CIB::logging. Link here. I am glad CIB doesn't make the logging parsing tool a cpp requiring "native" compilation.

I use Meson build though. Probably I will port your examples over to Meson once CIB has a dev kit.

[mhanuel26]

Hi @lukevalenty I know you are super busy and I have see you very active here but so far no joy with the the dev. kit example. I myself don't have any clue where to start, maybe you can share something here to star playing around and get familiar with library? Or maybe some instructions how to set up the AVR example and go from there? Thanks a mil

[basavarajubv]

@lukevalenty : I thought your cppcon talk from last year would be starting point for all!?

Composition on Tiny Embedded Systems in C++

Can that be added as an example here!?

[lukevalenty]

We are working on a dedicated repo that can be used to build projects with CIB. It's a bit more involved that what fits in the example folder. :( Stay tuned.

[antonysigma]

I am also half-way through implementing a blinky demo with CIB with compile-time logging features. Here: https://github.com/antonysigma/compile-time-init-build?tab=readme-ov-file#quick-start

The gotcha is that we have to rollback cib to the version before the libfmt integration.

Here's the list of additional changes teach cib to to call libarduino APIs: https://github.com/antonysigma/compile-time-init-build/pull/1/files