AM6421: Software VIM Post Dispatching via HwiP_post() on the TI AM64x platform doesn't trigger interrupt

shraddha naik

Part Number: AM6421

Hello team,

I am using 2 HW timer DMTimer0 & DMTimer1, both with input clock MAIN_PLL1_HSDIV3_CLKOUT running at 192Mhz freq for period of 1.25ms & other on 156us on interrupt mode & callback method.

My requirement is to generate SW interrupt based on ticks, so from timer DMTimer0, on every 2nd , 4th , 5th & 40th tick i do my other tasks which are running at 2.5ms, 5ms, 10ms, 50ms etc.

I have assigned SW VIM lines 140,141,142,143 vector for each tick so that based on ticks in callback function of DMtimer0t, i post VIM SW interrupt instaed of calling the handler inline using HwiP_post(VIMLine) but it never fired interrupt & callback function (2.5ms, 5ms etc )are not getting called on SW VIM lines. Callback function of DMTimer0 works but not SW interrupts

Calling the handler function (callback function of 2.5ms, 5ms) inline impacts my both DMTimer0 & DMtimer1 time peiod.

How we can achieve this?

Regards,

Shraddha

2 months ago

0 Tushar Thakur 2 months ago

TI__Guru 65698 points

Hi Shraddha,

Can you please tell which version of SDK are you using?

Also are this SWI interrupts being called from an ISR of other interrupts?

Which core are you using?

Regards,

Tushar

0 shraddha naik 2 months ago in reply to Tushar Thakur

Intellectual 450 points

Hi Tushar

its mcu_plus_sdk_am64x_11_02_00_24

I am using R50 core

Once DMtimers0 ISR executes, it maintains tick count,, on 2nd tick, it calls HwiP_post(VIM Sw vector)

0 Tushar Thakur 2 months ago in reply to shraddha naik

TI__Guru 65698 points

shraddha naik said:
Once DMtimers0 ISR executes, it maintains tick count,, on 2nd tick, it calls HwiP_post(VIM Sw vector)

Does this means, HwiP_Post(SW) API is called from the ISR itself?

Also how are you checking that ISR didn't hit? Are you using DebugP_log API inside the ISR?

Regards,

Tushar

0 shraddha naik 2 months ago in reply to Tushar Thakur

Intellectual 450 points

Tushar Thakur said:
Does this means, HwiP_Post(SW) API is called from the ISR itself?

yes

Tushar Thakur said:
Also how are you checking that ISR didn't hit? Are you using DebugP_log API inside the ISR?

pin toggle inside SW ISR callback

0 Tushar Thakur 2 months ago in reply to shraddha naik

TI__Guru 65698 points

I have tried the same on my end. Calling the HwiP_post API for interrupts from timer callback and I am able to get the interrupt callback.

Below is the attached project.

Project - empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.zip

Let us know if the above works.

0 shraddha naik 2 months ago in reply to Tushar Thakur

Intellectual 450 points

Hi,

I have just modified your example as per my requirement,, & pin toggle function added,, pin toggle happens,, but timer period is not as expected.

for 1.25ms timer, pin toggles at 124ms ,

Yellow-5ms toggle,

Blue-1.25ms toggle

Red-10ms toggle

It looks counts coming proper but timing we need to confirm, I will attach my modified project too.

7673.empty_am64x-evm_r5fss0-0_nortos_ti-arm-clang.zip

Regards

Shraddha

0 Tushar Thakur 2 months ago in reply to shraddha naik

TI__Guru 65698 points

Please allow some time to review the above code and revert back.

+1 Tushar Thakur 2 months ago in reply to Tushar Thakur

TI__Guru 65698 points

I have found the root cause for the issue. The issue is coming because of the CCS logs which is enabled in your example application.

After disabling the CCS logs in your application code, the interrupts should then fire on correct timings.

Please refer image below

Let us know if the above works.

Processors

Processors forum

AM6421: Software VIM Post Dispatching via HwiP_post() on the TI AM64x platform doesn't trigger interrupt