topic Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors in S32K

S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Veereshh — Wed, 30 Sep 2026 11:30:29 GMT

Hello Community,

I am currently working with the S32K344MINI-EVB (FRDM Automotive Evaluation Board) and would like to gain hands-on experience with basic peripheral drivers before starting development on a custom project based on the NXP S32K3 family.

Development Environment

S32 Design Studio (S32DS) 3.5.8
SW32K3_S32M27x_RTD_R21-11_4.0.0_P19_D2403
EB tresos 29

Current Status

I successfully imported and ran the following example projects:

SIUL2_DIO_IP_Example_S32K344
Dio_Example_S32K344

For both AUTOSAR and Non-AUTOSAR configurations, the projects built successfully and produced the expected output on the S32K344MINI-EVB.

Issue

I then imported the following CAN example projects:

FlexCAN_IP_Example_S32K344
Can_Example_S32K344

While configuring and building these projects, I encountered the errors shown in the attached screenshot.

Request

Could anyone please advise:

Are any board-specific modifications required for the S32K344MINI-EVB?
Are there additional FlexCAN, clock, pin, or EB tresos configurations needed?
Is there a guide for running these CAN examples on the MINI-EVB?

The attached screenshot shows the errors encountered during configuration/build.

Thank you for your support.

Regards,
Veer

Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Julián_AragónM — Wed, 30 Sep 2026 21:46:58 GMT

Hello @Veereshh,

Pinout is fairly similar between S32K344 EVB and FRDM-A-S32K344 (formerly S32K344MINI).

1. No

2. Yes. Both FlexCAN_IP_Example_S32K344 & Can_Example_S32K344 projects only configure FlexCAN in "loopback" mode, meaning there are no pins configured, and FlexCAN_0 is listening to its own messages.

Inside the project's MEX, you must:

Change FlexCAN 'Loopback' to 'Normal/User mode'
Add Siul2_Port (or Port in MCAL), and configure both PTA6 & PTA7 (CAN_H CAN_L in FRDM-A-S32K344).
Add port initialization in your project.

FRDM-A-S32K344 also uses TJA1043 CAN transceiver, which must set CAN_EN & CAN_STB to HIGH in order to set the transceiver in normal operation. These are routed to PTC21 & PTC20, as stated in the FRDM's user manual:

These must be set to HIGH inside your project as well. You can use the following examples as reference: [RTD600 MCAL & IP] S32K3X4EVB-T172 FlexCAN Example Interrupt/Polling.

Keep in mind they are based on RTD 6.0.0, not RTD 4.0.0.

After setting this, you can use J15.1 CANH and J15.2 CANL connected to another CAN node (PCAN USB analyzer, another MCU, etc.) to test CAN communication. In the examples I've shared, PCAN-USB analyzer was used.

Best regards,
Julián

Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Veereshh — Thu, 01 Oct 2026 13:58:54 GMT

Hi Julian,

Thank you for your support. Your guidance helped me successfully resolve the original configuration issues and build the CAN example. I have shared the build steps and screenshots below for the benefit of other users facing the same issue.

I have one additional question. After successfully running the Loopback example, I configured CAN_EN (PTC21) and CAN_STB (PTC20) and then modified the CAN configuration as follows:

Disabled Can Loop Back Mode
Changed Can Rx Processing Type from Polling to Interrupt

After these changes, validation/build errors are generated.

Could you please advise if any additional FlexCAN, IntCtrl_Ip, NVIC, or RTD-specific settings are required when switching from Polling to Interrupt mode?

Thank you again for your continued support.

Steps to Build CAN Example Successfully

Import Can_Example_S32K344 project.
Open the .mex file.
Enable Pins Tool if not already available.
Rename Functional Group to PortContainer_0_VS_0.
Configure:
- CAN0_RX → PTA6
- CAN0_TX → PTA7
Add PORT module under MCAL.
Configure PortPin settings and assign the required MSCR values.
Update code and resolve validation errors.
Generate code and build the project.
Program the board and verify CAN Loopback communication.

Best regards,
Veer

Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Julián_AragónM — Thu, 01 Oct 2026 16:48:05 GMT

Hello

I'm glad the information has been helpful.

In order to operate FlexCAN through interrupts, you must install the interrupt handler:

Also, the error you are seeing is because when FlexCAN driver uses Polling mode, you must specify the CanMainFunctionRWPeriods for both read and write calls. If Interrupt mode is used, this container must be removed from "CanHardwareObjetc > Can MainFunction RW Period Reference"

Best regards,
Julián

Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Veereshh — Wed, 07 Oct 2026 05:38:13 GMT

Hi @Julián_AragónM,

Thank you for the clarification and continued support.

Following your latest guidance, I:

Installed the FlexCAN interrupt handlers in the Platform interrupt configuration.
Removed the CanMainFunctionRWPeriods reference from CanHardwareObject > Can MainFunction RW Period Reference, as Interrupt mode is being used.
Regenerated the code and the configuration completed successfully without validation errors.

I also referred to the [RTD600 MCAL & IP] S32K3X4EVB-T172 FlexCAN Example Interrupt/Polling example that you shared and applied the equivalent settings to my RTD 4.0.0 P19 project.

However, after the configuration was successfully generated, I encountered the following build/linker errors:

Could you please advise whether any additional CanIf callback configuration or application-level implementation is required when enabling Interrupt mode in the AUTOSAR CAN example?

Best regards,
Veer

Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Julián_AragónM — Wed, 07 Oct 2026 13:56:24 GMT

Hello @Veereshh,

CanIf (and all other interface AUTOSAR modules such as EthIf, WdgIf, LinIf, MemIf, among others) are delivered as "stub" modules, meaning that they are provided simply as a placeholder, and must be overwritten by the customer application, or by a third-party stack (such as Vector).

In the posted examples, CanIf.c file was removed from build path, and CanIf APIs were declared inside main.c:

/*======================================================================== * GLOBAL FUNCTIONS ==========================================================================*/ void CanIf_ControllerBusOff(uint8 ControllerId) { (void)ControllerId; } void CanIf_ControllerModeIndication(uint8 ControllerId, Can_ControllerStateType ControllerMode ) { (void)ControllerId; (void)ControllerMode; } extern void CanIf_TxConfirmation(PduIdType CanTxPduId) { (void)CanTxPduId; CanIf_bTxFlag = TRUE; } extern void CanIf_RxIndication( const Can_HwType * Mailbox, const PduInfoType * PduInfoPtr ) { (void)Mailbox; (void)PduInfoPtr; CanIf_bRxFlag = TRUE; }

Can you try excluding CanIf.c from path and declaring the functions inside main?

Best regards,
Julián

Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Veereshh — Wed, 07 Oct 2026 15:34:01 GMT

Hi Julián,

Thank you for the explanation regarding the CanIf stub implementation.

I followed your recommendation: excluded CanIf.c from the build path and declared the required CanIf callbacks in main.c. After making these changes, the project built successfully with 0 errors and 0 warnings.

I then started debugging step-by-step. The application now breaks during Port initialization, specifically at:

/* Initialize All UnUsed Port Pins */

Port_Ipw_Init_UnusedPins(pConfigPtr);

inside: static inline void Port_Ipw_Init_UnusedPins(...)

The debugger then broke at:

Break at address "0x0" with no debug information available, or outside of program code.

Additionally, PCAN-View reports a Bus Heavy condition.

Could this indicate an issue with the Port configuration (unused pins configuration), interrupt configuration, or another missing initialization step?

If needed, I can share the complete project for your review.

Thank you for your continued support.

Best regards,

Veer

Re: S32K344MINI-EVB: FlexCAN_IP_Example_S32K344 and Can_Example_S32K344 Configuration Errors

Julián_AragónM — Wed, 07 Oct 2026 16:05:09 GMT

Hello @Veereshh,

Good to know your project now builds successfully.

The first disconnection issue seems to be regarding the UnTouchedPortPin container from the "Port" driver. In RTD 4.0.0 and below, the debugger pins must be included inside the UnTouchedPortPin container so that connection is maintained.

From the PORT_UM.pdf:

In order to be able to use the debug capabilities, the JTAG and Reset pins need to be configured in the Port driver using mechanism B. This means that the following pins/functionalities need to be added to the UnTouchedPortPin list:

Reset_b having PortPin Mscr set to 5 and SIUL2 Instance set to SIUL2_0
JTAG_TMS having PortPin Mscr set to 4 and SIUL2 Instance set to SIUL2_0
JTAG_TDO having PortPin Mscr set to 10 and SIUL2 Instance set to SIUL2_0
JTAG_TCK having PortPin Mscr set to 68 and SIUL2 Instance set to SIUL2_0
JTAG_TDI having PortPin Mscr set to 69 and SIUL2 Instance set to SIUL2_0

Adding the following 4 pins is enough:

As for the Bus Heavy error message, it could be caused by many reasons. Can you check the following?

CAN Bit Rate is the same between S32K3 and PCAN-USB (e.g. 500kbps and 75% sample point).
CAN0_EN & CAN0_STB pins are set to HIGH, which enables TJA1043 CAN Transceiver on-board.
Connections are correct between CAN0_OUT and PCAN-USB.

Best regards,
Julián