Model-Based Design Toolbox (MBDT)のトピックRe: After compilation is complete, it doesn't run normally.

After compilation is complete, it doesn't run normally.

youngkugpark — Tue, 23 Feb 2021 08:44:42 GMT

Hello, everyone.

Currently, I am using MBD Toolbox_MPC57xx version 3.2 in Matlab 2019b.

It is designing an electric vehicle controller (VCU) and is planning to mount it on the MPC5744P.
In more detail, VCU logic was developed in the Freescale S12x MCU before, and now only the Target MCU is changed.
In other words, VCU control logic was complex but logically functional.

However, the program does not run at all after downloading it to the MCU even though it is normally compiled.

I was wondering if Stack overflow was the cause of the problem so I changed it like 1225445 but the problem still hasn't been solved.

I've been thinking about this problem for a long time, and I'd like to ask for help like this.

The attachment is a code generation report, and if you look at the Static Code Metrics Report section, you can see that the MCU-related setup files are not found.

I definitely ran "mbd_mpc_path" in the folder I was working on to check all the work paths on Matlab, but I have no idea why such errors are occurring.
Because of these errors, it is believed that the program is not running normally.

I'm desperate for your help.

Re: After compilation is complete, it doesn't run normally.

youngkugpark — Tue, 23 Feb 2021 09:00:50 GMT

I'm reposting the entire code generation report just in case.

Re: After compilation is complete, it doesn't run normally.

mariuslucianand — Tue, 23 Feb 2021 10:02:39 GMT

Hello @youngkugpark ,

So you are trying to run the code on the MPC5744P?

Can you try to run a simple GPIO example?

Can you please provide me the board revision you have?

Regards,

Marius

Re: After compilation is complete, it doesn't run normally.

youngkugpark — Tue, 23 Feb 2021 12:50:35 GMT

Hi, Marius

Yes, I am currently using DevKit-MPC5744P.

The back of this board is marked SCH-29333 REVB.

I confirmed that the example program GPIO you mentioned works normally.

The VCU control model, which is not currently running, is more complex than GPIO, contains many Subsystems, and the "function packing" of these Subsystems is set to "Auto". (Subsystem > Block Parameters > Code Generation)

I desperately need your help because I don't know the cause of the problem at all.

Regards,

Peter

Re: After compilation is complete, it doesn't run normally.

youngkugpark — Sat, 27 Feb 2021 05:50:45 GMT

Hi, Marius

To solve my current problem, I ran "Simulink Model Advisor" on my control model.
However, it was confirmed that an unexpected error occurred.
To explain in detail, an error is occurring regarding the "S-Function" of the MBDT Toolbox included in my control model.
Usually, this error is caused by Matlab work path setting or Tool License problem, so I checked the work path setting and the license of the tool box, but it still occurs.
Question 1.
Why is the S-Function problem with the attachment occurring?
The GPIO example also identified the same S-Function problem.
Question 2.
Due to this S-Function problem, isn't my control model working normally now?
Question 3.
According to MBDT "Quick Start Guide", the toolbox has a license location of \MATLAB\Add-Ons\Toolboxes\NXP_MBDToolbox_MPC57xx\code\lic.
When MBDT ver3.2 is installed, the "code/lic" directory is not created, but only the "lic" directory is automatically created.
Then should I create a "code/lic" directory manually? Or should I copy and paste the license file to the automatically generated "lic" directory?