0000255: Provide wrapper and support for XGATE Outputs

View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000255

Firmware

XGATE Bit Bang

public

2011-09-02 16:15

2011-09-02 16:55

Reporter

Fred

Assigned To

Fred

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

assigned

Resolution

open

Platform

OS Version

Product Version

0.2.0-SNAPSHOT

Target Version

0.4.0

Fixed in Version

Summary

0000255: Provide wrapper and support for XGATE Outputs

Description

To really prove Sean's XGATE code we need a proper interface that pulls its data out of the scheduler in the same way that the ECT stuff does. I need to provide a way of flagging whether we want each channel to be an XGATE channel or an ECT channel in config somewhere and a wrapper in the decoderInterface for the code that schedules that on the XGATE side, and a little if else block which calls one or the other based on which type it was intended to be. In the mean time Sean can keep working with his block and/or macro as I get this done for him.

Tags

No tags attached.

FirmwareVersion

Issue Type

Task

Risk of Breakage

medium

Attached Files

Relationships

Notes
(0000254) Fred (administrator) 2011-09-02 16:45	Interface should look something like this: XGS(channel8, edgeTimeStamp16, numOfDelays8, delayTime16, runTime16) Storing the data in the XGATE ram area, and then calling the XGATE sched interrupt when stored and ready. Because N can be scheduled in one decoder iteration, we need an array of data areas for this, and an array length for the XGATE code to read before iterating over them.