Hi all,
I began to test SBS PC6 embedded computer. It has PENTIUM compatible CPU.
There is BSP for this target for Tornado II. I use R3.13.6 Epics release.
To build Epics I added file CONFIG.Vx.sbs_pc6 derived from CONFIG.Vx.pc486
just by replacing appropriate compilation options (taken from BSP).
This file looks like:
# Created by Korobov for SBS PC6
# CONFIG.Vx.sbs_pc6
#
# This file is maintained by the EPICS community.
# Vx GNU cross compiler suffix
CMPLR_SUFFIX = 386
# For Vx directories of form:
# $(VX_DIR)/$(HOST_ARCH).$(ARCH_CLASS)/bin
ARCH_CLASS = sbs_pc6
ARCH_DEP_CFLAGS = -DCPU=PENTIUM -mpentium -DCPU_VARIANT=PENTIUM
ARCH_DEP_CXXFLAGS += -x 'c++'
ARCH_DEP_CFLAGS += -fno-builtin -fno-defer-pop
----------------------------------------------------
Epics core was built successfully. I created some test database and
downloaded it into the IOC. From IOC side it seems to work OK.
But when I try to access any records from outside after starting any
CA clients I get messages (on client side):
.../iocinf.c: bad UDP msg from epicsPC20.desy.de:5064
What could be the cause of such behaviour.
Thanks in advance for any help or ideas,
V.Korobov
- Replies:
- RE: "bad UDP msg ..." error message Jeff Hill
- Navigate by Date:
- Prev:
xy542 and koDevLib Allan Honey
- Next:
CA problem Pedro Gigoux
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
<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:
xy542 and koDevLib Allan Honey
- Next:
RE: "bad UDP msg ..." error message Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
<2002>
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|