I think you can think about each of these 3
parts of this separately:
1) Cross compiler host system
2) OPI (e.g. edm, medm,
etc.) host
3) Boot server host
You really need to run win32 on 1), the
cross-compiler. I assume that works OK, since you say it is supported.
You can use win32 as the OPI if you are
using medm, but not if you are using edm, it does not support win32. But
this is not a problem, you can always run your OPIs on Linux or other systems,
even if you use win32 to cross-compile.
To boot from win32 you would need to get
an ftp, tfpt or rsh system running on win32. But again, this is not
necessary. You could use win32 as your cross-compiler, but build from a
Linux file system with Samba. That is what I do. Then you can boot
the vxWorks system from Linux, not from Windows.
Mark
My
task is to port a LLRF system to
EPICS, I use vxWorks5.5.1 and EPICS-3.14.8.2, but the CPU board has
not been finally determined,
probably CPCI6200 or CPCI6190.
A
recommended CPU board is CPCI6200 with high
performance and a
MPC8572 dual core processor, which the
crossgcc2.9.6 from SNS does not support. So I think I can
use win32 as EPICS development environment, OPI and server(such as ftp and
tftp), tornado2.2.1(supports MPC8572) on win32 as the
cross compiler.
But
I am not sure whether it is an advisable choice, since I have no experience of
developing EPICS application on win32, I don't know whether win32
is suitable as
EPICS host, and what problem may occur frequently.