• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 625 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

why? msp432 driverlib registerInterrupts/unregisterInterrupts

Eric Decker
Expert 1420 points

I'm using the MSP432 Driverlib version v3_21_00_05 as well as the Driverlib that is imbedded in the silicon.

The silicon I'm using is an XMS432P401R Rev C on a version 2.0 EXP-MSP432P401R Launchpad.

I've notice that there are no ROM entry points defined for registerInterrupt and unregisterInterrupt.  Rather one has to pick them up either from the msp432p4xx_driverlib.a library or directly from the source file.

Why are the {,un}registerInterrup entry points to the ROM disabled/turned off?

thanks,

eric

  • 0
    TI__Mastermind 31355 points

    Hello Eric,

    These functions are a bit special in that they will copy to interrupt vector table from flash memory to RAM. By default, the interrupt vector table is stored as a const value in flash memory. When the registerInterrupt function is called for the first time, it will copy the interrupt vector table from flash memory to RAM so that we are able to dynamically change each interrupt's function pointer in this table.

    The DriverLib in ROM was made to be completely independent with no requirements/attachments  to a user application's memory configuration. For this reason, any DriverLib functions (such as registerInterrupt) that depend on RAM (outside of the stack) are omitted from the ROM library. 

    Let me know if this answers your question and don't hesitate to let me know if you have any questions. 

    Best Regards,

  • 0 in reply to Timothy Logan
    Expert 1420 points
    thanks tim,

    does it make sense that function calls that aren't in the ROM to still be defined in rom_map.h?
  • 0 in reply to Eric Decker
    TI__Mastermind 31355 points

    The rom_map.h file is meant to be a sort of "catch all" for users to reference. If they use the MAP_fooBar function in their code it will use the ROM function if available, but default to the library version if not available. 

**Attention** This is a public forum