Looking for open source enthusiasts to improve the BabyOS open source project

liklon

Looking for open source enthusiasts to improve the BabyOS open source project [Copy link]

 

In December last year, when the BabyOS open source project was launched, it was shared on eeworld: https://en.eeworld.com/bbs/thread-1102261-1-1.html

At that time, it was not mature enough and was not recognized by engineers. However, BabyOS did not stop updating. After six months of development, its framework and structure had become stable, and it was selected into the GVP project of Code Cloud in May.

So I share it again this time, hoping that the code can be further optimized and improved through the inspection of the engineers here.

After reading the positioning of BabyOS, you will understand that it needs the contribution of netizens to reflect its value. Now the overall framework has been perfected and needs to be filled with content. Are there any friends willing to develop together:

Many hands make light work
We hope that some netizens can be responsible for the design and development of the following items:
1. Communication module
2. Motion sensor
3. Environmental sensor
4. Biosensor
(each person can be responsible for one item, and it is better to be responsible for multiple items. Each item will have subdivisions, and you can also be responsible for only one of the subdivisions, such as only responsible for the NB module of the communication module, etc.)

I hope that netizens can develop together and integrate our resources, so that it will be extremely convenient and hassle-free to develop projects in the future.

Below is the repository address and latest documentation of the BabyOS open source project:

链接已隐藏，如需查看请登录或者注册

BabyOS设计和使用手册.pdf (889.19 KB, downloads: 20)

2020-6-9 15:38 上传

点击文件名下载附件

liklon

I am sincerely looking for friends who are willing to develop together. I hope that friends who are interested can go to the repository to clone a copy of the code and take a look. After reading the code and README, if you are still interested, please join us. If you find areas that need improvement, please join us to optimize! If you have not read the code or README, I can only say thank you for visiting this post!

okhxyyo

Give the author a thumbs up! Keep it up! I'll put you on the Today's Focus to promote it

liklon

okhxyyo posted on 2020-6-9 17:04 Like the OP! Come on! I'll promote you on Today's Focus

Thank you for your support Thank you for your support

GuyGraphics

It looks like a pan-AUTOSAR project. Thumbs up to the author!

yang_alex

What MCU kernels does BabyOS support? Different MCUs have different instructions, and the underlying drivers need to be encapsulated. In addition, it is best to implement the configuration function of the graphical interface first, so there is no need to copy and paste manually.

liklon

GuyGraphics posted on 2020-6-9 20:10 It looks like a pan-AUTOSAR project. Thumbs up to the author!

Thank you for your support

liklon

yang_alex published on 2020-6-9 23:19 What MCU kernels does BabyOS support? Different MCUs have different instructions, and the underlying drivers must be encapsulated again. In addition, it is best to implement the configuration of the graphical interface first...

You can take a look at the code first. BabyOS does not consider instructions. It is currently recommended to use MCUs with M series kernels. BabyOS has a hardware abstraction layer. Different MCUs only need to implement the API in the hardware abstraction layer. The driver and functional modules do not need to be modified and can be used directly. There is no need for a graphical configuration interface. For the driver, you only need to modify the hardware interface definition in b_hal. For the functional module, if you are using MDK, you can use the graphical configuration interface that comes with MDK. It is recommended that you actually take a look at the code or the README of the repository first.

arm8686

Star it first! Then take a closer look.

Like the following integrations (external links removed):

BabyOS includes third-party open source code, which is quite useful in MCU projects.
The b_shell function module is based on the open source project nr_micro_shell, thanks to the author Nrush.
The b_button function module is based on the open source project FlexibleButton, thanks to the author Murphy.
The b_gui function module is based on the open source project uGUI, thanks to the
author Achimdoebler. The b_trace function module is based on the open source project CmBacktrace, thanks to the author Armink.

liklon

arm8686 posted on 2020-6-10 08:59 Star first! Take a closer look. Like the following integration (external links have been removed): BabyOS includes third-party open source code, which is...

Thank you for your support. In addition to the following items, FatFS LittleFS and SFUD are also integrated, which are all enabled with one click, which is quite convenient and saves trouble.

ilovefengshulin

It's a bit like a RTOS family bucket, help

Alaric

Support, feels like a device framework

liklon

ilovefengshulin published on 2020-6-10 15:48 It's a bit like a RTOS family bucket, help me

Thank you for your support, this is not an RTOS, there are many RTOS now, so we don't want to join in the fun, and position this code for bare metal development users, with framework function modules and driver libraries. Users who use RTOS can also use this code as a function library and driver library

liklon

Alaric posted on 2020-6-11 09:48 Support, it feels like a device framework

Thank you for your support. The device driver structure is also a key point here. Another part is the function module. The function module to be used is selected through the configuration file

wbhb2011

I hope to make some contribution through research. Many devices really only need a very simple OS, just like a baby that is fed when it cries and is sleeping when it is not crying.