• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 30 subscribers
  • Views 421 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0L1306: Interrupt handlers setup and change

Wayne Huang
Genius 16285 points
Part Number: MSPM0L1306
Other Parts Discussed in Thread: SYSCONFIG,

Dear Champs,

I am asking this for our customer.

1.

In Sysconfig, how does the user know the name of an interrupt handler?

2

How does the user change the name of handler if needed?

For example, in the example,

uart_tx_multibyte_fifo_dma_interrupts_LP_MSPM0L1306_nortos_ticlang

we use a UART interrupt below,

void UART_0_INST_IRQHandler(void){}

But how does the user know the handler name is "UART_0_INST_IRQHandler" from Sysconfig and how does the user change it?

  • 0
    TI__Guru 70726 points

    Hi Wayne,

    The name of the ISR handler is generated by Sysconfig for the peripheral and is located in the ti_msp_dl_config.h, which is located under the project folder Generated Source.

    Here is an example how to modify the name of the handler and interrupt number (optional).

  • 0 in reply to Dennis Lehman
    TI__Genius 16285 points

    Dear Dennis,

    It's still confusing.

    For example, in the example "gpio_input_capture_LP_MSPM0L1306_nortos_ticlang", how does the user know below handler from Sysconfig?

    void GROUP1_IRQHandler(void)

    ti_msp_dl_config.h does not have such information.

    Do we have a list to show this in a systematic way in Sysconfig or another file?

  • 0 in reply to Wayne Huang
    TI__Genius 16285 points

    Dear Dennis,

    Do you have any update?

  • 0 in reply to Wayne Huang
    TI__Guru 70726 points

    Hi Wayne,

    I super apologize for the delay.  The SW team is supposed to be adding a feature that will auto-generate an ISR Handler template specific to each peripheral.  Until then, the only way is to copy a handler from an example and modify as needed.  The downside to this is the example handler you find may not show all the possible interrupt IIDX for that peripheral. 

  • +1 in reply to Dennis Lehman
    TI__Genius 16285 points

    Dear Dennis,

    Thank you for your information.

    It will be better if Sysconfig can handle this in the future, like C2000 Sysconfig, which can customize all interrupt handlers.

    So far, based on ARM Cortex M0 definition, the IRQn vectors are placed from 0x0 after stack and reset vectors.

    Therefore, we have found a workaround by referring to the fundamental definition file placed on default vectors from 0x0 including all 32x IRQn hanlders, like 

    C:\ti\mspm0_sdk_2_00_00_03\source\ti\devices\msp\m0p\startup_system_files\ticlang\startup_mspm0l130x_ticlang.c

    Do you think this is a good workaround?

  • +1 in reply to Wayne Huang
    TI__Guru 70726 points

    Hi Wayne,

    Yes, Sysconfig for M0 will most likely do this in the future.  For now, yes, the proposed workaround will work.