2416166_en-US

[#1]

Migrating custom model from S32K3xx MBDT 1.5.0 to 1.8.0, Hardware Settings error

Hi NXP Support Team,

We need your assistance migrating an existing Simulink model from Model-Based Design Toolbox for S32K3xx version 1.5.0 to version 1.8.0.
Our model incorporates our custom IOC toolbox and previously worked with MBDT 1.5.0. After upgrading to 1.8.0 while using MATLAB/Simulink R2024b, our engineer encounters an error when opening the model’s Hardware Settings.

The steps to reproduce are:

1. Install MBDT for S32K3xx version 1.8.0.
2. Open our existing demo model, IOC_DemoPrj.slx.
3. Select HARDWARE → Hardware Settings.
The Configuration Parameters dialog fails to open and displays this error:
Output argument "out" (and possibly others) not assigned a value
in the execution with "mbd_s32k3.nxp.target.get_target_memory_entries"
function.

The dialog also references getTargetHardwareDetailWidgets.p. Please see the attached screenshot for the full message.

We contacted MathWorks Technical Support under case #09014041. They advised us to consult NXP because the MBDT add-on is developed by NXP; the root cause has not yet been confirmed.

Could you please help us with the following?
1. Migration procedure: What is the supported process for migrating a model from MBDT 1.5.0 to 1.8.0? Is a migration guide or conversion utility available, and can we upgrade directly?
2. Error diagnosis: Is this get_target_memory_entries error a known issue? Are there any applicable patches or workarounds?
3. Existing configuration: Does the model’s hardware, target memory, or peripheral configuration need conversion or regeneration? If so, how should we perform this when Hardware Settings cannot open?
4. Custom IOC toolbox: Which changes between these versions could require updates to our custom blocks, model callbacks, or build integration? Please identify the relevant interfaces and recommended changes.
5. Diagnostic information: What model files, configuration files, logs, and installation details would you need to determine whether this is a migration, installation/path, or custom toolbox integration issue?
Our goal is to retain the existing IOC functionality and make the changes necessary to configure, build, and run the model successfully with MBDT 1.8.0.

Thanks.