module ti.sysbios.family.msp430.Hwi

MSP430 Hardware Interrupt Manager

This module implements the generic Hwi module functions Hwi_enable, Hwi_disable, and Hwi_restore as defined by IHwi. [ more ... ]
C synopsis target-domain sourced in ti/sysbios/family/msp430/Hwi.xdc
#include <ti/sysbios/family/msp430/Hwi.h>
Functions
Void
Void
Void
Void
Functions common to all IHwi modules
Void 
macro UInt 
UInt 
macro UInt 
UInt 
Bool 
Ptr 
Bool 
Void 
macro Void 
Void 
Void 
Void 
Void 
Functions common to all target instances
Functions common to all target modules
Typedefs
typedef Void 
typedef Hwi_Object *
typedef struct
typedef UArg 
typedef enum
typedef struct
typedef struct
typedef struct
typedef struct
typedef Void 
Constants
extern const Assert_Id 
extern const Bool 
extern const Bool 
extern const Bool 
extern const Bool 
extern const Error_Id 
extern const Error_Id 
extern const Log_Event 
extern const Log_Event 
extern const Int 
 
DETAILS
This module implements the generic Hwi module functions Hwi_enable, Hwi_disable, and Hwi_restore as defined by IHwi.

Calling Context

Function Hwi Swi Task Main Startup
clearInterrupt Y Y Y Y Y
create N N Y Y N
disable Y Y Y Y Y
disableInterrupt Y Y Y Y N
enable Y Y Y N N
enableInterrupt Y Y Y Y N
Params_init Y Y Y Y Y
restore Y Y Y Y Y
restoreInterrupt Y Y Y Y Y
construct N N Y Y N
delete N N Y Y N
destruct N N Y Y N
getHookContext Y Y Y Y N
setFunc Y Y Y Y N
setHookContext Y Y Y Y N
Definitions:
  • Hwi: API is callable from a Hwi thread.
  • Swi: API is callable from a Swi thread.
  • Task: API is callable from a Task thread.
  • Main: API is callable during any of these phases:
    • In your module startup after this module is started (e.g. Hwi_Module_startupDone() returns TRUE).
    • During xdc.runtime.Startup.lastFxns.
    • During main().
    • During BIOS.startupFxns.
  • Startup: API is callable during any of these phases:
    • During xdc.runtime.Startup.firstFxns.
    • In your module startup before this module is started (e.g. Hwi_Module_startupDone() returns FALSE).
 
enum Hwi_MaskingOption

Shorthand interrupt masking options

C synopsis target-domain
typedef enum Hwi_MaskingOption {
    Hwi_MaskingOption_NONE,
    Hwi_MaskingOption_ALL,
    Hwi_MaskingOption_SELF,
    Hwi_MaskingOption_BITMASK,
    Hwi_MaskingOption_LOWER
} Hwi_MaskingOption;
 
VALUES
MaskingOption_NONE — No interrupts are disabled
MaskingOption_ALL — All interrupts are disabled
MaskingOption_SELF — Only this interrupt is disabled
MaskingOption_BITMASK — User supplies interrupt enable masks
MaskingOption_LOWER — All current and lower priority interrupts are disabled.
Only a few targets/devices truly support this masking option. For those that don't, this setting is treated the same as MaskingOption_SELF.
 
typedef Hwi_FuncPtr

Hwi create function type definition

C synopsis target-domain
typedef Void (*Hwi_FuncPtr)(UArg);
 
 
typedef Hwi_Irp

Interrupt Return Pointer

C synopsis target-domain
typedef UArg Hwi_Irp;
 
DETAILS
This is the address of the interrupted instruction.
 
typedef Hwi_VectorFuncPtr

Hwi vector function type definition

C synopsis target-domain
typedef Void (*Hwi_VectorFuncPtr)(Void);
 
 
struct Hwi_HookSet

Hwi hook set type definition

C synopsis target-domain
typedef struct Hwi_HookSet {
    Void (*registerFxn)(Int);
    Void (*createFxn)(IHwi_Handle,Error_Block*);
    Void (*beginFxn)(IHwi_Handle);
    Void (*endFxn)(IHwi_Handle);
    Void (*deleteFxn)(IHwi_Handle);
} Hwi_HookSet;
 
DETAILS
The functions that make up a hookSet have certain restrictions. They cannot call any Hwi instance functions other than Hwi_getHookContext() and Hwi_setHookContext(). For all practical purposes, they should treat the Hwi_Handle passed to these functions as an opaque handle.
 
struct Hwi_StackInfo

Structure contains Hwi stack usage info

C synopsis target-domain
typedef struct Hwi_StackInfo {
    SizeT hwiStackPeak;
    SizeT hwiStackSize;
    Ptr hwiStackBase;
} Hwi_StackInfo;
 
DETAILS
Used by getStackInfo() and viewGetStackInfo() functions
 
config Hwi_NUM_INTERRUPTS  // module-wide

The MSP430 supports up to 64 interrupts/exceptions

C synopsis target-domain
extern const Int Hwi_NUM_INTERRUPTS;
 
DETAILS
The actual number supported is device specific and provided by the catalog device specification.
 
config Hwi_A_unsupportedMaskingOption  // module-wide

Assert when bad maskSetting parameter provided

C synopsis target-domain
extern const Assert_Id Hwi_A_unsupportedMaskingOption;
 
 
config Hwi_E_alreadyDefined  // module-wide

Error raised when Hwi is already defined

C synopsis target-domain
extern const Error_Id Hwi_E_alreadyDefined;
 
 
config Hwi_E_notImplemented  // module-wide

Error raised when an unimplemented Hwi function is called

C synopsis target-domain
extern const Error_Id Hwi_E_notImplemented;
 
DETAILS
The MSP430 does not implement all of the functions defined by ti.sysbios.interfaces.IHwi. If applications call such a function, an E_notImplemented error is raised with the name of the unimplemented function passed as an argument. See xdc.runtime.Error.raise.
 
config Hwi_LD_end  // module-wide

Issued just after return from Hwi function (with interrupts disabled)

C synopsis target-domain
extern const Log_Event Hwi_LD_end;
 
 
config Hwi_LM_begin  // module-wide

Issued just prior to Hwi function invocation (with interrupts disabled)

C synopsis target-domain
extern const Log_Event Hwi_LM_begin;
 
 
config Hwi_dispatcherAutoNestingSupport  // module-wide

Include interrupt nesting logic in interrupt dispatcher?

C synopsis target-domain
extern const Bool Hwi_dispatcherAutoNestingSupport;
 
DETAILS
Default is true.
This option provides the user with the ability to optimize interrupt dispatcher performance when support for interrupt nesting is not required.
Setting this parameter to false will disable the logic in the interrupt dispatcher that manipulates interrupt mask registers and enables and disables interrupts before and after invoking the user's Hwi function.
Set this parameter to false if you don't need interrupts enabled during the execution of your Hwi functions.
 
config Hwi_dispatcherIrpTrackingSupport  // module-wide

Controls whether the dispatcher retains the interrupted thread's return address

C synopsis target-domain
extern const Bool Hwi_dispatcherIrpTrackingSupport;
 
DETAILS
This option is enabled by default.
Setting this parameter to false will disable the logic in the interrupt dispatcher that keeps track of the interrupt's return address and provide a small savings in interrupt latency.
The application can get an interrupt's most recent return address using the getIrp API.
 
config Hwi_dispatcherSwiSupport  // module-wide

Include Swi scheduling logic in interrupt dispatcher?

C synopsis target-domain
extern const Bool Hwi_dispatcherSwiSupport;
 
DETAILS
Default is inherited from BIOS.swiEnabled, which is true by default.
This option provides the user with the ability to optimize interrupt dispatcher performance when it is known that Swis will not be posted from any of their Hwi threads.
WARNING
Setting this parameter to false will disable the logic in the interrupt dispatcher that invokes the Swi scheduler prior to returning from an interrupt. With this setting, Swis MUST NOT be posted from Hwi functions!
 
config Hwi_dispatcherTaskSupport  // module-wide

Include Task scheduling logic in interrupt dispatcher?

C synopsis target-domain
extern const Bool Hwi_dispatcherTaskSupport;
 
DETAILS
Default is inherited from BIOS.taskEnabled, which is true by default.
This option provides the user with the ability to optimize interrupt dispatcher performance when it is known that no Task scheduling APIs (ie Semaphore_post()) will be executed from any of their Hwi threads.
Setting this parameter to false will disable the logic in the interrupt dispatcher that invokes the Task scheduler prior to returning from an interrupt.
 
Hwi_clearInterrupt()  // module-wide

Clear a specific interrupt

C synopsis target-domain
Void Hwi_clearInterrupt(UInt intNum);
 
ARGUMENTS
intNum — interrupt number to clear
DETAILS
Clears a specific interrupt's pending status. The implementation is family-specific.
 
Hwi_disable()  // module-wide

Globally disable interrupts

C synopsis target-domain
macro UInt Hwi_disable();
 
RETURNS
opaque key for use by Hwi_restore()
DETAILS
Hwi_disable globally disables hardware interrupts and returns an opaque key indicating whether interrupts were globally enabled or disabled on entry to Hwi_disable(). The actual value of the key is target/device specific and is meant to be passed to Hwi_restore().
Call Hwi_disable before a portion of a function that needs to run without interruption. When critical processing is complete, call Hwi_restore or Hwi_enable to reenable hardware interrupts.
Servicing of interrupts that occur while interrupts are disabled is postponed until interrupts are reenabled. However, if the same type of interrupt occurs several times while interrupts are disabled, the interrupt's function is executed only once when interrupts are reenabled.
A context switch can occur when calling Hwi_enable or Hwi_restore if an enabled interrupt occurred while interrupts are disabled.
Hwi_disable may be called from main(). However, since Hwi interrupts are already disabled in main(), such a call has no effect.
CONSTRAINTS
If a Task switching API such as Semaphore_pend(), Semaphore_post(), Task_sleep(), or Task_yield() is invoked which results in a context switch while interrupts are disabled, an embedded call to Hwi_enable occurs on the way to the new thread context which unconditionally re-enables interrupts. Interrupts will remain enabled until a subsequent Hwi_disable invocation.
Swis always run with interrupts enabled. See Swi_post() for a discussion Swis and interrupts.
 
Hwi_disableInterrupt()  // module-wide

Disable a specific interrupt

C synopsis target-domain
UInt Hwi_disableInterrupt(UInt intNum);
 
ARGUMENTS
intNum — interrupt number to disable
RETURNS
key to restore previous enable/disable state
DETAILS
Disable a specific interrupt identified by an interrupt number.
 
Hwi_enable()  // module-wide

Globally enable interrupts

C synopsis target-domain
macro UInt Hwi_enable();
 
RETURNS
opaque key for use by Hwi_restore()
DETAILS
Hwi_enable globally enables hardware interrupts and returns an opaque key indicating whether interrupts were globally enabled or disabled on entry to Hwi_enable(). The actual value of the key is target/device specific and is meant to be passed to Hwi_restore().
This function is called as part of SYS/BIOS Startup_POST_APP_MAIN phase.
Hardware interrupts are enabled unless a call to Hwi_disable disables them.
Servicing of interrupts that occur while interrupts are disabled is postponed until interrupts are reenabled. However, if the same type of interrupt occurs several times while interrupts are disabled, the interrupt's function is executed only once when interrupts are reenabled.
A context switch can occur when calling Hwi_enable or Hwi_restore if an enabled interrupt occurred while interrupts are disabled.
Any call to Hwi_enable enables interrupts, even if Hwi_disable has been called several times.
Hwi_enable must not be called from main().
 
Hwi_enableInterrupt()  // module-wide

Enable a specific interrupt

C synopsis target-domain
UInt Hwi_enableInterrupt(UInt intNum);
 
ARGUMENTS
intNum — interrupt number to enable
RETURNS
key to restore previous enable/disable state
DETAILS
Enables a specific interrupt identified by an interrupt number.
 
Hwi_getCoreStackInfo()  // module-wide

Get Hwi stack usage Info for the specified coreId

C synopsis target-domain
Bool Hwi_getCoreStackInfo(IHwi_StackInfo *stkInfo, Bool computeStackDepth, UInt coreId);
 
ARGUMENTS
stkInfo — pointer to structure of type StackInfo
computeStackDepth — decides whether to compute stack depth
coreId — core whose stack info needs to be retrieved
RETURNS
boolean to indicate a stack overflow
DETAILS
getCoreStackInfo returns the Hwi stack usage info for the specified coreId to its calling function by filling stack base address, stack size and stack peak fields in the StackInfo structure.
This function should be used only in applications built with ti.sysbios.BIOS.smpEnabled set to true.
getCoreStackInfo accepts three arguments, a pointer to a structure of type StackInfo, a boolean and a coreId. If the boolean is set to true, the function computes the stack depth and fills the stack peak field in the StackInfo structure. If a stack overflow is detected, the stack depth is not computed. If the boolean is set to false, the function only checks for a stack overflow.
The isr stack is always checked for an overflow and a boolean is returned to indicate whether an overflow occured.
Below is an example of calling getCoreStackInfo() API:
  #include <ti/sysbios/BIOS.h>
  #include <ti/sysbios/hal/Hwi.h>
  #include <ti/sysbios/hal/Core.h>
  #include <ti/sysbios/knl/Task.h>

  ...

  Void idleTask()
  {
      UInt idx;
      Hwi_StackInfo stkInfo;
      Bool stackOverflow = FALSE;

      // Request stack depth for each core's Hwi stack and check for
      // overflow
      for (idx = 0; idx < Core_numCores; idx++) {
          stackOverflow = Hwi_getCoreStackInfo(&stkInfo, TRUE, idx);

          // Alternately, we can omit the request for stack depth and
          // request only the stack base and stack size (the check for
          // stack overflow is always performed):
          //
          // stackOverflow = Hwi_getCoreStackInfo(&stkInfo, FALSE, idx);

          if (stackOverflow) {
              // isr Stack Overflow detected
          }
      }
  }

  Int main(Int argc, char* argv[])
  {
      ...
      BIOS_start();
      return (0);
  }
 
Hwi_getStackInfo()  // module-wide

Get Hwi stack usage Info

C synopsis target-domain
Bool Hwi_getStackInfo(IHwi_StackInfo *stkInfo, Bool computeStackDepth);
 
ARGUMENTS
stkInfo — pointer to structure of type StackInfo
computeStackDepth — decides whether to compute stack depth
RETURNS
boolean to indicate a stack overflow
DETAILS
getStackInfo returns the Hwi stack usage info to its calling function by filling stack base address, stack size and stack peak fields in the StackInfo structure.
getStackInfo accepts two arguments, a pointer to a structure of type StackInfo and a boolean. If the boolean is set to true, the function computes the stack depth and fills the stack peak field in the StackInfo structure. If a stack overflow is detected, the stack depth is not computed. If the boolean is set to false, the function only checks for a stack overflow.
The isr stack is always checked for an overflow and a boolean is returned to indicate whether an overflow occured.
Below is an example of calling getStackInfo() API:
  #include <ti/sysbios/BIOS.h>
  #include <ti/sysbios/hal/Hwi.h>
  #include <ti/sysbios/knl/Swi.h>
  #include <ti/sysbios/knl/Task.h>

  Swi_Handle swi0;
  volatile Bool swiStackOverflow = FALSE;

  Void swi0Fxn(UArg arg1, UArg arg2)
  {
      Hwi_StackInfo stkInfo;

      // Request stack depth
      swiStackOverflow = Hwi_getStackInfo(&stkInfo, TRUE);
 
      // Alternately, we can omit the request for stack depth and 
      // request only the stack base and stack size (the check for
      // stack overflow is always performed):
      //
      // swiStackOverflow = Hwi_getStackInfo(&stkInfo, FALSE);

      if (swiStackOverflow) {
          // isr Stack Overflow detected
      }
  }

  Void idleTask()
  {
      Swi_post(swi0);
  }

  Int main(Int argc, char* argv[])
  {
      swi0 = Swi_create(swi0Fxn, NULL, NULL);

      BIOS_start();
      return (0);
  }
 
Hwi_post()  // module-wide

Generate an interrupt for test purposes

C synopsis target-domain
Void Hwi_post(UInt intNum);
 
ARGUMENTS
intNum — ID of interrupt to generate
 
Hwi_restore()  // module-wide

Globally restore interrupts

C synopsis target-domain
macro Void Hwi_restore(UInt key);
 
ARGUMENTS
key — enable/disable state to restore
DETAILS
Hwi_restore globally restores interrupts to the state determined by the key argument provided by a previous invocation of Hwi_disable.
A context switch may occur when calling Hwi_restore if Hwi_restore reenables interrupts and another Hwi occurred while interrupts were disabled.
Hwi_restore may be called from main(). However, since Hwi_enable cannot be called from main(), interrupts are always disabled in main(), and a call to Hwi_restore has no effect.
 
Hwi_restoreInterrupt()  // module-wide

Restore a specific interrupt's enabled/disabled state

C synopsis target-domain
Void Hwi_restoreInterrupt(UInt intNum, UInt key);
 
ARGUMENTS
intNum — interrupt number to restore
key — key returned from enableInt or disableInt
DETAILS
Restores a specific interrupt identified by an interrupt number. restoreInterrupt is generally used to restore an interrupt to its state before disableInterrupt or enableInterrupt was invoked
 
Hwi_startup()  // module-wide

Initially enable interrupts

C synopsis target-domain
Void Hwi_startup();
 
DETAILS
Called within BIOS_start
Module-Wide Built-Ins

C synopsis target-domain
Types_ModuleId Hwi_Module_id();
// Get this module's unique id
 
Bool Hwi_Module_startupDone();
// Test if this module has completed startup
 
IHeap_Handle Hwi_Module_heap();
// The heap from which this module allocates memory
 
Bool Hwi_Module_hasMask();
// Test whether this module has a diagnostics mask
 
Bits16 Hwi_Module_getMask();
// Returns the diagnostics mask for this module
 
Void Hwi_Module_setMask(Bits16 mask);
// Set the diagnostics mask for this module
Instance Object Types

C synopsis target-domain
typedef struct Hwi_Object Hwi_Object;
// Opaque internal representation of an instance object
 
typedef Hwi_Object *Hwi_Handle;
// Client reference to an instance object
 
typedef struct Hwi_Struct Hwi_Struct;
// Opaque client structure large enough to hold an instance object
 
Hwi_Handle Hwi_handle(Hwi_Struct *structP);
// Convert this instance structure pointer into an instance handle
 
Hwi_Struct *Hwi_struct(Hwi_Handle handle);
// Convert this instance handle into an instance structure pointer
Instance Config Parameters

C synopsis target-domain
typedef struct Hwi_Params {
// Instance config-params structure
    IInstance_Params *instance;
    // Common per-instance configs
    UArg arg;
    // ISR function argument. Default is 0
    Bool enableInt;
    // Enable this interrupt when object is created? Default is true
    Int eventId;
    // Interrupt event ID (Interrupt Selection Number)
    IHwi_MaskingOption maskSetting;
    // override maskSetting - Hwi does not manage nesting on 430
    Int priority;
    // Interrupt priority
} Hwi_Params;
 
Void Hwi_Params_init(Hwi_Params *params);
// Initialize this config-params structure with supplier-specified defaults before instance creation
 
config Hwi_Params.arg  // instance

ISR function argument. Default is 0

C synopsis target-domain
struct Hwi_Params {
      ...
    UArg arg;
 
 
config Hwi_Params.enableInt  // instance

Enable this interrupt when object is created? Default is true

C synopsis target-domain
struct Hwi_Params {
      ...
    Bool enableInt;
 
 
config Hwi_Params.eventId  // instance

Interrupt event ID (Interrupt Selection Number)

C synopsis target-domain
struct Hwi_Params {
      ...
    Int eventId;
 
DETAILS
Default is -1. Not all targets/devices support this instance parameter. On those that don't, this parameter is ignored.
 
config Hwi_Params.maskSetting  // instance

override maskSetting - Hwi does not manage nesting on 430

C synopsis target-domain
struct Hwi_Params {
      ...
    IHwi_MaskingOption maskSetting;
 
 
config Hwi_Params.priority  // instance

Interrupt priority

C synopsis target-domain
struct Hwi_Params {
      ...
    Int priority;
 
DETAILS
The default value of -1 is used as a flag to indicate the lowest (logical) device-specific priority value.
Not all targets/devices support this instance parameter. On those that don't, this parameter is ignored.
Runtime Instance Creation

C synopsis target-domain
Hwi_Handle Hwi_create(Int intNum, IHwi_FuncPtr hwiFxn, const Hwi_Params *params, Error_Block *eb);
// Allocate and initialize a new instance object and return its handle
 
Void Hwi_construct(Hwi_Struct *structP, Int intNum, IHwi_FuncPtr hwiFxn, const Hwi_Params *params, Error_Block *eb);
// Initialize a new instance object inside the provided structure
ARGUMENTS
intNum — interrupt number
hwiFxn — pointer to ISR function
params — per-instance config params, or NULL to select default values (target-domain only)
eb — active error-handling block, or NULL to select default policy (target-domain only)
DETAILS
A Hwi dispatcher table entry is created and filled with the function specified by the fxn parameter and the attributes specified by the params parameter.
If params is NULL, the Hwi's dispatcher properties are assigned a default set of values. Otherwise, the following properties are specified by a structure of type Hwi_Params.
  • The arg element is a generic argument that is passed to the plugged function as its only parameter. The default value is 0.
  • The enableInt element determines whether the interrupt should be enabled in the IER by create.
  • The maskSetting element defines the dispatcherAutoNestingSupport behavior of the interrupt.
Hwi_create returns a pointer to the created Hwi object.
Instance Deletion

C synopsis target-domain
Void Hwi_delete(Hwi_Handle *handleP);
// Finalize and free this previously allocated instance object, setting the referenced handle to NULL
 
Void Hwi_destruct(Hwi_Struct *structP);
// Finalize the instance object inside the provided structure
 
Hwi_getFunc()  // instance

Get Hwi function and arg

C synopsis target-domain
IHwi_FuncPtr Hwi_getFunc(Hwi_Handle handle, UArg *arg);
 
ARGUMENTS
handle — handle of a previously-created Hwi instance object
arg — pointer for returning hwi's ISR function argument
RETURNS
hwi's ISR function
 
Hwi_getHookContext()  // instance

Get hook instance's context for a Hwi

C synopsis target-domain
Ptr Hwi_getHookContext(Hwi_Handle handle, Int id);
 
ARGUMENTS
handle — handle of a previously-created Hwi instance object
RETURNS
hook instance's context for hwi
 
Hwi_getIrp()  // instance

Get address of interrupted instruction

C synopsis target-domain
IHwi_Irp Hwi_getIrp(Hwi_Handle handle);
 
ARGUMENTS
handle — handle of a previously-created Hwi instance object
RETURNS
most current IRP of a Hwi
 
Hwi_setFunc()  // instance

Overwrite Hwi function and arg

C synopsis target-domain
Void Hwi_setFunc(Hwi_Handle handle, IHwi_FuncPtr fxn, UArg arg);
 
ARGUMENTS
handle — handle of a previously-created Hwi instance object
fxn — pointer to ISR function
arg — argument to ISR function
DETAILS
Replaces a Hwi object's hwiFxn function originally provided in create.
 
Hwi_setHookContext()  // instance

Set hook instance's context for a Hwi

C synopsis target-domain
Void Hwi_setHookContext(Hwi_Handle handle, Int id, Ptr hookContext);
 
ARGUMENTS
handle — handle of a previously-created Hwi instance object
id — hook instance's ID
hookContext — value to write to context
Instance Convertors

C synopsis target-domain
IHwi_Handle Hwi_Handle_upCast(Hwi_Handle handle);
// unconditionally move one level up the inheritance hierarchy
 
Hwi_Handle Hwi_Handle_downCast(IHwi_Handle handle);
// conditionally move one level down the inheritance hierarchy; NULL upon failure
Instance Built-Ins

C synopsis target-domain
Int Hwi_Object_count();
// The number of statically-created instance objects
 
Hwi_Handle Hwi_Object_get(Hwi_Object *array, Int i);
// The handle of the i-th statically-created instance object (array == NULL)
 
Hwi_Handle Hwi_Object_first();
// The handle of the first dynamically-created instance object, or NULL
 
Hwi_Handle Hwi_Object_next(Hwi_Handle handle);
// The handle of the next dynamically-created instance object, or NULL
 
IHeap_Handle Hwi_Object_heap();
// The heap used to allocate dynamically-created instance objects
 
Types_Label *Hwi_Handle_label(Hwi_Handle handle, Types_Label *buf);
// The label associated with this instance object
 
String Hwi_Handle_name(Hwi_Handle handle);
// The name of this instance object
 
Configuration settings sourced in ti/sysbios/family/msp430/Hwi.xdc
var Hwi = xdc.useModule('ti.sysbios.family.msp430.Hwi');
module-wide constants & types
        const Hwi.MaskingOption_NONE;
        const Hwi.MaskingOption_ALL;
        const Hwi.MaskingOption_SELF;
        const Hwi.MaskingOption_BITMASK;
        const Hwi.MaskingOption_LOWER;
 
        obj.registerFxn = Void(*)(Int)  ...
        obj.createFxn = Void(*)(IHwi.Handle,Error.Block*)  ...
        obj.beginFxn = Void(*)(IHwi.Handle)  ...
        obj.endFxn = Void(*)(IHwi.Handle)  ...
        obj.deleteFxn = Void(*)(IHwi.Handle)  ...
 
        obj.hwiStackPeak = SizeT  ...
        obj.hwiStackSize = SizeT  ...
        obj.hwiStackBase = Ptr  ...
module-wide config parameters
 
        msg: "A_unsupportedMaskingOption: unsupported maskSetting."
    };
        msg: "E_alreadyDefined: Hwi already defined: intr# %d"
    };
        msg: "E_notImplemented: Function not implemented: %s"
    };
        mask: Diags.USER2,
        msg: "LD_end: hwi: 0x%x"
    };
        mask: Diags.USER1 | Diags.USER2,
        msg: "LM_begin: hwi: 0x%x, func: 0x%x, preThread: %d, intNum: %d, irp: 0x%x"
    };
 
    Hwi.resetFunc// Reset handler = Void(*)(Void) undefined;
module-wide functions
per-instance config parameters
    var params = new Hwi.Params// Instance config-params object;
        params.arg// ISR function argument. Default is 0 = UArg 0;
        params.loggingEnabled// Does this interrupt support logging? = Bool false;
        params.priority// Interrupt priority = Int -1;
per-instance creation
    var inst = Hwi.create// Create an instance-object(Int intNum, Void(*)(UArg) hwiFxn, params);
 
 
enum Hwi.MaskingOption

Shorthand interrupt masking options

Configuration settings
values of type Hwi.MaskingOption
    const Hwi.MaskingOption_NONE;
    const Hwi.MaskingOption_ALL;
    const Hwi.MaskingOption_SELF;
    const Hwi.MaskingOption_BITMASK;
    const Hwi.MaskingOption_LOWER;
 
VALUES
MaskingOption_NONE — No interrupts are disabled
MaskingOption_ALL — All interrupts are disabled
MaskingOption_SELF — Only this interrupt is disabled
MaskingOption_BITMASK — User supplies interrupt enable masks
MaskingOption_LOWER — All current and lower priority interrupts are disabled.
Only a few targets/devices truly support this masking option. For those that don't, this setting is treated the same as MaskingOption_SELF.
C SYNOPSIS
 
struct Hwi.HookSet

Hwi hook set type definition

Configuration settings
var obj = new Hwi.HookSet;
 
    obj.registerFxn = Void(*)(Int)  ...
    obj.createFxn = Void(*)(IHwi.Handle,Error.Block*)  ...
    obj.beginFxn = Void(*)(IHwi.Handle)  ...
    obj.endFxn = Void(*)(IHwi.Handle)  ...
    obj.deleteFxn = Void(*)(IHwi.Handle)  ...
 
DETAILS
The functions that make up a hookSet have certain restrictions. They cannot call any Hwi instance functions other than Hwi_getHookContext() and Hwi_setHookContext(). For all practical purposes, they should treat the Hwi_Handle passed to these functions as an opaque handle.
C SYNOPSIS
 
struct Hwi.StackInfo

Structure contains Hwi stack usage info

Configuration settings
var obj = new Hwi.StackInfo;
 
    obj.hwiStackPeak = SizeT  ...
    obj.hwiStackSize = SizeT  ...
    obj.hwiStackBase = Ptr  ...
 
DETAILS
Used by getStackInfo() and viewGetStackInfo() functions
C SYNOPSIS
 
config Hwi.NUM_INTERRUPTS  // module-wide

The MSP430 supports up to 64 interrupts/exceptions

Configuration settings
const Hwi.NUM_INTERRUPTS = Int computed value;
 
DETAILS
The actual number supported is device specific and provided by the catalog device specification.
C SYNOPSIS
 
config Hwi.A_unsupportedMaskingOption  // module-wide

Assert when bad maskSetting parameter provided

Configuration settings
Hwi.A_unsupportedMaskingOption = Assert.Desc {
    msg: "A_unsupportedMaskingOption: unsupported maskSetting."
};
 
C SYNOPSIS
 
config Hwi.E_alreadyDefined  // module-wide

Error raised when Hwi is already defined

Configuration settings
Hwi.E_alreadyDefined = Error.Desc {
    msg: "E_alreadyDefined: Hwi already defined: intr# %d"
};
 
C SYNOPSIS
 
config Hwi.E_notImplemented  // module-wide

Error raised when an unimplemented Hwi function is called

Configuration settings
Hwi.E_notImplemented = Error.Desc {
    msg: "E_notImplemented: Function not implemented: %s"
};
 
DETAILS
The MSP430 does not implement all of the functions defined by ti.sysbios.interfaces.IHwi. If applications call such a function, an E_notImplemented error is raised with the name of the unimplemented function passed as an argument. See xdc.runtime.Error.raise.
C SYNOPSIS
 
config Hwi.LD_end  // module-wide

Issued just after return from Hwi function (with interrupts disabled)

Configuration settings
Hwi.LD_end = Log.EventDesc {
    mask: Diags.USER2,
    msg: "LD_end: hwi: 0x%x"
};
 
C SYNOPSIS
 
config Hwi.LM_begin  // module-wide

Issued just prior to Hwi function invocation (with interrupts disabled)

Configuration settings
Hwi.LM_begin = Log.EventDesc {
    mask: Diags.USER1 | Diags.USER2,
    msg: "LM_begin: hwi: 0x%x, func: 0x%x, preThread: %d, intNum: %d, irp: 0x%x"
};
 
C SYNOPSIS
 
config Hwi.dispatcherAutoNestingSupport  // module-wide

Include interrupt nesting logic in interrupt dispatcher?

Configuration settings
Hwi.dispatcherAutoNestingSupport = Bool true;
 
DETAILS
Default is true.
This option provides the user with the ability to optimize interrupt dispatcher performance when support for interrupt nesting is not required.
Setting this parameter to false will disable the logic in the interrupt dispatcher that manipulates interrupt mask registers and enables and disables interrupts before and after invoking the user's Hwi function.
Set this parameter to false if you don't need interrupts enabled during the execution of your Hwi functions.
C SYNOPSIS
 
config Hwi.dispatcherIrpTrackingSupport  // module-wide

Controls whether the dispatcher retains the interrupted thread's return address

Configuration settings
Hwi.dispatcherIrpTrackingSupport = Bool true;
 
DETAILS
This option is enabled by default.
Setting this parameter to false will disable the logic in the interrupt dispatcher that keeps track of the interrupt's return address and provide a small savings in interrupt latency.
The application can get an interrupt's most recent return address using the getIrp API.
C SYNOPSIS
 
config Hwi.dispatcherSwiSupport  // module-wide

Include Swi scheduling logic in interrupt dispatcher?

Configuration settings
Hwi.dispatcherSwiSupport = Bool undefined;
 
DETAILS
Default is inherited from BIOS.swiEnabled, which is true by default.
This option provides the user with the ability to optimize interrupt dispatcher performance when it is known that Swis will not be posted from any of their Hwi threads.
WARNING
Setting this parameter to false will disable the logic in the interrupt dispatcher that invokes the Swi scheduler prior to returning from an interrupt. With this setting, Swis MUST NOT be posted from Hwi functions!
C SYNOPSIS
 
config Hwi.dispatcherTaskSupport  // module-wide

Include Task scheduling logic in interrupt dispatcher?

Configuration settings
Hwi.dispatcherTaskSupport = Bool undefined;
 
DETAILS
Default is inherited from BIOS.taskEnabled, which is true by default.
This option provides the user with the ability to optimize interrupt dispatcher performance when it is known that no Task scheduling APIs (ie Semaphore_post()) will be executed from any of their Hwi threads.
Setting this parameter to false will disable the logic in the interrupt dispatcher that invokes the Task scheduler prior to returning from an interrupt.
C SYNOPSIS
 
metaonly config Hwi.alwaysLog  // module-wide

Always emit Log messages from interrupt stubs?

Configuration settings
Hwi.alwaysLog = Bool false;
 
DETAILS
This parameter serves as a global 'switch' to control whether Log begin and end messages will be emitted from interrupt stubs. Note that the behavior of each interrupt instance can be controlled individually (see loggingEnabled); when set to true, alwaysLog serves as an override of the individual instance selections, forcing logging from the stubs of all configured interrupts.
 
metaonly config Hwi.alwaysWake  // module-wide

Always keep the CPU awake upon return from interrupt?

Configuration settings
Hwi.alwaysWake = Bool false;
 
DETAILS
This parameter serves as a global 'switch' to control whether the CPU is kept awake (i.e., not allowed to return to a low power mode) at the end of servicing a hardware interrupt (Hwi) managed by SYS/BIOS. The behavior of each interrupt instance can be controlled individually (see keepAwakeEnabled); when set to true, this parameter serves as an override of the individual instance selection, to force keep awake of the CPU. This parameter is provided to assist with debug, and to ease use and transition of legacy code to work with SYS/BIOS.
 
metaonly config Hwi.common$  // module-wide

Common module configuration parameters

Configuration settings
Hwi.common$ = Types.Common$ undefined;
 
DETAILS
All modules have this configuration parameter. Its name contains the '$' character to ensure it does not conflict with configuration parameters declared by the module. This allows new configuration parameters to be added in the future without any chance of breaking existing modules.
 
metaonly config Hwi.fillVectors  // module-wide

Plug all unused interrupt vectors

Configuration settings
Hwi.fillVectors = Bool true;
 
DETAILS
This parameter allows one to plug all unused interrupt vectors with a spin loop, to catch unexpected interrupts and "run away" code.
 
metaonly config Hwi.resetFunc  // module-wide

Reset handler

Configuration settings
Hwi.resetFunc = Void(*)(Void) undefined;
 
DETAILS
This parameter specifies the interrupt service routine triggered on reset. The default is c_int00.
 
metaonly Hwi.addHookSet()  // module-wide

addHookSet is used in a config file to add a hook set (defined by struct HookSet)

Configuration settings
Hwi.addHookSet(IHwi.HookSet hook) returns Void
 
ARGUMENTS
hook — structure of type HookSet
DETAILS
HookSet structure elements may be omitted, in which case those elements will not exist.
 
metaonly Hwi.plugMeta()  // module-wide

Statically plug an interrupt vector with an ISR address

Configuration settings
Hwi.plugMeta(UInt intNum, Fxn fxn) returns Void
 
ARGUMENTS
intNum — interrupt number
fxn — pointer to ISR function
Instance Config Parameters

Configuration settings
var params = new Hwi.Params;
// Instance config-params object
    params.arg = UArg 0;
    // ISR function argument. Default is 0
    params.enableInt = Bool true;
    // Enable this interrupt when object is created? Default is true
    params.eventId = Int -1;
    // Interrupt event ID (Interrupt Selection Number)
    params.isrStackEnabled = Bool true;
    // Switch to ISR stack for this interrupt? Default is true
    params.keepAwakeEnabled = Bool false;
    // Should keep CPU awake following this interrupt? Default is false
    params.loggingEnabled = Bool false;
    // Does this interrupt support logging?
    params.maskSetting = IHwi.MaskingOption IHwi.MaskingOption_ALL;
    // override maskSetting - Hwi does not manage nesting on 430
    params.nestingEnabled = Bool false;
    // Does this interrupt allow nesting by other interrupts? Default is false
    params.priority = Int -1;
    // Interrupt priority
    params.swiEnabled = Bool true;
    // Does this interrupt support posting of Swis? Default is true
    params.taskEnabled = Bool true;
    // Does this interrupt support task pre-emption? Default is true
    params.threadTypeEnabled = Bool true;
    // Does this interrupt support thread-type tracking? Default is true
 
config Hwi.Params.arg  // instance

ISR function argument. Default is 0

Configuration settings
var params = new Hwi.Params;
  ...
params.arg = UArg 0;
 
C SYNOPSIS
 
config Hwi.Params.enableInt  // instance

Enable this interrupt when object is created? Default is true

Configuration settings
var params = new Hwi.Params;
  ...
params.enableInt = Bool true;
 
C SYNOPSIS
 
config Hwi.Params.eventId  // instance

Interrupt event ID (Interrupt Selection Number)

Configuration settings
var params = new Hwi.Params;
  ...
params.eventId = Int -1;
 
DETAILS
Default is -1. Not all targets/devices support this instance parameter. On those that don't, this parameter is ignored.
C SYNOPSIS
 
config Hwi.Params.maskSetting  // instance

override maskSetting - Hwi does not manage nesting on 430

Configuration settings
var params = new Hwi.Params;
  ...
 
C SYNOPSIS
 
config Hwi.Params.priority  // instance

Interrupt priority

Configuration settings
var params = new Hwi.Params;
  ...
params.priority = Int -1;
 
DETAILS
The default value of -1 is used as a flag to indicate the lowest (logical) device-specific priority value.
Not all targets/devices support this instance parameter. On those that don't, this parameter is ignored.
C SYNOPSIS
 
metaonly config Hwi.Params.isrStackEnabled  // instance

Switch to ISR stack for this interrupt? Default is true

Configuration settings
var params = new Hwi.Params;
  ...
params.isrStackEnabled = Bool true;
 
DETAILS
If "true", the SYS/BIOS interrupt/system stack will be used when running this interrupt's ISR function (instead of the interrupted Task's dedicated stack). If "false", no switching to the interrupt/system stack will occur for this interrupt.
Note that this parameter is only relevant for the Task module; if the Task module is not enabled in the application only a single stack is used (i.e., the "system/interrupt stack").
 
metaonly config Hwi.Params.keepAwakeEnabled  // instance

Should keep CPU awake following this interrupt? Default is false

Configuration settings
var params = new Hwi.Params;
  ...
params.keepAwakeEnabled = Bool false;
 
DETAILS
If "true", this interrupt stub will modify the status register (SR) value that was pushed onto the stack (automatically, at the start of servicing the interrupt), so that when it is restored by the RETI instruction, the CPU will stay in the Active mode.
If left as "false", the unmodified SR value will be restored by the RETI instruction, and the CPU may return to a previous low power mode (LPM) that was in effect when the interrupt was triggered.
 
metaonly config Hwi.Params.loggingEnabled  // instance

Does this interrupt support logging?

Configuration settings
var params = new Hwi.Params;
  ...
params.loggingEnabled = Bool false;
 
DETAILS
If set to true, Log statements are inserted into the generated interrupt stub that calls the user's interrupt function. The stub posts an LM_begin event at the beginning of the interrupt service routine and a LD_end event after the user's function returns.
In addition to enabling this flag, you must also enable USER1 and/or USER2 logging for this module. Otherwise, the events posted by the inserted Log statments will be ignored.
 
metaonly config Hwi.Params.nestingEnabled  // instance

Does this interrupt allow nesting by other interrupts? Default is false

Configuration settings
var params = new Hwi.Params;
  ...
params.nestingEnabled = Bool false;
 
DETAILS
Set to "true" if the configured ISR function will enable global interrupts temporarily within the function, to allow other interrupts to nest on top of this interrupt. If the ISR does not enable other interrupts, then leave as the default of "false".
 
metaonly config Hwi.Params.swiEnabled  // instance

Does this interrupt support posting of Swis? Default is true

Configuration settings
var params = new Hwi.Params;
  ...
params.swiEnabled = Bool true;
 
DETAILS
If "true", the interrupt stub will disable the Swi scheduler upon stub entry, and restore it upon interrupt completion.
If no Swi-scheduling APIs (for example, Swi_post()) are called from within this interrupt's ISR function, then swiEnabled can be set to "false".
 
metaonly config Hwi.Params.taskEnabled  // instance

Does this interrupt support task pre-emption? Default is true

Configuration settings
var params = new Hwi.Params;
  ...
params.taskEnabled = Bool true;
 
DETAILS
If "true", the interrupt stub will disable the Task scheduler upon stub entry, and restore it upon interrupt completion.
If no Task-scheduling APIs (e.g., Semaphore_post()) are called from within this interrupt's ISR function, then taskEnabled can be set to "false".
 
metaonly config Hwi.Params.threadTypeEnabled  // instance

Does this interrupt support thread-type tracking? Default is true

Configuration settings
var params = new Hwi.Params;
  ...
params.threadTypeEnabled = Bool true;
 
DETAILS
If "true", this stub will enable full tracking of the execution context. For example, if the ISR function (or one of the functions it calls) were to call BIOS_getThreadType(), the returned value would be BIOS_ThreadType_Hwi.
Setting this parameter to "false" will slightly reduce the interrupt stub overhead, but may result in an incorrect thread type being reported during the processing of the interrupt.
Static Instance Creation

Configuration settings
var params = new Hwi.Params;
// Allocate instance config-params
params.config =   ...
// Assign individual configs
 
var inst = Hwi.create(Int intNum, Void(*)(UArg) hwiFxn, params);
// Create an instance-object
ARGUMENTS
intNum — interrupt number
hwiFxn — pointer to ISR function
params — per-instance config params, or NULL to select default values (target-domain only)
eb — active error-handling block, or NULL to select default policy (target-domain only)
DETAILS
A Hwi dispatcher table entry is created and filled with the function specified by the fxn parameter and the attributes specified by the params parameter.
If params is NULL, the Hwi's dispatcher properties are assigned a default set of values. Otherwise, the following properties are specified by a structure of type Hwi_Params.
  • The arg element is a generic argument that is passed to the plugged function as its only parameter. The default value is 0.
  • The enableInt element determines whether the interrupt should be enabled in the IER by create.
  • The maskSetting element defines the dispatcherAutoNestingSupport behavior of the interrupt.
Hwi_create returns a pointer to the created Hwi object.
generated on Tue, 09 Oct 2018 20:57:41 GMT