EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <2021>  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <2021>  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository
From: "Johnson, Andrew N. via Core-talk" <core-talk at aps.anl.gov>
To: Chris Johns <chrisj at rtems.org>
Cc: Core talk <core-talk at aps.anl.gov>, Joel Sherrill <joel at rtems.org>, "rtems-devel at rtems.org" <devel at rtems.org>
Date: Fri, 5 Mar 2021 00:29:51 +0000
On Mar 4, 2021, at 5:36 PM, Chris Johns <chrisj at rtems.org> wrote:

This comes back to the first comment I made, RTEMS would
love to have a current and valid list of BSPs active in EPICS so we can make
sure they build. In time if we can add public hardware test results we will be
in great shape.

The rtems5 branch of EPICS Base which may be nearing merge soon currently contains configuration files for these RTEMS BSPs:

configure/os/CONFIG.Common.RTEMS-at91rm9200ek
configure/os/CONFIG.Common.RTEMS-beagleboneblack
configure/os/CONFIG.Common.RTEMS-beatnik
configure/os/CONFIG.Common.RTEMS-gen68360
configure/os/CONFIG.Common.RTEMS-mcp750
configure/os/CONFIG.Common.RTEMS-mvme167
configure/os/CONFIG.Common.RTEMS-mvme2100
configure/os/CONFIG.Common.RTEMS-mvme2700
configure/os/CONFIG.Common.RTEMS-mvme3100
configure/os/CONFIG.Common.RTEMS-mvme5500
configure/os/CONFIG.Common.RTEMS-pc386
configure/os/CONFIG.Common.RTEMS-pc386-qemu
configure/os/CONFIG.Common.RTEMS-pc686
configure/os/CONFIG.Common.RTEMS-pc686-qemu
configure/os/CONFIG.Common.RTEMS-psim
configure/os/CONFIG.Common.RTEMS-qoriq_e500
configure/os/CONFIG.Common.RTEMS-uC5282
configure/os/CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
configure/os/CONFIG.Common.RTEMS-xilinx_zynq_zedboard

Now the -qemu variants are our internal names so you can ignore them. I don’t believe anyone is using the at91rm9200ek, gen68360, mcp750, mvme167 or psim BSPs so similarly I would ignore them (I’ll try to get those files dropped from EPICS someday). There is probably no need for the separate mvme5500 BSP since that board can run the beatnik instead, but there might be one or two sites using it. That leaves this list for future use, to a first approximation:

configure/os/CONFIG.Common.RTEMS-beagleboneblack
configure/os/CONFIG.Common.RTEMS-beatnik
configure/os/CONFIG.Common.RTEMS-mvme2100
configure/os/CONFIG.Common.RTEMS-mvme2700
configure/os/CONFIG.Common.RTEMS-mvme3100
configure/os/CONFIG.Common.RTEMS-mvme5500
configure/os/CONFIG.Common.RTEMS-pc386
configure/os/CONFIG.Common.RTEMS-pc686
configure/os/CONFIG.Common.RTEMS-qoriq_e500
configure/os/CONFIG.Common.RTEMS-uC5282
configure/os/CONFIG.Common.RTEMS-xilinx_zynq_a9_qemu
configure/os/CONFIG.Common.RTEMS-xilinx_zynq_zedboard

Note that this branch only builds the pc386 on RTEMS-4 and the pc686 on RTEMS-5 and above, so for your purposes you can drop the separate pc386 as well. Several of the above are only just being added so wouldn’t be used with RTEMS-4, but I’m pretty sure we have users currently running RTEMS-4 on the PowerPC BSPs and the uC5282.


BTW why do both the --host= and --target= options there (equivalent to %defines
in the .bset file) specify the RTEMS target? That seems weird to me.

The RSB started a long time ago as a personal tool to build the GNU tool chain
for MacOS using RPM spec files. These arguments matched the triplet terms
configure scripts use. The RSB can Candian cross compile (Cxc) tools, for
example building on Linux a Windows compiler for RTEMS and what you have here is
based on how those match up. The RSB internally has a "macro" database and all
the command line parsing ever did was set a macro. A build set (bset) can also
set a macro so the defines are a cheap trick to do this.

I would have expected a Canadian cross to have --host be the same as the build host, not as the final target ("please build me a compiler that can run on that host and produce binaries for that target”). That’s why they seem weird. Just wondering.

Thanks,

- Andrew


-- 
Complexity comes for free, simplicity you have to work for.

References:
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Joel Sherrill via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Heinz Junkes via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Joel Sherrill via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Chris Johns via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Johnson, Andrew N. via Core-talk
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Chris Johns via Core-talk
Navigate by Date:
Prev: Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Chris Johns via Core-talk
Next: Build failed: epics-base base-integration-642 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  2023  2024 
Navigate by Thread:
Prev: Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Chris Johns via Core-talk
Next: [Bug 1902560] Re: Read info items using a filter Dirk Zimoch 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 
ANJ, 05 Mar 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·