It is usually faster to ask for help on the tech-talk mailing list, I am
not the only person who can answer questions about VxWorks.
On 06/22/2017 04:00 AM, firstname.lastname@example.org wrote:
> I'm yongnian, a control engineer at SSRF.
> We need upgrade our vxWorks form 5.5.1 with tornado2.2 to 6.8 with
> How we can compile an EPICS IOC under the new software environment?
> For example, we need to control a step motor with MAXv controller, the
> cross compiler will be different with tornado2.2.
> What should we do to build the new cross compiler software environment?
You shouldn't need to build your own cross compiler, just use the
version of GCC that comes with your Workbench and VxWorks 6.8
installation. Note that you cannot use Wind River's Diab compiler to
build EPICS though, we only support builds for VxWorks using GCC.
You haven't explained whether both versions of VxWorks need to co-exist
in the same EPICS build tree, or which host architecture you will be
using. My answers below assume that you will be installing a new copy of
EPICS Base and all the necessary support modules for your IOCs, but that
isn't necessary — here at the APS we have installations of EPICS that
are built for 3 different VxWorks versions simultaneously, although that
is a slightly more advanced topic.
Once you have installed Wind River Workbench with the GCC compiler, you
tell EPICS where to find it by editing the file
You have to say which version of VxWorks you have, so uncomment the line
VXWORKS_VERSION = 6.8
and make sure the other versions are commented out.
Then adjust the setting of WIND_BASE to point to your installation
WIND_BASE = /path/to/vxWorks-6.8
You also have to set the versions of WorkBench and Utilities, so
WORKBENCH_VERSION = 3.2
UTILITIES_VERSION = 1.0
You will also need to tell EPICS to cross-build for your particular
VxWorks target architecture by including the target architecture name in
the build variable CROSS_COMPILER_TARGET_ARCHS. There are several places
where you could set this, the easiest being in the configure/CONFIG_SITE
file, but you can also use the
configure/os/CONFIG_SITE.<host-arch>.Common file which is the right
place if you will be building Base for several different host
architectures. Cross-building should work on both Linux and Windows
hosts, although most people use Linux so there might be some bugs in the
Windows configurations (ask for help on tech-talk if you're using
Windows and it doesn't seem to work properly).
Once all your configuration edits are saved, you should just be able to
run 'make' at the top of the Base source tree and it will build
everything, first for your host architecture and then for the VxWorks
If you have problems, please write back to tech-talk for help and make
sure you copy and paste the last few lines of the build output along
with any error messages that you're getting.
Hope this helps,
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- Navigate by Date:
Re: modbus write 2 16 bits holding registers with modbus function 16 Claudio Lambert
Re: jca question J. Lewis Muir
- Navigate by Thread:
Re: jca question Jeong Han Lee
css running not fluent 王鹏鹏