Introduction and preparation for the "Add BSP for Polarfire based Beagle" Project

[Vijay Kumar Banerjee]

Hi Purva,

On Tue, Apr 23, 2024 at 3:18 PM Purva Yeshi <purvayeshi550 at gmail.com> wrote:

> Hello Sir,
>

Please feel free to call me Vijay :)


>
> Up until now, I have been studying the BSP driver documentation from
> https://docs.rtems.org/branches/master/bsp-howto/ . I have gained a good
> understanding of why and how target-dependent files are written.
> Additionally, I am currently working on how the console and clock driver
> are written.
>
> That's great! You might be able to relate some of the documentation to the
riscv BSP code in the repository.


> Furthermore, I have been modifying the target-dependent files by adding
> more examples to make them more understandable for new users.
>

Have you set up any public repository that we might be able to follow and
provide early feedback? It is okay to have work-in-progress commits in your
repository.


Best regards,
Vijay

>
> On Fri, 5 Apr 2024 at 21:36, Purva Yeshi <purvayeshi550 at gmail.com> wrote:
>
>> Thank you for all the resources.
>>
>> Yes, I go through the documentation and the codebase, and I'll try to
>> send patches
>> Okay, got the point about mailing list and github
>>
>> On Fri, 5 Apr 2024 at 02:21, Vijay Kumar Banerjee <vijay at rtems.org>
>> wrote:
>>
>>> Hi Purva,
>>>
>>>
>>>
>>> On Thu, Apr 4, 2024 at 6:05 AM Purva Yeshi <purvayeshi550 at gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am Purva Yeshi, I applied for the project "Add BSP for Polarfire
>>>> based Beagle" for GSoC 2024. I proposed a project to create a BSP for the
>>>> Beagle-V fire board from scratch. The primary objective of the project is
>>>> to run a "Hello World" code and a ticker on the board. After that, I will
>>>> focus on developing support for other devices such as Ethernet and U54 MMU.
>>>>
>>>> Great! Thanks for completing the proposal and submitting it on the
>>> portal.
>>>
>>>
>>>> During this waiting period for acceptance, I want to familiarize myself
>>>> with the codebase of existing supported components of other RISC-V BSP
>>>> variants. As part of my preparation, I have already built an RTEMS
>>>> development environment and successfully completed the RTEMS Hello World
>>>> project on the Qemu spike simulator for the riscv/rv64imafdc BSP variant.
>>>>
>>>>
>>> Since you already have a working RTEMS environment, it would be a great
>>> idea to start looking at the source code organization of riscv bsps (
>>> https://git.rtems.org/rtems/tree/bsps/risc). It would also be helpful
>>> to find some smaller issues (maybe in the documentation) and try to send
>>> patches for that. Submitting patches for smaller issues is a great idea to
>>> become familiar with the code contribution process. The documentation for
>>> riscv bsps can be found at
>>> https://docs.rtems.org/branches/master/user/bsps/bsps-riscv.html
>>>
>>> You can also utilize this time to read up on the Beagle-V fire
>>> documentation and the prior FreeBSD efforts to support that board.
>>>
>>> Could you please provide guidance on this. Additionally, is there any
>>>> specific task or area you suggest I focus on during this period for the
>>>> project?
>>>>
>>>
>>> Feel free to ask about anything you find interesting (or confusing)
>>> while going through the source code and the documentation. Especially with
>>> the documentation, if something confuses you it likely confuses other
>>> people too, it can be a place to make a great contribution!
>>>
>>> The mailing list is the best place to discuss longer questions, and the
>>> discord channel is better for quick help from people who are signed in. The
>>> discord channel has a subset of the RTEMS developers on it, the mailing
>>> list has a wider audience.
>>>
>>>
>>> Good luck with the GSoC application!
>>>
>>> Best regards,
>>> Vijay
>>>
>>> _______________________________________________
>>>
>>>> devel mailing list
>>>> devel at rtems.org
>>>> http://lists.rtems.org/mailman/listinfo/devel
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20240423/614d80b7/attachment-0001.htm>