how to improve S32k3 interrupt callback execute speed?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

how to improve S32k3 interrupt callback execute speed?

Jump to solution
659 Views
Vandarkholme
Contributor III

hello! I'm migrate project from microchip's PIC series to S32K312.

In PIC chips, set 1us timer -> start timer -> hit timer interrupt  -> toggle pin, can see 1us toggle wave in scope. 

But in S32k3, it's not worked. the minimal toggle time is 6.2us,  I'm confused that why mcu running 120Mhz, but can't interrupt in 1us.

here's scope's 6.2us wave(set pit 1us interrupt) and test project(modified by pit example)

Vandarkholme_0-1731980968290.jpeg

Vandarkholme_1-1731981064195.png

 

 

0 Kudos
Reply
1 Solution
633 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @Vandarkholme,

Some SW overhead is always expected, but especially with the RTD.

Have a look at Pit_Ip_ProcessCommonInterrupt() in Pit_Ip.c.

This function is called from the PIT interrupt handler before the callback notification is called where you toggle the pin.

 

Regards,

Daniel

 

 

 

View solution in original post

0 Kudos
Reply
1 Reply
634 Views
danielmartynek
NXP TechSupport
NXP TechSupport

Hi @Vandarkholme,

Some SW overhead is always expected, but especially with the RTD.

Have a look at Pit_Ip_ProcessCommonInterrupt() in Pit_Ip.c.

This function is called from the PIT interrupt handler before the callback notification is called where you toggle the pin.

 

Regards,

Daniel

 

 

 

0 Kudos
Reply