S32G-VNP-GLDBOX3

[arulom16]

Hi Team,

We are working on the following platform:
S32G-VNP-GLDBOX3

We are integrating a third-party runtime SDK and the vendor has requested the Yocto/toolchain details associated with this BSP

Could you please help clarify the following:
Which Yocto release/version is used for this BSP?
What is the recommended Yocto SDK/toolchain package for this platform?
What is the expected cross-compiler/toolchain triplet?
(example: aarch64-oe-linux-gcc)
Which glibc version is used in the BSP/runtime filesystem?
Is there an official NXP SDK/environment setup script for cross-compilation?
Are there recommended guidelines for integrating third-party ARM64 runtime packages into this BSP?
Does the default BSP image include only runtime components, or is there a separate Yocto SDK/toolchain package provided by NXP?
Could you share the recommended method for building and deploying third-party applications for this platform?

[arulom16]

Hi Chenyin,

Thank you for the information.

Hardware:
• S32G-VNP-GLDBOX3
• Processor: NXP S32G3
• CPU Architecture: ARM Cortex-A53 (aarch64 / ARM64)

Current OS Details:
uname -a
Linux s32g399ardb3 5.10.41-rt42+g91779bd5e303 #1 SMP PREEMPT Tue Nov 23 11:05:17 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

lscpu
Architecture: aarch64
CPU(s): 8
Model name: Cortex-A53

We would like to share the exact toolchain details with a third-party SDK vendor for ARM64 runtime compatibility validation.

Could you please help provide the following details specifically for the S32G3 GoldBOX3 BSP environment:

Exact toolchain triplet/compiler name
(example: aarch64-oe-linux-gcc)
Toolchain package/SDK name
SDK environment setup script name/path
(example: environment-setup-*)
Yocto SDK generation/install method

Any recommended compiler flags or ABI compatibility notes for third-party ARM64 runtime packages

This information will help the SDK vendor provide binaries compatible with the NXP S32G3 BSP runtime environment.

Thanks & Regards,

ezhil

[chenyin_h]

Hello, @arulom16 

Thanks for your reply.

For different BSP version provisioned by NXP, there may be different Yocto/toolchain/environment/building flags involved.

From the available information you shared, you are likely talking about the BSP31, which is indeed an old version, below are the available information for BSP31:

1. Yocto version:3.2

2. For manually building the BSP components, the following toolchain is suggested:

Sorry that the BSP31 is quite outdated(5 years ago), I do not find a correct Host to build and deploy it, thus I am not able to double confirm the detailed name/combinations of the toolchain used in Yocto(maybe arch64-poky-linux, but not confirmed), I suggest you installing it on a Ubuntu 20.04 host according to the following guide

Then, you may get the BSP31 deployed on your host, and you are able to check the toolchain name/version from it.

At last, for more stable/convenient development, I suggest using more recent BSP version for your reference instead of BSP31 mentioned.

BR

Chenyin

[chenyin_h]

Hello, @arulom16 

Thanks for your post.

1. NXP provided Linux BSP release for the S32G products, Yocto/toolchain version varies across different releases.

2. Take BSP44 version for example.

Yocto 5.0.6 is used, while the BSP is tested with GCC13.3.0 for arm64 toolchain.

Glibc used is 2.39

3. For more details, I suggest direct applying for the BSP access from the following link:

https://www.nxp.com/app-autopackagemgr/automotive-software-package-manager:AUTO-SW-PACKAGE-MANAGER

Once approved, you may find the BSP UM from your NXP account, with details for downloading, building, deploying and using the BSPs on your GoldBOX3.

BR

Chenyin