S32K358 BESS_Demo_Application

[Shivanand]

I have downloaded s32DS version 3.5.0 and s32k358 bess_bundle. When i am trying build the project, it is throwing some errors regarding version errors. I have attached the images regarding extenion packs and errors I have installed.

[VaneB]

Hi @Shivanand 

Usually, the "no such file or directory" error is caused by a missing configuration. In most cases, before running the example, a configuration needs to be generated. To do this, follow these steps:

1. Go to the Project Explorer view in S32 Design Studio and select the current project.
2. From the menu, select S32 Configuration Tool, then choose the desired configuration tool (Pins, Clocks, Peripherals, etc.).
3. Clicking on any of these tools will generate the necessary components.
4. Make any desired changes (if needed), and then click on S32 Configuration Tool → Update Code to apply the changes.

Additionally, please verify if the include file path contains any extra spaces or if the issue is caused by missing RTD/SDK installation or incorrect user configuration. To check this:

1. Right-click on the project in the Project Explorer.
2. Select Project Properties.
3. Go to C/C++ Build → Settings → Standard S32DS C Compiler → Includes.

Ensure that the file paths are correct and do not contain unnecessary spaces.

BR, VaneB

[Shivanand]

I have tried the recommended solution, but still a few errors are remaining.

[VaneB]

Hi @Shivanand 

The BESS demo application comes with a file listing all the required software dependencies. Could you please confirm if all of these dependencies have been installed in your S32DS instance?

[Shivanand]

Hi @VaneB   Yes, I have installed packages mentioned in the dependency list. But still facing the same issue

[VaneB]

Hi @Shivanand 

I have not been able to reproduce the error you are encountering, but I have made some important modifications that allow the S32K3-BESS-Firmware-Version-0.8.0-Demo to compile without any issues. Please follow the changes below and let me know if this resolves your problem:

Before importing the project into your workspace:

1. Navigate to your S32DS installation folder.
2. Open the file saf_itm_manifest.xml. Path: C:\NXP\S32DS.3.5\S32DS\software\PlatformSDK_S32K3
3. Change the version number to "3.0.0" to avoid any build errors.

Known issue with IPCF 4.0.0 (related to vendor IDs):

This issue affects files ipcf_Ip_Cfg.c and ipc-shm.h, where the vendor IDs are mismatched. To fix it:

1. Navigate to your S32DS installation folder.
2. Open the files ipcf_Ip_Cfg.c and ipcf_Ip_Cfg.h. Path: C:\NXP\S32DS.3.5\eclipse\mcu_data\components\PlatformSDK_S32K3\ipcf
3. Manually set the Vendor ID to 43: In ipcf_Ip_Cfg.c, update IPCF_IP_CFG_VENDOR_ID_C and in ipcf_Ip_Cfg.h, update IPCF_IP_CFG_VENDOR_ID.
4. Restart S32DS.

[Shivanand]

Hi @VaneB. The error I'm getting is different; I'm posting an image of errors. There are two reference applications, 0 & 2. Application_2 is built, but application_0 has errors

[VaneB]

Hi @Shivanand 

Could you please provide your S32DS installation details? I want to verify if there are any conflicts between packages or if there are any missing packages that could be causing the error you are experiencing.

[Shivanand]

Hi @VaneB Installation Details

Package: S32 Design Studio Platform package; Version: 3.5.14; Build id: 202409241924
Package: S32K3 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202303311831
Package: SW32K3 IPCF 4.0.0 D2306; Version: 4.0.0; Build id: 202306301110
Package: HB200X for S32K3XX; Version: 0.8.0; Build id: 202307140229
Package: S32K3xx development package; Version: 3.5.0 RTM; Build id: 202304051438
Package: S32K396 development package; Version: 3.5.0 EAR2; Build id: 202209290838
Package: NXP GCC for Arm Embedded Processors v10.2 build 1728; Version: 1728; Build id: 202109281337
Package: TCPIP_STACK for S32K3 version 1.0.3; Version: 1.0.3; Build id: 202306190957
Package: NXP GCC for Arm Embedded Processors Build 1620; Version: 1620; Build id: 202005201521
Package: GDB Client for Arm Embedded Processors 12.1 Build 1702; Version: 1702; Build id: 202309251304
Package: FS26 for S32K3 version 2.0.0; Version: 2.0.0; Build id: 202308040805
Package: NXP GCC for Arm Embedded Processors v9.2 build 1649; Version: 1649; Build id: 202005201157
Package: GNU ARM PEMicro Interface Debugging Support; Version: 5.5.7; Build id: 202304031909
Package: S32K3 SAF_EVAL RTM 1.0.4; Version: 1.0.4; Build id: 202312210949
Package: SW32K3 BMS SDK Autosar 4.4 R21-11 Version 1.0.1; Version: 1.0.1; Build id: 202308301443
Package: FreeRTOS for S32K3 3.1.0; Version: 3.1.0; Build id: 202304240736
Package: S32 Design Studio Platform Tools package; Version: 3.5.11; Build id: 202403280939
Package: SW32K3 BMS SL SDK Autosar 4.4 R21-11 Version 1.0.1 DEMO; Version: 1.0.1; Build id: 202308301406
Package: S32K396 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202303311831
Package: S32 Design Studio Debugger Core; Version: 3.5.11; Build id: 202403271836
Package: S32K3XX RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202303311831

[VaneB · Accepted solution]

Hi @Shivanand 

I have compared the packages you have installed with my environment, and I noticed that some of your packages are not up-to-date. To rule out any potential issues caused by this, could you please update the packages I have highlighted in yellow?

Once you have done that, kindly let me know if you observe any changes in the project.