Re: GSoC project suggestion for the BSP Raspberry pi 4B aarch64

The Pynq is a low cost Zynq board I have wanted to have support for. http://www.pynq.io/board.html Basic support should be a matter of tweaking the settings and adding a bsp variant On Sat, Feb 25, 2023, 10:21 AM Alan Cudmore wrote: > Improving Raspberry Pi 4 support would be a great GSOC proj

Re: GSoC project suggestion for the BSP Raspberry pi 4B aarch64

Improving Raspberry Pi 4 support would be a great GSOC project. Right now the Beagleboard is my default for a low cost network enabled RTEMS board. But a Pi4 with network and SMP support would be a great board to learn RTEMS. Even better if the supply problems are addressed this year. In addition t

Re: GSoC project suggestion for the BSP Raspberry pi 4B aarch64

That's all great information to include in the ticket and/or the Users Guide. On Sun, Feb 19, 2023, 7:44 AM Noor Aman wrote: > I booted freeBSD on the Raspberry pi, I was able to confirm that it used > genet driver together with miibus for the NIC. This is further confirmed > with the FreeBSD

Re: GSoC project suggestion for the BSP Raspberry pi 4B aarch64

I booted freeBSD on the Raspberry pi, I was able to confirm that it used genet driver together with miibus for the NIC. This is further confirmed with the FreeBSD manual page. https://man.freebsd.org/cgi/man.cgi?query=genet One more thing to follow is that i noticed that FreeBSD is using PSCI, so

Re: GSoC project suggestion for the BSP Raspberry pi 4B aarch64

On Sat, Feb 18, 2023 at 11:09 AM Noor Aman wrote: > > Hey everyone, > Last year I helped with the porting of RTEMS-aarch64 for Raspberry Pi 4B > with Kinsey, Alan and Hesham. I'm looking forward to continuing my project > further. As of now, I have 2 projects in my mind. > Every GSoC project sho

Re: GSoC Project - Beagle BSP Projects

Hi, Sorry for not providing detailed explanations and for the late response. On Sun, May 2, 2021 at 5:31 PM Christian Mauderer wrote: > Hello Husni, > > On 01/05/2021 23:38, Ahamed Husni wrote: > > Hi all, > > > > My project proposal > > > https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4

Re: GSoC Project - Beagle BSP Projects

Hello Husni, On 01/05/2021 23:38, Ahamed Husni wrote: Hi all, My project proposal https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing I tried to set

Re: GSoC Project - Beagle BSP Projects

Hi all, My project proposal https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing I tried to set up the JTAG Environment for the Beaglebone Black. But I couldn't find the hardware anywhere in my country (Sri Lanka). I tried to, 1. Find TI XDS Debugg

Re: GSOC project: #4272 BSP Executable Conversion

Hello everyone , I am working on project "BSP Executable Conversion" (https://devel.rtems.org/ticket/4272) where I have to make BSP specific script for conversion of executables from RTEMS executable format to the BSP boot loader format so that it can be run on target. I know that the previous vers

Re: GSoC Project - Beagle BSP Projects

Hi all, I have prepared a draft proposal . Added the proposal link to RTEMS Wiki. Husni Faiz - https://devel.rtems.org/wiki/GSoC/2021 Please have a look and let me know your thoughts. The project desc

Re: GSOC project: #4272 BSP Executable Conversion

Sir I have made a draft for the project https://devel.rtems.org/ticket/4272 after some discussion about it on discord and mail-list . I would be highly grateful to get some comments and reviews about it in improving the draft (for example the part related to adding support of newly created scripts

Re: GSOC project: #4272 BSP Executable Conversion

On Tue, Apr 6, 2021 at 6:22 AM Ayushman Mishra wrote: > I checked all the BSPs having bsp-post-link in their config file (find > . -name *.cfg | xargs -e grep define | grep bsp-post-link) but > couldn't find similarity between them (other than "$(OBJCOPY) -O > binary --strip-all \ $(basename $@)$

Re: GSOC project: #4272 BSP Executable Conversion

On Tue, Apr 6, 2021 at 5:22 AM Ayushman Mishra wrote: > > I checked all the BSPs having bsp-post-link in their config file (find > . -name *.cfg | xargs -e grep define | grep bsp-post-link) but > couldn't find similarity between them (other than "$(OBJCOPY) -O > binary --strip-all \ $(basename $@)

Re: GSOC project: #4272 BSP Executable Conversion

I checked all the BSPs having bsp-post-link in their config file (find . -name *.cfg | xargs -e grep define | grep bsp-post-link) but couldn't find similarity between them (other than "$(OBJCOPY) -O binary --strip-all \ $(basename $@)$(EXEEXT) $(basename $@)$(BINEXT) " in most of them . Sir I wante

Re: GSoC Project- BSP Executable Conversion

On Sat, Apr 3, 2021 at 1:29 PM Daman Bir Singh wrote: > > Thanks for the update. > > If It's not too late, another project I would like to suggest is 4213, > libbsd: Reduce footprint of minimal buildset. Please tell me if I can go > ahead with this project. > Yes, #4213 would be suitable for pro

Re: GSOC project: #4272 BSP Executable Conversion

Boot-loader is used to initialize the hardware device , but is there any way to simulate the boot-loader without hardware?. And I suppose the command "rtems-boot-image" performs somewhat similar function to one of the objective of this project "This project is about capturing the commands and logic

Re: GSoC Project- BSP Executable Conversion

Thanks for the update. If It's not too late, another project I would like to suggest is 4213 , libbsd: Reduce footprint of minimal buildset. Please tell me if I can go ahead with this project. Thanks & Regards, Daman On Tue, Mar 30, 2021 at 9:48 PM Gedare Blo

Re: GSoC Project - Beagle BSP Projects

On 02/04/2021 08:36, Ahamed Husni wrote: >     Yes, this seems like an area that can be chipped away at, with a >     strong plan of activities. My concern would be whether it is about >     writing code or not? > > > After completing the above

Re: GSOC project: #4334 Replace Mongoose with Civetweb

On Thu, Apr 1, 2021 at 10:13 PM Ayushman Mishra wrote: > > Respected Sir, > > 1. I successfully build and installed the tool suit in rtems6 > (../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 > devel/qemu.bset) , this time all executable related to qemu This is building and inst

Re: GSoC Project - Beagle BSP Projects

> > > Yes, this seems like an area that can be chipped away at, with a >> > strong plan of activities. My concern would be whether it is about >> > writing code or not? >> > >> > >> > After completing the above milestones, if we have more time I can start >> > to work on >> > the Mass s

Re: GSOC project: #4334 Replace Mongoose with Civetweb

Respected Sir, 1. I successfully build and installed the tool suit in rtems6 (../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6 devel/qemu.bset) , this time all executable related to qemu (qemu-system-arm) were installed in 6/bin but the gcc file (arm-rtems6-gcc) and other arm-rt

Re: GSoC project: #3850 Modular Network Stacks

Dear mentors, Thank you for providing information regarding the project. I have started making the proposal for this ticket. I'll share it once I have a draft of it ready. Thanks and regards, Rajiv On Mon, 22 Mar 2021 at 21:43, Joel Sherrill wrote: > > > On Mon, Mar 22, 2021, 10:23 AM Christia

Re: GSOC project: #4334 Replace Mongoose with Civetweb

On Wed, Mar 31, 2021 at 3:18 AM Ayushman Mishra wrote: > > Sir, > I am trying to integrate mongoose web-server in simple rtems > application (https://devel.rtems.org/wiki/Developer/Mongoose_Web_Server), > for that I have to configure networking in rtems. I am using > xilinx_zynq_a9_qemu for simula

Re: GSOC project: #4334 Replace Mongoose with Civetweb

Sir, I am trying to integrate mongoose web-server in simple rtems application (https://devel.rtems.org/wiki/Developer/Mongoose_Web_Server), for that I have to configure networking in rtems. I am using xilinx_zynq_a9_qemu for simulation bsp and following steps given here https://git.rtems.org/rtems-

Re: GSoC Project- BSP Executable Conversion

Hi Daman, On Sat, Mar 27, 2021 at 12:00 AM Daman Bir Singh wrote: > > Hello, > > Another project I am interested in is ticket #3302, Build System conversion > of BSP Config (.cfg) files to pkg-config (.pc) files. Please guide me which > one is more relevant for GSOC'21 and how to start working

Re: GSOC project: #4334 Replace Mongoose with Civetweb

Hello Ayushman, hello Gedare, Am 29.03.21 um 18:50 schrieb Gedare Bloom: CC: Christian On Mon, Mar 29, 2021 at 10:34 AM Ayushman Mishra wrote: Sir , It would be very helpful to know about potential mentors of (Replace mongoose with civetweb) https://devel.rtems.org/ticket/4334 this project.

Re: GSOC project: #4334 Replace Mongoose with Civetweb

CC: Christian On Mon, Mar 29, 2021 at 10:34 AM Ayushman Mishra wrote: > > Sir , > It would be very helpful to know about potential mentors of (Replace mongoose > with civetweb) https://devel.rtems.org/ticket/4334 this project. > I think Christian is the most likely potential mentor. > On Mon, M

Re: GSOC project: #4334 Replace Mongoose with Civetweb

Sir , It would be very helpful to know about potential mentors of (Replace mongoose with civetweb) https://devel.rtems.org/ticket/4334 this project. On Mon, Mar 29, 2021, 9:39 PM Gedare Bloom wrote: > On Mon, Mar 29, 2021 at 9:49 AM Ayushman Mishra > wrote: > > > > I have installed libbsd packa

Re: GSOC project: #4334 Replace Mongoose with Civetweb

On Mon, Mar 29, 2021 at 9:49 AM Ayushman Mishra wrote: > > I have installed libbsd package (made > RTEMS_POSIX_API=True,RTEMS_NETWORKING=True in config.ini file to > enable POSIX and networking) but I am still confused about the work That doesn't look right. RTEMS_NETWORKING=True enables the legac

Re: GSOC project: #4334 Replace Mongoose with Civetweb

I have installed libbsd package (made RTEMS_POSIX_API=True,RTEMS_NETWORKING=True in config.ini file to enable POSIX and networking) but I am still confused about the work already done in this project in past. Also after interacting on discord I think completely replacing mongoose with another web-

Re: GSOC project: #4334 Replace Mongoose with Civetweb

Greetings to all the respected mentors, 1. I saw there has been a lot of discussion regarding replacing mongoose with civetweb ( https://lists.rtems.org/pipermail/devel/2016-April/014661.html ). I think the basic outline of the project is like this a. Completely removing mongoose and replace it wit

Re: GSoC project: Memory protection (Ticket no: 2904)

Hello Rajiv, The project is a bit advanced. To be able to use MMU, RTEMS has to be ported to RISC-V's S-Mode. I created a ticket for that a few years ago [1]. This needs a decent understanding of RISC-V and non-trivial efforts to refactor RTEMS and its exception/interrupt handling, context-switchi

Re: GSoC Project- BSP Executable Conversion

Hello, Another project I am interested in is ticket #3302 , Build System conversion of BSP Config (.cfg) files to pkg-config (.pc) files. Please guide me which one is more relevant for GSOC'21 and how to start working on it. On Fri, Mar 19, 2021 at 7:52 AM Dam

Re: GSoC Project : Package Micro-python

On Fri, Mar 26, 2021 at 5:46 AM Joel Sherrill wrote: > > > On Wed, Mar 24, 2021, 1:43 PM Gedare Bloom wrote: > >> On Wed, Mar 24, 2021 at 11:38 AM Eshan Dhawan >> wrote: >> > >> > >> > >> > On Wed, Mar 24, 2021 at 12:34 AM Gedare Bloom wrote: >> >> >> >> On Tue, Mar 23, 2021 at 12:16 PM Eshan

Re: GSoC Project - Beagle BSP Projects

Hello Ahamed, Am 26.03.21 um 15:31 schrieb Ahamed Husni: USB OTG would be a nice area. But that will be less writing a driver for Beagle but more finding out how that works with libbsd and finding a good way to configure it. I once put a few hours into it didn't take too

Re: GSoC Project - Beagle BSP Projects

> > USB OTG would be a nice area. But that will be less writing a driver for > Beagle but more finding out how that works with libbsd and finding a > good way to configure it. I once put a few hours into it didn't take too > much time till a PC detected an USB device (see > https://gitlab.com/c-mau

Re: GSoC project: Memory protection (Ticket no: 2904)

Dear Hesham, Thank you for providing information about the RISC-V MMU. I want to know what work has to be done in improving MMU in RISC-V and if it can be a GSoC project. It would be great if you could provide the details regarding this. Thanks and regards, Rajiv On Wed, 24 Mar 2021 at 00:03, He

Re: GSoC Project : Package Micro-python

On Wed, Mar 24, 2021, 1:43 PM Gedare Bloom wrote: > On Wed, Mar 24, 2021 at 11:38 AM Eshan Dhawan > wrote: > > > > > > > > On Wed, Mar 24, 2021 at 12:34 AM Gedare Bloom wrote: > >> > >> On Tue, Mar 23, 2021 at 12:16 PM Eshan Dhawan > wrote: > >> > > >> > > >> > Apologies for the late reply. >

Re: GSoC Project : Package Micro-python

On Wed, Mar 24, 2021 at 11:38 AM Eshan Dhawan wrote: > > > > On Wed, Mar 24, 2021 at 12:34 AM Gedare Bloom wrote: >> >> On Tue, Mar 23, 2021 at 12:16 PM Eshan Dhawan >> wrote: >> > >> > >> > Apologies for the late reply. >> > >> > On Mon, Mar 22, 2021 at 10:27 PM Joel Sherrill wrote: >> >> >>

Re: GSoC Project : Package Micro-python

On Wed, Mar 24, 2021 at 12:34 AM Gedare Bloom wrote: > On Tue, Mar 23, 2021 at 12:16 PM Eshan Dhawan > wrote: > > > > > > Apologies for the late reply. > > > > On Mon, Mar 22, 2021 at 10:27 PM Joel Sherrill wrote: > >> > >> > >> > >> On Mon, Mar 22, 2021 at 11:55 AM Gedare Bloom wrote: > >>> >

Re: GSoC Project : Package Micro-python

On Tue, Mar 23, 2021 at 12:16 PM Eshan Dhawan wrote: > > > Apologies for the late reply. > > On Mon, Mar 22, 2021 at 10:27 PM Joel Sherrill wrote: >> >> >> >> On Mon, Mar 22, 2021 at 11:55 AM Gedare Bloom wrote: >>> >>> On Mon, Mar 22, 2021 at 10:50 AM Joel Sherrill wrote: >>> > >>> > >>> > >>>

Re: GSoC project: Memory protection (Ticket no: 2904)

On Tue, 23 Mar 2021 at 17:14, Gedare Bloom wrote: > > CC: Hesham > CC: devel > > On Tue, Mar 23, 2021 at 6:34 AM Rajiv Vaidyanathan > wrote: > > > > Dear Gedare, > > > > Thank you for providing information regarding the project. For risk-v MMU > > support, will I require to have hardware? > > >

Re: GSoC Project : Package Micro-python

Apologies for the late reply. On Mon, Mar 22, 2021 at 10:27 PM Joel Sherrill wrote: > > > On Mon, Mar 22, 2021 at 11:55 AM Gedare Bloom wrote: > >> On Mon, Mar 22, 2021 at 10:50 AM Joel Sherrill wrote: >> > >> > >> > >> > On Mon, Mar 22, 2021 at 11:30 AM Gedare Bloom wrote: >> >> >> >> On Sat

Re: GSoC Project - Beagle BSP Projects

On Tue, Mar 23, 2021 at 9:36 PM Nils Hölscher wrote: > Hi, > > Regarding the PRU. > I was able to load code to the PRU. > However I wasn't able to map IRQ interrupts to the PRU, thus unable to > communicate with it in a meaningful way > Just a small addition, AFAIK the issue with this was the f

Re: GSoC project: Memory protection (Ticket no: 2904)

On Tue, Mar 23, 2021 at 5:49 PM Rajiv Vaidyanathan < rajiv.vaidyanath...@gmail.com> wrote: > Dear Utkarsh, > > Thank you for providing these links. I would like to know if these pending > tasks are long enough to take it up as a GSoC project. > > Resolving the issues related to user extension iter

Re: GSoC Project - Beagle BSP Projects

Hello Gedare, Am 23.03.21 um 16:48 schrieb Gedare Bloom: CC: Nils, Utkarsh On Tue, Mar 23, 2021 at 9:17 AM Christian MAUDERER wrote: Hello Ahamed, Am 23.03.21 um 11:24 schrieb Ahamed Husni: Hi everyone, I'm really interested to work on the *Beagle BSP Projects* [#2891

Re: GSoC Project - Beagle BSP Projects

CC: Nils, Utkarsh On Tue, Mar 23, 2021 at 9:17 AM Christian MAUDERER wrote: > > Hello Ahamed, > > Am 23.03.21 um 11:24 schrieb Ahamed Husni: > > Hi everyone, > > > > I'm really interested to work on the *Beagle BSP Projects* [#2891 > > ]. * > > * > > *Adding P

Re: GSoC Project - Beagle BSP Projects

Hello Ahamed, Am 23.03.21 um 11:24 schrieb Ahamed Husni: Hi everyone, I'm really interested to work on the *Beagle BSP Projects* [#2891 ]. * * *Adding PRU Support* [#3730 ] project seems really interesting to me. This

Re: GSoC project: Memory protection (Ticket no: 2904)

CC: Hesham CC: devel On Tue, Mar 23, 2021 at 6:34 AM Rajiv Vaidyanathan wrote: > > Dear Gedare, > > Thank you for providing information regarding the project. For risk-v MMU > support, will I require to have hardware? > That's a good question. I don't know if the current risc-v simulators suppor

Re: GSoC project: Memory protection (Ticket no: 2904)

Dear Utkarsh, Thank you for providing these links. I would like to know if these pending tasks are long enough to take it up as a GSoC project. Thanks and regards, Rajiv On Tue, 23 Mar 2021 at 16:15, Utkarsh Rai wrote: > > > On Mon, Mar 22, 2021 at 9:54 PM Gedare Bloom wrote: > >> Hi Rajiv, >

Re: GSoC project: Memory protection (Ticket no: 2904)

On Mon, Mar 22, 2021 at 9:54 PM Gedare Bloom wrote: > Hi Rajiv, > > On Sat, Mar 20, 2021 at 12:40 AM Rajiv Vaidyanathan > wrote: > > > > Hello RTEMS community, > Hello Rajiv, > > > > I am interested in the ticket: Memory protection. I saw that this topic > has been pursued a few times in GSoC

Re: GSoC Project : Package Micro-python

On Mon, Mar 22, 2021 at 11:55 AM Gedare Bloom wrote: > On Mon, Mar 22, 2021 at 10:50 AM Joel Sherrill wrote: > > > > > > > > On Mon, Mar 22, 2021 at 11:30 AM Gedare Bloom wrote: > >> > >> On Sat, Mar 20, 2021 at 12:33 PM Eshan Dhawan > wrote: > >> > > >> > Hello Everyone, > >> > I wanted to ta

Re: GSoC Project : Package Micro-python

On Mon, Mar 22, 2021 at 10:50 AM Joel Sherrill wrote: > > > > On Mon, Mar 22, 2021 at 11:30 AM Gedare Bloom wrote: >> >> On Sat, Mar 20, 2021 at 12:33 PM Eshan Dhawan >> wrote: >> > >> > Hello Everyone, >> > I wanted to take Packaging Micro Python up as GSOC project this summer and >> > the pr

Re: GSoC Project : Package Micro-python

On Mon, Mar 22, 2021 at 11:30 AM Gedare Bloom wrote: > On Sat, Mar 20, 2021 at 12:33 PM Eshan Dhawan > wrote: > > > > Hello Everyone, > > I wanted to take Packaging Micro Python up as GSOC project this summer > and the project will also include packaging LUA and picoC > > The ticket for Micro Py

Re: GSoC Project : Package Micro-python

On Sat, Mar 20, 2021 at 12:33 PM Eshan Dhawan wrote: > > Hello Everyone, > I wanted to take Packaging Micro Python up as GSOC project this summer and > the project will also include packaging LUA and picoC > The ticket for Micro Python : https://devel.rtems.org/ticket/4349 > What would be the co

Re: GSoC project: Memory protection (Ticket no: 2904)

Hi Rajiv, On Sat, Mar 20, 2021 at 12:40 AM Rajiv Vaidyanathan wrote: > > Hello RTEMS community, > > I am interested in the ticket: Memory protection. I saw that this topic has > been pursued a few times in GSoC. It would be great if someone can let me > know the current status of this project a

Re: GSoC project: #3850 Modular Network Stacks

On Mon, Mar 22, 2021, 10:23 AM Christian Mauderer wrote: > Hello Rajiv, > > Am 22.03.21 um 16:11 schrieb Rajiv Vaidyanathan: > > Dear mentors, > > > > Thankyou for providing information about the project. I want to pursue > > this as my GSoC project. From the above discussion, I understand that >

Re: GSoC project: #3850 Modular Network Stacks

Dear mentors, Thankyou for providing information about the project. I want to pursue this as my GSoC project. From the above discussion, I understand that the following has to be done: 1. Collecting existing lwip drivers for BSPs and writing new ones. 2. Adding config files for driver management a

Re: GSOC project: #4334 Replace Mongoose with Civetweb

Thanks a lot for help and information , actually i am trying to setup mongoose on simple rtems application (https://devel.rtems.org/wiki/Developer/Mongoose_Web_Server) and for that right now I am trying to configure networking and file-system in the application. On Sun, Mar 21, 2021 at 8:54 PM Joe

Re: GSoC project: #3850 Modular Network Stacks

On 21/03/2021 18:53, Joel Sherrill wrote: On Sun, Mar 21, 2021, 12:47 PM Vijay Kumar Banerjee > wrote: Hi Rajiv and Joel, On Sun, Mar 21, 2021 at 9:06 AM Joel Sherrill mailto:j...@rtems.org>> wrote: > > > > On Sun, Mar 21, 2021, 9:20 AM R

Re: GSoC project: #3850 Modular Network Stacks

On Sun, Mar 21, 2021, 12:47 PM Vijay Kumar Banerjee wrote: > Hi Rajiv and Joel, > > On Sun, Mar 21, 2021 at 9:06 AM Joel Sherrill wrote: > > > > > > > > On Sun, Mar 21, 2021, 9:20 AM Rajiv Vaidyanathan < > rajiv.vaidyanath...@gmail.com> wrote: > >> > >> Hello RTEMS community, > >> > >> I found t

Re: GSoC project: #3850 Modular Network Stacks

Hi Rajiv and Joel, On Sun, Mar 21, 2021 at 9:06 AM Joel Sherrill wrote: > > > > On Sun, Mar 21, 2021, 9:20 AM Rajiv Vaidyanathan < rajiv.vaidyanath...@gmail.com> wrote: >> >> Hello RTEMS community, >> >> I found the ticket: Modular Network Stacks interesting. It would be great if someone can tell

Re: GSOC project: #4334 Replace Mongoose with Civetweb

On Sun, Mar 21, 2021, 4:45 AM Christian Mauderer wrote: > Hello Ayushman, > > On 21/03/2021 04:15, Ayushman Mishra wrote: > > Ayushman > > Hello everyone , I am very much interested in taking > > https://devel.rtems.org/ticket/4334 > > as a GSOC 2021 project. I know some basic networking concepts

Re: GSoC project: #3850 Modular Network Stacks

On Sun, Mar 21, 2021, 9:20 AM Rajiv Vaidyanathan < rajiv.vaidyanath...@gmail.com> wrote: > Hello RTEMS community, > > I found the ticket: Modular Network Stacks interesting. It would be great > if someone can tell the current status of this ticket and what > contributions can be done as a GSoC pro

Re: GSOC project: #4334 Replace Mongoose with Civetweb

Hello Ayushman, On 21/03/2021 04:15, Ayushman Mishra wrote: Ayushman Hello everyone , I am very much interested in taking https://devel.rtems.org/ticket/4334 as a GSOC 2021 project. I know some basic networking concepts and would like to learn more about it and how its applied to OS like RTEMS ,

Re: GSoC Project- BSP Executable Conversion

Thanks for the reply, Sorry for being impatient, I will keep that in mind from now on. Daman On Sat, Mar 20, 2021 at 11:28 AM Gedare Bloom wrote: > Hi Daman, > > On Fri, Mar 19, 2021 at 11:32 PM Daman Bir Singh > wrote: > > > > Hello, > > > > Should I look for any other project other than this

Re: GSoC Project- BSP Executable Conversion

Hi Daman, On Fri, Mar 19, 2021 at 11:32 PM Daman Bir Singh wrote: > > Hello, > > Should I look for any other project other than this? > I think the project is of interest. Please note that generally the mailing list is less active on the weekends. Usually, if your email doesn't get any response

Re: GSoC Project- BSP Executable Conversion

Hello, Should I look for any other project other than this? On Fri, Mar 19, 2021 at 7:52 AM Daman Bir Singh wrote: > Hello everyone, > > I am interested in pursuing ticket 4272 > as my GSoC project. I have started > going through the documentation to get t

Re: GSoC Project Wrap Up Activities

https://docs.google.com/document/d/1AhBCmFxOikBG7EBcAaTF7ol_D7SZGn0TJrPcifuVHnE/edit?usp=sharing is this link and I should have added both of you. If any mentor or student needs write access, just ask. It is hard to remember everyone. --joel On Wed, Aug 21, 2019 at 3:15 AM Vaibhav Gupta wrote:

Re: GSoC Project Wrap Up Activities

On Tue, Aug 20, 2019, 7:45 PM Joel Sherrill wrote: > Hi > > This has been a fantastic and productive GSoC. As part of wrapping > things up, we would like to make sure the following get taken care of: > > + Make sure all code and documentation is submitted, cleaned up and merged. >Ping mentors

Re: GSoC Project Wrap Up Activities

> > + GSoC Lightning Slides: I have shared a Google presentation with as some > of the >students and mentors. Please add 1-2 slides on your project. The > presentation >we are starting from is last year's. The slide deck will be used > for two purposes: > - 3 minute presentation at GSo

Re: GSoC Project Wrap Up Activities

https://www.rtems.org/gsoc2013_final_report That was the best one I found. I am embarrassed it is old. On Tue, Aug 20, 2019 at 12:21 PM Nils Hölscher wrote: > > Hi Joel, > > Can you link to one or two older reports as reference? > That would be great. > > Best, > Nils > > Joel Sherrill schrieb

Re: GSoC Project Wrap Up Activities

Hi Joel, Can you link to one or two older reports as reference? That would be great. Best, Nils Joel Sherrill schrieb am Di., 20. Aug. 2019, 16:15: > Hi > > This has been a fantastic and productive GSoC. As part of wrapping > things up, we would like to make sure the following get taken care o

Re: GSoC Project | Basic Support for Trace Compass

Documentation patch review is pending: https://lists.rtems.org/pipermail/devel/2019-August/027215.html > -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) , Dhanbad

Re: GSoC Project | Basic Support for Trace Compass

> > > What's the procedure for getting code merged? Do I have to raise PR on > > GitHub or simply send a patch on devel? > > First we have to integrate the initial support for the rtems-record > program: > > https://lists.rtems.org/pipermail/devel/2019-August/027278.html > > Then you can rebase you

Re: GSoC Project | Basic Support for Trace Compass

On 12/08/2019 12:27, Ravindra Kumar Meena wrote: This is too complicated: +    strcpy( filename, "event_" );       snprintf( file_index, sizeof( file_index ), "%ld", i );       strcat( filename, file_index ); In addition, the strcpy() and strcat() functions are dangerous t

Re: GSoC Project | Basic Support for Trace Compass

> > This is too complicated: > > +strcpy( filename, "event_" ); > snprintf( file_index, sizeof( file_index ), "%ld", i ); > strcat( filename, file_index ); > > In addition, the strcpy() and strcat() functions are dangerous to use. > Why don't you simply use: > > snprintf( filename,

Re: GSoC Project | Basic Support for Trace Compass

On 11/08/2019 09:51, Ravindra Kumar Meena wrote: rtems-main.c coding style fix: https://github.com/rmeena840/rtems-tools/commit/eeb2067783f7e375087bee913342ce3fecce7883 This is too complicated: +strcpy( filename, "event_" ); snprintf( file_index, sizeof( file_index ), "%ld", i );

Re: GSoC Project | Basic Support for Trace Compass

rtems-main.c coding style fix: https://github.com/rmeena840/rtems-tools/commit/eeb2067783f7e375087bee913342ce3fecce7883 > -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) , Dhanbad ___

Re: GSoC Project | Basic Support for Trace Compass

> > > Ok, good. Please always check if the babeltrace and Trace Compass give > the right results after the changes. > Yes. Both are displaying same output. > > If you use cctx->switch_event[ item->cpu ] and similar a couple of times > in a function, then please assign it to a local pointer and use

Re: GSoC Project | Basic Support for Trace Compass

- Am 9. Aug 2019 um 16:11 schrieb joel j...@rtems.org: > On Fri, Aug 9, 2019, 8:45 AM Sebastian Huber < > sebastian.hu...@embedded-brains.de> wrote: > >> >> - Joel Sherrill schrieb: >> > Coming in late but there isn't there a helper method to turn object names >> > into strings from eith

Re: GSoC Project | Basic Support for Trace Compass

On Fri, Aug 9, 2019, 8:45 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > > - Joel Sherrill schrieb: > > Coming in late but there isn't there a helper method to turn object names > > into strings from either 32 bit values or strings? Shouldn't that be > used? > > This progra

Re: GSoC Project | Basic Support for Trace Compass

- Joel Sherrill schrieb: > Coming in late but there isn't there a helper method to turn object names > into strings from either 32 bit values or strings? Shouldn't that be used? This program runs on the host. > > On Fri, Aug 9, 2019, 8:17 AM Sebastian Huber < > sebastian.hu...@embedded-bra

Re: GSoC Project | Basic Support for Trace Compass

Coming in late but there isn't there a helper method to turn object names into strings from either 32 bit values or strings? Shouldn't that be used? On Fri, Aug 9, 2019, 8:17 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 09/08/2019 15:06, Ravindra Kumar Meena wrote: > > rte

Re: GSoC Project | Basic Support for Trace Compass

On 09/08/2019 15:06, Ravindra Kumar Meena wrote: rtems-main.c cleanup: https://github.com/rmeena840/rtems-tools/commit/61d5dc45e43f0998ad9305d565926090215a5bdc Switch_event per CPU added: https://github.com/rmeena840/rtems-tools/commit/8ffe8bd2adea27772a9ab0e578539dd99fa0174b Have a look. Ok,

Re: GSoC Project | Basic Support for Trace Compass

rtems-main.c cleanup: https://github.com/rmeena840/rtems-tools/commit/61d5dc45e43f0998ad9305d565926090215a5bdc Switch_event per CPU added: https://github.com/rmeena840/rtems-tools/commit/8ffe8bd2adea27772a9ab0e578539dd99fa0174b Have a look. > -- *Ravindra Kumar Meena*, B. Tech. Computer Scienc

Re: GSoC Project | Basic Support for Trace Compass

> > > What to do for bound access for api_id? Should I use exit( EXIT_SUCCESS > > ) for this? > > You ignore this item an continue. > Okay https://github.com/rmeena840/rtems-tools/commit/24c7753238ab20fc8c002936657ee0f4c16a6e61 -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering

Re: GSoC Project | Basic Support for Trace Compass

On 08/08/2019 17:29, Ravindra Kumar Meena wrote: print_item() cleanup: https://github.com/rmeena840/rtems-tools/commit/76f1d2898729c9f885abaef1e33a58247c4760dd What to do for bound access for api_id? Should I use exit( EXIT_SUCCESS ) for this? You ignore this item an continue. The LTTng

Re: GSoC Project | Basic Support for Trace Compass

print_item() cleanup: https://github.com/rmeena840/rtems-tools/commit/76f1d2898729c9f885abaef1e33a58247c4760dd What to do for bound access for api_id? Should I use exit( EXIT_SUCCESS ) for this? The LTTng metadata also needs a license at the top. What should I add there? Thanks -- *Ravindra

Re: GSoC Project | Basic Support for Trace Compass

rtems-main.c cleanup: https://github.com/rmeena840/rtems-tools/commit/527fc0f2f3c971c21741b28b1f0ecde6efb6eb4a Copyright added: https://github.com/rmeena840/rtems-tools/commit/dc0cc02e805691bd0fd6a42abe4a0e068587c0ed Have a look. > -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engin

Re: GSoC Project | Basic Support for Trace Compass

On Thu, Aug 8, 2019 at 1:06 PM Ravindra Kumar Meena wrote: > > Should I include whole metadata content in that char metadata[]? >> >> Yes, if everything is constant. >> > Okay > > https://github.com/rmeena840/rtems-tools/commit/13c81bfb3a72dd777507f3bf92a96ec50ab7dd17 > > > At the end of the file

Re: GSoC Project | Basic Support for Trace Compass

> > > Should I include whole metadata content in that char metadata[]? > > Yes, if everything is constant. > Okay https://github.com/rmeena840/rtems-tools/commit/13c81bfb3a72dd777507f3bf92a96ec50ab7dd17 At the end of the file fwrite() is writing some small binary data. I don't know why that is ha

Re: GSoC Project | Basic Support for Trace Compass

On 08/08/2019 08:43, Ravindra Kumar Meena wrote: No, not a typedef. Something like this: diff --git a/misc/record/record-main.c b/misc/record/record-main.c index 314bb78..b5d1a66 100644 --- a/misc/record/record-main.c +++ b/misc/record/record-main.c @@ -422,19 +422,28 @@

Re: GSoC Project | Basic Support for Trace Compass

> > No, not a typedef. Something like this: > > diff --git a/misc/record/record-main.c b/misc/record/record-main.c > index 314bb78..b5d1a66 100644 > --- a/misc/record/record-main.c > +++ b/misc/record/record-main.c > @@ -422,19 +422,28 @@ static rtems_record_client_status handler( > return RTEM

Re: GSoC Project | Basic Support for Trace Compass

On 08/08/2019 06:10, Ravindra Kumar Meena wrote: Could you please move the const metadata content to as few as possible static const metadata_xyz[] = "... ... ..."; variables and write them with fwrite(). Sorry. I didn't get which part of the metadata you want to move. Ar

Re: GSoC Project | Basic Support for Trace Compass

> > Could you please move the const metadata content to as few as possible > > static const metadata_xyz[] = "... > ... > ..."; > > variables and write them with fwrite(). > Sorry. I didn't get which part of the metadata you want to move. Are you talking about typedef? > > > > > Is there any codin

Re: GSoC Project | Basic Support for Trace Compass

- Am 7. Aug 2019 um 17:53 schrieb Ravindra Kumar Meena rmeena...@gmail.com: > Metadata cleanup: > https://github.com/rmeena840/rtems-tools/commit/6eb069cbf6639653a7df3b183a86a58f4da8cdbd > > Generated metadata in client-side: > https://github.com/rmeena840/rtems-tools/commit/1e07b1ea3bb334ee5

Re: GSoC Project | Basic Support for Trace Compass

Metadata cleanup: https://github.com/rmeena840/rtems-tools/commit/6eb069cbf6639653a7df3b183a86a58f4da8cdbd Generated metadata in client-side: https://github.com/rmeena840/rtems-tools/commit/1e07b1ea3bb334ee56b142f08659869576e76db8 Have a look. Is there any coding style guideline mentioned somewh

Re: GSoC Project | Basic Support for Trace Compass

Code Cleanup: https://github.com/rmeena840/rtems-tools/commit/f19ec63810347f6e532e13b1fb27002554344d3f -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) , Dhanbad _

Re: GSoC Project | Basic Support for Trace Compass

- Am 6. Aug 2019 um 17:30 schrieb Ravindra Kumar Meena rmeena...@gmail.com: >> >> > I think this can be the right way to check bound access. >> > >> https://github.com/rmeena840/rtems-tools/commit/81bf2a9b9e57e7911d519c4719c5126e29a7adbe >> >> No, the API classes are 1, 2, and 3. The indices i

  1   2   3   4   >