EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: minimum CA Server requirements
From: Andrew Johnson <[email protected]>
To: [email protected]
Date: Fri, 1 Jul 2011 16:24:19 -0500
Hi,

On 2011-06-30 Circuit6 Engineering wrote:
> I am very new to EPICS and only just started to work my way through the
> lectures, documentation and program text. I wonder how lean and trim a
> channel access server could be? For example, is it ridiculous to think
> about running CA Server on a 100MHz ARM Cortex-M3 with 256 KB flash
> memory, 64 KB SRAM and 10/100 Mbps Ethernet?

Hmm, interesting question, 256K of Flash and 64K of RAM seems pretty tiny 
nowadays.  I have a pretty minimal CAS program which I build statically on 
Linux; after I strip the binary, the executable is 702KB built for x86_64, and 
817KB built for x86, and that doesn't include all the Linux system libraries.  
I don't know how much smaller an ARM version might be, but I think it most 
likely that the answer is no way with our current code, because you have to 
allow for the rest of the OS as well.

As a comparison, compiling our example IOC application for the RTEMS-mvme3100 
target (a 32-bit PowerPC CPU) results in a 1.6MB bootable binary image (which 
includes the RTEMS OS code).  Now that's not using the same code as the CAS 
program I was discussing above and it is actually a full IOC, but it gives 
another minimal example.  I also looked at the boot images for several of our 
ColdFire-based IOCs here, the bootable image for them are all in the 1.7-1.8MB 
range too.

> I am also very new to RTEMS. If RTEMS is too heavy for a minimal hardware
> environment, could a trim CA server be ported to FreeRTOS with the lwIP
> (Lightweight IP) stack without serious re-engineering?

I think you'd be in the "serious re-engineering" range, although I don't know 
anything about FreeRTOS or lwIP — I'm not saying that porting EPICS would 
necessarily be that hard, but the code volume may be too big to overcome.

HTH,

- Andrew
-- 
Optimization is the process of taking something that works and
replacing it with something that almost works, but costs less.
-- Roger Needham


References:
minimum CA Server requirements Circuit6 Engineering

Navigate by Date:
Prev: RE: SNL seq-2.0.13 on Linux 64 bits: not all monitored PVs receive their first monitor event Allison, Stephanie
Next: Re: SNL seq-2.0.13 on Linux 64 bits: not all monitored PVs receive their first monitor event Ben Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: minimum CA Server requirements Circuit6 Engineering
Next: Announce: sequencer 2.1.0 release candidate Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·