vxWorks boot ROM image ..

[brooks o. thornhill]

News Group,

Can someone tell me exactly the difference between a 'vxWorks boot ROM
image' and a 'vxWorks standalone ROM image' ?

I want to get a copy of vxWorks and my application code into FLASH and
currently using a MVME162 board ... Between the 'Tornado Reference
Guide' and the man page for mv162 I am a little confused as to what
exactly I need to accomplish next ..

Do I simply need to run the 'vxWorks.st_rom_bin' command or is there
more that I need to accomplish .. Two things that I do know is that 1) I
do not want a compressed image and 2) I do want a symbol table included
..

Any help would be great !

Thanks,
Brooks

[Charlie Hamilton]

brooks o. thornhill wrote:
>
> News Group,
>
> Can someone tell me exactly the difference between a 'vxWorks boot ROM
> image' and a 'vxWorks standalone ROM image' ?

The boot ROM image is made using the bootConfig.c file, whereas
the standalone image is made using the usrConfig.c file. They do
basically the same thing, except bootConfig.c is stripped down
a lot more, and has support for interactive booting.

> I want to get a copy of vxWorks and my application code into FLASH and
> currently using a MVME162 board ... Between the 'Tornado Reference
> Guide' and the man page for mv162 I am a little confused as to what
> exactly I need to accomplish next ..

We're doing exactly the same thing, and I made some ROMs using
the vxWorks.st image (built with usrConfig.c) that look for a
file in flash to boot. You can use the "bootLoadModule" function,
which is undocumented, but you should be able to get source from
your FAE. It supports various object file formats. One of the
big benifits about booting from a file vs. running from a ROM is
that you get better use of memory.

> Do I simply need to run the 'vxWorks.st_rom_bin' command or is there
> more that I need to accomplish .. Two things that I do know is that 1) I
> do not want a compressed image and 2) I do want a symbol table included
> ..

Just define the following

#define INCLUDE_SYM_TBL /* symbol table package */
#define INCLUDE_STANDALONE_SYM_TBL /* compiled-in symbol table */

in the vxWorks.st build, and you should be able to boot it using
bootLoadModule().

[John Kevin Fabiani]

brooks o. thornhill wrote:
>
> News Group,
>
> Can someone tell me exactly the difference between a 'vxWorks boot ROM
> image' and a 'vxWorks standalone ROM image' ?
>

> I want to get a copy of vxWorks and my application code into FLASH and
> currently using a MVME162 board ... Between the 'Tornado Reference
> Guide' and the man page for mv162 I am a little confused as to what
> exactly I need to accomplish next ..
>

> Do I simply need to run the 'vxWorks.st_rom_bin' command or is there

??

> more that I need to accomplish .. Two things that I do know is that 1) I
> do not want a compressed image and 2) I do want a symbol table included

No compression and symbol table are no problem.

Assuming you are using vxWorks 5.3.1:

Make vxWorks_rom.hex (mot srec, which can be burned into prom)

Make sure the config.h does include the following:

#define INCLUDE_CONFIGURATION_5_2

That pulls in the target tools (see /src/config/usrDepend.c)

If you want to burn into flash, then use aoutToBin
(or aoutToBinDec for Windows host) to make a binary.

aoutToBin < vxWorks_rom > vxWorks_rom.bin

The exactly follow target.nr instructions for burning it
into the mv162's flash for booting.

> ..

>
> Any help would be great !
>
> Thanks,
> Brooks

--
/=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-\
| __ |
| John Kevin Fabiani /\ \ |
| Corporate Consulting Engineer / \ \ |
| Wind River Systems / /\ \ \ |
| / / /\ \ \ |
| (510) 814-2167 Office / / /__\_\ \ |
| (510) 814-2010 Fax / / /________\ |
| (800) 872-4977 \/___________/ |
| http://www.wrs.com |
| jo...@wrs.com "Music is my mistress and she plays |
| sup...@wrs.com second fiddle to no one" - Ellington |
| |
\=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-/