So you've just installed the S32DS and are using it for the first time and would like to see how it works. Here is a quick and simple project to get you started. Prerequisite Before following the steps in this HOWTO, ensure you have the S32V2xx development package installed to S32DS. 1. Launch S32DS for Vision 2. Select 'S32DS Application Project' 3. Enter a name for the project 4. Select the 'A53 Linux' processor option 5. Click Next 6. Click the '...' next to the SDKs field 7. Check the box next to 'VSDK_MODULE_WIN' for Windows OS or 'VSDK_MODULE_LINUX' for Linux OS and click OK. 8. Click Finish 9. Build the project for Debug 10. Project is now built, ELF file is ready to be loaded to EVB for execution. However, if we have not prepared the EVB, we must first complete HOWTO: Setup S32V234 EVB2 for debugging with S32DS and Linux BSP. 11. Once the EVB is properly prepared, we must complete HOWTO: Setup A Remote Linux Connection in S32DS (S32V234)  12. With the project debug configuration and remote linux connection selected, select the debug dropdown menu and click Debug Configurations 13. Make sure the Debug_Remote_Linux debug configuration is selected and the connection setup in step 10 is selected (points to the IP address of your EVB). Click Debug 14. The first time you connect to a new IP address (i.e. the first time you debug after booting the board), you will receive a warning message, Click Yes and proceed. 15. The executable file is copied to Linux file system and gdbserver starts. 16. The Debug perspective is opened. You can now step through the code*     *Only debugging of the A53 code is supported by Linux GDB. For multicore debugging, including ISP and APEX2, additional debugger and probe(S32 Debugger with S32 Debug Probe, Lauterbach, etc) will be required.

        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power v1.2, Update 2             What is new? AMMCLIB v1.1.9 support for MPC56xx (MPC560xB, MPC560xP, MPC5643L, MPC567xF, MPC567xK) and for MPC57xxx (MPC574xC, MPC5748G, MPC574xP, MPC574xR, MPC577xC, MPC577xK, MPC577xM) updated PEmicro Eclipse Plugin Update v1.6.9 which fixes HSM mass erase problem for MPC5748G (see e.g.MPC5748G can not attach JTAG )   Installation instructions The update is available for online (Eclipse Updater) or offline (direct download link) installation.   online installation: go to menu "Help" -> "Install New Software..." dialog select predefined NXP S32 Design Studio update repository http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_POWER_1_2/com.freescale.s32power.updatesite  select all available items and click "Next" button   offline installation: go to S32 Design Studio product page -> Downloads section or use the direct download link to download the "S32 Design Studio for Power v1.2 - Update 2" file.   Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded Update 2 archive file: Select all available items and click "Next" button.

In this document, we show the steps to use the New Project Wizard to create a new application project for APEX2, ISP, or both.   1. Launch S32DS for Vision 2. Select File -> New -> S32DS Application Project 3. Enter a name for the project 4. Select the 'A53 APEX2/ISP Linux' processor option 5. Click Next 6. Select the APEX2/ISP options you need.       a. APEX2 programming - will add support to your project for an APEX2 application, you need this for any new APEX2 project       b. ISP programming - will add support to your project for an ISP application, you need this for any new ISP project       c. ISP visual modeling - will create a separate project for your ISP data flow diagram, you will not need this if you plan to use an existing graph diagram. This can also be created later. 7. Select the SDK(s) as appropriate for your setup. For example, 'VSDK_MODULE_WIN' for Windows OS or 'VSDK_MODULE_LINUX' for Linux OS, the one which corresponds to your OS is selected for you by default. 7. Click Finish 8. You now have a project or set of projects for development on the S32V234.

There are 2 methods to run; GUI, and terminal window. GUI Method 1) Make sure EVB is powered and connected to PC via USB (micro to USB) 2) Launch DDR Stress Test Tool, C:\NXP\S32DS_Vision_v2.0\utils\ddr_stresstool\DDR_Tester.exe 3) Load Image (C:\NXP\S32DS_Vision_v2.0\utils\ddr_stresstool\bin\s32v234_ddr_test.bin) 4) Load Init Script (C:\NXP\S32DS_Vision_v2.0\utils\ddr_stresstool\scripts\S32V234_LDDR2_MMDC0_2Gb.inc) 5) Select COM port 6) Press Download, then wait for it to complete. (may temporarily show 'not responding') 7) In 32bit Memory Read/Write section, enter address 80000000 in ADDR field. 😎 Change SIZE to 32 WORD 9) Click Read 10) See results 11) In DDR Stress Test section, enter 533 in both Start Freq and End Freq fields 12) Click Stress Test 13) See results 14) Results can be saved (C:\NXP\S32DS_Vision_v2.0\utils\ddr_stresstool\log) Terminal window Method (JTAG) This checks what settings are already uploaded in MMDC module 1) Make sure EVB is powered and connected to PC via PEMicro (Universal Multilink) or Lauterbach AND via USB cable. 2) In S32DS, create a simple project a. File->New->S32DS Application Project b. Enter name 'test' c. Select S32V234 Cortex-A53 d. Next e. Uncheck boxes for cores 2-4 f. Finish 3) Setup debug configuration a. Run->Debug Configurations… b. Select test_A53_1_PNE c. Change C/C++ Application to C:\NXP\S32DS_Vision_v2.0\utils\ddr_stresstool\ddr-test-uboot-jtag-s32v234.elf d. Select Debugger tab e. Click Advanced Options f. Check box for Enable initialization script g. Browse to find C:\NXP\S32DS_Vision_v2.0\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_3.1.3.201709051622\win32\gdi\P&E\supportFiles_ARM\NXP\S32Vxxx\S32V234M100_DDR.mac h. OK 4) Click Debug. You will see error message indicating the source file could not be found. This is expected. 5) Open terminal (such as PuTTY.exe) and connect a serial line using the USB port you have connected to the EVB, speed set to 115200, 8 data bits, 1 stop bit, and no parity or flow control. 6) Click Resume in S32DS Debugger. 7) In terminal window, you will see the test script has started. 😎 Select the MMDC channel (for example, enter 1 for MMDC1) 9) Select the DDR density (for example, enter 6 for 32MB) 10) Enter 'n' to decline the DDR Calibration 11) Enter 'y' to accept the DDR Stress Test 12) Enter Start and End frequencies (for example, enter 533, as was done in GUI method) 13) Enter 0 to run only once 14) See the results

This example performs basic initialization, sets PLL to maximum allowed frequency 200MHz, sets clock for peripherals, GPIO pins, PIT timer and interrupt controller. After initialization it blinks LED2 in the main loop using timeout counter variable. PIT timer generates periodical interrupts and toggles LED1 with 1s period. Test HW: MPC5746R-252BGA, MPC57xxMB Motherboard MCU:  PPC5746R 1N83M Fsys: PLL0 266MHz       Z4 Core 200MHz Debugger: PeMicro USB-ML-PPCNEXUS IDE/Compiler: S32DS for Power 2017.R1 / GCC Target: internal_FLASH - debug, release              internal_SRAM - debug_ram EVB connection:   Default EVB jumper setup   Connect LED1 to P14.3 on motherboard   Connect LED2 to P14.4 on motherboard

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture 2017.R1 Update 1          What is new? S32 SDK for Power Architecture 0.8.2 EAR (Early Access Release) for MPC574x-B-C-G and MPC574xP derivatives (see attached release notes for more details) MPC5744B, MPC5745B, MPC5746B MPC5744C, MPC5745C, MPC5746C - 1N84S (Cut 2.1), MPC5747C, MPC5748C MPC5746G, MPC5747G, MPC5748G - 0N78S (Cut 3.0) MPC5741P, MPC5742P, MPC5743P, MPC5744P - 1N15P (Cut 2.2B) S32 SDK  Power Architecture v0.8.2 Examples - "Create S32DS Project from Example" Installation instructions The update is available for online (via Eclipse Updater) or offline installation (direct download link) online installation:  go to menu "Help" -> "Install New Software..." dialog  select predefined update site "S32DesignStudio - http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_POWER_2017.R1/updatesite" select all available items and click "Next" button   offline installation:   go to S32 Design Studio for ARM product page -> Downloads section or use  direct link to download the update archive zip file Start S32DS and go to "Help" -> "Install New Software..." Add a new "Archive" repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select all available items and click "Next" button.   This will starts the update installation process.

        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio v3.1         Austin, Texas, USA April 4, 2019    The Automotive Microcontrollers and Processors' Embedded Tools Team at NXP Semiconductors is pleased to announce the release of the S32 Design Studio v3.1.  Here are some of its major features: NXP GCC toolchains for ARM32 and aarch64 bareboard and Linux targets (GCC version 6.3.1 20170509, build 1574 revision g924fb68) S32 Debug Probe support provided with S32 Debugger and S32 Trace tool for S32V234 S32 Trace tool is integrated to provide software analysis features (profiling, code coverage, and other) P&E Debugger support for S32V23x Lauterbach Trace32® support S32 Flash Tool is delivered to support Flash/SD/MMC memory programming for S32V234 S32 SDK for S32V23x 0.9.0 Beta is integrated. Release notes here. The S32DS Extensions and Updates S32 Configuration Tool framework (EAR7) with the Pin, Clock, Peripheral, DCD, IVT, and DDR Configuration tools S32 Design Studio Versions Versioning convention has changed. The version of this release identified in red box below: Complete S32 Design Studio v3.1 release notes are available here.   Installation To download the installer please visit the S32 Design Studio product page download section or click the direct here.     The installer requires the Activation ID to be entered. You should receive a notification email including the Activation ID after the download of the installation package starts. The installer installs just the base tools/package. In order to start development it is necessary to install at least one Development package. Currently the only application package available is Vision S32V2xx  (Other packages are coming soon). The application packages are managed by S32DS Extensions and Updates. Technical Support S32 Design Studio issues are tracked through the S32DS Public NXP Community space. https://community.nxp.com/community/s32/s32ds  

Example shows how can be expanded default 512kB flash memory by 64 kB using FlexNVM as a program/data flash. In FlexNVM are stored two ASCII images and function PrintImage. FlexNVM is divided into 32kB data section and 32kB code section in the linker file. Output is printed on terminal. As a output device you can use putty or any other serial terminal. Terminal settings: 9600, 8N1 - no flow control. In debugger settings you have to Enable partitioning device with code 0F0C. This value is written into FCCOB4 and FCCOB5 registers before flashing. Putty settings: Test HW: S32K144EVB, MCU: S32K144 Debugger: OpenSDA Target: internal_FLASH (debug mode and release mode)

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio 3.1  Update 190508          What is new? S32 Design Studio Platform Package 3.1.1 S32 Design Studio Platform Tools Package 3.1.1 Updated S32 Debugger and S32 Flash tool to support S32S247TV S32S2xxTV Development Package 3.1.0 S32V2xx Development Package 3.1.0 Vision Extension Package for S32V2xx 1.0.0 This is a cumulative update - it is applicable to S32 Design Studio 3.1 Installation instructions The update is available for online (via Eclipse Updater) or offline installation (direct download link)  online installation:  go to menu "Help" -> "S32DS Extensions and Updates" dialog  select all available items and click "Install/Update" button   offline installation:   go to S32 Design Studio product page -> Downloads section or use direct link to download the update archive zip file Start S32 Design Studio and go to "Help" -> "S32DS Extensions and Updates" Add a new "Add.." S32DS Software Site and browse to select the downloaded update archive .zip file you downloaded in the previous step          Select all available items and click "Install/Update" button.   This will start the update installation process.

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio 3.2  Update 191226          What is new? Vision Extension Package for S32V234 1.1.0 with VSDK 1.5.0 integrated.(VSDK Release Notes) This is a cumulative update (includes previous updates: Update 191219) Installation instructions The update is available for online (via Eclipse Updater) or offline installation (direct download link)  online installation:  go to menu "Help" -> "S32DS Extensions and Updates" dialog  select from available items and click "Install/Update" button   offline installation:   go to S32 Design Studio product page -> Downloads section or use direct link to download the update archive zip file Start S32 Design Studio and go to "Help" -> "S32DS Extensions and Updates" Add a new "Add.." S32DS Software Site and browse to select the downloaded update archive .zip file you downloaded in the previous step         Select from available items and click "Install/Update" button. This will start the update installation process.

This document details how to create a new project in S32 Design Studio and build using the existing code and makefile provided within the NXP Vision SDK example projects. If you are creating a new makefile project with code from any other source, the procedure may be different. Before creating a new makefile project from existing code we need to add some paths to the environment variable PATH and a couple of new environment variables. There are 3 main methods for adding these paths and variables. Which method depends upon your needs. Method 1 The paths and variables can be added to each project individually. This is useful if you only want these changes to affect a small number of projects. Or if your projects require different paths and variables. Note: these changes would be made after the project is created (shown in steps 15 - 17 below) Method 2 The paths and variables can be added to the entire workspace within S32DS . These will not be visible outside of S32DS and therefore will not affect the entire Windows environment. This is useful if you have a large number of projects with common requirements for paths and variables and do not want them visible any tools outside of S32DS. Method 3 The paths and variables can be added globally to the Windows environment and will affect all installed tools. This method is not recommended. Once you have selected a method, add the following paths to the PATH variable (paths shown using the default installation settings for S32DS): C:\NXP\S32DS.3.1\S32DS\build_tools\gcc-6.3-arm32-eabi\bin C:\NXP\S32DS.3.1\S32DS\build_tools\gcc-6.3-arm64-eabi\bin C:\NXP\S32DS.3.1\S32DS\build_tools\gcc-6.3-arm64-linux\bin C:\NXP\S32DS.3.1\S32DS\build_tools\msys32\mingw32\bin or if within Eclipse (can use variables, which don't need to be updated should the layout of S32DS installation change in a future release) ${S32DS_ARM32_TOOLCHAIN_DIR} ${S32DS_ARM64_LINUX_TOOLCHAIN_DIR} ${S32DS_ARM64_TOOLCHAIN_DIR} ${S32DS_GCC_TOOCHAIN_DIR} It is also necessary to add the following Windows system variables: Variable Name: S32V234_SDK_ROOT Variable Value: C:\NXP\S32DS_Vision_v2018.R1\S32DS\s32v234_sdk Variable Name: APU_TOOLS Variable Value: C:\NXP\S32DS_Vision_v2018.R1\S32DS\APUC The following steps demonstrate the procedure based on Method 1 above. 1) Launch S32DS for Vision 2) Click New 3) Select 'Makefile Project with Existing Code' 4) Select Next 5) Enter a name for the project. 6) For 'Existing Code Location',    a) Select 'Browse...' and then select the directory  C:\NXP\S32DS.3.1\S32DS\software\VSDK_S32V2_RTM_1_3_0\s32v234_sdk\demos\isp\isp_sonyimx224_rgb_yuv_gs8    b) Click OK 7) For 'Toolchain for Indexer Settings', select the option which matches your desired build configuration. For our example here, we will select 'ARM Linux 64-bit Target Binary Toolchain'. See the Vision Extension Package User Guide for more details on the toolchain options. This sets up some toolchain paths, but later we will set more for the specific needs of the VSDK examples. 😎 Click Finish 9) Right-click on the project from the Project Explorer. Select Properties 10) Go to section 'C/C++ Build' 11) Go to the 'Behavior' tab and in the field next to 'Build', enter:    ISP examples: 'allsub'    APEX examples: 'APU_COMP=nxp allsub' 12) Go to 'Builder Settings' tab, in 'Build location' section change the path for the 'Build directory'. Click on 'Workspace...' button 13) In the Folder selection menu, select the subfolder 'build-v234ce-gnu-linux-d' and click OK 14) Go to section 'Environment' 15) Select the environment variable 'PATH' and click 'Edit...' 16) Add the path variables to the value field, each separated by a comma ';' ${S32DS_ARM32_TOOLCHAIN_DIR} ${S32DS_ARM64_LINUX_TOOLCHAIN_DIR} ${S32DS_ARM64_TOOLCHAIN_DIR} ${S32DS_GCC_TOOCHAIN_DIR} Click OK 17) Click 'Add...' 18) Click 'Add...' and enter variable name 'APU_TOOLS' and value '${S32DS_APU_TOOLCHAIN_DIR}' Click OK 19) Click OK to close the Properties menu. 20) Click on 'Build' 21) Once the build is complete, the binary file (ELF) will be created

This document describes, how to add software site and how to install update from the 3rd party software site. 1) In S32DS, click Help->Install New Software 2) Click Available Software Sites. 3) Select required site, if available. 4) Select required site in Work with line: 5) Available updates will appear in the window below. Check GNU E200 PEMicro Interface Debugging Support 6) Click Next and new window will appear. Select required software and click Next. 7) Accept the license terms and click Finish. New software will be downloaded and installed. Hope it helps. Martin

        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Vision 2018.R1          Austin, Texas, USA November 23, 2018 The Automotive Microcontrollers and Processors’ Embedded Tools Team at NXP Semiconductors, is pleased to announce the release of the S32 Design Studio for Vision  2018.R1. The S32 Design Studio enablement simplifies and accelerates the deployment of ADAS vision and neural network solutions in automotive, transportation and industrial applications. Here are some of its major features: Release Content S32 Debugger ISP Graph Tool APEX2 Graph Tool NXP GCC Compiler 6.3 NXP Compiler for APU Vision SDK 1.2.0 Complete S32 Design Studio for Vision 2018.R1 release notes are available here. Installation To download the installer please visit the S32 Design Studio product page downloads section or click the direct here. The installer requires the Activation ID to be entered. You should receive a notification email including the Activation ID after the download of the installation package starts. For more information about the product installation see S32DS Vision Installation Manual.   Technical Support S32 Design Studio issues are tracked through the S32DS Public NXP Community space. https://community.nxp.com/community/s32/s32ds  

S32DS contains many example projects from which you can learn how S32DS can be used with the help of the Vision SDK to develop vision applications. The example projects contain generated and hand-written code, which utilize the Vision SDK to demonstrate a workflow using S32DS. In this document, the procedure for creating a project from one of the provided ISP examples through to execution on the EVB is detailed. This project was run using S32DS version 3.2 and VSDK version 1.5.0.   1) Launch S32DS 2) Select 'File -> New -> S32DS Project from Example' 3) Select 'isp_h264dec_single_stream' project    In this particular project, the ISP graph diagram is included. If you wish to view it, go to the Project Explorer panel and expand 'isp_h264dec_single_stream_graph'. Then double click on 'ISP data flow : h264dec_single_stream'. The ISP graph diagram will appear in the editor panel. 4) If not in the C/C++ Perspective, switch over by clicking on the icon showed below (Hovering over the correct icon should display 'C/C++'). The current perspective is displayed on the top bar. 5) Select isp_h264dec_single_stream: A53 in the Project Explorer panel 6) Build project for A53  7) Start a debug session using method as described in HOWTO Create A53 Linux Project in S32DS for Vision, beginning at step 9. 😎 Click Resume  The program takes the input H264 encoded image img_1280x960.h264 located in the /home/root/vsdk/data/common folder on the Linux BSP and outputs it on the display The output image should look like below.

PEmicro’s GDB Server can take advantage of four useful SWO debug tools: Power Measurement SWO ITM Console SWO Data capture Real-Time Expressions. This document describes how to enable and use these features. Note: To set up streaming for SWO debug features, the user should check the “Enable Streaming” checkbox in Debug Configurations during setup. Then the port should be specified in the Streaming Server Port text box. Hardware Requirements The following versions (or later) of PEmicro hardware interfaces are required to take advantage of SWO streaming functionality: Multilink FX Rev. C Multilink Universal Rev. D Multilink ACMP Rev. B Real-Time Power Measurement To enable Power Measurement capture, an active debug session must already be in process. Click the Gear Icon on the title bar of the PEmicro "Power Measurement” window. Select the frequency of data capture and check the Enable box. After clicking OK, Power Recording is now active. Note:    The Multilink FX debug probe is required for Real-Time Power Measurement Power Configuration Dialog The next time the target MCU is run, real-time power measurement readings will be shown. The user can start/stop power recording, zoom, export data, and more SWO Printf Console The SWO Printf Console will display messages which are streamed through the SWO pin and captured by the Multilink. There are two main configuration steps needed to leverage this feature. First, the project must be configured to re-direct the printf() statements to the SWO Printf peripheral. This is done at project creation time. Second, the green "Play" button on the SWO ITM Console needs to be clicked during an active debug session. This will cause data collection of SWO printf information to occur on the next Resume. Once data is streaming, the red “Stop” button will stop data streaming. Printf() Statements Displayed In SWO ITM Console The Multilink automatically measures the data communication rate on the SWO pin and adjusts to it automatically. This auto-detect sequence is done each time the processor is stopped in debug mode. If the running code changes the core frequency, a breakpoint should be set after the frequency change so the Multilink can adjust to the new SWO communications rate (which is a function of the core frequency). SWO Data capture The SWO Data view allows the user to configure variables to be tracked such that any reads and writes to these variables are captured and streamed to the Multilink via the SWO pin. This view shows all of the realtime access which have occurred along with the timing of the different accesses. For SWO data, there is a bit more setup.  The user needs to select the 'Eyeglasses+' symbol which will bring up a popup of Add datawatch items.  Simply enter the information of the different variables to be tracked. Up to four separate variables can be tracked simultaneously. In this example, we select that we wish to capture read and writes of the ledsOn and seconds variables. Once added, the user needs to select which watches data will be captured by checking the "Enable trace" boxes in the SWO Data window and then click the Green Arrow to set the program to start capture on Resume.Upon resuming the application, the right side of the window will show the access which are occurring. Note that this happens in real-time; the microcontroller is not stopped when accesses occur (i.e. the is separate from data breakpoints). Variable Read/Writes Displayed In Real Time The Multilink automatically measures the data communication rate on the SWO pin and adjusts to it automatically. This auto-detect sequence is done each time the processor is stopped in debug mode. If the running code changes the core frequency, a breakpoint should be set after the frequency change so the Multilink can adjust to the new SWO communications rate (which is a function of the core frequency). Real-Time Expressions This view is similar to the standard Eclipse "Expressions" window with the exception that its contents will update in real-time without the device being halted in debug mode. Just add the appropriate variables to the Real Time Expressions window and you will see them updating in real-time. Add Variables To Real-Time Expressions Windows

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio 3.1  Update 190708          What is new? S32 Design Studio Platform Package 3.1.2 S32 Design Studio Platform Tools Package 3.1.2 Updated S32 Debugger and S32 Flash tool to support S32S247TV NXP GCC for Arm Embedded Processor build 1620 S32S2xxTV Development Package 3.1.2 Integrated S32 SDK EAR 0.8.0 for S32S (Windows only), S32 Configuration Tool IVT and DCD tools S32V2xx Development Package 3.1.1 Integrated S32 SDK for S32V23x RTM 1.0.0 (Windows only) Vision Extension Package for S32V2xx 1.0.0 This is a cumulative update - it is applicable to S32 Design Studio 3.1 Installation instructions The update is available for online (via Eclipse Updater) or offline installation (direct download link)  online installation:  go to menu "Help" -> "S32DS Extensions and Updates" dialog  select from available items and click "Install/Update" button   offline installation:   go to S32 Design Studio product page -> Downloads section or use direct link to download the update archive zip file Start S32 Design Studio and go to "Help" -> "S32DS Extensions and Updates" Add a new "Add.." S32DS Software Site and browse to select the downloaded update archive .zip file you downloaded in the previous step         Select from available items and click "Install/Update" button. This will start the update installation process.

S32DS contains many example projects from which you can learn how S32 can be used with the help of the Vision SDK to develop vision applications. The example projects contain generated and hand-written code, which utilize the Vision SDK to demonstrate a workflow using S32DS. In this document, the procedure for creating a project from one of the provided APEX2 examples through to execution on the EVB is detailed. This tutorial was made with S32DS Version 3.2 and VSDK Version 1.5.0. 1) Launch S32DS 2) Select 'File -> New -> S32DS Project from Example' 3) Select apex2_rotate_180 project 4) Click Finish 5) If not in the C/C++ Perspective, switch over by clicking on the icon showed below (Hovering over the correct icon should display 'C/C++'). The current perspective is displayed on the top bar. 6) Select apex2_rotate_180: A53 in the Project Explorer panel. Build the project using build config 'TEST_A53'. 7) Start a debug session using method as described in HOWTO: Create A53 Linux Project in S32DS for Vision, beginning at step 9. 😎 Click Resume  The program takes the input image  in_grey_256x256.png located in the /home/root/vsdk/data/common folder on the Linux BSP and rotates it 180 degrees The output image out.png is located inside the /home/root/vsdk folder 9) To see the output, access the device from the remote systems view. If this has not been set up, complete the steps described in HOWTO: Access Linux BSP file system on S32V234-EVB from S32DS for Vision.  10) Open both the input and output files from the remote systems view to verify that the program ran correctly.

Trace functionality is supported in the S32 Debugger for A53 cores on the S32V, RAM-target builds. With Trace, you can record some execution data on an application project and then review it to determine the actions and data surrounding an event of interest.   This document outlines the method to begin using Trace on the S32V234 device. We start by creating a project on which to execute the trace, however, you may start at step 2, if you are starting with an existing project. Please note, you will need to have debug configurations for the S32 Debugger setup for each core which you intend to capture trace. If you do not already have such configurations, you may copy them from another project and adapt them to the new project as shown in HOWTO: Add a new debugger configuration to an existing project.   Create a new application project, selecting the 'S32V234 Cortex-A53' processor and 'S32 Debugger' options.  There should now be 4 new application projects in your workspace. One for each A53 core. The first core of the S32V234, A53_0_0, is also a possible boot core, so this project will have build configurations for RAM and FLASH. The other A53 cores (0_1, 1_0, 1_1) will not. Build all projects for Debug_RAM and check that they build clean before proceeding. Open 'Debug Configurations...' and select the 'Debug_RAM' configuration for the first core (A53_0_0_Debug_RAM_S32Debug). Select the 'Debugger' tab. Enter the Debug Probe Connection settings as appropriate for your hardware setup. Now select the Launch Group configuration for 'Debug_RAM'. It is important to use the launch group to start the debug for each core, not just because it makes it easier, but also because it is necessary to allow for some delay after the first A53 core is started before bringing the other A53 cores from reset to debug state. Press Debug Once the code is loaded to the target and the debugger has started each core and executed to the first line within main(), then it is ready to perform any of the standard debug functions including Trace. Trace does not start automatically, it must be turned on before it will start logging data. To do this, it is necessary to add the view 'Trace Commander'. It can be found by either Window -> Show View -> Other, then search for 'Trace Commander' or enter 'Trace Commander' in the Quick Access field of the toolbar and select Trace Commander from the list. The Trace Commander view will show in the panel with the Console, Problems, etc. Double-click on the tab to enlarge it. Click on the configure button to change settings. Click on the Advanced Trace Generators configuration button For each core to be logged, set the associated ELF file. Select the core, click Add, then '...', and select the elf file for that core. Select Data Streams. Now it is possible to change how the data is captured. Since the buffers have finite memory, they can be set to collect data until full, or to overwrite. If set to One buffer, the data will be collected until the buffer is full, then data collection stops. It is useful to gather data when starting logging from a breakpoint to gather data during execution of a specific section of code. If set to Overwrite, the data collection continues and starts overwriting itself once the buffer is full. This is useful when trying to gather data prior to a breakpoint triggered by a condition.  To turn on the Trace logging, click on the 'Close this trace stream' button. The Trace is now enabled. To collect trace data, the cores must be executing. First double-click the Trace Commander tab to return to the normal Debug Perspective view. Then, one by one, select the main() thread on each core and press Resume to start them all. If collecting from a breakpoint, start the code first with Trace disabled, wait for the breakpoint to be reached, then enable the Trace. Allow the cores to run for a period of time to gather the data, then press Suspend on each one until they are all suspended. Look to the Trace Commander tab to see that the data icon is no longer shaded and click on it to upload the trace data. A new tab, Analysis Results, has appeared. Double-click this tab to see it better. Click on the arrow next to ETF 0 to show the data collected in the trace buffer. Notice there are 5 separate views on the captured data: Trace (raw data), Timeline, Code Coverage, Performance, and Call Tree. Trace - this is the fully decoded trace data log Timeline - displays the functions that are executed in the application and the number of cycles each function takes, separate tabs for each core Code Coverage - displays the summarized data of a function in a tabular form, separate tabs for each core Performance - displays the function performance data in the upper summary table and the call pair data for the selected function and it's calling function Call Tree - shows the call tree for identification of the depth of stack utilization See the S32DS Software Analysis Documentation for more details on settings, ways to store the logged data, etc.

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture v2.1 Update 2          What is new? Integrated S32 SDK RTM-SR 3.0.1 (see the S32 SDK release notes) This is a cumulative update - it includes all the content of previous updates (Update 1 ) Installation instructions The update is available for online installation (via S32DS Extensions and Updates) or offline installation (direct download link)  installation:  go to menu "Help" -> "S32DS Extensions and Updates" dialog  select from available items and click "Install/Update" button offline installation:   go to S32 Design Studio for Power product page -> Downloads section or use direct link to download the update archive zip file  Start S32 Design Studio and go to "Help" -> "S32DS Extensions and Updates", then click 'Go to Preferences' link And add a new site "Add..." repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select the 'RSDK 1.3.0 for S32R274 and S32R372' package and click "Install/Update" button.   This will start the update installation process.

So you have created a project in S32DS for Vision with target of S32V234 Cortex-A53 APEX2/ISP Linux . You have built the project and now want to execute it on the S32V234-EVB, which is running the Linux BSP from the VSDK on a SD card. There are many ways to do this, however, the simplest is to use the built-in support within S32DS to run and/or debug over an Ethernet connection to the Linux BSP OS running on the EVB. In order for S32DS to connect to the Linux BSP OS, the following steps should be followed: 1) First, we must complete the steps to Setup S32V234 EVB for debugging with Linux BSP. 2) With the Linux running on the EVB, start a terminal program (for ex. PuTTY) on your PC 3) Set Connection type to Serial 4) Set speed to 115200, Data bits 8, Stop bits 1, Parity None 5) Set Serial line to the COM port associated with the USB port setup in step 1 of this document. (for ex. COM3) 6) Click Open to start the terminal session 7) Press enter key to bring up login prompt 😎 Log into Linux (login name is "root") 10) Get IP address, enter command:    ifconfig       Make note of the IP address 11) Launch S32DS for Vision. From the C/C++ Perspective, select Run->Debug Configurations... 12) From 'C/C++ Remote Application'. Select '<project_name>_Remote_Linux' debug configuration. 13) Select New to create new debug connection. 14) Select SSH 15) Enter the IP address noted earlier 16) Enter user ID as "root". The Linux BSP uses Password based authentication, but by default, no password is set. So the password can be left blank. 17) Select Finish 19) Select Apply, and then if you wish, Debug