Hi, @SoulWorker,
Thank you for your interest in using our MBDT for S32K3 in your projects.
In the attached pictures I can see that you are encountering two different issues.
I will answer them in the following order:
First of all, I would like to mention that there is a difference between the deployment of the Dio application on target and an External Mode Simulation, described as it follows:
Therefore, this serial communication needs to be configured, both hardware and software when running an External Mode Simulation.
Hardware:
You can use either:
LPUART6 is routed to the EVB's OpenSDA chip. The MCU's LPUART13 instance is connected to ChannelB of the USB2Serial converter on the EVB.
When you connect the board to the PC via the USB2Serial port, DeviceManager will display two COM ports for both FTDI channels; typically, the higher COM port number corresponds to our LPUART13 instance (it depends on how Windows assigns COM port numbers).Software: After making this connection press the refresh button under Hardware Implementation --> Target Hardware Resources --> External mode group and select the COM Port as identified inside Device Manager under the Ports tab on your PC.
If you are using the dedicated USB2Serial converter of the EVB, you should select UartChannel_1 inside the model settings and start with the highest COM port number in the list. Otherwise, use UartChannel0 for the OpenSDA USB2Serial converter.
For more details about how to run an External Mode Simulation, use the s32k3xx_extmode_s32ct example delivered with our toolbox and check the s32k3xx_extmode_s32ct_example_readme.html file found next to the model.
My suggestion for now is to start with a fresh setup for this example and try to rebuild the model.
To do this you need to:
Please let me know if this helped you.
Cheers,
Victor
Hi, @SoulWorker,
Thank you for your interest in using our MBDT for S32K3 in your projects.
In the attached pictures I can see that you are encountering two different issues.
I will answer them in the following order:
First of all, I would like to mention that there is a difference between the deployment of the Dio application on target and an External Mode Simulation, described as it follows:
Therefore, this serial communication needs to be configured, both hardware and software when running an External Mode Simulation.
Hardware:
You can use either:
LPUART6 is routed to the EVB's OpenSDA chip. The MCU's LPUART13 instance is connected to ChannelB of the USB2Serial converter on the EVB.
When you connect the board to the PC via the USB2Serial port, DeviceManager will display two COM ports for both FTDI channels; typically, the higher COM port number corresponds to our LPUART13 instance (it depends on how Windows assigns COM port numbers).Software: After making this connection press the refresh button under Hardware Implementation --> Target Hardware Resources --> External mode group and select the COM Port as identified inside Device Manager under the Ports tab on your PC.
If you are using the dedicated USB2Serial converter of the EVB, you should select UartChannel_1 inside the model settings and start with the highest COM port number in the list. Otherwise, use UartChannel0 for the OpenSDA USB2Serial converter.
For more details about how to run an External Mode Simulation, use the s32k3xx_extmode_s32ct example delivered with our toolbox and check the s32k3xx_extmode_s32ct_example_readme.html file found next to the model.
My suggestion for now is to start with a fresh setup for this example and try to rebuild the model.
To do this you need to:
Please let me know if this helped you.
Cheers,
Victor