MVME5100 backplane boot fail on vxworks 6.1 - VxWorks
This is a discussion on MVME5100 backplane boot fail on vxworks 6.1 - VxWorks ; Hi all,
We've got a problem booting both MVME5101 (64MB) boards from the
backplane running on vxworks 6.1. We use Wind River Workbench IDE and
VxWorks 6.1 for our project.
We included #define INCLUDE_SM_NET and INCLUDE_SM_COMMON in config.h
of MV5100 ...
-
MVME5100 backplane boot fail on vxworks 6.1
Hi all,
We've got a problem booting both MVME5101 (64MB) boards from the
backplane running on vxworks 6.1. We use Wind River Workbench IDE and
VxWorks 6.1 for our project.
We included #define INCLUDE_SM_NET and INCLUDE_SM_COMMON in config.h
of MV5100 folder, which is the directory of the MVME5100 BSP. We also
added the route to the host route table using route add on windows XP.
The problem is we DO NOT see anything indicating Initializing backplane
net with anchor at ....statement. No error. It just loads the Master
kernel image vxWorks and vxWorks.sym. No slave board boots from it.
----add to route table---
C:\> route add 172.16.0.104 MASK 255.255.255.255 172.16.0.101
----master board----
boot device : fei
unit number : 0
processor number : 0
host name : rtte
file name :
C:\WindRiver\workspace\VxWorksMV5100Master\default \vxWorks
inet on ethernet (e) : 172.16.0.101:ffffff00
inet on backplane (b): 172.16.0.103:ffffff00
host inet (h) : 172.16.0.149
user (u) : vxworks
ftp password (pw) : vxworks
flags (f) : 0x0
target name (tn) : mv5100_master
Attached TCP/IP interface to fei0.
Attaching network interface lo0... done.
Loading... 1419028 + 134760
Starting at 0x100000...
Attaching interface lo0... done
Attached IPv4 interface to fei unit 0
Loading symbol table from rtte:C:\WindRiver\workspace\VxWorksMV5100
Master\default\vxWorks.sym ...done
VxWorks
Copyright 1984-2005 Wind River Systems, Inc.
CPU: Motorola MVME5101-2133 - MPC 7400
Runtime Name: VxWorks
Runtime Version: 6.1
BSP version: 2.0/5
Created: Mar 03 2006, 18:45:07
ED&R Policy Mode: Deployed
WDB Comm Type: WDB_COMM_END
WDB: Ready.
---slave board configuration---
boot device : sm=0x20004100
unit number : 0
processor number : 1
host name : rtte
file name :
C:\WindRiver\workspace\VxWorksMV5100Slave\default\ vxWorks
inet on backplane (b): 172.16.0.104:ffffff00
host inet (h) : 172.16.0.149
gateway inet (g): 172.16.0.103
user (u) : vxworks
ftp password (pw) : vxworks
flags (f) : 0x0
target name (tn) : mv5100_slave
Please help!
Ray
-
Re: MVME5100 backplane boot fail on vxworks 6.1
Hi Ray,
Just thought I'd let you know that we tried for literally months to get
shared memory boot happening with the mv5100 BSP... never got it
working once! (This was with VxWorks 5.5.1.) We just ended up booting
both boards from their own fei interfaces. I had a local WindRiver
consultant try to help us through it, but we still couldn't get it
going. Don't know if it's for exactly the same reasons as you - our
slave board would at least attempt to load it's image, but would always
timeout (errno 0x3c from memory).
A couple of things to note:
- There is a WRS patch which allegedly addresses the issue using an END
network driver, however it didn't fix anything for us. You can find it
on WindSurf - it's called "t22-cp1-smend". Seeing as you're on Vx6 I
don't suppose you'll be able to use it, but just FYI.
(https://portal.windriver.com/cgi-bin...inaryid=104120)
- Someone here fixed their shared memory booting problem by adding
INCLUDE_BSD to their config.h (don't know if it's relevant here
though):
http://groups.google.com/group/comp....df6e5314a6de51
Anyway, not wanting to discourage you, but I'd hate to see you waste as
much time on this as we did! Good luck... let us know if you get it
working.
Ben
