Lesson 14. Super Loop and Software Module Patterns

[@Zahkcary]

This video is extremely informative, and you're an excellent narrator. I really appreciate the effort you put into it.

[@geneschroedertech7501]

Thanks for the kind words. I hope the course is helpful.

[@mihaelgradillasantiago724]

This is wonderful information. I wish you could have been my teacher for my embedded systems course. I appreciate you making these videos and sharing your knowledge with us.

[@geneschroedertech7501]

Thank you for your kind words.

[@michaelliuzzi]

Im a developer for work, but not on MCUs. This class has been extremely helpful for me in my hobby work, and i really appreciate you taking the time to put this together. It's such an excellent resource.

[@geneschroedertech7501]

@michaelliuzzi Thanks, I'm glad you found it helpful, and I'm impressed that you are taking the time to learn at this level as a hobbyist.

[@Pyrografpl]

Wow thank you 😃

[@geneschroedertech7501]

Thanks, I hope it is useful.

[@salmantechnologies282]

what is API as you are mentioning every time can i ask

[@geneschroedertech7501]

I am referring to the very informal API I have for my modules. I made it up and you can make up your API as well, based on your needs. The idea is that all modules have a common set of "core" APIs, plus some specialized APIs specified to the module. Like most software developers, I liked consistency in my design, so having a common set of "core" APIs makes me feel better :). So when I create a new module, I first define the "core" functions for that module and not have to think about it too much. To be clear, the base APIs are: XXX_get_def_cfg() XXX_init() XXX_start() XXX_run() where "XXX" is the module name. See the header files in modules/include folder for examples.