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  <20212022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Information request on RTEMS 6+ needs/wants
From: Michael Davidsaver via Core-talk <core-talk at aps.anl.gov>
To: Gedare Bloom <gedare at rtems.org>, EPICS Core Talk <core-talk at aps.anl.gov>
Cc: Joel Sherrill <joel at rtems.org>
Date: Thu, 11 Feb 2021 13:56:27 -0800
On 2/11/21 12:32 PM, Gedare Bloom via Core-talk 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?

* BSP Status

I've been confused about the status of the various architectures/BSPs
in the RTEMS >=5 era.  My questions for each are:

1. Is libbsd (new network stack) supported?
2. Does it build?
3. Does it boot in emulation?  (assuming there is an emulator)
4. Has it been tested on metal?

I think I can answer "yes" to the first 3 for i386/pc686 and powerpc/mvme3100.

Another surprising (to me) question which came up recently is whether
the VME bridge driver is usable on targets without libbsd support.
So maybe my question 1. should be which features depend on libbsd?


The current set of BSPs with configuration in EPICS 7.0 series
repository are:

arm
  at91rm9200ek
powerpc
  beatnik
  mcp750
  mvme2100
  mvme2700
  mvme3100
  mvme5500
  psim
i386
  pc386   (we're switching to pc686 w/ RTEMS5)
m68k
  gen68360
  mvme167
  uC5282


* Toolchain builds

It seems like everyone I know who is working with RTEMS5 is using a different
process to build RTEMS.  Some people are using RSB in part or in full.  Others
build some piece individually with autoconf or waf (I guess).  The result has
been repeatability and "works for me" issues.  I'd love to have a recommended
recipe to focus everyone on.

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: Re: Information request on RTEMS 4.10 needs/wants Johnson, Andrew N. via Core-talk
Next: Re: Information request on RTEMS 4.10 needs/wants Michael Davidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: 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  <20212022  2023  2024 
ANJ, 12 Feb 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·