[GSoC 2020: Daily Update]: Building EPICS with RTEMS5
junkes at fhi-berlin.mpg.de
Sat Jul 11 14:46:08 UTC 2020
It's not my experience.
I made my first attempts with RTEMS5 for a beatnik-board (MVME6100).
For this I created the BSP like this:
../../rtems/configure --enable-maintainer-mode --prefix=$HOME/RTEMS/rtems-5 --target=powerpc-rtems5 --enable-rtemsbsp="beatnik" --enable-posix --enable-cxx --enable-networking
Through "--enable-networking" I was able to use the "old" rtems-bsdnet. With NTP, NFS etc. .
At the moment I am in the process of using the "new" netbsd. For this I am no longer allowed to specify "--enable-networking" when building the bsp. That's what it says
in the documentation and it works. The old NFS also works with it, it just lacks NTP (or PTP). And what I still miss very much is the support for the RTC and above all
the libpci to access the vmebus.
So I played a little with xilinx-zynq and beaglebone. Now I make the rtems_init at EPICS dependent on
xilinx_zynq_zedboard/make/bsp.cfg:HAS_NETWORKING = no (new bsdlib)
beatnik/make/bsp.cfg:HAS_NETWORKING = yes (old rtemsbsd code)
> On 11. Jul 2020, at 00:14, Joel Sherrill <joel at rtems.org> wrote:
> Wading in late but I thought I saw something that was contradictory:
> Build BSP with --enable-networking
> Code needs rtems-libbsd
> If the code needs rtems-libbsd, then you MUST build fill with --disable-networking.
> If EPICS code needs rtems-libbsd, that limits the number of BSPs that can be used but you need to always use libbsd.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel