EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  <19951996  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  Index 1994  <19951996  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 
<== Date ==> <== Thread ==>

Subject: Re: cross-compile mvme162
From: Ralph Lange <[email protected]>
To: [email protected] (Zhao Dong)
Cc: [email protected] (EPICS Tech-Talk)
Date: Thu, 3 Aug 1995 16:10:56 +0200 (MESZ)
Hi.

> The difference between compiling a mvme167 and compiling a mvme162 is that the
> former uses -m68040 option while the latter one uses -msoft-float option.

Right.
There are two different processor versions of the mvme162: One is equipped
with an 68040 (which includes a floating point processor), the other uses an
68LC040 (low cost: with no floating point arithmetics).

To run successfully on *all* mvme162s, the -msoft-float option is set which
replaces the floating point operations by library calls.

> When I loaded  base/bin/mv162/iocCore into a mvme162, I got the error messge as
> following:

> ld < targetmv162/iocCore
> undefined symbol: ___eqdf2
> undefined symbol: ___gtdf2
> undefined symbol: ___ltdf2
> undefined symbol: ___floatsidf
> undefined symbol: ___adddf3
> undefined symbol: ___divdf3
> undefined symbol: ___floatsisf
> undefined symbol: ___addsf3
>  ......
> ld error: error reading file (errno = 0x1c0001)

The VxWorks BSP for the mvme162 includes two kernels: one for each processor
type. When you boot the non-LC-kernel, the floating point libraries are not
included which leads to missing symbols when loading code compiled with
-msoft-float.

> When I loaded base/bin/mv167/iocCore,drvSup, recSup, devSup and a simple
> database into a mvme162, it didn't give me any error message, but the IOC hang.
> (drvSup and devSup caused it)

The mvme167 has got an FPU, the library routines are not used -> no missing
symbols at load time.
I don't know what causes the hanging IOC, but there might be more
differences between mvme167 and mvme162 than price ... ;-)

> I don't have any problem to load mv167/stuff into a mvme167.

Fine.

> Could anybody give me a help? Thanks a lot.

Just boot the mvme162 with the appropriate kernel.

Hope that helps,
Ralph
-- 
       __    Ralph Lange                          eMail:       [email protected]
      /\ \
     /  \ \    BESSY II                           Snail:             BESSY II
    / /\ \ \    Berliner Elektronenspeicherring-                Geb"aude 15.1
   / / /\ \ \    Gesellschaft f"ur Synchrotron-            Rudower Chaussee 5
  / / /__\_\ \    strahlung m.b.H.                        D-12489 Berlin, FRG
 / / /________\                                   Phone:     +49 30 6392-4862
 \/___________/   Control System Division         Fax:            ...   -4859


References:
cross-compile mvme162 Zhao Dong

Navigate by Date:
Prev: cross-compile mvme162 Zhao Dong
Next: Natl Inst CPU030 fyi Jeff Hill
Index: 1994  <19951996  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: cross-compile mvme162 Zhao Dong
Next: Natl Inst CPU030 fyi Jeff Hill
Index: 1994  <19951996  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·