20.12.2012 Views

2.2 BSP Rel. 1.0 for PPMC-275 Programmer's Guide

2.2 BSP Rel. 1.0 for PPMC-275 Programmer's Guide

2.2 BSP Rel. 1.0 for PPMC-275 Programmer'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.

List of APIs API Call Reference<br />

RETURN<br />

System Interrupt Controller<br />

Supported Features<br />

Software Modules<br />

Software Requirements<br />

OK If the output was successful.<br />

ERROR If the output failed.<br />

A system interrupt controller is necessary because of the Power PC<br />

architecture restriction concerning interrupts. Since the Power PC<br />

has only one external interrupt exception (vector 0x500), it is<br />

essential to have an interrupt controller on board. This interrupt<br />

controller provides the support <strong>for</strong> the following routines:<br />

• intConnect()<br />

• intDisable()<br />

• intenable()<br />

The system interrupt controller uses the General Purpose Port<br />

(GPP) Interrupt Controller services to implement those functionalities.<br />

This driver is fully compatible with VxWorks. Thus, to connect an<br />

interrupt routine to one of the above external interrupts, use the<br />

standard VxWorks intConnect() routine.<br />

This driver is fully compatible with the VxWorks interrupt API.<br />

For example, to connect an interrupt routine to an external interrupts<br />

event, use the standard VxWorks intConnect() routine.<br />

The following software modules are available:<br />

• sysIntCtrl.c<br />

• sysIntCtrl.h<br />

The software requirements are:<br />

WindRiver VxWorks Operating system, Version 5.3.1 or later<br />

GPP Interrupt Controller driver.<br />

5 - 12 VxWorks 5.5/Tornado <strong>2.2</strong> <strong>BSP</strong> <strong>Rel</strong>. <strong>1.0</strong> <strong>for</strong> <strong>PPMC</strong>-<strong>275</strong>

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

Saved successfully!

Ooh no, something went wrong!