EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
<== Date ==> <== Thread ==>

Subject: What is the next step for RTEMS and EPICS? Does a small (virtual) workshop make sense?
From: Heinz Junkes via Core-talk <core-talk at aps.anl.gov>
To: Heinz Junkes via Core-talk <core-talk at aps.anl.gov>
Date: Fri, 14 Jul 2023 10:55:15 +0200
Hallo,

right now I see a lot of RTEMS related EPICS activity. However, these activities do not seem
to be well synchronized (from my point of view) and also a bit jumbled.
Wouldn't we like to meet online one afternoon (Europe time) and discuss our common approach?
I am happy to organize this.

Here my view:

Due to the request from some places (e.g. gemini) that the lack of NFSv4 support for RTEMS 
precludes further use, I started looking into RTEMS a little more intensively.

It turned out that NFSv4 can only be realized with a (the) new network stack.
For this new network stack Chris Johns then developed a first NFSv4 version.
There is a PR (#295, https://github.com/hjunkes/epics-base/tree/rtems6) from
me to epics-base which has not yet been merged. In it I tried to keep the older versions
of Epics and also the old LEGACY_STACK running.
I did the developments primarily on an MVME6100. Here it quickly turned out that there is no support
for the Ethernet controller of the MVME6100 for the new stack. Then at an EPICS Codeathlon, Till Straumann
(Danke!) built a Nexus driver for it. This then allowed NFSv4 to be used to start st.cmd, etc..

Now I can also read the NVRAM settings, I am still in the process of reading the settings from U-Boot, etc.

I also wanted to use ntpd and other things like ptpd etc that are now available at RTEMS. But I haven't gotten around to it yet.

I had focused on the addon modules like asyn, motor, vmelib ... to get them running.
And then got stopped at autosave from problems with writes on NFSv4, described here:
https://devel.rtems.org/ticket/4723

And now of course I'm surprised that none of the NFSv4 claimers stumbled upon it. 
And in parallel, developments are run based on the legacy stack even though it can never support NFSv4?

That's why I would be very happy if we could talk about this in a concentrated way.

Danke, Heinz

Replies:
Re: What is the next step for RTEMS and EPICS? Does a small (virtual) workshop make sense? Gedare Bloom via Core-talk

Navigate by Date:
Prev: Build failed: EPICS Base 7 base-7.0-967 AppVeyor via Core-talk
Next: Build failed: EPICS Base 7 base-7.0-969 AppVeyor via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
Navigate by Thread:
Prev: Build failed: EPICS Base 7 base-7.0-967 AppVeyor via Core-talk
Next: Re: What is the next step for RTEMS and EPICS? Does a small (virtual) workshop make sense? Gedare Bloom via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
ANJ, 19 Jul 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·