[OSPP 2025] Project - Adding Standard Device Tree support for Embox RTOS

[Shankari]

Hello,

My name is Shankari and I'm excited to introduce myself and express interest in the project “Adding Standard Device Tree support for Embox RTOS” under the OSPP program.

To begin, I plan to go through open issues on the GitHub repository and familiarize myself with how device configuration is currently implemented in Embox. If you have any suggestions, pointers, or relevant code areas I should start with, I’d be grateful for your guidance.

Looking forward to learning and contributing!

Thanks and regards,  
Shankari

[Anton Bondarev]

Hello Shankari,

Thank you for your interest in the project.

You have a good plan for entering the project!

One more point for starting if you've not seen it yet we described our experience to involving students in the article (https://anton-bondarev.medium.com/embox-participating-in-gsoc2020-f130815368ed)

Feel free to ask any questions

Best regards,

Anton

пн, 5 мая 2025 г. в 23:46, Shankari <shankari...@gmail.com>:

--
You received this message because you are subscribed to the Google Groups "embox-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to embox-devel...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/embox-devel/CAB6LErdTrCJ6p%2BRQyPdKvuxbbR4nyi4fUTFvpZgMw7204Gvm0A%40mail.gmail.com.

[Zixian Zeng]

Hello Shankari,

Thank you for your email and interest in the project "Adding Standard

Device Tree support for Embox RTOS" under the OSPP program.

On 25/05/06 02:16AM, Shankari wrote:
> Hello,
>
> My name is Shankari and I'm excited to introduce myself and express
> interest in the project “Adding Standard Device Tree support for Embox
> RTOS” under the OSPP program.
>
> To begin, I plan to go through open issues on the GitHub repository and
> familiarize myself with how device configuration is currently implemented
> in Embox. If you have any suggestions, pointers, or relevant code areas I
> should start with, I’d be grateful for your guidance.
>

Issue in Github is an excellent place to record. Go ahead..

> Looking forward to learning and contributing!
>
> Thanks and regards,
> Shankari

I already replied to your private email, but I will repeat it here for
public mailing list :-)

First of all, welcome to the project! I am glad to see your interest in
Embox and the OSPP program. Embox open source community is very welcoming
for newcomers.

Getting started, please read the following document of Embox GsoC 2020[1]
for some background information. Embox has an English wiki[2] and a
Russian wiki[3]. Please read some parts which you think are useful.

After that, you can take the Good First Issues to get familiar with the
whole code base. Embox use the Mybuild build system, which might not
used elsewhere. Familiarity with the building system will help for sure :-)

Back to the topic of our project, the device tree. The device tree is a
already used in the Linux kernel and U-boot for a long time. Taking that
for example is easier than starting from scratch.[4]

DTC/libfdt is an open source project which provides generic functionality.
You need to consider what actually it gives conveniently to Embox and
**YOU**, this requires some embedded system experience.
And you need to consider whether functions are basic or can be added later-on.

As mentioned above, Embox uses the Mybuild build system, which actually
contains parts of the platform/board-dependent information which we
want to move to the device tree. Design a proper way to integrate both
but without breaking too much existing design is a challenge and worth
thinking about.

At last, Embox is very willing to accept PRs and contributions. Have
Fun in Open Source!

Link: https://anton-bondarev.medium.com/embox-participating-in-gsoc2020-f130815368ed
[1]
Link: https://github.com/embox/embox/wiki [2]
Link:
https://web.archive.org/web/20160105031702/https://code.google.com/p/embox/wiki/QuickOverview?wl=ru
[3]
Link: https://docs.kernel.org/devicetree/index.html [4]


Best regards,
Damon

[Shankari]

Hello,

> One more point for starting if you've not seen it yet we described our experience to involving students in the article (https://anton-bondarev.medium.com/embox-participating-in-gsoc2020-f130815368ed)

Sure, I'll read through the doc. Thanks!

> Back to the topic of our project, the device tree. The device tree is a
> already used in the Linux kernel and U-boot for a long time. Taking that
> for example is easier than starting from scratch.[4]


> DTC/libfdt is an open source project which provides generic functionality.
> You need to consider what actually it gives conveniently to Embox and
> **YOU**, this requires some embedded system experience.
> And you need to consider whether functions are basic or can be added later-on.


> As mentioned above, Embox uses the Mybuild build system, which actually
> contains parts of the platform/board-dependent information which we
> want to move to the device tree. Design a proper way to integrate both
> but without breaking too much existing design is a challenge and worth
> thinking about.

> Link: https://anton-bondarev.medium.com/embox-participating-in-gsoc2020-f130815368ed
> [1]
> Link: https://github.com/embox/embox/wiki [2]
> Link:
> https://web.archive.org/web/20160105031702/https://code.google.com/p/embox/wiki/QuickOverview?wl=ru
> [3]
> Link: https://docs.kernel.org/devicetree/index.html [4]

Thanks for the resources, I'll devise a good plan to follow after
going through these and update on my findings.

Regards,
Shankari

[Shankari]

Hello,

I've successfully set up Embox on my system and have submitted a pull request for the good first issue #3594. I'm looking forward to taking on a few more issues to continue contributing and learning.

In parallel, I'm also beginning to explore the inclusion of device tree support, and I’ll be sure to share updates as I make progress.

Thank you for the opportunity, and I’m excited to keep contributing to the project.

Thanks and regards,

Shankari

[Anton Bondarev]

Hello Shankari,

Thank you for the contributions!

Best regards,

Anton

вс, 11 мая 2025 г. в 08:55, Shankari <shankari...@gmail.com>:

--

You received this message because you are subscribed to the Google Groups "embox-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to embox-devel...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/embox-devel/CAB6LEre%3DE4hwvzpP%2BXrLm%2Bj4S%2B2f1Vd6TmRwbhC11neED25ntg%40mail.gmail.com.

[Shankari]

Hello, 

I was going through the resources given here - adding-standard-device-tree-support-for-embox-rtos
This link - (Device Tree spec: https://www.devicetree.org/specifications/) seems to be broken. Should it be pointing somewhere else? 

[Anton Bondarev]

Hello Shankari,

Thanks for the information. I see the trouble, I hope it will be fixed soon!

You can get specification on the github
https://github.com/devicetree-org/devicetree-specification/releases

Best regards,

Anton Bondarev

сб, 17 мая 2025 г. в 07:45, Shankari <shankari...@gmail.com>:

To view this discussion visit https://groups.google.com/d/msgid/embox-devel/514a3a0d-fd25-419d-bcac-74547596d7b8n%40googlegroups.com.

[Shankari]

Thanks!

[Shankari]

Hello,

I was trying to test embox on rpi zero w as per this issue -
https://github.com/embox/embox/issues/3251.
I had a doubt about the image I have to create on the sd card. I tried
creating only the embox image after make -
make confload/platform_raspberrypi/rpi0w
make
sudo dd if=build/base/bin/embox.img of=/dev/mmcblk0p1 bs=4M
status=progress conv=fsync

But the rpi_zero_w won't boot in this image. It was working if I built
the normal raspberry pi OS. So am I supposed to build the embox image
above the raspberry pi OS?

On Sun, May 18, 2025 at 6:35 PM Shankari <shankari...@gmail.com> wrote:
>
> Thanks!
>
> On Saturday, May 17, 2025 at 4:22:38 PM UTC+5:30 Anton Bondarev wrote:
>>
>> Hello Shankari,
>>
>> Thanks for the information. I see the trouble, I hope it will be fixed soon!
>> You can get specification on the github
>> https://github.com/devicetree-org/devicetree-specification/releases
>>
>> Best regards,
>> Anton Bondarev
>>
>> сб, 17 мая 2025 г. в 07:45, Shankari <shankari...@gmail.com>:
>>>
>>> Hello,
>>>
>>> I was going through the resources given here - adding-standard-device-tree-support-for-embox-rtos
>>> This link - (Device Tree spec: https://www.devicetree.org/specifications/) seems to be broken. Should it be pointing somewhere else?
>>>
>>>

> You received this message because you are subscribed to a topic in the Google Groups "embox-devel" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/embox-devel/F1WUjd_WEJo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to embox-devel...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/embox-devel/8bd88096-11b1-4138-8f8d-e0c8c71092ben%40googlegroups.com.

[Shankari]

Hello, 
Minor tag to follow up on the issue. Thanks!

[Damon Bryce]

Hello, Shankari
Sorry for late reply, I suggest putting the discussion to github issue.
I guess the problem is that you broken the file system using dd command. Maybe you can paste your detailed log on github issue, and we find out the problem here

Cheers,

Damon

[Shankari]

> Hello, Shankari
> Sorry for late reply, I suggest putting the discussion to github issue.
> I guess the problem is that you broken the file system using dd command. Maybe you can paste your detailed log on github issue, and we find out the problem here
> Cheers,
> Damon

Sure, I'll do that

> To view this discussion visit https://groups.google.com/d/msgid/embox-devel/c83aa00e-9da5-4af3-85ce-26b815636fc3n%40googlegroups.com.