S32 Design Studio Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

S32 Design Studio Knowledge Base

Discussions

      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture v2.1   Update 7           What is new? Integrated S32 SDK for Power Architecture RTM 3.0.2 (see the S32 SDK release notes) This is a cumulative update - it includes all the content of previous updates (Update 1,Update 2 ) Installation instructions The update is available f or 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 a dd a new site "Add..." repository and browse to select the downloaded update archive zip file you downloaded in the previous step Select the 'S32 Design Studio for Power Architecture Device Package' and 'Update with S32 SDK 3.0.2 for Power Architecture' packages and click "Install/Update" button.   This will start the update installation process.
View full article
UART0 communication is supported in the latest version of MPC5746R Bootloader .rbf file (attached below) + Supported UART0/LINFlexD_0: PD13-PD14 pins(Speed: 115200b/s)   Tested on the dev boards:   Development Board MPC5746R-252DC MPC57xx-MOTHERBOARD Processor PPC5746RTMMT5 - 1N83M  
View full article
Example contains modified startup code to be able run in BookE only mode. For GNU gcc and as you need to add -mno-vle parameter in project properties:  For debugging with PE Micro you need to use modified Initialization script in Advanced options: Please note that there is no STD C BookE only library available:
View full article
Quick Fix is a feature of the Java editor in Eclipse which enables a user to resolve problems found in the Java code of their project. This feature is available to be used within S32 Design Studio for some problems. Such problems will be identified with the 'light bulb' icon in the description field, as shown below: For example, such problems sometimes occur when importing a project created in a previous version of S32 Design Studio, are provided from another user, or some files in a project have become corrupted. To resolve issues identified with the 'light bulb' icon, right-click on the problem and from the pop-up menu, select 'Quick Fix'.  The Quick Fix menu will appear, providing the available solutions for the problem. In most cases, there will be just one solution. Click finish to implement the fix. In some cases, more information will be required from the user to complete the fix. Complete the form to provide the additional information, then click OK. Now the problem should be resolved.
View full article
Migration guide You can use a project that was created in an earlier version of S32 Design Studio for Power Architecture 2.1 , but it requires changes according to the new product directory structure. The following explains how to import and configure your project. Click File > Import... > General > Existing Projects into Workspace , then click Next . Click Browse... and browse to the project location, click OK , select the Copy projects into workspace option, then click Finish . If the Problems view displays the following warning: "The hardware settings required for project not found", right-click it and select Quick Fix on the context menu. Select the project from the Resource list and click Finish . Specify the Family, Device and Core settings. Click OK. For the EWL source code debugging, open the debug configuration settings, switch to the Source tab, select Path Mapping: EWL and click Edit . Update the e200_ewl2 location: Compilation Path: e200_ewl2 Local file system path: <s32ds_for_power_dir>\S32DS\build_tools\e200_ewl2 Depending on the project type, update the following environment variables and file locations. For projects with the SPT tools: open the project settings, click C/C++ Build > Settings > SPT Assembler . Update the SPT include files location: "${SPT_TOOLCHAIN_DIR}/inc" for the SPT1 tools, "${SPT2_TOOLCHAIN_DIR}/inc" for the SPT2 tools, and "${SPT2.5_TOOLCHAIN_DIR}/inc" for SPT2.5 accordingly. For projects with the attached PEx SDK: after you import the project, the path validation notification appears. Click Yes to open the S32 SDK Specific properties page and update SDK path (click Browse and navigate to the <s32ds_for_power_dir>/S32DS/software/<sdk_name> folder). If you import the project example, additionally open the project settings, click C/C++ Build > Build Variables and update the S32_SDK_PATH value: ${eclipse_home}/../S32DS/software/<sdk_name> . For projects with the attached FreeMaster or AMMCLIB SDKs: open the project settings, click C/C++ Build > Settings and update the SDK paths on the following pages: Standard S32DS C/C++ Compiler > Includes Standard S32DS C/C++ Linker > Libraries Standard S32DS Assembler > General For the FreeMaster SDK project, additionally navigate to the project folder, open the .project file, and update the linkedResources locations. If some errors and warnings still occur, try to close and reopen your project, or restart S32DS for Power Architecture .
View full article
      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for ARM® 2018.R1   Update 11           What is new? S32K1xx SDK RTM-SR 3.0.2: SBC driver now supports UJA1169 as well as both UJA1168 and UJA1168A SBC variants (S32 SDK release notes) AMMCLIB v.1.1.18 for S32K1xx, KEA and S32V234 (AMMCLIB release notes) This is a cumulative update - it includes all the content of previous updates ( Update 1,   Update 2,   Update 3,   Update 4,   Update 5,   Update 6,   Update 7, Update 8, Update 9, Update 10  ) Installation instructions The update is available f or  online   (via Eclipse Updater) or   offline  installation (direct download link)   installation:  go to menu  "Help" -> "Install New Software..." dialog   select predefined update site   "S32DesignStudio -   http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_ARM_2018.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.
View full article
Introduction In this document, we will discuss the S32DS Extensions & Updates tool and how to use it to install the device support you need. S32 Design Studio for S32 Platform has been designed to allow users to customize their installation, enabling them to integrate support for just the NXP devices they need and just the tools they need. With the new modular design, parts of the tool have been moved into one of 4 different package types. The Platform and Tools Packages are default packages which are included as part of the base install, cannot be uninstalled, however, they can be updated. The Platform package contains the base components of the IDE, modular installer, general documentation and integration mechanisms. The Tools Package contains the compilers, debuggers, and MSYS2. The Development Package contains hardware specific support such as New Project Wizard, S32 Configuration Tools, SDKs and Libraries. The Extension Package contains Accelerator Compiler, Debugger, Graph Tool and advanced SDKs. Downloading the various components from our cloud-based update server, allows you to assemble and complete the customized installation of the tools and software to meet your development needs. It is also via the update server that the updates and bug fixes will be provided. And of course, all of these will be available as downloads from our product page for users who are installing to an offline PC. S32DS Extensions and Updates Menu When you first launch the S32 Design Studio for S32 Platform, you are presented with the S32DS Extensions and Updates menu. This menu provides a listing of the add-on packages which have been installed, those that are available to be installed, and those which have updates available to be installed. In the panel to the right is displayed detailed information specific to the package which is selected in the panel to the left. If there is an update available for the selected package, the currently installed version number will be shown on the left and the update version number will be shown on the right. Online Package Installation Setup If your PC is connected to the internet, then it will link to NXP's update server (http://www.nxp.com/lgfiles/updates/Eclipse/S32DS_3.2) and any new or updated packages will be automatically added to the list. See Package Installation section below for installation procedure and details. Offline Package Installation Setup If your PC is not connected to the internet, you must first download the desired packages from the NXP website, in the form of an archive file, to a separate PC and have them transferred to your target PC. Then you would select the link 'Go to Preferences' and add each downloaded archive file as a separate software site. After selecting OK, you will see the new packages contained within the archive files listed. Procedure: Go to  S32 Design Studio for S32 Platform download page and select   Download for the package or update you need. Sign in to your account. Select the package name Select 'I Agree' to accept the Software Terms and Conditions Select the filename of the package to begin the download. You will be asked to select a location to save the downloaded file. Once the file is downloaded, it must be installed within S32 Design Studio. Launch S32DS and wait for the S32DS Extensions and Updates window to appear. Then select the 'Go to Preferences' link. The Preferences window appears. Select the 'Add...' button to add a new software site to the list. The file you downloaded will be a software site. Now the Add Site window appears. Since the downloaded file is an archive of type ZIP, the 'Archive...' button should be used to select it. Navigate to the location where the file was saved. Select the downloaded file and then Open. Enter a name for the site you are adding, this will make it easier to recognize later. Suggest using the name of the package as listed on the Product Page, Downloads section. Then select OK. Now the downloaded file has been added as a new site. Select OK to return to the main S32DS Extensions and Updates window. Now the new package(s) will appear in the S32DS Extensions and Updates window, just as it would from the update server.  See  Package Installation   section below for installation procedure and details.   Package Installation To install the new packages or updates, check the box to the left of the desired package in the left panel and select 'Install/Update'. The tool will automatically detect any dependencies on other packages and select them to meet all requirements for the installation. Follow the prompts and the packages will be installed, followed by a request to restart S32 Design Studio. Dependencies and Errors If there are dependencies between two or more updates, the tool will detect this and inform you of the package which cannot yet be installed. If you try to install a package which is not compatible with the version of S32 Design Studio you have installed, a notice will appear, and the package will not be listed in the S32DS Extensions and Updates menu. Example Dependency Message Example Notice Message - Unsupported Package Uninstalling Unwanted Packages If you no longer need a particular package or installed one by mistake, just check the box next to the package and select 'Uninstall'.   Reinstalling Packages If you believe your installed package has become corrupted, if you accidentally deleted part of it (such as an example project, etc.), or if for any reason you need to restore the package, just check the box next to the package and select 'Reinstall'.   Additional Information If you wish to not see the S32DS Extensions and Updates menu at startup, you can uncheck the box at the lower left. For internet connected PCs, the update server will still be linked and checked for new packages at S32DS startup, but you will no longer see the S32DS Extensions and Updates menu. However, you will still see a notice at the lower right of the tool at startup when new packages are detected. Example of Available Update Notification
View full article
        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for S32 Platform  v3.2         Austin, Texas, USA Sep 30, 2019    The Automotive Microcontrollers and Processors' Embedded Tools Team at NXP Semiconductors is pleased to announce the release of the S32 Design Studio for S32 Platform v3.2.  Here are some of its major new features: Multiple builds of the GNU tools can be installed. The SDK integration is provided with additional software packages. The SDK packages can be installed and updated with the S32DS Extensions and Updates tool. The GHS toolchain support is provided by the project wizard (available for particular devices). The CMSIS-DAP debugging is supported by particular devices. The UART communication speed of S32 Flash Tool is improved. The latest versions of P&E debugger plug-in and drivers are provided. S32 Debugger provides OS Awareness support for FreeRTOS and OSEK. S32 Debugger provides preliminary support for secure debugging with the Password and Challenge/Response authentication methods. New type of Launch Groups is defined for S32 Debugger, which allows you to create S32 Debugger specific configurations and use the new "Wait for stop on breakpoint" post launch action. The SDK migration support is provided to upgrade an SDK version attached to the project. The S32DS Extensions and Updates tool notifies about dependencies and incompatible packages. The progress bar is displayed for the S32 Debugger flash programmer. S32 Design Studio Versions   S32DS IDE for S32 Platform S32DS IDE for Arm® S32DS IDE for Power Architecture® S32DS IDE for Vision Devices Supported S32V23x S32K1xx MPC56xx S32V234 S32S247TV KEA MPC57xx   S32 Platform Devices MAC57D54H S32R2xx/S32R3xx   Integrated NXP Tools S32 Flash Tool FreeMASTER FreeMASTER DDR stress tool DDR stress tool     Integrated Configuration Tools S32 Configuration Tools Processor Expert Configuration Tool Processor Expert Configuration Tool  DDR configuration tool Pins Wizard Pins Wizard Pins Wizard Clocks configuration Peripheral/Drivers configuration   Peripheral/Drivers configuration   Peripheral/Drivers configuration   DCD/IVT configuration       DDR configuration tool       Integrated NXP Software S32 SDK S32K1 SDK S32 SDK Vision SDK FreeRTOS FreeRTOS FreeRTOS Linux BSP AMMCLib for S32V23x AMMCLib for KEA and S32K AMMCLib for MPC56xx and MPC57xx MCUs   Vision SDK KEA SDK Radar SDK Linux BSP MQX OS/MQX Drivers for MAC57D54H     Compilers: NXP GCC 6.3.1* NXP GCC 6.3.1* NXP GCC 4.9* NXP GCC 6.3.1* GreenHills GreenHills GreenHills   IAR IAR Diab     GCC 4.9*     DEBUGGERS Built-in GDB interface : S32 Debugger/ S32 Debug Probe P&E Multilink/Cyclone/OpenSDA P&E Multilink/Cyclone/OpenSDA S32 Debugger/S32 Debug Probe P&E Multilink/Cyclone/OpenSDA Segger J-Link   P&E Multilink/Cyclone/OpenSDA DEBUGGERS supported: Lauterbach Lauterbach Lauterbach Lauterbach   iSystem iSystem   IAR PLS   Host Operating Systems: Microsoft Windows® 7/8/10 64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Microsoft Windows® 7/8/10 32/64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Microsoft Windows® 7/8/10 32/64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Microsoft Windows® 7/8/10 32/64-bit OS (with 32-bit binaries)  – Ubuntu 14.04, 16.04 (64 bit) – Debian 8 (64 bit) – CentOS 7 (64 bit) Vision specific tools : NXP APU Compiler     NXP APU Compiler ISP assembler     ISP assembler ISP and APEX graph tools     ISP and APEX graph tools Radar specific tools :     SPT assembler       SPT Explorer/ SPT graph tool   Complete S32 Design Studio for S32 Platform v3.2 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 packages available are S32S2xxTV and S32V2xx. 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  
View full article
Condition:  I am trying FreeRTOS using S32K118 EVB and run in DEBUG mode. When I set the break point in vTaskDelay and press Resume for the first time, there is a smooth stop at the break point. The second time I press Resume, the debugger should enter the same break point again, but there is no response. Then I press Suspend and can't press Resume again, at this point I can only leave. However, I am free to run this project with no problem, what's wrong? Analysis: This is due to an access of DDR memory region which is not initialized by default project settings. Solution: To resolve it, a macro initializing the DDR memory should be selected to run at the beginning of a debug session. A user should go to Advanced Options dialog and check "Enable initialization script". Our DDR init macros can be found at the following location within S32DS3.2 layout: eclipse\plugins\com.pemicro.debug.gdbjtag.pne_4.2.8.201909091700\win32\gdi\P&E\supportFiles_ARM\NXP\S32Vxxx\S32V234M100_DDR3_EVB29288.mac. Please note that the type of the macro might depend on the revision of the board and S32V23x device one is working with. I am also attaching a picture of debug configuration and Advanced Options dialog with all the settings in place.
View full article
Condition: Enable Stopindebug bit for PIT and STM module. Counter could be stop when debug project, but when i set debug mode on, counter not count, project can't be run. Analysis: In order for PIT timer to count when a FRZ bit is enabled, all cores on S32V23x devices need to be running. The reason why it does not work out of the box with current plugin configuration, is because we halt all device cores, which is especially necessary for RAM based projects. Solution: We created a start-up macro to keep all cores running when S32V232M80 or S32V234M100 debug sessions are launched. In order to use it, please go to the following directory without your S32DS3.2 IDE: eclipse\plugins\com.pemicro.debug.gdbjtag.pne_4.2.8.201909091700\win32\gdi\P&E\supportFiles_ARM\NXP\S32Vxxx. Please rename S32V234M100_All_Cores_Running.mac or S32V232M80_All_Cores_Running.mac to default macro names, saving existing default macros in renamed form, or a separate location: S32V234M100.mac or S32V232M80.mac.separate location: S32V234M100.mac or S32V232M80.mac.
View full article
Version of MPC5777C Bootloader .rbf file for BookE (non-VLE) applications  + Supported UART0/eSCI_0(J20 on DB): GPIO89-90 pins(Speed: 115200b/s) + Supported  MCAN0(J5 on MB):  GPIO83-84 pins(Speed: 500Kb/s) + BookE (Non-VLE) code 
View full article
      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 f or 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 a dd 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.
View full article
CAN communication is supported in the latest version of MPC5777C Bootloader .rbf file (attached below) + Supported UART0/eSCI_0(J20 on DB): GPIO89-90 pins(Speed: 115200b/s) + Supported  MCAN0(J5 on MB):  GPIO83-84 pins(Speed: 500Kb/s)   Tested on the dev board:   Motherboard MPC57xxMB Development Board X-MPC5777C-516DS Processor SPC5777CDMMO3 3N45H Also included is a version of the .rbf file where the delay before app start is 1 second (instead of 3 seconds)
View full article
When a new application project is created using the New Project Wizard, it is possible to select the debugger to be used. This results in the associated debugger configurations being created within the new project. But what if support for multiple debuggers is required or it is desired to switch to a different debugger? There is an easy way to resolve this. It is as simple as creating another new application project, selecting the new debugger to be supported. Then either directly modifying or copying then modifying the debug configurations to support instead the previously existing project. This minimizes the effort by benefiting from the automation of the New Project Wizard. Detailed below are the steps to add a new debug configuration. Add S32 Debugger configuration Create new project New -> S32DS Application Project New Project Wizard, processor and toolchain page Enter a project name Select the device and core to match the existing project If necessary, select the toolchain to match the existing project Click Next New Project Wizard, cores and parameters page Select the number of cores to match the existing project Select the debugger, S32 Debugger If necessary, select other parameters to match the existing project Click Finish Open existing project which does not already have the S32 Debugger debug configurations (for this demonstration, we will use the hello_world_s32v234 example project from the S32 SDK) Copy debug configurations and modify settings to adapt to existing project Run -> Debug Configurations... Debug Configurations window Within the S32 Debugger grouping, select the debug configuration for the new project which corresponds to the build configuration and core of the existing project Change the name of the debug configuration. Change the portion of the name containing the project name to match the name of the existing project. Main tab Project field Click Browse... Select existing project C/C++ Application Click Search Project... Select the ELF file Common tab Save as field Click Browse... Select {existing_project_name}\Project_Settings\Debugger Debugger tab Debug Probe Connection Setup connection parameters Click Apply Repeat as needed for all core/build config options The existing project now has the S32 Debugger configurations and is ready for debug with the S32 Debug Probe.
View full article
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.
View full article
You can use a project that was created in an earlier version of S32 Design Studio, but it requires changes to the build configuration settings and the project structure. Migrating ISP Application Project The following explains how to configure your ISP application project. Click File > Import... > General > Existing Projects into Workspace, then click Next. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish. Remove all VSDK specific settings from the build configuration settings: Right-click the project in the Project Explorer view and click Properties on the context menu. Open C/C++ Build > Settings and remove the following settings for the A53 build configuration: Standard S32DS C Compiler/Standard S32DS C++ Compiler > Preprocessor: Remove VSDK_UMAT_USE_OPENCV from the Defined symbols list. Standard S32DS C Compiler/Standard S32DS C++ Compiler > Includes: Remove all the ${S32DS_VSDK_DIR} paths from the Include paths list. Standard S32DS C++ Linker > Libraries: Remove all libraries from the Libraries and Library search paths lists. Click SDKs on the left pane of the project properties, then attach VSDK_MODULE_WIN to the A53 build configuration. Remove typedefs.h from the A53_inc folder. Migrating APEX2 Application Project The following explains how to configure your APEX2 application project. Click File > Import... > General > Existing Projects into Workspace, then click Next. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish. Remove some build configuration settings: Right-click the project in the Project Explorer view and click Properties on the context menu. Open C/C++ Build > Settings and remove the following settings for the A53 and TEST_A53 build configurations: Standard S32DS C Compiler/Standard S32DS C++ Compiler > Preprocessor: Clear the Defined symbols and Undefined symbols lists. Standard S32DS C Compiler/Standard S32DS C++ Compiler > Includes: Remove all the ${S32DS_VSDK_DIR} paths from the Include paths list. Standard S32DS C++ Linker > Libraries: Clear the Libraries and Library search path lists. Remove the following settings for the APU build configuration: APU C Compiler/APU C++ Compiler > Preprocessor: Clear the Defined symbols lists. APU C Compiler/APU C++ Compiler > Includes: Remove all the ${S32DS_VSDK_DIR} paths from the Include paths list and clear the Include files list. APU C++ Linker > General: Remove the script file. APU C++ Linker > Libraries: Clear the Libraries and Library search path lists. Remove the following settings for the EMU and TEST_EMU build configurations: Cross G++ Compiler > Preprocessor: Clear the Defined symbols list. Cross G++ Compiler > Includes: Remove all paths except the ${ProjDirPath} ones from the Include paths list. Cross G++ Linker > Libraries: Clear the Libraries and Library search path lists. Replace the Project_Settings/Scripts/gen_apu_load.tcl file with a copy from any APEX2 project created in new S32 Design Studio. Remove typedefs.h from the A53_inc folder and S32V_APU.lcf from Project_Settings/ Linker_Files . Right-click the project in the Project Explorer view and click SDKs on the context menu. Attach VSDK_MODULE_WIN to all build configurations. Emit the source code from the updated Visual Graph Tools projects. If you want to debug your application using APEX2 Emulator, update the debug configuration settings: Right-click the project in the Project Explorer view and click Debug As > Debug Configurations... on the context menu. In the left pane, open the configuration under C/C++ Application. In the right pane, go to the Environment tab. Edit the PATH value: ${S32DS_GCC_TOOLCHAIN_DIR};${S32DS_OPENCV_DIR}/x86/mingw/bin  Then select the Replace native environment with specified environment check box. Go to the Debugger tab and update the GDB debugger location: ${S32DS_GCC_TOOLCHAIN_DIR}/gdb.exe Migrating APEX2 Graph Project The following explains how to update your APEX2 graph diagram. Click File > Import... > General > Existing Projects into Workspace, then click Next. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish. Open the graph diagram. In the Palette pane, drag Add Kernels and drop it to the canvas. Select the kernel used in your old project. You can start typing the kernel name in the search box or use the filtering button to specify the kernel location. Click OK. Remove your old kernel and connect the Input and Output elements with the respective ports of the newly added kernel. Repeat the 5-7 steps for each kernel on the diagram. Right-click the canvas and click Validate diagram on the context menu. If a validation problem was found, the Problems view displays an error or warning. The element that caused the error is marked on the diagram with a red cross icon, so you can easily find and fix it. Migrating APEX2 Program Project The following explains how to update your APEX2 program diagram. Click File > Import... > General > Existing Projects into Workspace, then click Next. Click Browse... and browse to the project location, click OK, select the Copy projects into workspace option, then click Finish. Open the program diagram. In the Palette pane, drag Process from Graph and drop it to the canvas. Select the updated graph. Click OK. Remove your old process and connect the Inlet and Outlet elements with the respective ports of the newly added process. Repeat the 5-7 steps for each process on the diagram. Right-click the canvas and click Validate diagram on the context menu. If a validation problem was found, the Problems view displays an error or warning. The element that caused the error is marked on the diagram with a red cross icon, so you can easily find and fix it.
View full article
      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture v2.1   Update 1           What is new? Integrated Radar SDK RTM 1.3.0 (see the Radar SDK release notes) Installation instructions The update is available f or 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 a dd 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.
View full article
      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 f or  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.
View full article
        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture v2.1         The Automotive Microcontrollers and Processors’ Embedded Tools Team at NXP Semiconductors, is pleased to announce the release of the  S32 Design Studio for Power Architecture version  v2. 1. It is the successor of S32 Design Studio for Power 2017.R1. - the versioning scheme has changed. Release content   ( What is new? ) Eclipse Neon 4.6 Framework GNU Build Tools for e200 processors bld=1607 rev=gceb1328 (support VLE and BookE ISA, based on gcc 4.9.4 [1.February 2019], binutils 2.28 and gdb 7.8.2) - see the complete GCC release notes Libraries included: newlib, newlib-nano and Freescale EWL2 P&E Multilink/Cyclone/OpenSDA (with P&E GDB Server) -   updated (v1.7.2.201709281658) New Project wizards to create application and library projects and projects from project examples for supported devices Peripherals Register and Special Purpose Registers View Fully integrated S32 SDK RTM v.3.0.0 (Windows only) . For the details on the feature set  of SDK please refer to SDK Release notes attached and Reference Manuals ( Please note that SDK has Early Access Release status, which means that there could be some limitations and/or issues. Also note, the SDK is available for Windows host only). SDK management included: o   FreeMASTER  Serial Communication driver (v2.0 August 31th 2016) o Automotive Math and Motor Control Libraries(v1.1.15) o Support for importing MCAL configuration to a custom SDK o An SDK can be attached to a library project using the project wizard Windriver Diab, and GreenHills compiler support by new project wizard (The Green Hills Software (GHS) compiler support depends on the availability of the Eclipse plug-in integrating GHS compiler compatible with the Eclipse Neon. Full support for the Green Hills Software compiler Eclipse Neon-compatible plug-in within S32DS for PA 2.1 was not validated in time for this release.) Lauterbach, iSystem, and PLS debuggers support by new project wizard (The plugins to support Diab, iSystem, Lauterbach, and GreenHills are not included and have to be installed from the corresponding update site or installation.) Kernel Aware debugging for FreeRTOS, eCOS, OSEK Devices supported: S32R274 S32R372 MPC5775B, MPC5775E MPC5775K, MPC5774K MPC5746R, MPC5745R, MPC5743R MPC5777M MPC5777C MPC5748G, MPC5747G, MPC5746G MPC5744B, MPC5745B , MPC5746B , MPC5744C , MPC5745C, MPC5746C MPC5744P, MPC5743P, MPC5742P, MPC5741P MPC5601P, MPC5602P, MPC5603P, MPC5604P MPC5644B, MPC5644C, MPC5645B, MPC5645C, MPC5646B, MPC5646C MPC5601D, MPC5602B, MPC5602C, MPC5602D, MPC5603B, MPC5603C, MPC5604B, MPC5604C, MPC5605B, MPC5606B, MPC5607B MPC5606S MPC5604E MPC5644A, MPC5642A MPC5643L MPC5676R MPC5632M, MPC5633M, MPC5634M MPC5674F MPC5673K, MPC5674K, MPC5675K Collateral Getting Started page The S32DS Extensions and Updates tool Migration guide to help migrate projects from an earlier version to S32 Design Studio for Power Architecture 2. Bug Fixes For detailed list of the GNU Tools bug fixes, refer to the release notes located in S32DS/ build_tools/powerpc-eabivle-4_9/ Fixed the semihosting issues with the EWL and NewLib libraries Fixed the FLASH programming algorithm for MPC5744P Added missing linker script sections for MPC5748G Fixed reading values from the peripheral bridge A registers for MPC5634M Fixed access to the RAM memory for MPC5634M Removed unavailable addresses from the MPC574xB linker files Added the -fstrict-volatile-bitfield compiler option to the project settings Fixed secure connection to MPC5744P Disabled RTTI for EWL library due to incompatibility with the GNU tools Fixed importing/exporting projectinfo.xml with library settings Complete S32 Design Studio for Power Architecture v2.1 release notes are available   here Installation Notes To download the installer please visit the S32DS for Power Architecture product page:  downloads section. The installer requires the the NEW Activation ID to be entered during the installation. You should receive an email that includes your Activation ID after starting the installer downloading process: Technical Support S32 Design Studio issues are tracked through the S32DS Public NXP Community space: https://community.nxp.com/community/s32/s32ds    
View full article
CAN communication is supported in the latest version of MPC5744P Bootloader .rbf file (attached below) + Supported UART1/LINFlexD_1(OpenSDA on DevKit): PD9-PD12 pins(Speed: 115200b/s) + Supported  CAN_0 (J5 on DevKit):  PB0-PB1 pins(Speed: 500Kb/s)   Tested on the dev boards:   Development Board DEVKIT-MPC5744P MPC5744P-144DC MPC5744P-257DC Processor MPC5744P-FML09 1N15P MPC5744P-FMLQ8 0N65H PPG5744P-FMMM8 0N65H  
View full article