• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 198 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.

AM263P4: How to set up Vectored Interrupt Manager

Zaara
Prodigy 20 points
Part Number: AM263P4


Tool/software:

Hello,

I am setting up VIM from scratch on the AM263P4. I followed the steps in the TRM under Servicing IRQ Through MMR Interface. As I have not done something like this before I am not too familiar with what other steps I would need in order for VIM to successfully work.

Should I create an interrupt vector table, and if so, how do I know which address each ISR would be at? I know I would need to write the ISRs myself, but are there already set addresses for the source interrupts found in the R5FSS0_CORE0 Interrupt Map? 

Additionally, would I need to context switch in order to initialize VIM or is that something done inside of VIM before going into an ISR?

Thank you!

  • 0
    TI__Mastermind 18772 points

    Hi Zaara,

    I would like to understand the reason for setting up VIM from scratch, instead of just using it as it is present in the MCU_PLUS_SDK. You can enable VIM through TRM steps but that would not be an easy task. All this is already handled and provided in the out-of-box SDK (enabled by default).

    Zaara said:
    I am setting up VIM from scratch on the AM263P4.

    You can refer the SDK implementation present in the SDK files: mcu_plus_sdk\source\kernel\nortos\dpl\r5. Refer the vim and interrupt related files in this section and you can compare it with the TRM for your understanding.

    Regards,
    Shaunak