S32K3 Interrupt names and handlers, how to configure

[Hareesh_S]

Hello,

I am relatively new to developing with the S32K3 and it's accompanying RTD (using RTD 6 RFP currently).

I am confused by the interrupt control driver (IntCtrl_Ip) configuration.

I vaguely recall coming across a table in NXP's documentation that described what each IRQn signified (For example FlexCAN0_0_IRQn vs FlexCAN0_1_IRQn) under the "interrupt name" column, but I cannot seem to find it again in the reference manual or user manuals for the IntCtrl_Ip driver or the related drivers (such as FlexCAN and Siul2_Icu in my example), so I was hoping someone in the forum could point me in the right direction to find this documentation?

Additionally, How do I know which handler to assign for the interrupts? So far I have been able to figure it out based on example projects and knowledge base posts, but for future reference, is there a list of all the predefined handlers that I should be using/is there any documentation that mentions this, as I am not able to find any myself.

Much thanks in advance for the assistance.

[VaneB]

Hi @Hareesh_S 

You can refer to the S32K3xx_memory_map.xlsx file, which is included as an attachment in the S32K3xx Reference Manual. This document provides a detailed list of the available device-specific interrupts. Additionally, you can consult the S32K3xx_COMMON.h file for your specific device, which contains an enumeration of the device-specific interrupts, including their names and numbers.

Regarding interrupt handlers, most are already defined. You can find the relevant definitions for each driver in the corresponding Driver Integration Manual, specifically in the section titled "ISR to configure within AutosarOS - dependencies." These manuals can typically be found in paths such as:

C:\NXP\S32DS.3.6.0\S32DS\software\PlatformSDK_S32K3\RTD\Can_43_FLEXCAN_TS_T40D34M50I0R0\doc

Please note that the exact path may vary depending on the driver and the installation directory of your S32 Design Studio instance.

BR, VaneB

[Hareesh_S]

Hello @VaneB,

Thank you for the response, this was indeed what I was looking for! Did not know the driver integration manual was even a thing!

On a side note, random question, but what does the prevalence of "43" signify? I see it in a lot of the driver names, such as CAN, LIN, mem etc.

[VaneB]

Hi @Hareesh_S 

The "43" refers to NXP’s AUTOSAR vendor ID, which is 0x002B in hexadecimal or 43 in decimal (AUTOSAR-Vendor ID). This naming convention helps distinguish vendor-specific implementations of AUTOSAR modules.

[Hareesh_S]

@VaneB That makes sense, thank you for the clarification and the assistance so far!