<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 11, 2020 at 2:07 AM Gedare Bloom <<a href="mailto:gedare@rtems.org">gedare@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Jul 10, 2020 at 12:14 PM Mritunjay Sharma<br>
<<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
><br>
> Apologies for the delay in response,<br>
> It’s an important update that I want to give to my mentors that my current development laptop showed some problems yesterday and which worsened today.<br>
><br>
> I have submitted my laptop for repair. The good thing is that I have the backup of the work done till day and I have arranged a spare laptop as well which will be available tomorrow.<br>
><br>
> Configuring and setting up my laptop for the development may take a couple of days and so I will like to request you all to kindly pardon my inactivity for the next 2 days.<br>
><br>
<br>
Meanwhile, you may also think about reading/writing some more<br>
documentation, or planning out your next steps.<br></blockquote><div><br></div><div>Yes, Gedare, I did exactly the same today and wrote this beginner-friendly tutorial to </div><div>introduce more beginners like me to RTEMS community. </div><div>The link to blog is: <a href="https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902">https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902</a></div><div><br></div><div>The spare laptop is also arranged and almost configured. Only a few tweaks remaining. </div><div>I will publish more blogs tomorrow related to EPICS+RTEMS and QEMU. </div><div><br></div><div>I will certainly request Heinz, Chris and You to help me decide what should be my next steps now and</div><div>what should be the goal for the following week. </div><div><br></div><div>Thanks</div><div>Mritunjay</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> I hope to be back active on Monday with everything set up on the new laptop.<br>
><br>
> Thanks<br>
> Mritunjay<br>
><br>
> Get Outlook for iOS<br>
> ________________________________<br>
> From: <a href="mailto:Jan.Sommer@dlr.de" target="_blank">Jan.Sommer@dlr.de</a> <<a href="mailto:Jan.Sommer@dlr.de" target="_blank">Jan.Sommer@dlr.de</a>><br>
> Sent: Thursday, July 9, 2020 12:43:30 PM<br>
> To: <a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a> <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>>; <a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a> <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>><br>
> Cc: <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a> <<a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a>><br>
> Subject: RE: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5<br>
><br>
><br>
><br>
> > -----Original Message-----<br>
> > From: devel [mailto:<a href="mailto:devel-bounces@rtems.org" target="_blank">devel-bounces@rtems.org</a>] On Behalf Of Gedare Bloom<br>
> > Sent: Wednesday, July 8, 2020 9:45 PM<br>
> > To: Mritunjay Sharma<br>
> > Cc: RTEMS Devel<br>
> > Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5<br>
> ><br>
> > On Wed, Jul 8, 2020 at 12:33 PM Mritunjay Sharma<br>
> > <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > ><br>
> > > [UPDATE]: I tried to build the EPICS 7 with RTEMS 5 for pc386 with Heinz's<br>
> > <a href="https://github.com/hjunkes/epicsBaseOwnPlayground" rel="noreferrer" target="_blank">https://github.com/hjunkes/epicsBaseOwnPlayground</a><br>
> > > while switching to Branch "7". The previous errors are gone but I am facing<br>
> > the following error:<br>
> > ><br>
> > > "../posix/rtems_init.c:38:10: fatal error: rtems/bsd/bsd.h: No such file or<br>
> > directory<br>
> > > #include <rtems/bsd/bsd.h><br>
> > > ^~~~~~~~~~~~~~~~~<br>
> ><br>
> > This error indicates it is looking for an installed rtems-libbsd. My<br>
> > guess is you need to build/install the rtems-libbsd to get this<br>
> > playground to work.<br>
> ><br>
><br>
> I did not read everything in this thread, so maybe I misunderstand something.<br>
> If you want to build rtems-libbsd for a pc-based BSP, please be aware of the following:<br>
> - It should build fine if you use the 5-freebsd-12 branch.<br>
> - With master branch is should build if you set the option "dev_nic_e1000" to off in your buildset.ini. It should compile, but depending on your network adapter there might be problems to actually use the network devices.<br>
><br>
> Finishing a patchset for the master branch to fix that is on my todo list, but I haven't come around to do it yet.<br>
><br>
> > > compilation terminated.<br>
> > ><br>
> > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/<br>
> > RULES_BUILD:234: recipe for target 'rtems_init.o' failed<br>
> > > make[4]: *** [rtems_init.o] Error 1<br>
> > > make[4]: Leaving directory<br>
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/<br>
> > libcom/RTEMS/O.RTEMS-pc386'<br>
> > ><br>
> > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/<br>
> > RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386' failed<br>
> > > make[3]: *** [install.RTEMS-pc386] Error 2<br>
> > > make[3]: Leaving directory<br>
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/<br>
> > libcom/RTEMS'<br>
> > ><br>
> > /home/mritunjay/development/EPICS/epicsBaseOwnPlayground/configure/<br>
> > RULES_DIRS:84: recipe for target 'RTEMS.install' failed<br>
> > > make[2]: *** [RTEMS.install] Error 2<br>
> > > make[2]: Leaving directory<br>
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules/<br>
> > libcom'<br>
> > > ../configure/RULES_DIRS:84: recipe for target 'libcom.install' failed<br>
> > > make[1]: *** [libcom.install] Error 2<br>
> > > make[1]: Leaving directory<br>
> > '/home/mritunjay/development/EPICS/epicsBaseOwnPlayground/modules'<br>
> > > configure/RULES_DIRS:84: recipe for target 'modules.install' failed<br>
> > > make: *** [modules.install] Error 2"<br>
> > ><br>
> > > Today's update is that I tried to fix the above error however I still have not<br>
> > been able to clear it.<br>
> > > If anyone has idea, please do tell what can be done.<br>
> > ><br>
> > > Thanks<br>
> > > Mritunjay<br>
> > ><br>
> > > On Wed, Jul 8, 2020 at 1:12 AM Mritunjay Sharma<br>
> > <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > >><br>
> > >><br>
> > >><br>
> > >> ________________________________<br>
> > >> From: Heinz Junkes <<a href="mailto:junkes@fhi-berlin.mpg.de" target="_blank">junkes@fhi-berlin.mpg.de</a>><br>
> > >> Sent: Wednesday, July 8, 2020 1:05 AM<br>
> > >> To: Mritunjay Sharma<br>
> > >> Cc: Gedare Bloom; Joel Sherrill; Chris Johns; RTEMS Devel<br>
> > >> Subject: Re: [GSoC 2020: Daily Update]: Building EPICS with RTEMS5<br>
> > >><br>
> > >> I’m away from my keyboard. If you use the epics Adaption to rtems from<br>
> > my github “playground?” and bsp’s with —enable-networks should compile.<br>
> > >> Heinz<br>
> > >><br>
> > >> FHI, Heinz Junkes<br>
> > >><br>
> > >> Thank you Heinz, I was doing the same. I went to your GitHub and am<br>
> > experimenting with "playground" right now.<br>
> > >><br>
> > >> Thanks,<br>
> > >> Mritunjay<br>
> > >><br>
> > >> On 7. Jul 2020, at 18:14, Mritunjay Sharma<br>
> > <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > >><br>
> > >><br>
> > >> [UPDATE]: I tried building EPICS with RTEMS5 for pc-386 and pc-386-qemu.<br>
> > >> Everything worked fine while building the pc-386 with RTEMS5.<br>
> > >><br>
> > >> After this when I entered epics-base and made the following change:<br>
> > >><br>
> > >> epics-base/os/CONFIG_SITE.Common.RTEMS<br>
> > >> RTEMS_VERSION = 5<br>
> > >> RTEMS_BASE =<br>
> > /home/mritunjay/development/rtems_dev/$(RTEMS_VERSION)<br>
> > >><br>
> > >> As an experiment, I ran the make and as expected got the following error<br>
> > >><br>
> > >> Error:<br>
> > >><br>
> > >> ```...de/compiler/gcc -I../../../../include/os/RTEMS -I../../../../include -<br>
> > c ../rtems_init.c<br>
> > >> ../rtems_init.c:21:10: fatal error: sys/termios.h: No such file or directory<br>
> > >> #include <sys/termios.h><br>
> > >> ^~~~~~~~~~~~~~~<br>
> > >> compilation terminated.<br>
> > >> ../../../../configure/RULES_BUILD:240: recipe for target 'rtems_init.o'<br>
> > failed<br>
> > >> make[4]: *** [rtems_init.o] Error 1<br>
> > >> make[4]: Leaving directory '/home/mritunjay/development/EPICS/epics-<br>
> > base/modules/libcom/RTEMS/O.RTEMS-pc386'<br>
> > >> ../../../configure/RULES_ARCHS:58: recipe for target 'install.RTEMS-pc386'<br>
> > failed<br>
> > >> make[3]: *** [install.RTEMS-pc386] Error 2<br>
> > >> make[3]: Leaving directory '/home/mritunjay/development/EPICS/epics-<br>
> > base/modules/libcom/RTEMS'<br>
> > >> ../../configure/RULES_DIRS:85: recipe for target 'RTEMS.install' failed<br>
> > >> make[2]: *** [RTEMS.install] Error 2<br>
> > >> make[2]: Leaving directory '/home/mritunjay/development/EPICS/epics-<br>
> > base/modules/libcom'<br>
> > >> ../configure/RULES_DIRS:85: recipe for target 'libcom.install' failed<br>
> > >> make[1]: *** [libcom.install] Error 2<br>
> > >> make[1]: Leaving directory '/home/mritunjay/development/EPICS/epics-<br>
> > base/modules'<br>
> > >> configure/RULES_DIRS:85: recipe for target 'modules.install' failed<br>
> > >> make: *** [modules.install] Error 2<br>
> > >> ```<br>
> > >><br>
> > >> I am trying to figure out the error and making the changes in code to<br>
> > debug it.<br>
> > >> However, I will appreciate if Heinz and everyone else can help me a little,<br>
> > if they have an<br>
> > >> idea of this error.<br>
> > >><br>
> > >> Thanks<br>
> > >> Mritunjay<br>
> > >><br>
> > >> On Tue, Jul 7, 2020 at 7:30 PM Mritunjay Sharma<br>
> > <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > >>><br>
> > >>><br>
> > >>><br>
> > >>> On Tue, Jul 7, 2020 at 5:33 AM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>><br>
> > wrote:<br>
> > >>>><br>
> > >>>> On Mon, Jul 6, 2020 at 5:49 PM Joel Sherrill <<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>> wrote:<br>
> > >>>> ><br>
> > >>>> ><br>
> > >>>> ><br>
> > >>>> > On Mon, Jul 6, 2020, 6:14 PM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>><br>
> > wrote:<br>
> > >>>> >><br>
> > >>>> >> On Mon, Jul 6, 2020 at 10:12 AM Mritunjay Sharma<br>
> > >>>> >> <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > >>>> >> ><br>
> > >>>> >> > Hello everyone,<br>
> > >>>> >> ><br>
> > >>>> >> > Thank you, Heinz, Gedare, Chris and Joel for your advice.<br>
> > >>>> >> > If there are issues in making a buildset for 4.10<br>
> > >>>> >> > then should I build EPICS with RTEMS 5 by hand first and note<br>
> > >>>> >> > down the process and then proceed to make the buildset for it?<br>
> > >>>> >> ><br>
> > >>>> >><br>
> > >>>> >> Yes.<br>
> > >>>> ><br>
> > >>>> ><br>
> > >>>> > +1<br>
> > >>>> ><br>
> > >>>> > And by 5, we definitely mean the 5 branch for all rtems repo and the<br>
> > similarly named one for libbsd.<br>
> > >>>><br>
> > >>>> Excellent point. We want to add support for easy build (and eventually<br>
> > >>>> test) of EPICS+RTEMS starting with 5.1 and moving forward, which<br>
> > means<br>
> > >>>> also doing it for RTEMS 6, Mritunjay.<br>
> > >>>><br>
> > >>> Sounds good, I have begun building it hand by today for RTEMS 5 branch<br>
> > and later on continue the<br>
> > >>> same for RTEMS6<br>
> > >>><br>
> > >>> Thank you so much Gedare and Joel.<br>
> > >>> Mritunjay<br>
> > >>>><br>
> > >>>> >><br>
> > >>>> >><br>
> > >>>> >> > Please suggest for the future steps.<br>
> > >>>> >> ><br>
> > >>>> >> > Thanks<br>
> > >>>> >> > Mritunjay<br>
> > >>>> >> ><br>
> > >>>> >> > On Mon, Jul 6, 2020 at 5:38 AM Joel Sherrill <<a href="mailto:joel@rtems.org" target="_blank">joel@rtems.org</a>><br>
> > wrote:<br>
> > >>>> >> >><br>
> > >>>> >> >><br>
> > >>>> >> >><br>
> > >>>> >> >> On Sun, Jul 5, 2020, 6:12 PM Chris Johns <<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>><br>
> > wrote:<br>
> > >>>> >> >>><br>
> > >>>> >> >>> On 6/7/20 12:47 am, Heinz Junkes wrote:<br>
> > >>>> >> >>> > Thank you, this is exactly where I was unsure.<br>
> > >>>> >> >>> > @Chris: Can you give a recommendation here?<br>
> > >>>> >> >>> > Danke Heinz<br>
> > >>>> >> >>> > ---------------------------------------------------------------------------<br>
> > ---<br>
> > >>>> >> >>> > Fritz-Haber-Institut | Phone: (+49 30) 8413-4270<br>
> > >>>> >> >>> > Heinz Junkes | Fax (G3+G4): (+49 30) 8413-5900<br>
> > >>>> >> >>> > Faradayweg 4-6 | VC: <a href="mailto:102220181216@bjn.vc" target="_blank">102220181216@bjn.vc</a><br>
> > >>>> >> >>> > D - 14195 Berlin | E-Mail: <a href="mailto:junkes@fhi-berlin.mpg.de" target="_blank">junkes@fhi-berlin.mpg.de</a><br>
> > >>>> >> >>> > ---------------------------------------------------------------------------<br>
> > ---<br>
> > >>>> >> >>> ><br>
> > >>>> >> >>> >> On 5. Jul 2020, at 16:20, Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>><br>
> > wrote:<br>
> > >>>> >> >>> >><br>
> > >>>> >> >>> >> On Sat, Jul 4, 2020 at 1:18 PM Mritunjay Sharma<br>
> > >>>> >> >>> >> <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > >>>> >> >>> >>><br>
> > >>>> >> >>> >>><br>
> > >>>> >> >>> >>><br>
> > >>>> >> >>> >>> On Sun, Jul 5, 2020 at 12:28 AM Heinz Junkes <junkes@fhi-<br>
> > <a href="http://berlin.mpg.de" rel="noreferrer" target="_blank">berlin.mpg.de</a>> wrote:<br>
> > >>>> >> >>> >>>><br>
> > >>>> >> >>> >>>> Hello, Mritunjay,<br>
> > >>>> >> >>> >>>> that's good news. Don't you want to try to develop a rsb-<br>
> > set for exactly this combination of RTEMS4.10 and EPICS7?<br>
> > >>>> >> >>> >>><br>
> > >>>> >> >>> >>><br>
> > >>>> >> >>> >>> Sure, I am ready to do this and then do it with RTEMS5 in<br>
> > the same way. Please tell how to begin or some existing similar<br>
> > >>>> >> >>> >>> work that can guide me how to proceed further in relation<br>
> > to rsb-set for RTEMS4.10 and EPICS7.<br>
> > >>>> >> >>> >>><br>
> > >>>> >> >>> >><br>
> > >>>> >> >>> >> I don't know if this is best. RSB didn't exist in 4.10. I haven't<br>
> > >>>> >> >>> >> looked to see how well the rtems-source-builder/4.10 would<br>
> > support a<br>
> > >>>> >> >>> >> package build. It should be discussed with Chris probably. A<br>
> > couple of<br>
> > >>>> >> >>> >> packages were added in the 4.11 branch.<br>
> > >>>> >> >>><br>
> > >>>> >> >>> I would leave 4.10 and move on. It may work but these things<br>
> > can expose issues<br>
> > >>>> >> >>> that turn into distractions.<br>
> > >>>> >> >>><br>
> > >>>> >> >>> Would making a script that does the build so we can document<br>
> > the steps be worth<br>
> > >>>> >> >>> while<br>
> > >>>> >> >><br>
> > >>>> >> >><br>
> > >>>> >> >> Yes. Emphatically yes. We need to make sure we know how it is<br>
> > best built by hand to automate it.<br>
> > >>>> >> >><br>
> > >>>> >> >> I firmly believe you should not attempt to automate something<br>
> > until doing it manually is well understood and documented.<br>
> > >>>> >> >><br>
> > >>>> >> >> After you have this down for one BSP, we need to ask questions<br>
> > like:<br>
> > >>>> >> >><br>
> > >>>> >> >> + Is there any per BSP tailoring beyond the obviod architecture<br>
> > and compilation settings?<br>
> > >>>> >> >><br>
> > >>>> >> >> + Any tweaks to settings users may want?<br>
> > >>>> >> >><br>
> > >>>> >> >> The manual process should include testing. The RSB is a great<br>
> > way to automate and ease building but it doesn't address testing the<br>
> > packages yet.<br>
> > >>>> >> >><br>
> > >>>> >> >> --joel<br>
> > >>>> >> >><br>
> > >>>> >> >>><br>
> > >>>> >> >>> Chris<br>
> > >>>> >> >>> _______________________________________________<br>
> > >>>> >> >>> devel mailing list<br>
> > >>>> >> >>> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> > >>>> >> >>> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> > >>>> >> >><br>
> > >>>> >> >> _______________________________________________<br>
> > >>>> >> >> devel mailing list<br>
> > >>>> >> >> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> > >>>> >> >> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> > _______________________________________________<br>
> > devel mailing list<br>
> > <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
> > <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div></div>