About Eth_InternalLoopback_S32G399A_M7

xiaoshumiao

In C:\NXP\SW32G_RTD_4.4_4.0.2_HF02\eclipse\plugins\Eth_TS_T40D11M40I2R0\examples\EBT\S32G3\Eth_InternalLoopback_S32G399A_M7

I want to test Ethernet loopback，My execution steps：

1. eb tresos open the project， and Generate Project.

2. make build.

But an error occurred，and Port.h, Eth.h, OsIf.h all cannot be found.

xiaoshumiao

Thank you very much for your reply.

I have solved this problem! The problem is version mismatch。

I'll list the solutions：

1. Find the corresponding eb tresos version from the RTD you are using.

for example:

open this file

2. Install the corresponding eb tresos.

3. NOTE:

You must Activate the eb tresos with Corresponding activation code even if other versions of eb tresos has been already activated.

4. copy all "<mod>_TS_T40D11M40I2R0" directories and .JAR files from C:\NXP\SW32G_RTD_4.4_4.0.2_HF02\eclipse\plugins to the "<Tresos Install Path>\plugins" directory.

View solution in original post

Daniel-Aguirre

Hi,

We are able to compile the example no problem from our side:

We see that you are using the windows form for the different paths that are required. We understand that this is wrong and you should be using the unix form, as shown below:

Please, let us know.

xiaoshumiao

Thank you very much for your reply

According to your answer, the previous question has been resolved.

Now there is a new problem.

I wonder if there is some configuration missing or a version mismatch.

Daniel-Aguirre

Hi,

Thanks for your feedback. We might not understand this last inquiry, were you able to compile successfully? Or are you still not able to compile the project?

As from our side, we are still unable to reproduce the outcome you are seeing, we can compile the example no problem.

As for problems under the parameters, we see that following:

The TRESOS_DIR is not pointing to the typical EB Tresos installation path. Can you confirm if under that path you are able to see the EB Tresos installation folder?
The PLUGINS_DIR is not pointing to the typical plugins folder. Also, the plugin that you are using does not seem to be the typical NXP RTD plugins. As shown under our previous example, all plugins should be available under the plugins folder of Tresos, we recommend using it.