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.

AM2634: TMDSCNCD263

Part Number: AM2634

Hello,

I have an issue while the interrupt is executing.

I am triggering RTI1_INT0 interrupt by writing 0x08000000 into the VIM_RAW_2 register. vimIrqDispatcher extract the required info and check the handler is not null and then executes the handler.

The problem is the handler does not execute. The next picture contains the call stack, and the vimIrqDispatcher calls the handler.



Then the handler starts to execute. The next picture shows the assembly of the handler.


After doing an assembly step into this unknown behavior happens.


I don't know what is the problem, If I configured a gpt timer and made the above function as the callback function triggered by the gpt isr it works fine, but by making it directly the isr as mentioned the issue occurs.

Your help is appreciated,
Yours,

  • Hi,

    Apologies for the delay, it seems the thread is assigned to another owner(and he was on vacation) as the thread doesn't talk about whether you're using MCAL code or MCU+SDK code. Please mention the package of code you're using from next time so the ticket is assigned to respective owners. Is this issue resolved or you're facing the issue?

    by writing 0x08000000 into the VIM_RAW_2 register

    Are you registering the VIM interrupts in the MCAL application using the functions like as shown below? If not try by registering it, it is not recommended to directly trigger peripheral interrupt sources like how we do SW_INT. In the below snapshot, change the handler and interrupt number with your desired number and handler. This properly registers the interrupt in the VIM and try to trigger it.

    Thanks