Migrating S32K344 Development to Linux/VS Code Without S32 Design Studio

[sergiomauro]

Hello Everyone,

I am working on a project involving the S32K344 microcontroller. While I know that S32 Design Studio is available for Linux, my team is aiming to use Visual Studio Code exclusively as the IDE for development on Linux, avoiding the use of S32 Design Studio altogether.

However, we are encountering several challenges and would greatly appreciate any insights or advice from the community.

Challenges and Questions:

Code Generation Outside S32 Design Studio

• Are there any tools, scripts, or workflows available to handle tasks such as clock configuration, peripheral initialization, and pin setup outside of S32 Design Studio?
• Is it possible to extract and reuse the logic behind the autogenerated files from S32 Design Studio?

Toolchain and Build System

• Are there recommendations for configuring the ARM GCC toolchain to build S32K344 projects in a custom workflow?
• Is there a way to export the build settings from S32 Design Studio for integration into alternative build systems (e.g., Makefiles, CMake)?

Debugging and Flashing

• What are the best Linux-compatible tools for debugging and flashing firmware on the S32K344?
• Has anyone successfully integrated these tools with Visual Studio Code (e.g., using OpenOCD, GDB, or other debuggers)?

Maintaining Configuration Consistency

• Without S32 Design Studio, how can we maintain consistent and up-to-date configurations for clock, peripherals, and other hardware settings?

Goal:

Our ultimate goal is to migrate entirely to a lightweight, flexible development setup based on Linux and Visual Studio Code, while still leveraging NXP's tools or community best practices to simplify the workflow.

If anyone has attempted a similar setup or has any resources, documentation, or advice to share, it would be incredibly helpful!

Thank you in advance for your time and insights!

Best regards,
Sergio Mauro

[jiri_kral]

Hi, 

1. RTD code generation is not possible without S32DS. But the code generation can be used with EB Tresos. 

2. You can re-use generated Makefiles and .args file from existing project 

3. PE Micro has debug environment for Linux. 

4. This is not possible without S32DS. Only way is manually edit generated files, but you will be not able add for example new drivers for peripherals and so on.