Dio_Example_S32G247A_M7 has compilation errors

[VadimIdelchuk]

Hi,

I tried to build example project Dio_Example_S32G247A_M7, but meet number of problems.

1st problem related to S32DS itself installed on Linux Ubuntu 20.04.

Configuration tool reported about absent scripts ../dio/dio_utils.js, ../port/port_utils.js and ../mcu/mcu_codegen.js.

I found that these scripts are present, but folders names have different names - Dio, Port and MCU.

I created symbolic links to these folders without capital first letter and after S32DS restarting received message that different tools detected. Enabling the using these tools solved the problem with absent scripts.

Code generation by configuration tool succeeded, but compilation created a lot of errors like:

"AutoSar Version Numbers of Mcu_Cfg.h and Mcu_VS_0_PBcfg.h are different".

I found that the second file from the error message is present, but it is empty.

What can be a problem with generating the content for this file.

The following is list of these empty files:

- Mcu_VS_0_PBcfg.h

- Power_Ip_VS_0_PBcfg.h

- Ram_Ip_VS_0_PBcfg.h

[VadimIdelchuk · Accepted solution]

After removing default version RTD (4.0.0) and installing RTD version 4.0.2 the problem solved

[VadimIdelchuk]

After removing the suggested package RTD S32 The following is list of S32 packages installed:

VadimIdelchuk_0-1710169291949.png

And opening the configuration tool creates the following message:

VadimIdelchuk_1-1710169376716.png

and configuration tool no starts.

I downloaded RTD 4.0.1 pacakge as ZIP file and opened it to folder.

While I start to install the package, the following installation details displayed:

VadimIdelchuk_2-1710169718857.png

Appropriate to you suggestion I installed only packages with version 4.0.1:

VadimIdelchuk_3-1710169791069.png

And after installation the list of installed packages looks:

VadimIdelchuk_4-1710170111766.png

But the same problem with opening configuration tool occurred:

VadimIdelchuk_5-1710170196224.png

What is the next step?

[VadimIdelchuk]

Hi Daniel-Aguirre,

I added suggested packages:

VadimIdelchuk_0-1710237381999.png

and problem with opening configuration tool solved.

I decided to re-create Dio example from scratch.

The known problem with missed package dio.driver. I solved as in the past by adding it.

The next problems were in Published information of Dio and Port configuration - the SwPatchVersion of both defined as 0. but required 1.

I change both to 1 and no errors detected.

I updated the code successful:

VadimIdelchuk_6-1710240761193.png

But compilation failed because include files

- Mcu_VS_0_PBcfg.h

- Power_IP_VS_0_PBcfg.h

- Ram_IP_VS_0_PBcfg.h

are empty:

VadimIdelchuk_7-1710241005227.png

VadimIdelchuk_8-1710241029764.png

VadimIdelchuk_9-1710241054874.png

What can be a problem?

[Daniel-Aguirre]

Hi,

Thanks for your feedback.

Given the following comment:

"The known problem with missed package dio.driver. I solved as in the past by adding it."

We understand that did the same steps you did before of adding the package manually, is this correct?

If so, this should not be done. When you click the "Update Code" button, the missing packages will be added automatically, if no errors are detected.

From our side we are not seeing any problems as the ones you are seeing, since we see the files have code under them:

DanielAguirre_0-1710253622955.pngDanielAguirre_1-1710253638606.pngDanielAguirre_2-1710253651344.png

Since we understand that you did some modifications to the S32DS scripts due to problems related to Linux, could be a problem of S32DS instead of the RTD's. At this moment, we can recommend reinstalling S32DS with the new installation steps for the RTD's.

We do apologize.

Please, let us know.

[VadimIdelchuk]

Hi Daniel-Aguirre,

Thank you for the fast answer.

Appropriate to your suggestion I re-created the example.

After this I opened configuration tool by double clicking to MEX file.

The first message received:

VadimIdelchuk_0-1710257583875.png

After clicking "Ok" configuration tool displayed error "Pins tool is disabled. Enable it or select a different tool":

VadimIdelchuk_1-1710257745595.png

I enabled it and opened.

But it shows the following error:

VadimIdelchuk_2-1710257917561.png

Appropriate to your recommendation I ignored it and clicked to "Update Code".

The list of the files for generation displayed with errors:

VadimIdelchuk_3-1710258098525.png

I clicked "Ok", but errors notification still displayed:

VadimIdelchuk_4-1710258253035.png

The Pins error is the same as I notified before - resource "platform.drivers.pins" is still absent.

I should add manually by clicking to

VadimIdelchuk_5-1710258370949.png

The tool suggested to install 5 packages:

- clock

- Mcu

- Pins

- Port

- Dio

VadimIdelchuk_6-1710258559656.pngVadimIdelchuk_7-1710258598884.pngVadimIdelchuk_8-1710258634888.png

The number of errors in errors notification reduced to 2:

VadimIdelchuk_9-1710258769709.png

I opened Periferials tool for looking the errors:

VadimIdelchuk_10-1710258864447.png

I solved them like in previous times by updating Published information SwPatchVersion to 1 from 0.

The error notification shows absence of errors:

VadimIdelchuk_11-1710259013890.png

and "Update Code" required.

I clicked "Update Code" and preview shown that known problematic files (Mcu/Power/Ram)_VS_0_PBcfg.h will not be generated again.

I canceled the code generation and found that these files are empty.

Is it possible to sign that code generation will generate all files, not only changed or missed?

[Daniel-Aguirre]

Hi,

Thanks for your feedback. It seems that there is a mistake under the steps being followed for using the Dio example. Since the Dio example is an AUTOSAR example, the usage of pin tools is disabled since it is not used by AUTOSAR.

When you enable the pins tool, it might be creating a problem since you are mixing AUTOSAR and non-AUTOSAR configurations. We can recommend looking into the below HOWTO's examples, in which some differences are shown differences between AUTOSAR and non-AUTOSAR projects:

• non-AUTOSAR > HOWTO: Create a Blinking LED application project for S32G using S32 RTD No AUTOSAR - NXP Community
• AUTOSAR > HOWTO: Create a Blinking LED application project for S32G using S32 RTD with AUTOSAR - NXP Community

If you want to use the Pins Tool, help us using the non-AUTOSAR example "Siul2_Dio_ToggleLed_S32G274A_M7".

Please, let us know.

[Daniel-Aguirre]

Hi,

Thanks for your feedback. The behavior you are seeing after uninstalling the RTD is correct, since Config Tools will not have any reference to the RTD version the *.mex was created for.

As for the installation steps, we see that you uncheck the following items:

DanielAguirre_0-1710176733291.png

You should not uncheck these items. All items from each respective section should be selected.

As for the last error, seems to be that the installation was done incorrectly.

Please, let us know.

[VadimIdelchuk]

Hi,
The version of S32DS is

VadimIdelchuk_0-1710050318134.png

The versions of additional S32 packages are:

VadimIdelchuk_1-1710050513060.png

[Daniel-Aguirre]

Hi,

Thanks for your feedback.

From what we are able to tell, it seems that the RTD was not installed correctly, since we are seeing that a package is missing on your setup. Below an image from our setup:

DanielAguirre_0-1710165519526.png

Can you help us reinstall the respective RTD package? First you are required to uninstall all RTD dependent packages (from what we can see, should be LLCE and IPCF) to uninstall the RTD correctly. Once done, you can reinstall the RTD package.

Once reinstalled, help us verifying the example is working, since you are not required to have the LLCE nor the IPCF package for the Dio example. If successful, then you can proceed to install the additional packages.

We apologize for the inconvenience.

Please, let us know.

[Daniel-Aguirre]

Hi,

Can you let us know which S32DS/RTD version are you using?

As for the error, it refers to using 2 modules with a different RTD version, which may be incompatible. If you are seeing that one of the files is empty, seems to be an error of the code being generated. Either there was an error that was not corrected, or since you say that the installation had some issues, the scripts where not found and could not generate the code.

Please, let us know.