Support Request – S32K116 LIN/GPIO Pin Conflict and Missing Boards in Simulink (MBDToolbox v4.3.0)

VictorPastrana — Thu, 08 May 2025 23:03:53 GMT

Hi team, I’m working with a customer developing on the S32K116 using the NXP MBDToolbox (v4.3.0) for Simulink integration. We’re encountering two issues related to hardware configuration and would appreciate your guidance:

1. PTC2 Dual-Use: LIN Rx + GPIO ISR Wake-Up

The application requires PTC2 to serve both as a LIN Rx pin and as a GPIO interrupt source for sleep/wakeup events. The generated code configures the pin twice (once by the LIN block and again by the GPIO ISR block), which results in only the last configuration taking effect.

To bypass this, the customer edited the TLC for the GPIO block to skip pin initialization.

Question: Is there any *official* or *supported* way to allow this kind of dual-use scenario on the same pin in the S32K116? Or is this strictly limited by the hardware MUX constraints?

2. Missing NXP Boards in Simulink (Hardware Board Selector)

Despite having the MBDToolbox installed, no NXP boards (e.g., **S32K116 EVB**) appear in the Simulink hardware selection dialog.

Question: Is this a known issue with the toolbox or its installation process? Should we expect these boards to appear automatically, or does this require additional setup (e.g., reinstallation, registration of the `.mltbx` package, or environment variables)?

Thanks in advance for your support.

Let me know if you need more details or logs from the environment.

Model-Based Design Toolbox (MBDT)のトピックSupport Request – S32K116 LIN/GPIO Pin Conflict and Missing Boards in Simulink (MBDToolbox v4.3.0)

Support Request – S32K116 LIN/GPIO Pin Conflict and Missing Boards in Simulink (MBDToolbox v4.3.0)