02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A<br />

Upgrading a <strong>BSP</strong> for<br />

Tornado 2.0<br />

This appendix describes how to port a <strong>BSP</strong> from Tornado 1.0.1/VxWorks 5.3.1 to<br />

Tornado 2.0/VxWorks 5.4.<br />

<strong>BSP</strong>s written for VxWorks 5.2, or earlier releases, are designated as version 1.0<br />

<strong>BSP</strong>s. <strong>BSP</strong>s written for Tornado 1.0.1, or earlier, are designated as version 1.1 <strong>BSP</strong>s.<br />

<strong>BSP</strong>s written to the standard outlined in this document, specifically for Tornado<br />

2.0, are designated as version 1.2 <strong>BSP</strong>s.<br />

All version 1.1 <strong>BSP</strong>s that have been modified to use END drivers and the SENS<br />

network stack are compatible with Tornado 2.0. Third-party <strong>BSP</strong>s using<br />

specialized make sequences and modified versions of kernel files may or may not<br />

translate well to projects. They will work correctly if the traditional command line<br />

is used to build the project.<br />

A.1 Porting Issues<br />

Porting an existing Tornado 1.0.1 <strong>BSP</strong> to Tornado 2.0 involves three main steps:<br />

■<br />

■<br />

Update the <strong>BSP</strong> for the SENS network stack. If an END-style driver is available<br />

for the <strong>BSP</strong>, then it should become the default network driver. Any custom<br />

network drivers that are not END or BSD 4.4 compatible must be upgraded for<br />

SENS. See C. Upgrading a <strong>BSP</strong> for the VxWorks Network Stack.<br />

Create a default project and the HTML documentation for the <strong>BSP</strong>. This is done<br />

using the command make release man.<br />

203

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

Saved successfully!

Ooh no, something went wrong!