Good morning Gedare,
Now I'll get in touch with you too.
Unfortunately, I haven't really gotten around to continuing with RTEMS this year.
Fortunately, Brendan Chandler has tried to bring everything together here.
Andrew has already pointed this out:
"Progress on our RTEMS-5 port of EPICS Base can be followed at this GitHub PR.” :
https://github.com/epics-base/epics-base/pull/105
For me it looks like this at the moment:
I use RTEMS5 und EPICS7 with the MVME6100 in production.
Unfortunately I can't use libbsd because the ethernet controller of the board is not supported.
I tried to convert the driver from Till Strauman to the nexus driver, but unfortunately didn't get
it done in 2-3 days and then aborted. Also there is no PCI/VMEbus support yet in the
libbsd. I also still use the rudimentary VME, NTP support and Till's NFS (v2).
I am satisfied with this so far in our environment. But other labs would like to use the MVME6100
(MVME5500) with NFS3, NTP (PTP2) and especially VMEbus and loadable modules(lib).
If I have noticed correctly there is funding for dyn link loader (by HZB, Bessy)
and NFS3 (by Gemini) for RTEMS5/6 and libbsd.
I have the MVME2500 (qoriq_e500) running quite well with libbsd and Till's NFS2.
I miss the support for PCI/VMEbus, Time-client (NTP, PTP2) and RTC.
I would like to use my new playground (MTCa4, IFC1420, FPGA) also with RTEMS. The board
is also a Qoriq based system. But again, support for PCI will be critical. I couldn't try anything yet though.
I am currently developing EPICS7 with RTEMS5 and libbsd on xilinx_zynq_a9_qemu. This works so far quite ok.
(I haven't managed to boot an image on the xilinx_zynq_a9 hardware with U-Boot yet, though, unfortunately).
Viele Grüße
Heinz
> On 11. Feb 2021, at 21:32, Gedare Bloom via Core-talk <core-talk at aps.anl.gov> wrote:
>
> Hello again EPICS Core,
>
> I'm looking to collect some feedback from you all related to
> EPICS+RTEMS. I'm trying to also keep in touch with monitoring the
> progress on EPICS7/RTEMS5 (And, I'm planning to participate with
> students in the upcoming hackathon! if you have tasks related, I might
> be able to help knock them out). My ask right now is:
> * What feature improvements would you like to see in future RTEMS releases?
> * What are your pain points with current RTEMS versions and/or workflows?
>
> And anything else positive/negative you'd like to put out here is
> certainly welcome.
>
> -Gedare
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- Replies:
- Re: Information request on RTEMS 6+ needs/wants Gedare Bloom via Core-talk
- References:
- Information request on RTEMS 6+ needs/wants Gedare Bloom via Core-talk
- Navigate by Date:
- Prev:
Build failed: epics-base base-integration-621 AppVeyor via Core-talk
- Next:
Re: Information request on RTEMS 4.10 needs/wants 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
2023
2024
- Navigate by Thread:
- Prev:
Re: Information request on RTEMS 6+ needs/wants Gedare Bloom via Core-talk
- Next:
Re: Information request on RTEMS 6+ needs/wants 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
2023
2024
|