metaonly interface ti.catalog.msp430.peripherals.ref.IREF |
![](../../../../../Arrow_up.png) |
![](../../../../../Arrow_right.png) |
MSP430 REF Interface
metaonly interface IREF { ...
instance: ...
module-wide constants & types
};
module-wide functions
instance:
per-instance config parameters
}
typedef IREF.IPeripheralArray |
![](../../../../../Arrow_up.png) |
typedef IREF.StringArray |
![](../../../../../Arrow_up.png) |
typedef String StringArray[];
struct IREF.ForceSetDefaultRegister_t |
![](../../../../../Arrow_up.png) |
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
IREF.getAll() // module-wide |
![](../../../../../Arrow_up.png) |
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
IREF.getRegisters() // module-wide |
![](../../../../../Arrow_up.png) |
Find all registers defined by the peripheral
RETURNS
Returns an array of register names
config IREF.name // instance |
![](../../../../../Arrow_up.png) |
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 IREF.owner // instance |
![](../../../../../Arrow_up.png) |
String specifying the entity that manages the peripheral
generated on Thu, 27 Sep 2012 23:24:41 GMT