<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 19, 2020 at 4:20 AM <<a href="mailto:Jan.Sommer@dlr.de">Jan.Sommer@dlr.de</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"><br>
<br>
> Von: devel [mailto:<a href="mailto:devel-bounces@rtems.org" target="_blank">devel-bounces@rtems.org</a>] Im Auftrag von Joel Sherrill<br>
> Gesendet: Mittwoch, 18. März 2020 22:18<br>
> An: Heinz Junkes<br>
> Cc: <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
> Betreff: Re: Successfully built EPICS 7 with RTEMS 5 for mvme6100<br>
> <br>
> <br>
> <br>
> On Wed, Mar 18, 2020 at 2:38 PM Heinz Junkes <<a href="mailto:junkes@fhi-berlin.mpg.de" target="_blank">junkes@fhi-berlin.mpg.de</a>> wrote:<br>
> Hello, Mritunjay,<br>
> <br>
> I will contact you tomorrow during the day (European time). We have here institute closings because of Corona Virus etc.. <br>
> <br>
> It's great that you've come this far. I can also provide you with an MVME6100 remotely so you can get a feeling for target development. <br>
> Yes, I have also started development of libbsd and the MVME2500. More on this tomorrow.<br>
> <br>
> But the first, important step in this proposal would be to get EPICS7 running with RTEMS5 on e.g. qemu, ideally on i386?<br>
> I think I had some problems with the psim in the past. Unfortunately I don't know exactly what it is anymore. <br>
> More tomorrow.<br></blockquote><div><br></div><div>psim has a network driver for the legacy stack. I have no idea how to run it. It would be great to see that BSP with NIC running again and then updated to the new stack. I don't know that there is a PowerPC simulator configuration with networking available at the moment.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
> <br>
> We have had good experiences with RTEMS+libbsd with the Qemu ARM Zynq. <br>
> We have been able to telnet to the RTEMS target from Linux and use the RTEMS<br>
> NFS client to mount Linux files plus dynamic loading works. Personally I would <br>
> start with that since the goal is EPICS not fixing a BSP. :)<br>
> <br>
> My second would be Qemu i386 pc386 but I don't know the status of libbsd on <br>
> pc386 at the moment. This should work the same as the Zynq qemu but I <br>
> personally don't know. Heinz.. do you have recent experience on it?<br>
> <br>
<br>
If the patches here (<a href="https://lists.rtems.org/pipermail/devel/2020-March/058119.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-March/058119.html</a>) make it through the review, rtems-libbsd should compile again for the pc386 BSP.<br></blockquote><div><br></div><div>Ping Sebastian to push them. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
We also could successfully run network tests in qemu with tap devices.<br>
Next step are real hardware tests. There were some issues during initialization, </blockquote><div><br></div><div>We were re-establishing our hardware testing setup after moving offices a twice over the past three years. When we got to the PC386, we had trouble. We tried an embedded PC and a couple of odd desktops old enough to have COM1. COM1 support appears to be broken for us. That's unfortunate for automated testing.</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">but we were interrupted with the preparations for Corona.<br></blockquote><div><br></div><div>+1 </div><div><br></div><div>I'm starting at home today. Not sure how long this will go on. I've done a lot of work remote but never done extended work from home. This will be interesting.</div><div><br></div><div>--joel </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Best regards,<br>
<br>
Jan<br>
<br>
> Gedare is correct though. Work on the proposal next. You are far enough along<br>
> with what you have done to been into debugging and integrating on a real<br>
> embedded target. <br>
> <br>
> <br>
> Many greetings and stay healthy,<br>
> <br>
> Everything here is closed with teleworking. Two confirmed cases here <br>
> in town so far but one was at NASA Marshall and the other was a<br>
> pharmacist at the Army clinic. I expect we will have more in the near future.<br>
> <br>
> --joel<br>
> <br>
> Heinz<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>
> > On 18. Mar 2020, at 19:56, Mritunjay Sharma <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > <br>
> > Thank you so much for the feedback. I will research more on the targets that can run with the simulator and would like to tell you that looking at <a href="https://github.com/hjunkes/epicsBaseOwnPlayground/tree/7.0" rel="noreferrer" target="_blank">https://github.com/hjunkes/epicsBaseOwnPlayground/tree/7.0</a>, I feel that @Heinz Junkes is already working on libbsd for RTEMS-MVME2500 and I would like to hear more from him to get some clarity on what can be done. Being a beginner, it's really a great welcome to the world of cross-compiler development and testing. :) Thank you for always helping me out! <br>
> > <br>
> > On Wed, Mar 18, 2020 at 11:51 PM Gedare Bloom <<a href="mailto:gedare@rtems.org" target="_blank">gedare@rtems.org</a>> wrote:<br>
> > On Wed, Mar 18, 2020 at 11:40 AM Mritunjay Sharma<br>
> > <<a href="mailto:mritunjaysharma394@gmail.com" target="_blank">mritunjaysharma394@gmail.com</a>> wrote:<br>
> > ><br>
> > > Hi everyone,<br>
> > ><br>
> > > As a part of working on ticket #3835 (BSP Buildset for EPICS), this is to inform the community that after a lot of research, help from RTEMS and EPICS community and <a href="https://epics.mpg.de/index.php?n=Software.EPICSRTEMS?userlang=en" rel="noreferrer" target="_blank">https://epics.mpg.de/index.php?n=Software.EPICSRTEMS?userlang=en</a>, I was able to build EPICS 7 for RTEMS 5 for mvme6100 (powerpc-rtems5).<br>
> > > After this, my development environment is almost completely set up with RTEMS, rtems-source-builder and epics7 (taken from <a href="https://github.com/hjunkes/epicsBaseOwnPlayground/tree/7.0" rel="noreferrer" target="_blank">https://github.com/hjunkes/epicsBaseOwnPlayground/tree/7.0</a> ). While going through the entire process, I learnt about the changes to be made in epics7/configure/os/CONFIG_STATUS.Common.RTEMS and also encountered few errors while the 'make' process, however, it got fixed by commenting line 325 to 329 in '/home/mritunjay/development/rtems/5/powerpc-rtems5/beatnik/lib/include/rtems/confdefs/libio.h':<br>
> > > // #ifdef CONFIGURE_FILESYSTEM_ENTRY_DEVFS<br>
> > > // CONFIGURE_FILESYSTEM_ENTRY_DEVFS,<br>
> > > // #endif<br>
> > > I would like to know more on why this behaviour occurred. Is it a bug? Or something else?<br>
> > ><br>
> > Include some of this detail in your proposal. I don't have time at the<br>
> > moment to delve into details.<br>
> > <br>
> > Next step would be to identify a target you can build EPICS7+RTEMS5<br>
> > with simulator support. This one is challenging since AFAIK there<br>
> > haven't been any successes in that regards. Find out what are the<br>
> > blockers and maybe you can work on those.<br>
> > <br>
> > > I wanted to test it but I am facing issues in connecting with tftp server when I run 'scp bin/RTEMS-beatnik/libComTestHarness.boot root@epics:/var/lib/tftp'<br>
> > > The following error was encountered:<br>
> > > /usr/bin/ssh: /lib/x86_64-linux-gnu/libcrypto.so.1.0.0: no version information available (required by /usr/bin/ssh)<br>
> > > /usr/bin/ssh: /lib/x86_64-linux-gnu/libcrypto.so.1.0.0: no version information available (required by /usr/bin/ssh)<br>
> > > ssh: Could not resolve hostname epics: Name or service not known<br>
> > > lost connection<br>
> > > I was wondering what can be the reason behind this, please help me fix this.<br>
> > ><br>
> > Test it how -- do you have a powerpc MVME6100 board?<br>
> > <br>
> > I'm guessing whoever gave you that scp command line has a board with a<br>
> > local /etc/hosts entry for 'epics' pointing to some local IP address<br>
> > they connect to their board over.<br>
> > <br>
> > Welcome to the world of cross-compiler development and testing. :)<br>
> > <a href="https://docs.rtems.org/branches/master/user/hosts/index.html#development-host" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/hosts/index.html#development-host</a><br>
> > <br>
> > > Also, what are the next steps? I am working on the GSoC proposal currently and since the current ticket #3835 is a shorter project, I have to add certain similar sub-tasks within the GSoC timeline as suggested by @Gedare Bloom :<br>
> > > "* compile CFS by hand, create an RSB "recipe" to build it, then<br>
> > > integrate it with vertical buildset configuration.<br>
> > > * create vertical buildsets for PC, Raspberry Pi, and other boards.<br>
> > > ** EPICS community uses many powerpc boards so adding something there<br>
> > > would be good."<br>
> > <br>
> > Identify what might be potential simulator targets for you to use, and<br>
> > look at how easy they are to build with RSB. If any are missing<br>
> > support, work on adding them. If any are broken, poke into why.<br>
> > <br>
> > psim is a good powerpc simulator, although it may not have enough<br>
> > support for running epics--I haven't looked.<br>
> > <br>
> > For EPICS it is best to get something working in qemu so that you can<br>
> > run some networking. So I'd look at some qemu simulator targets and<br>
> > check what is their status and whether you can build and run anything<br>
> > for RTEMS on them. After that, can you build/run any RTEMS networking<br>
> > applications?<br>
> > <br>
> > Does the EPICS7+RTEMS5 stack still using cpukit/libnetworking, or is<br>
> > it able to use libbsd? That is an interesting question to find out.<br>
> > <br>
> > > I would like to have suggestions on resetting the timeline as I work on refining the proposal for GSoC based on Dr. @Gedare Bloom's suggestions.<br>
> > ><br>
> > For timeline the first step is to break down all the tasks to figure<br>
> > out what you need to do to accomplish each of your goals. Then you<br>
> > should try to estimate how long you (or mentors) think each task will<br>
> > take, and use that create your plan. (Estimating time is notoriously<br>
> > difficult, but do your best. If it comes in too heavy or light, that<br>
> > is fine, you should put some activities in "Future Improvements" that<br>
> > can be moved into your summer work in case you get through your<br>
> > planned work faster than you expect; if you don't complete all your<br>
> > planned work, we understand and will take everything into<br>
> > consideration during evaluation. Do NOT think of your plan as a<br>
> > contract: it is not, it is a guideline for your summer.)<br>
> > <br>
> > > Thanks<br>
> > > Mritunjay<br>
> > ><br>
</blockquote></div></div>