NXP CUP
NXP CUP
NXP CUPNXP CUP
NXP CUP
NXP CUPNXP CUP
  • Welcome to NXP Cup
  • Downloads and links
  • Support Material
  • Contact
  • 2024-Fall/2025 NXP-CUP Bare Metal Drivers
    • Getting started with RTD and 3D printing
    • Kit components
    • 3D printed kit build guide
    • Electrical connections
    • S32K144 RTD software setup
      • S32 Design Studio installation
      • RTD Software packet installation
      • Importing the NXP Cup sample app
    • Drivers description and usage
      • Servo
      • ESC
      • H Bridge
      • Display
      • Receiver
      • Linear camera
      • Pixy camera
    • S32 Design Studio usage tips
      • Setting up pins
      • Peripherals tool
      • Using interrupts
      • Adding RTD drivers
      • Setting clocks
  • 2024 NXP-CUP using MR-B3RB
    • Getting started with MR-B3RB
  • 2022 MR-Buggy3 Developer Guide
    • FCC-CE EMC Notification
    • Getting started
    • MR-Buggy3 build guide
      • Step 1: Preparing Car for upgrades
      • Step 2: Installing new Servo
      • Step 3: Installing ESC
      • Step 4: Installing PDB
      • Step 5: Install Mounting PCB
      • Step 6: Install FMU
      • Step 7: Install GPS
      • Step 8: Install Pixy Camera mount
      • Step 9: Installing top PCB
      • Step 10: Installing the RC receiver
      • Step 11: Wiring the Buggy3
    • MR-Buggy3 software setup
    • Configuring the PixyCam
    • NXP Cup Example Application
    • UWB-control sample Application
    • Ignition Gazebo Simulation
  • 2019 DFRobot Chassis Developer Guide
    • Getting started
      • Rover kits contents
      • Not included items
    • Assembly
      • DFRobot chassis
        • Lower plate, servo motor and front wheels
        • Brushless: Motors, ESCs and Power Module
        • Brushed: Motors and Power connection
        • Rear wheels and top plate
        • Camera mount
      • Known Issues
      • RDDRONE-CUPK64 (AKA Micro E board or ARC board)
      • RDDRONE-FMUK66
        • FMU enclosure
        • FMU assembly
        • GPS and Telemetry
        • Connecting all FMU wires
      • Commissioning the Pixy 2
    • Development tools
      • RDDRONE-CUPK64 AKA Micro E Board Development
        • Setting up MCUXpresso
        • Working with the example code
      • RDDRONE-FMUK66 Development
        • Virtual machine
        • Installing Ubuntu
        • PX4 Toolchain
        • MCUXpresso
        • Programming the RDDRONE-FMUK66
          • Programming FMUK66 for first use
          • Building PX4 firmware
          • Program software using debugger
          • PX4 configuration using QGroundControl
            • Firmware
            • Airframe
            • Sensors
            • Power
        • Working with the Example-Application
        • Adding distance sensors to the FMUK66
    • Landzo car model (OLD)
      • Hardware
        • NXP FRDM-KL25Z
        • Model Alamak ->out of order
          • Special: Camera module
          • Special: Camera Mount
      • Assembly
        • Model Alamak with FRDM-KL25Z
          • Circuit Boards
            • Adding Headers to FRDM-KL25Z
          • Chassis
          • Installing Motor Power Cables and Connection
          • Installing Motor Driver Board
          • Camera Mount
          • System Board, Servo and OLED
          • Mounting the FRDM-KL25Z
          • Battery Mount
      • Software
        • Software-Mathworks
        • 2017 TFC Hardware Overview
          • System Structure
            • System Board
            • Motor Driver Board
          • System Block Diagram
          • Schematics
          • Power Distribution
      • Known Issues
        • Camera Module
          • LZCAMADAPT2 Camera Adapter
          • [Deprecated] LZCAMADAPT Camera adapter
        • Steering Servo Connection
        • Board Mounting Holes
        • LCD Module
        • FRDM Board Socket Headers
  • 2020-2021 NXP Gazebo Summer Camp 2020-21
    • Introduction to NXP Gazebo Summer Camp
    • Milestone 1 - Intro to NXP Gazebo and ROS
      • Installation of NXP Gazebo
      • Running NXP Gazebo
      • Basics of ROS and how to write your algorithms in NXP Gazebo
      • Change between C++ and Python
    • Milestone 2 - Time to go fast!
      • Configuring the simulation
    • Milestone 3 - Simple Reaction
      • Detecting AprilTags within simulation
      • AprilTag Example Code Overview
    • Milestone 4 - Advanced Reaction
    • Updating NXP Gazebo
    • Video Tutorials
    • [NOTICE] Update - 12.2.2021
  • HARDWARE REFERENCE
    • RDDRONE-CUPK64 (AKA ARC Board) schematics
    • RDDRONE-FMUK66 Schematics
    • FMU Connectors and pinout
  • EXTERNAL SOURCES
    • NXP Cup Supported Material
    • Pixy 2 Wiki
    • PX4 User Guide
    • PX4 Developer Guide
    • QGroundControl User Guide
    • MAVSDK Guide
    • PX4 Github
  • ARCHIVE
    • Battery Charger US/EU Plug
    • Setting up Visual Studio Code
    • Installation of NXP Gazebo [OLD]
    • Overview of the NXP Gazebo stack [OLD]
    • Overview of the self-driving example code [PX4]
  • NavQ on NXP Cup Car
    • Setting up NavQ for use on the NXP Cup Car
Powered by GitBook
On this page

Was this helpful?

  1. 2024-Fall/2025 NXP-CUP Bare Metal Drivers
  2. S32K144 RTD software setup

S32 Design Studio installation

PreviousS32K144 RTD software setupNextRTD Software packet installation

Last updated 5 months ago

Was this helpful?

To install the S32 Design Studio IDE, an account on the NXP site must be created. Please create an account at this link.

After the account has been created or if you already have an account on the NXP site, go to the Design Studio page found at this link.

1. Click S32DS for S32 Platform link

2. Click on the orange button Downloads on the new page

3. In the search bar type S32 Design Studio 3.5 – Windows/Linux

  1. Click Download

  2. Click on S32 Design Studio for S32 Platform v3.5 (last entry)

6. Download the Windows Installer S32 Design Studio v3.5 Windows installer and S32 Design Studio v3.5 Installation Guide

7. Follow the steps of the S32 Design Studio v3.5 Installation Guide for installing the tool

Note: Make sure you install S32DS for Platform, not other tool versions
Note: The updates are not necessary