Issues setting up RTD in S32 design studio 3.5 for S32K358

Rnk7 · ‎01-10-2024

I am trying to configure a setup for S32K358, for which I installed the following in a fresh installation of S32 design studio 3.5:

1> S32K3XX development package (from internal installer)

2> S32K3 RTD Autosar 3.0.0 P01 (from internal installer)

3> AMMCLIB version 1.1.35 (This wasnt working from the S32 installation window where it said RTD was not compatible, so I checked its release notes, where it says it should be. This was then downloaded from the website and installed via .exe instaler)

The resultant installation details are as follows:

Package: GDB Client for Arm Embedded Processors 12.1 Build 1702; Version: 1702; Build id: 202309251304
Package: S32 Design Studio Platform package; Version: 3.5.9; Build id: 202312191958
Package: S32K3.P01 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202304031555
Package: NXP GCC for Arm Embedded Processors v9.2 build 1649; Version: 1649; Build id: 202307190917
Package: GNU ARM PEMicro Interface Debugging Support; Version: 5.7.6; Build id: 202312041432
Package: S32K3xx development package; Version: 3.5.8; Build id: 202311290134
Package: NXP GCC for Arm Embedded Processors v10.2 build 1728; Version: 1728; Build id: 202307190908
Package: S32 Design Studio Platform Tools package; Version: 3.5.9; Build id: 202312191958
Package: NXP GCC for Arm Embedded Processors Build 1620; Version: 1620; Build id: 202005201521
Package: S32K3XX.P01 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202304031555
Package: S32 Design Studio Debugger Core; Version: 3.5.9; Build id: 202312191723

Now, when I try to build any of the examples (For this demonstration, its Adc_example_S32K358), I get the following error: "fatal Error: Adc.h: No such file or directory"

If I go to project>properties>C/C++ build>Settings>Standard S32DS C Compiler>include and add the path where the file is in the rtd, "C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32K3\RTD\Adc_TS_T40D34M30I0R0\include", the error changes to: "fatal Error: Adc_Cfg.h: No such file or directory", which is in a different directory, indicating that the RTD hasn't configured right.

I don't know how to proceed here, since S32K3XX.P01 RTD AUTOSAR R21-11 Version 3.0.0 is the one where the support for S32K358 is first seen and S32K3XX support packages for S32DS 3.4 don't show support for S32K358 i its release notes, and I am unsure if there is anything i can downgrade here.

VaneB · ‎01-10-2024

Hi @Rnk7

Have you generated the code from Config Tools? The following is said under the "description.txt" file provided under the example:

"Before running the example a configuration needs to be generated. First, go to Project Explorer View in S32 DS and select the current project. Select the "S32 Configuration Tool" menu then click on the desired configuration tool (Pins, Cocks, Peripherals, etc...). Clicking on any one of those will generate all the components. Make the desired changes(if any) then click on the "S32 Configuration Tool->Update Code" button."

B.R.

VaneB

Rnk7 · ‎01-11-2024

Oh, thanks. Yes, that works now.

To follow up, after I have built the project, when I go to the C/C++ debugger config, it returns an "Error with command: gdb --version not found" when I try to run it.

Does the nxp compiler have it, do I have to configure/locate it somehow to use it, or do I use the gdb from my local minGW.

VaneB · ‎01-11-2024

Hi @Rnk7

This error could be caused by the selected debug configuration, the first debug is launched by clicking on the debug button and there was no debug configuration launched previously - Eclipse creates a new generic GDB configuration which is missing some important paths/settings required to run GDB client.

I'd suggest you to go the Debug Configuration dialog select the correct debug configuration and press debug:

Rnk7 · ‎01-12-2024

Hi @VaneB ,

I have configured the debugger, but I am a bit unsure if it i working right. I am using an PEmicro universal multilink, and on running a debug session, after setting the breakpoint as shown, it starts as expected, but once I go step over on the inbuilt function in Fig 2, it will abruptly freeze and stay there.

At breakpoint, still working. Stepped over.Attempting to step over at this lineIt hangs.

Is this some setup problem?

Also when I try to run, must I remove the PEmicro debugger? As with debugger, the default one doesnt work. It gives the following error

Error starting process.
Cannot run program "C:\Users\conta\workspaceS32DS.3.5\Adc_example_S32K358\Debug_FLASH\Adc_example_S32K358.elf": Launching failed
Cannot run program "C:\Users\conta\workspaceS32DS.3.5\Adc_example_S32K358\Debug_FLASH\Adc_example_S32K358.elf": Launching failed
Cannot run program "C:\Users\conta\workspaceS32DS.3.5\Adc_example_S32K358\Debug_FLASH\Adc_example_S32K358.elf": Launching failed

Also I dont see the PEmicro Interface option in run configurations.

Regards,

Rnk7

VaneB · ‎01-15-2024

Hi @Rnk7

Is this some setup problem? Could you share an image of the error? Also if you are working with an S32K3X8 board, by default it will have a 3.3V voltage reference selected (J45.3 - J45.4). So the following actions must be done in order to work at 5V VREF:
- Connect J45.1 to J45.2 in the board
- Comment the macro '#define ADC_3V3_VREF_SELECTED' in file 'main.c'

Also when I try to run, must I remove the PEmicro debugger? When you are debugging a code you do not have to remove the debugger.

Rnk7 · ‎01-16-2024

Hi @VaneB ,

I am not sure what is the problem is communication here, but

1. The error in question is not a pop up, but the program stopping in its functionality entirely. The debugger is not highlighting anything in the image, it perpetually shows that it is running at this step. And the program doesnt progress. My board is EVB of the same build, so jumpers are different for me, but I have set it to 5V.

2. I want to inquire on RUN configurations, not DEBUG configurations in the 2nd half of my inquiry. I have made connections to the board through the pemicro debugger. I wish to run my project after a while, but I have to change the interface again. I don't wish to do that everytime, so I want to inquire the possibility of the pemicro debugger interface when I run it through RUN configurations. It doesnt have a PEmicro option directly available.

Extending on that, I havent been able to use the RUN configuration properly for the given settings, so I wanted to troubleshoot that part too. The following is my RUN configuration window, over onboard JTAG interface.

Clicking RUN here with jtag interface gives the following issue:

Regards,

Rnk

VaneB · ‎01-16-2024

Hi @Rnk7

To ensure there is no problem with the board, please try running the application on the board using the Debug Configurations instead of Run Configurations.