CF2 API Reference (PDF) - Persistor Instruments Inc
CF2 API Reference (PDF) - Persistor Instruments Inc CF2 API Reference (PDF) - Persistor Instruments Inc
CF2 API ReferenceQRstring -- Query/Reply for string using: %sDescription:Prototype:Inputs:Returns:Query/Reply for string using: %s,bool QRstring(char *prompt, char *fmt, bool crok, char *strbuf, short len);prompt is a zero terminated C string to display as a prompt for the user.fmt is a standard C libary printf/scanf format stringcrok is set TRUE to accept the default reply with just a carriage-return (enter key)strbuf is a pointer to a character buffer to hold the replylen is the maximum number of character to place in the reply bufferReturns TRUE for all but query cancelled (CTRL-C typed).QRtime -- Query/Reply for timeDescription:Prototype:Inputs:Returns:Notes:Query/Reply for timebool QRtime(char *prompt, bool crok, struct tm *tm);prompt is a zero terminated C string to display as a prompt for the user.crok is set TRUE to accept the default reply with just a carriage-return (enter key)tm is a standard C library tm structure pointer from with fields tm_hour, tm_min, andtm_secs filled in from the scan.Returns TRUE for all but query cancelled (CTRL-C typed).Replies are accepted in the form: HOURSMINUTESSECONDS may be any single comma, space, dash, period, or slash.QRulong -- Query/Reply for ulong using: %li %ld %lu %loDescription:Prototype:Inputs:Returns:Query/Reply for ulong using: %li %ld %lu %lobool QRulong(char *prompt, char *fmt, bool crok, ulong *value, ulong min, ulongmax);prompt is a zero terminated C string to display as a prompt for the user.fmt is a standard C libary printf/scanf format stringcrok is set TRUE to accept the default reply with just a carriage-return (enter key)value is a pointer to a ulong variable that will hold the replymin if not equal to max, min is the minimum valid value to accept for a replymax if not equal to min, max is the maximum valid value to accept for a replyReturns TRUE for all but query cancelled (CTRL-C typed).QRushort -- Query/Reply for ushort using: %i %hi %d %hd %u %hu %o %hoDescription:Prototype:Inputs:Returns:Query/Reply for ushort using: %i %hi %d %hd %u %hu %o %hobool QRushort(char *prompt, char *fmt, bool crok, ushort *value, ushort min, ushortmax);prompt and fmt and crok same as described abovevalue is a pointer to a ushort variable that will hold the replymin and max same as described aboveReturns TRUE for all but query cancelled (CTRL-C typed).PERSISTORInstruments Inc.44 of 84CF2 API Reference7/19/2005
CF2 API ReferenceQueued PicoBUS (QSPI) Drivers and FunctionsSummary of QSPI Drivers and FunctionsQPBClearBusyClear busy flagQPBClearInterrupt Clear the QPB interrupt flagQPBFreeSlotQPBInitSlotQPBLockSlotQPBRepeatAsyncQPBSetupQPBTestBusyQPBTestLockedQPBTransactQPBUnlockSlotRemove a PicoBUS device slotInitialize a PicoBUS device slotLock and return true if slot available for exclusive useExecute a pre-set-up asynchronous transferSet up the QPB for future asynchronous transfersSet up the QPB for future asynchronous transfersSee if the QPB is lockedConduct a PicoBUS sessionUnlock PicoBus for unrestricted useQPBClearBusy -- Clear busy flagDescription:Prototype:Inputs:Returns:Clear busy flagvoid QPBClearBusy (void);NoneNothingQPBClearInterrupt -- Clear the QPB interrupt flagDescription:Prototype:Inputs:Returns:Notes:Clear the QPB interrupt flagvoid QPBClearInterrupt (void);NoneNothingWhen operating asynchronously, the function specified by the asynchf argument to eitherQPBSetup or QPBTransact, will be called upon completion of the transaction. This function mustbe called by the handler function so that the interrupt flag that forced the execution of thecompletion routine is cleared. If the flag is not cleared, then the completion routine will beexecuted for ever.PERSISTORInstruments Inc.45 of 84CF2 API Reference7/19/2005
- Page 1 and 2: PERSISTOR ® CF2API ReferenceCopyri
- Page 3 and 4: CF2 API ReferenceATA Device Drivers
- Page 5 and 6: CF2 API ReferenceBigIDEA IDE Driver
- Page 7 and 8: CF2 API ReferenceBIOSVersionCheck -
- Page 9 and 10: CF2 API ReferenceCheckSum32 -- Upda
- Page 11 and 12: CF2 API ReferenceChip Select Wrappe
- Page 13 and 14: CF2 API ReferenceCompactFlash Low L
- Page 15 and 16: CF2 API ReferenceBelow are macros d
- Page 17 and 18: CF2 API ReferenceCIOprintf - Simple
- Page 19 and 20: CF2 API Referenceuprintf -- A clone
- Page 21 and 22: CF2 API ReferenceDIRMatchName -- Re
- Page 23 and 24: CF2 API ReferenceLED Signal Functio
- Page 25 and 26: CF2 API ReferencePeriodic Interrupt
- Page 27 and 28: CF2 API ReferencePicoDOS Initializa
- Page 29 and 30: CF2 API ReferencePin I/O Drivers, F
- Page 31 and 32: CF2 API ReferencePinIO -- Make an I
- Page 33 and 34: CF2 API ReferencePIOClear -- Config
- Page 35 and 36: CF2 API ReferencePing-Pong Buffer F
- Page 37 and 38: CF2 API ReferencePPBPutWord -- Writ
- Page 39 and 40: CF2 API ReferenceQSMRun - Start the
- Page 41 and 42: CF2 API ReferenceQuery/Reply Functi
- Page 43: CF2 API ReferenceQRdouble -- Query/
- Page 47 and 48: CF2 API ReferenceQPBSetup -- Set up
- Page 49 and 50: CF2 API ReferenceReal Time Clock Dr
- Page 51 and 52: CF2 API ReferenceRTCtime -- ANSI st
- Page 53 and 54: CF2 API ReferenceSTDIO WarningThe A
- Page 55 and 56: CF2 API ReferenceSCIRxFlush -- Dele
- Page 57 and 58: CF2 API ReferenceSCIRxTxIdle -- Ret
- Page 59 and 60: CF2 API ReferenceSCITxWaitCompletio
- Page 61 and 62: CF2 API ReferenceTable Driven Comma
- Page 63 and 64: CF2 API ReferenceCmdIsNumber- Is Co
- Page 65 and 66: CF2 API ReferenceTime Processing Un
- Page 67 and 68: CF2 API ReferencePrototype:Inputs:N
- Page 69 and 70: CF2 API ReferenceTPU UartSummary of
- Page 71 and 72: CF2 API ReferenceTUOpen - Open a TP
- Page 73 and 74: CF2 API ReferenceTUTxFlush - Delete
- Page 75 and 76: CF2 API ReferenceUtility Functionse
- Page 77 and 78: CF2 API Referencesscantime -- scan
- Page 79 and 80: CF2 API ReferenceVEEDelete -- Delet
- Page 81 and 82: CF2 API ReferenceVEEStoreFloat -- S
- Page 83 and 84: CF2 API ReferencePinBus, 30PinClear
<strong>CF2</strong> <strong>API</strong> <strong>Reference</strong>Queued PicoBUS (QSPI) Drivers and FunctionsSummary of QSPI Drivers and FunctionsQPBClearBusyClear busy flagQPBClearInterrupt Clear the QPB interrupt flagQPBFreeSlotQPBInitSlotQPBLockSlotQPBRepeatAsyncQPBSetupQPBTestBusyQPBTestLockedQPBTransactQPBUnlockSlotRemove a PicoBUS device slotInitialize a PicoBUS device slotLock and return true if slot available for exclusive useExecute a pre-set-up asynchronous transferSet up the QPB for future asynchronous transfersSet up the QPB for future asynchronous transfersSee if the QPB is lockedConduct a PicoBUS sessionUnlock PicoBus for unrestricted useQPBClearBusy -- Clear busy flagDescription:Prototype:Inputs:Returns:Clear busy flagvoid QPBClearBusy (void);NoneNothingQPBClearInterrupt -- Clear the QPB interrupt flagDescription:Prototype:Inputs:Returns:Notes:Clear the QPB interrupt flagvoid QPBClearInterrupt (void);NoneNothingWhen operating asynchronously, the function specified by the asynchf argument to eitherQPBSetup or QPBTransact, will be called upon completion of the transaction. This function mustbe called by the handler function so that the interrupt flag that forced the execution of thecompletion routine is cleared. If the flag is not cleared, then the completion routine will beexecuted for ever.PERSISTOR<strong>Instruments</strong> <strong>Inc</strong>.45 of 84<strong>CF2</strong> <strong>API</strong> <strong>Reference</strong>7/19/2005
Change language