Hi Torben,
Run the 'h' command on the VxWorks boot prompt. At the end you will see
the list of "available boot devices".
Unfortunately in VxWorks the ethernet devices are named after the chip
(or rather the used driver) instead of something like "eth0".
Dirk
On 19.01.2015 21:05, tlauritsen wrote:
Hi,
We have recently acquired a set of new MVME5500 processors to be used in
our latest VxWorks/EPICS based DAQ systems. The MVME5500 processors were
supposed to be identical the the fleet of old MVME5500 IOCs we already
have, but there has been a change of some sort to the new processors.
When we load in the boot.bin from the EPICS build that we use on the old
processors, we loose the network gei0. On the old processors we see this
at the boot prompt:
[VxWorks Boot]: n gei0
Address for device "gei0" == 00:01:af:31:81:56
with the new processors:
[VxWorks Boot]: n gei0
Network interface gei unknown.
Cannot initialize interface named "gei0"
and we cannot communicate, so we are dead in the water. The only change
we have been able to detect is the PAL version from 2.4 to 2.5:
old
MVME5500> version
Copyright(C)2008-2009,Emerson Network Power-Embedded Computing,Inc.
All Rights Reserved
Copyright Motorola Inc. 1999-2007, All Rights Reserved
MOTLoad RTOS Version
2.0, PAL Version 2.4 RM01
Thu Feb 12 12:05:38 MST 2009
new
MVME5500> version
Copyright(C)2008-2013,Emerson Network Power-Embedded Computing,Inc.
All Rights Reserved
Copyright Motorola Inc. 1999-2007, All Rights Reserved
MOTLoad RTOS Version 2.0, PAL Version 2.5 RM01
Tue Jun 25 15:51:04 MST 2013
The version of the boot.bin we use comes from
[VxWorks Boot]: v
....
CPU: Motorola MVME5500-0163 - MPC 7457
Version: VxWorks5.5
BSP version: 1.2/1
Creation date: Jun 3 2008, 10:52:32
Has any of you experienced this problem and/or have a solution?
Thank you,
[email protected]
[email protected]
- Navigate by Date:
- Prev:
RE: AreaDetector / ADURL queries Heesterman, Peter J
- Next:
RE: AreaDetector / ADURL queries Mark Rivers
- 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:
Re: Multi-monitor for CSS opi palak shimpee
- Next:
StreamDevice exception handlers Eric Norum
- 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
|