metaonly interface ti.catalog.msp430.peripherals.rtc.IRTC |
|
|
MSP430 Real-Time Clock interface
metaonly interface IRTC { ...
instance: ...
module-wide constants & types
};
};
module-wide functions
instance:
per-instance config parameters
}
typedef IRTC.IPeripheralArray |
|
typedef IRTC.StringArray |
|
typedef String StringArray[];
struct IRTC.ForceSetDefaultRegister_t |
|
Force Set Default Register
metaonly struct ForceSetDefaultRegister_t {
String register;
Bool regForceSet;
};
DETAILS
Type to store if each register needs to be forced initialized
even if the register is in default state.
SEE
struct IRTC.regIntVect_t |
|
Interrupt vector description
metaonly struct regIntVect_t {
String registerName;
String registerDescription;
String isrToggleString;
String priorityName;
Bool interruptEnable;
Bool interruptHandler;
Int priority;
};
DETAILS
Type to describe a single interrupt vector pin and all its possible
configurations.
SEE
IRTC.getAll() // module-wide |
|
Find all peripherals of a certain type
DETAILS
The type of the peripherals returned is defined by the type of the
caller.
RETURNS
Returns an array of IPeripheral instances
IRTC.getRegisters() // module-wide |
|
Find all registers defined by the peripheral
RETURNS
Returns an array of register names
config IRTC.name // instance |
|
Specific peripheral name given by the device
DETAILS
Devices can have more than one peripheral of the same type. In such
cases, device data sheets give different names to the instances of a
same peripheral. For example, the name for a timer module could be
TimerA3, and a device that has two such timers can name them TA0
and TA1.
config IRTC.owner // instance |
|
String specifying the entity that manages the peripheral
generated on Thu, 27 Sep 2012 23:24:42 GMT