Mantis Bug Tracker

View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000255FirmwareXGATE Bit Bangpublic2011-09-02 16:152011-09-02 16:55
Assigned ToFred 
PrioritynormalSeverityminorReproducibilityhave not tried
PlatformOSOS Version
Product Version0.2.0-SNAPSHOT 
Target Version0.4.0Fixed in Version 
Summary0000255: Provide wrapper and support for XGATE Outputs
DescriptionTo 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.
TagsNo tags attached.
Issue TypeTask
Risk of Breakagemedium
Attached Files

- Relationships

-  Notes
User avatar (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.

Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker