Model-Based Design Toolbox (MBDT)のトピックRe: Simulink top level subsystem block names cause different code generated from compiler

Simulink top level subsystem block names cause different code generated from compiler

hubeiren — Mon, 30 Dec 2019 15:43:59 GMT

We use MBD_toolbox MPC57xx V3.1 for our motor control (MCU). We have four top level subsystems (Application, HW interface, OS and MPC Config). The four subsystems were named automatically by simulink as subsystem 1,2,3 and 4. We built it and run in our ECU without issue. For better readability, I changes subsystem names as Application, Interface, OS and Config. After built, it doesn't run in ECU anymore. And the code generated are quite different. I changed them to subsystemApplication, subsystemInterface, subsystemOS and subsystemConfig. They are OK. Under the top level subsystem, we have named the sub-subsystem with all kind of names. There is no issues.

My question: Why the top level subsystem have to be started with "subsystem"?

Thanks,

Re: Simulink top level subsystem block names cause different code generated from compiler

hubeiren — Mon, 30 Dec 2019 22:40:39 GMT

I did more test but couldn't figure out the causes.

- Subsystem Name Test

Summary:

Test #	Subsystem Names	Results
1	SubsystemApplication, SubsystemInterface, SubsystemOS, SubsystemConfig	pass
2	S_Application, S_Interface, S_OS, S_Config	pass
3	G_Application, G_Interface, G_OS, G_Config	Pass
4	Application, G_Interface, G_OS, G_Config	Pass
5	Application, Interface, G_OS, G_Config	Pass
6	Application, Interface, OS, G_Config	Pass
7	Application, Interface, OS, Config	Pass
8	Application, Interface, OS, MPC_Config	Fail
9	Application, Interface, OS, MPC_1Config	Fail
10	Repeat Test #7	Pass
11	Application, Interface, OS, MPC1_Config	Fail
12	Application, Interface, OS, MP_C_Config	Fail

Re: Simulink top level subsystem block names cause different code generated from compiler

constantinrazva — Mon, 06 Jan 2020 09:42:26 GMT

Hello hubeiren@yahoo.com‌,

Could you send us the model you are using? You can delete proprietary code and only leave parts of the model so that I can replicate your issue. Once I have it I can investigate and also contact Mathworks (if the issue is not caused by our toolbox, but by Simulink).

Kind regards,

Razvan.

Re: Simulink top level subsystem block names cause different code generated from compiler

hubeiren — Wed, 08 Jan 2020 15:28:00 GMT

After many trials, we found out that (at least at top level) model was built based on subsystem name's alphabet. It's not based from top to bottom, or from left to right. So anyone who want to make subsystem name has to be aware of this hidden rules.

Thanks for offering help!

Re: Simulink top level subsystem block names cause different code generated from compiler

constantinrazva — Mon, 20 Jan 2020 08:26:05 GMT

Hello hubeiren@yahoo.com,

Thank you for taking the time to share that information with the entire community!

Kind regards,

Razvan.