topic Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0) in Model-Based Design Toolbox (MBDT)

How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

Daniel_Popa — Tue, 18 Jul 2017 19:18:48 GMT

In case you need to export the generated code to S32 Design Studio for PA IDE, now there is an easy way. No more painful job of reconstruction the project manually and setting all sort of compiler flags. Here is what you need to do in just a few steps.

Prerequisite:

Toolbox for MPC5744P rev2.0: Model Based Design Toolbox For Panther (MPC574xP) Family of Processors 2.0 IS NOW AVAILABLE!

HotFix_4 for MPC5744P rev2.0: https://community.nxp.com/thread/451804#comment-925214

S32DS IDE v1.2 or newer: S32 Design Studio for Power v1.2.

How to:

#1: make sure the HotFix_4 is installed successfully and the "Generated S32 Design Studio ProjectInfo.xml file" option is visible and selected

#2: build the Simulink model as normal (e.g. Motor Control System example from Motor Control Class: Lecture 12 - Motor Control System since it is the most complex application we built so far on this community) and wait until is completed successfully.

#3: Open S32DS for PA and select Import/S32 Design Studio/ProjectInfo.xml Importer

#4: Press Next and select the ProjectInfo.xml from the location used to generated the C-code for the Simulink model. Also, select the E200 Executable option

#5: Click on Finish button to have the project imported into the S32 Design Studio workspace.

#6: Applicable for S32DS v1.2 (due to a bug in IDE): Open the Project Properties and go to Settings/Target Processor and select "generate code for E200Z4" as Target Processor and re=select the option shown near the Libraries Support. These will force the IDE to update the toolchain properties correctly. These limitations will be addressed in the newer versions of S32DS for PA.

#7: Build the project

Expected result: The executable file should be produced without any errors. In case of errors - please recheck #6.

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

hjhjhj — Sat, 22 Jul 2017 06:54:11 GMT

Hi Daniel,

Though having completed the whole process and builded the project sucessfully, the error ocurrs when I try to debug the project.The error message is as follows.Do you know the reason?

Thanks!

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

paulvlase — Sat, 22 Jul 2017 08:11:47 GMT

Hi hjhjhj‌,

Check this thread https://community.nxp.com/thread/454916 .

There is a bug in S32 Design Studio for Power v1.2, you need to set the GDB Executable to ${cross_prefix}gdb${cross_suffix}

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

hjhjhj — Sat, 22 Jul 2017 10:04:34 GMT

Hi@Paul Vlase

There isn't the option "GDB Executable" in the debug configuration page and it seems different between the project generated by S32DS and project generated by simulink.And I can't find "GDB Executable"in any other place as well.Can you help me find it?

Thanks!

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

paulvlase — Sat, 22 Jul 2017 10:41:54 GMT

Hi hjhjhj,

Try to set GDB debugger property to ${cross_prefix}gdb${cross_suffix} .

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

hjhjhj — Sat, 22 Jul 2017 11:10:02 GMT

Hi@Paul Vlase,

Setting GDB debugger property to ${cross_prefix}gdb${cross_suffix} works,but another error occurs .

Thanks!

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

Daniel_Popa — Sat, 22 Jul 2017 13:37:54 GMT

Hi hjhjhj

The easiest way to create a debug configuration is to start from an S32DS stationery project and then simply change its existing GDB debug launch configuration to debug the elf/project you wish to investigate.

Best regards,

Daniel

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

zhangrunhe — Wed, 17 Oct 2018 11:30:14 GMT

Hi daniel,

Why can't I open the projectInfo.xml file?

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

constantinrazva — Thu, 18 Oct 2018 07:26:41 GMT

Hello zhangrunhe@hotmail.com‌,

I'm not sure what the problem is - can you give me some more details to try and figure it out?

1) Did you select the ProjectInfo.xml file generated by our toolbox?

2) What version of S32 Design Studio do you have? (note: whatever version might it be, it has to be S32DS for Power Architecture if you want to import from a MPCxxxx toolbox and S32DS for ARM if you want to import from S32K14x toolbox).

3) Do you have another project with the same name already in your workspace? You can try changing the project name to someting like aaaClosedLooop_Control_mbd_rtw to see if that is the problem.

Kind regards,

Razvan.

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

zhangrunhe — Thu, 18 Oct 2018 08:07:18 GMT

Hi Razvan,

Sorry, I will provide more details.

1）yes,i select the ProjectInfo.xml file generated by my toolbox.

2)I'm sure my version of S32 Design Studio is S32DS for Power Architecture.

3)I have no another project with the same name already in your workspace.

Thank you very much and wait for your reply.

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

constantinrazva — Thu, 18 Oct 2018 13:54:17 GMT

Hello zhangrunhe@hotmail.com‌,

As the error message is not shown in S32DS and I could not find any of the common problems encountered when importing a project, I am not sure why this is happening. The ProjectInfo.xml file at my end works and I couldn't reproduce your issue. As I am not an expert in S32DS, could you post your question in the S32 Design Studio community? I think that without an error message associated, that is the best place to get your answer from.

Hope this helps,

Razvan.

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

1506840872 — Tue, 15 Jan 2019 06:58:24 GMT

Hi Constantin.

A question: Can I use the S32ds 2017R1 to replace the S32ds V1.2?

Or, any differences between the two kind of the S32ds? Which one is better?

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

mariuslucianand — Wed, 16 Jan 2019 08:09:13 GMT

Hello 1506840872@qq.com‌,

Yes, you can use the latest version of S32DS to import the generated code.

Best Regards,

Marius

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

c9356j — Thu, 09 May 2019 03:41:51 GMT

Hi Daniel,

Could you help me?

error

C:/NXP/S32DS_Power_v2017.R1/Cross_Tools/powerpc-eabivle-4_9/include/stdio.h unknown type name '__gnuc_va_list'

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

Daniel_Popa — Tue, 14 May 2019 10:09:38 GMT

Hi Jason Liu,

I see you are using the latest MBDT for MPC57xx 3.0 which is good. The toolbox can export the generated C code so that it can be later on imported into S32 Design Studio.

Can you please try to import & build the project attached here? I would like to exclude a S32DS configuration issue.

Thank you!

Daniel

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

c9356j — Wed, 15 May 2019 02:19:58 GMT

Hi Daniel,

Thanks for your support.

"adc_mpc574xP_mbd_rtw 20190515 am1008" -- > This file is ok .

"ClosedLoop_Control " (Lecture12_MPC5744P_v3.0.0) --- > Fail

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

Daniel_Popa — Wed, 15 May 2019 06:15:56 GMT

Hi c9356j@gmail.com‌,

Seems to be and issue with compatibility between the S32Design Studio and the built tools provided with MBDT.

To fix it, just remove the include path highlighted below. This path is not absolutely necessary since the S32DS has it's own compiler, hence it will avoid any compatibility issues.

Once you remove and rebuild the project it should work fine

Hope this helps!

Daniel

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

c9356j — Wed, 15 May 2019 09:20:50 GMT

Hi Daniel,

Thanks for your support.

But ..

(1).S32DS Build --> RAppID Fail

"ClosedLoop_Control_mbd_rtw.srec "--- > is not working properly

(2).Matlab --> S32DS --> RAppID Pass

" ClosedLoop_Control.mot" -- > This file is ok .

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

Daniel_Popa — Wed, 15 May 2019 10:06:40 GMT

Hi c9356j@gmail.com‌,

I do not know exactly how the S32DS works (not under my expertise). I think when you build with S32DS you should download the image via the JTAG with the built in debugger rather than using the RAppID bootloader. Is it working if you try that way ?

If so, then there might be an inference between the compiler shipped with the S32DS and the one from MBDT.

mikedoidge‌

Have you seen that kind of behavior ?

Thank you!
Daniel

Re: How to export Generated Code to S32 Design Studio IDE (applicable for MBDT for MPC5744P v2.0)

mikedoidge — Wed, 15 May 2019 21:15:02 GMT

Hello c9356j@gmail.com‌, dumitru-daniel.popa‌,

To be sure I understand correctly, the comparison is of the two scenarios:

1) Generate code and build model from MATLAB, then use RAppID Bootloader to flash over JTAG is WORKING.

2) Generate code and S32DS Project file from MATLAB, then use S32DS to builld and then use RAppID Bootloader to flash over JTAG is NOT WORKING.

Daniel, I echo your comments on using the flash tool within S32DS to program the code via either OpenSDA or JTAG. OpenSDA would be preferred since it is difficult to have the JTAG connected with the motor shield attached as well. However, I doubt this will produce the issue, the RAppID Boot Loader works well and is just an unnecessary extra tool for these scenarios.

I have not seen issues with this comparison since we worked out the bugs at the time this feature was added, however, we are introducing some opportunities for inconsistencies by generating the S32DS project file and then building from S32DS. It could be some of the settings produced when the S32DS project file is generated that cause the output to be different when the build is conducted within S32DS. It is possible these difference could be the result of updates to the S32DS for Power. Perhaps the compiler versions no longer match, introducing some difference. In general, I expect the resulting executable to work in either scenario.

If we can reproduce this issue locally, then it is something which should be resolved.

Best Regards,

Mike