Booting VxWorks
forums_mp
VxWorks 5.5, Win XP
So I opting to boot VxWorks but with zero success, this after 6+ hours
of reading manuals etc.
So now the list of devices available.
symeth0, gteth1, ppp, sl, scsi, tffs
Now which to use:
The board has a GT64260 chip (Discovery ethernet interface) which
according to the (I think it's the 181 hardware manual) manual
corresponds to a gteth device. So my set up is akin to:
boot device : gteth1
unit number : 0
processor number : 0
host name : antilla
file name : c:\User\Tornado\BSP\vxWorks
inet on ethernet (e) : 165.250.252.83
inet on backplane (b):
host inet (h) : 165.250.252.82
user (u) : user
ftp password :
target name (tn) : DY4
other (o) :
// later @
Attached TCP/IP interface to gteth1.
Warning: No netmask specified
Attaching network interface lo0... done.
Loading...
Error loading file: errno = 0x3c
I've got a call out to Windriver but in the interim, I'm not sure what
0x3c means but more importantly what's the specific problem?
In addition, i've got more questions after reading multiple manuals.
- I realize inet on ethernet is the IP address of the target which
means it gets LOADED into the target?
- Is there a manual/site out there with meaningful descriptions of
the list of devices? SCSI of course is intuitive. Then there's this.
How does 'it' (??) determine the list of devices available to me?
- Is it safe to state that the boot devices is predicated on the
ethernet chip? I've seen fei's/cpms and I'm not sure whats the
determining factor.
If anyone has used the 181 and has setup params they wouldn't mind
sharing I'd appreaciate it.
The interesting thing is that the board came with a default 'boot
image' programmed into it but I'm confused on how that's structured
internally. Theres separate IP addresses for host and inet but who's
the host and who's inet? haven't quite figured out how this works.
Boot device in this case is
tffs=0,0.
tffs doesn't apply to me (dont think) after reading the manual where
gteth was the device of choice.
I'm relatively new to 'vxWorks' land hence I apologize for what might
seem like silly questions.
Michael R. Kesti
>Environment: SBC 181 mounted in a tracewell chassis. IDE tornado 2.2
>VxWorks 5.5, Win XP
>
>So I opting to boot VxWorks but with zero success, this after 6+ hours
>of reading manuals etc.
>
>So now the list of devices available.
> symeth0, gteth1, ppp, sl, scsi, tffs
>
>Now which to use:
>The board has a GT64260 chip (Discovery ethernet interface) which
>according to the (I think it's the 181 hardware manual) manual
>corresponds to a gteth device.
That sounds right.
> So my set up is akin to:
>
>boot device : gteth1
>unit number : 0
>processor number : 0
>host name : antilla
>file name : c:\User\Tornado\BSP\vxWorks
>inet on ethernet (e) : 165.250.252.83
>inet on backplane (b):
>host inet (h) : 165.250.252.82
>user (u) : user
>ftp password :
>target name (tn) : DY4
>other (o) :
>
>// later @
>
>Attached TCP/IP interface to gteth1.
>Warning: No netmask specified
>Attaching network interface lo0... done.
>Loading...
>
>Error loading file: errno = 0x3c
>
>I've got a call out to Windriver but in the interim, I'm not sure what
>0x3c means but more importantly what's the specific problem?
See http://www.eelab.usyd.edu.au/tornado/docs/vxworks/errno/errnoNumList.html
Errno 0x3c is ETIMEDOUT which probably means that a timeout occurred on the
attempt to download the vxworks image specified by the "file name" field.
These boot parameters tell the boot image to access an FTP server on a
host whose IP address is specified in the "host inet" field and from which
it will load the file specified in the "file name" field. The "user" and
"ftp password" fields are used to access this FTP server. I suspect that
your host isn't running an FTP server and that this is why the boot fails.
Wind River supplies an FTP server for this purpose that you will find in
the directroy $(WIND_BASE)\host\x86-win32\bin, where $(WIND_BASE) is the
base directory into which vxworks and Tornado were installed on your PC.
>In addition, i've got more questions after reading multiple manuals.
This is typical. ;-)
>- I realize inet on ethernet is the IP address of the target which
>means it gets LOADED into the target?
I don't understand this question.
>- Is there a manual/site out there with meaningful descriptions of
>the list of devices? SCSI of course is intuitive. Then there's this.
> How does 'it' (??) determine the list of devices available to me?
The list of boot devices is determined at the time the boot ROM image is
built. The boot ROM image is the program that is built in the BSP directory
which is typically located at $(WIND_BASE)\target\config\bspname or the
like. The file config.h in the BSP directory specifies the features that
are to be built into the boot ROM including the bootable devices.
>- Is it safe to state that the boot devices is predicated on the
>ethernet chip? I've seen fei's/cpms and I'm not sure whats the
>determining factor.
Boot devices can be ethernet interfaces (usually using FTP), floppy, hard
and solid state disks, serial interfaces (SLIP) and the like.
>If anyone has used the 181 and has setup params they wouldn't mind
>sharing I'd appreaciate it.
>
>The interesting thing is that the board came with a default 'boot
>image' programmed into it but I'm confused on how that's structured
>internally.
This image should be that which is created by running make in the BSP
directory.
> Theres separate IP addresses for host and inet but who's
>the host and who's inet? haven't quite figured out how this works.
The host is the computer that you use to run Tornado and where you develop
and build bootable vxworks images and downloadable applications. "inet on
ethernet" is the IP address of the target which, in your case, is your SBC
181. The "inet on backplane" field is probably of no concern to you.
>Boot device in this case is
>tffs=0,0.
>
>tffs doesn't apply to me (dont think) after reading the manual where
>gteth was the device of choice.
If tffs is available as a boot device then it may very well apply to you
but its not going to be useful until you can boot from your host and copy
a boot image to the flash disk that is the tffs device. Once you do this
you can reconfigure your boot parameters to boot from the tffs device and
your target will be capable of running without the aid of a host!
>I'm relatively new to 'vxWorks' land hence I apologize for what might
>seem like silly questions.
We've all been through this and found it gets easier after you begin to
get the hang of the myriad of details required to make it all work. You're
asking the right questions so you're probably on your way to success!
--
========================================================================
Michael Kesti | "And like, one and one don't make
| two, one and one make one."
mke...@gv.net | - The Who, Bargain