Experimental Physics and
Industrial Control System

Dehong Zhang <[email protected]> · Fri, 14 Nov 2008 12:28:23 -0600

Hi Andrew,

Thank you very much for all your patience with me!

Our board actually has MPC7455 processor, with AltiVec coprocessor.
I followed your suggestions and tried vxWorks-ppc604_altivec.  Still
got the same error messages:

# Epics Startup command file
# cd "/home/vxworks_boot/fe/hinst1/epics"

# putenv("EPICS_TS_NTP_INET='127.0.0.1'")
putenv("EPICS_CA_MAX_ARRAY_BYTES=1048576")
value = 0 = 0x0

ld < hinst1.munch
Warning: module 0x329d640 holds reference to undefined symbol _Z7WireSetIfEvRKT_Ph.
Warning: module 0x329d640 holds reference to undefined symbol _Z7WireSetIiEvRKT_Ph.
Warning: module 0x329d640 holds reference to undefined symbol _Z7WireSetIsEvRKT_Ph.
value = 53073472 = 0x329d640
dbLoadDatabase("hinst1.dbd")
value = 0 = 0x0
hinst1_registerRecordDeviceDriver(pdbbase)

0x0013af88 vxTaskEntry  +0x54 : 0x0026b830 ()
0x0026b830 shellTask    +0x4ec: shellExec ()
0x0026b2bc shellExec    +0x194: 0x00262340 ()
0x002624c4 shellInterpCparse+0x1238: shellInOutRedirectScript ()
0x00258bf4 shellInOutRedirectScript+0x70 : shellExec ()
0x0026b2bc shellExec    +0x194: 0x00262340 ()
0x00262560 shellInterpCparse+0x12d4: shellInterpCparse ()
0x00262040 shellInterpCparse+0xdb4: 0x0025e294 ()
0x0025e2bc shellInterpCInit+0x13bc: 0x0025df90 ()
0x0025dfb8 shellInterpCInit+0x10b8: 0x0025de1c ()
0x0025ded4 shellInterpCInit+0xfd4: shellInternalFunctionCall ()
0x00259998 shellInternalFunctionCall+0xa4 : 0x032cbbd4 ()
0x032cbc08 hinst1_registerRecordDeviceDriver+0x38 : registerRecordTypes ()
0x0332eb88 registerRecordTypes+0x198: 0x00000004 ()

program
Exception current instruction address: 0x00000004
Machine Status Register: 0x0208b030
Condition Register: 0x20000442

Shell task 'tShellRem1' restarted...

Guess I missed something.  Please help to take a look.

Thank you again, best regards,
Dehong

----- Original Message -----
From: Andrew Johnson <[email protected]>
Date: Thursday, November 13, 2008 4:22 pm
Subject: Re: WireSet missing with 3.14.10
To: Dehong Zhang <[email protected]>
Cc: [email protected]

> Hi Dehong,
> 
> On Thursday 13 November 2008 15:11:02 Dehong Zhang wrote:
> >
> > We need the "vxWorks6-mv5100" architecture, but the base package 
> does not
> > have it.
> 
> Ah, that's the problem, no you don't; the vxWorks6 targets have been 
> merged 
> back into the regular vxWorks ones (they should never have been added 
> to 
> 3.14.8 in the first place).  Use the supplied vxWorks-ppc604_long or 
> vxWorks-ppc604_altivec targets instead; if your MVME5100 board has an 
> MPC750 
> CPU use vxWorks-ppc604_long, but if your board is really an MVME5110 
> and has 
> a MPC7410 CPU with altivec enabled then use vxWorks-ppc604_altivec instead.
> 
> I suggest you:
> 
> 1. Delete all the vxWorks6 files you created under base/configure/os
> 2. Edit base/configure/os/CONFIG_SITE.Common.vxWorksCommon and define 
> the 
> WIND_BASE setting in there to point to your vxWorks 6 installation
> 3. Edit base/configure/CONFIG_SITE and change 
> CROSS_COMPILER_TARGET_ARCHS to 
> use the appropriate target(s) as described above
> 4. In the base top level directory, run 'make distclean; make'
> 5. Repeat step 4 for all your support modules
> 6. In your IOC area, edit the iocBoot/ioc*/Makefile and change the 
> setting for 
> ARCH to the correct architecture as discussed above, then 'make 
> distclean; 
> make' in the application top level directory and try booting the IOC.
> 
> - Andrew
> -- 
> Talk is cheap. Show me the code. -- Linus Torvalds

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System