02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

2<br />

<strong>BSP</strong> Organization<br />

bootrom<br />

This file is an object module containing the binary VxWorks boot ROM.<br />

2<br />

bootrom.hex<br />

This is an ASCII file containing the VxWorks boot ROM code, suitable for<br />

downloading over a serial connection to a PROM programmer. The default<br />

encoding uses Motorola S-Records.<br />

bootrom.Z.s and bootrom.Z.o<br />

ctdt.o<br />

dataSegPad.o<br />

This is the source and object output that is the compressed image of the bootrom.o<br />

module.<br />

This module handles C++ constructor/destructor functionality.<br />

The module insuring that the text and data segments do not share a common<br />

memory page. For the VxVMI option, this module forces alignment of the data<br />

segment in a different MMU page from the text segment.<br />

symTbl.c and sysALib.o<br />

These are the source and object files for the built-in symbol table.<br />

sysLib.o and sysALib.o<br />

romInit.o<br />

These modules always go together as a pair. They are the output of the sysALib.s<br />

and sysLib.c modules.<br />

This module is the startup code for any ROM image, boot or VxWorks. For<br />

Tornado, it works in conjunction with the romStart.o module instead of bootInit.o.<br />

vxWorks and vxWorks.sym<br />

The vxWorks file is the complete, linked VxWorks binary to be run on the target.<br />

The vxWorks.sym file is the symbol table for the VxWorks binary. Both files are<br />

created with the supplied configuration files.<br />

29

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!