S32 デザインスタジオ・ナレッジベース

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

S32 Design Studio Knowledge Base

ディスカッション

ソート順:
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.
記事全体を表示
PE Micro is not able erase unused FLASH block - typically if your application resist in Large block and Low/Mid block is used for data storage. As a workaround you can flash empty s-record into desired area.  Create new empty project for MPC5777C for flashing custom .srecord Copy empty s-record (in attachment) into project folder. If you need different address range or s-record values - feel free modify attached python script and generate your own s-record.  Open debug configuration and modify C/C++ Application to empty s-record Add custom flash algorithm nxp_mpc5777c_1x32x64k_eeprom_highspeed.pcp via Debug -> Advanced Options. Scripts are lcated in [S32DS_INSTALL_DIR]\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_1.7.3.201803261737\win32\gdi\P&E\ Start debug session. You can check if memory is rewritten properly (in this case I write zeroes to Low/Mid block): 
記事全体を表示
      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 for Power Architecture v2.1 Update 12          What is new? Integrated S32 SDK for Power Architecture RTM 3.0.3 (replacing 3.0.2) Integrated AMMCLIB 1.1.21 This is a cumulative update - it includes all the content of previous updates (Update 1,Update 2, Update 7, Update 8, Update 10)   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 '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.
記事全体を表示
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.
記事全体を表示
In recent releases of S32DS (Power v2017.R1, ARM v2.0, Vision v2.0) is new feature - you can add custom example into example list by copy example folder into [S32DS_INSTALL]\S32DS\examples path:  If you select New project from example - you can see your recently added project in User Examples folder. You can filter all examples by name or MCU model (for example all examples for S32K148):  Another useful improvement is possibility rename project before is inserted into active workspace. It allows you to have more projects based on the same example: If in your project folder is present description.txt file - the content of the file is shown in Create project dialog:
記事全体を表示
This document shows the step-by-step process to create a simple blinking LED application for the S32R45 family using the S32 RTD AUTOSAR drivers. This example used for the S32R45 EVB, connected via ethernet connection through S32 Debugger. Preparation Setup the software tools Install S32 Design Studio for S32 Platform Install the S32R45 development package and the S32R45 RTD AUTOSAR 4.4. Both of these are required for the S32 Configuration Tools. Launch S32 Design Studio for S32 Platform Procedure New S32DS Project OR Provide a name for the project, for example 'Blinking_LED_RTD_With_AUTOSAR'. The name must be entered with no space characters. Expand Family S32R45, Select S32R45 Cortex-M7 Click Next Click '…' button next to SDKs   Check box next to PlatformSDK_S32RXX_4_0_0_S32R45_M7_0. (or whichever latest SDK for the S32R45 is installed). Click OK And also, uncheck the other cores Cortex_M7_1 ,  Cortex_M7_2.   Click Finish. Wait for project generation wizard to complete, then expand the project within the Project Explorer view to show the contents. To control the LED on the board, some configuration needs to be performed within the Pins Tool. There are several ways to do this. One simple way by double-click on the MEX file. Select the overview tab and disable Pins tool. Make sure to overview tab windows shows settings shown as below.  Here, we are disabling pin tools and using MCAL driver from peripheral tools for using AUTOSAR drivers. Now from Overview menu, select peripheral tools and double click to open it. In the driver sections, “Siul2_Port_1 driver” is the non-AUTOSAR version driver and so it must be replaced. Right click on ‘Siul2_Port_1’ and remove it. Keep osif_1 driver as it is. Click on the ‘+’ next to the MCAL box. Click on the ‘+’ next to the MCAL box again, and Locate and then select the ‘Dio’ component from the list and click OK. Click on the ‘+’ next to the MCAL box again, and Locate and then select the ‘Mcu’ component from the list and click OK. Click on the ‘+’ next to the MCAL box again, and Locate and then select the ‘Port’ component from the list and click OK. Now components tab should show like below : Now we required to configure the different MCAL drivers that we added. Starting with Dio configuration, open the Dio configuration. Now, open the ‘DioConfig’ tab, and Edit Dio Port id to 3 as shown below: Now, in “Dio Configuration” window only, Select  “+” sign adjacent to DioChannel. Then Edit Name to “Digital_Output_LED” and Dio Channel Id to ‘5’ instead of ‘0’. From the schematic for S32GR45 EVB, checking for user LED from the schematic, channel 5 is connected to user LED signal, so we use channel 5 signal line to the chip for the user LED. So, we select the singal line for Dio channel Id 5 for the user LED connected on the S32R45 EVB. Now Select Port tab for Port configuration. And open the Port Configuration tab, and from that open “PortConfigSet” tab. Change the PortPin Mscr to ‘53’ and slew rate to ‘SRE_208MHZ_1_8V_166MHZ_3_3V’ and, PortPin Direction to PORT_PIN_INOUT as shown below: Now, at the bottom you will find the “UnTouchedPortPin ’’ . Click on “+’’ and add PortPins. Now add port pins 0, 1, 2, 3 as per below configuration Now configure MCU component. Select Mcu component in MCAL, and then open the Mcu configuration. In Mcu configuration click on MCUModuleConfiguration and then select “McuModesettingConf” from the dropdown menu as shown below. From McuModeSettingConf, select McuPartitionConfiguration tab. Then open the “McuPartition0Config” tab. And under the McuCore0Configuration or “McuCoreClockEnable” select checkbox and for “McuCoreResetEnable” uncheck the checkbox. Similarly, And under the McuCore1Configuration for “McuCoreClockEnable” select checkbox  and for “McuCoreResetEnable” uncheck the checkbox. Similarly, And under the McuCore2Configuration for “McuCoreClockEnable” select checkbox and for “McuCoreResetEnable” uncheck  the checkbox. After modification it should be as shown below: Now open the “McuPartition1Config” tab. for " Partition1 Clock Enable" select checkmark to true and for " Partition1 Clock Reset Enable" uncheck the checkmark for " CA53 CORE 0 cluster0 Core Clock Enable" select checkmark to true and for " Cortex-A53 Core 0 cluster 0 Clock Reset Enable" uncheck  the checkmark In the McuCore1Configuration, and for " Cortex-A53 Core 1 cluster 0 Clock Reset Enable" uncheck the checkmark In the McuCore2Configuration, for " Cortex-A53 CORE 0 cluster 1 Core Clock Enable" select checkmark to true and for " Cortex-A53 CORE 0 cluster 1 Clock Reset Enable" uncheck the checkmark In the McuCore3Configuration, for " Cortex-A53 CORE 0 cluster 1 Clock Reset Enable" uncheck the checkmark After modification it should be as shown below: Now open the “McuPartition2Config” tab. for " Partition2 Clock Enable" select checkmark to true and for " Partition2 Clock Reset Enable" uncheck the checkmark Now open the “McuPartition3Config” tab. for " Partition3 Clock Enable" select checkmark to true and for " Partition3 Clock Reset Enable" uncheck the checkmark Now the device configurations are complete and the RTD configuration code can be generated. Click ‘Update Code’ from the menu bar. To control the output pin which was just configured, some application code will need to be written. Return to the ‘C/C++’ perspective. If not already open, in the project window click the ‘>’ next to the ‘src’ folder to show the contents, then double click ‘main.c’ file to open it. This is where the application code will be added. Before anything else is done, Initialize the clock tree and apply PLL as system clock, Apply a mode configuration, Initialize all pins using the Port driver by adding – editing code before write code here comment in main function.        /* Initialize the Mcu driver */        Mcu_Init(&Mcu_Config_BOARD_InitPeripherals);        /* Initialize the clock tree and apply PLL as system clock */        Mcu_InitClock(McuClockSettingConfig_0);        /* Apply a mode configuration */        Mcu_SetMode(McuModeSettingConf_0);        /* Initialize all pins using the Port driver */        Port_Init(NULL_PTR); Now replace the logic of for loop as shown below code section in the main function, which will enable the LED blinking for 10 times: You also need to declare and initialize the loop variable uint8 i = 0U; . Then replace the code as below after write your code comment: /*Logic for blinking LED 10 times*/ while (i++ < 10) {           /* Get input level of channels */           Dio_WriteChannel(DioConf_DioChannel_Digital_Output_LED, STD_HIGH);           TestDelay(3000000);           Dio_WriteChannel(DioConf_DioChannel_Digital_Output_LED, STD_LOW);           TestDelay(3000000); } Before the 'main' function, add a delay function as follows: void TestDelay(uint32 delay); void TestDelay(uint32 delay) {      static volatile uint32 DelayTimer = 0;      while(DelayTimer<delay)      {             DelayTimer++;      }      DelayTimer=0; } Update the includes lines at the top of the main.c file to include the headers for the drivers used in the application: Add #include "Mcu.h" #include "Port.h" #include "Dio.h" Build 'Blinking_LED_RTD_AUTOSAR'. Select the project name in 'C/C++ Projects' view and then press 'Build'. After the build completes, check that there are no errors. Open Debug Configurations and select 'Blinking_LED_RTD_with_AUTOSAR_Debug_RAM'. Make sure to select the configuration which matches the build type performed, otherwise it may report an error if the build output doesn’t exist. And make selection as shown in screenshot below. You need to select the ethernet connection for S32 debugger and provide its IP address Click Debug To see the LED blink, click ‘Resume' This code as it will blink the LED 10 times, you can make changes in for loop condition to blink it infinitely.
記事全体を表示
      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 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.
記事全体を表示
Product Release Announcement Analog & Automotive Embedded Systems S32 Design Studio 3.6.4   The Analog & Automotive Embedded Systems (AAES) - Software Development Tools Engineering Team at NXP Semiconductors is pleased to announce the release of the S32 Design Studio 3.6.4 with support for: AMCU AP RAS S32K3 Family S32G Family S32R41 Family S32K1 Family S32ZE Family S32R45 Family S32M2 Family S32N Family S32R47 Family     SAF8xxx Family   Major Features for S32 Design Studio 3.6.4 Installer S32 Design Studio 3.6.4 is delivered with all public NPI's in a single 2.49GB installer to improve first time user experience. Additional packages for alpha customers are available based on Flexera entitlement and can be installed on top of S32 Design Studio 3.6.4 using Extension and Updates. S32DS NXP compiler (GCC) delivery: Starting with S32DS 3.6.4, only GCC 11.4 will be delivered as part of the installer. The older versions of NXP compiler are still available on the web update site https://www.nxp.com/lgfiles/updates/Eclipse/S32DS_3.6 and can be added via S32DS Extensions and Updates. S32DS Modular installer: S32DS 3.6.4 comes with a new custom installation type for both new and upgrade installations allowing users to customize their installation. This change provides greater flexibility and enables a faster, lighter installation tailored to user needs. Note: As part of the new modular setup, components are no longer bundled, and they will not be installed by other packages anymore (e.g. installing a Development package will not update S32Debugger as well), users will have to explicitly select components to be installed/updated. For example, on S32K3xx development package, users must also select the new S32 Design Studio Debugger Core to get the latest debugger updates. S32DS portable installation: S32DS 3.6.4 new installations can be moved in different locations other than the original installation directory and still run without having to change any properties inside S32DS. If moving to different machines check S32DS_Installation_Guide Chapter 4.4, to install any missing drivers. S32 Flash Tool GUI has been removed from the S32 Design Studio installation: Command-line tools are still included in S32DS. Users who need the GUI can install the standalone Flash Tool application from its own separate catalog S32 Flash Tool for S32 Platform. S32DS Docker images: In the S32DS 3.6.4 Flexera product page you will see 2 Docker files, for Windows and Linux, which are samples for how to setup S32DS inside a Docker image. For Linux we provide examples with or without GUI, for Windows only command line interface is available. Docker files use the S32DS installer directly to build the image, no existing installation is needed. Check out S32DS_Installation_Guide Chapters 6 and 7 for additional details on how to setup and use this.   Platform IDE and UI The latest release of Platform IDE introduces several enhancements and a wide range of bug fixes to improve stability and usability: The New Project Wizard now displays a visual decorator next to each NPI to show whether the selected GCC version is installed. S32 Design Studio now detects if a project references a missing GCC version or S32 Debugger. If so, an error appears in the Problems view with a Quick Fix option. Clicking it will automatically install the missing tool with minimal user input. The Memory Spaces view now also displays the address where the monitor is set, even when monitoring is disabled. Users can now connect to an already running GTA instance instead of launching a new one. This can be configured in S32 Debugger configuration by unchecking the Launch Server option.   Major Features for NPIs S32K3 Family Enabled support for S32K324 on VDK R2.0.0 and S32K388 on VDK R6.0.0. Enabled full S32Debugger support for S32K356 and S32K36x derivatives. Extended real time printf with ITM functionality on S32K31x, S32K322 and S32K341/2 using Lauterbach. Integrated PEmicro v6.0.8 with debug support for S32K356 derivative. Integrated Segger v8.58 with debug support for S32K389 derivative. Enabled GCC 11.4 compiler in NPW and in example projects. S32K1 Family Enabled new devices in NPW: S32K116V, S32K118V and S32K144N. Enabled GCC 11.4 compiler in NPW and in example projects. Enabled Segger v8.58 with debug support for S32K142W and S32K144W derivatives. S32M2, S32G2/G3, S32Z2/E2, S32R41, S32R45, S32R47, S32N5 and SAF8xxx Families S32R47, S32N5 and S32SAF8xxx development packages are now public and delivered inside S32DS installer. Radar extensions and Add-on packages are also public and can be installed/updated using Extensions and Updates. Enabled GCC 11.4 in NPW and in example projects. Various bug fixes and improvements for arm cores and accelerators.   This release is available for download on: S32 Design Studio 3.6.4 can be found on  nxp.com  Flexera catalogue S32 Design Studio for S32 Platform v.3.6 Automotive Software Package Manager   Target Audience: S32 Design Studio 3.6.4 and bundled NPIs releases are targeted for public audience.   The Installation Procedure for Packages: Download S32 Design Studio v3.6.4, available on nxp.com , in Flexera catalogue S32 Design Studio for S32 Platform v.3.6, and in Automotive Software Package Manager. If you have any local admin restrictions(ex. Admin by Request) the installer will request elevation, alternatively you can use “Run as Administrator” to run the installer. Download any additional packages if it’s required. Start S32 Design Studio v3.6.4 and install the desired package. Go to  Help > S32DS Extensions and Updates. For additional packages, in the S32DS Extensions and Updates dialog box, click Add Update Sites. Navigate to the directory with the downloaded ZIP file. Choose it and click Open, then click OK. You will get back to S32DS Extensions and Updates and can use this dialog to select desired packages.​​   Technical Support: Please use the public community for general questions: https://community.nxp.com/community/s32/s32ds For internal packages please use INTERNAL S32DS NXP Community space:https://community.nxp.com/groups/internals32ds  
記事全体を表示
      Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio for Power Architecture 2017.R1 Update 7          What is new? MPC574xx SDK BETA 1.9.0 S32R SDK BETA 1.9.0  Radar SDK for S32R274 & S32R372 RTM 1.1.1 AMMCLib 1.1.13 for MPC560xB, MPC560xP, MPC564xL, MPC567xF, MPC567xK, MPC574xC, MPC574xG, MPC574xP, MPC574xR, MPC577xC, MPC577xK,  MPC577xM This is a cumulative update - it includes all of the content of previous updates (Update 1, Update 2, Update 3, Update 4, Updates 5 and 6). Installation instructions The update is available for  (via S32DS 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_POWER_2017.R1/updatesite" select all available items and click "Next" 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 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 start the update installation process.
記事全体を表示
There are a number of existing ISP Graph diagrams provided within the VSDK. It is possible to import them into S32DS for Vision and use them in a new C/C++ project. The steps to do this are detailed in this document. 1) Launch S32DS for Vision 2) Select File -> New -> S32DS Application Project or select "S32DS Application Project" from the toolbar. 3) Enter a project name, such as: ISP_ISP_Generic_demo 4) Select 'A53 APEX/ISP Linux' 5) Click Next 6) Unselect the APEX2 options and 'ISP Visual Modeling' option. 7) Click Finish 😎 Select File -> New -> S32DS Project from Example or select "S32DS Project from Example" from the toolbar. 9) Select isp_generic. 10) Select Finish 11) Open isp_generic in the project explorer 12) Double-click ISP data flow ; isp_generic. The ISP data flow graph will appear in the editor 13) Define a new configuration for emitting code from the graph       a) Create a folder in the application project to receive the emitted code. Right-click on the application project and select New -> Folder.       b) Enter a name for the folder and click Finish       c) Right-click in the ISP data flow window and select Emit As -> Emit Configurations...       d) Select ISP Emitter       e) Select New Launch Configuration       f) Enter a name       g) Select the graph, Browse Workspace       h) Expand each item until you can select the .isp file. Click OK       i) Select the location of the emitted output to the application project, select Browse Workspace       j) Select the name of your application project, then OK       k) Write A53_gen to the Dynamic sequences sources folder box. This is the folder within the target project that generated code will be stored. Check the box for Emit host code.       l)Now select the location to store the configuration file. Go to the Common tab, select Shared file and click Browse       m) Select the folder name you created earlier inside ISP_ISP_Generic_demo and click OK       n) Click Apply and Emit. Dialog box will appear when code generation is successful              o) Expand the folders within ISP_ISP_Generic_demo, A53_gen, src and inc, to see the newly generated output files 14) Change to C/C++ perspective, click on ‘C/C++ Development’ 15) Build the project 'ISP_ISP_Generic_demo' for ISP 16) Open file 'ISP_ISP_Generic_demo/A53_inc/isp_user_define.h' and change '#define __DCU_BPP' to "#undef __DCU_BPP" 17) Using the method detailed in steps 8 - 10, create the example project 'isp_sonyimx224_csi_dcu'. Take from this project the file 'isp_sonyimx224_csi_dcu/A53_src/main.cpp' and use it to replace the file 'ISP_ISP_Generic_demo/A53_src/main.cpp' in the current project. Then make the following modifications:  On line 40, change <#include "mipi_simple_c.h"> to <#include "isp_generic_c.h">. On line 303, change <gpGraph_mipi_simple> to <gpGraph> AND <gGraphMetadata_mipi_simple> to <gGraphMetadata> On line 330, change <FDMA_IX_FastDMA_Out_MIPI_SIMPLE> to <FDMA_IX_ISP_OUTPUT>. Please see C:\NXP\S32DS_Vision_v2.0\S32DS\s32v234_sdk\docs\drivers\SDI_Software_User_Guide.pdf for details on what this code is for. 18) In Project Explorer, right-click on "...\A53_gen\src\isp_process.cpp" and select Build path -> Remove from -> A53 19) Select 'ISP_ISP_Generic_demo:A53' in the Project Explorer panel, then Build for A53 20) Run it remotely on the target using the method fromHOWTO: Create A53 Linux Project in S32DS for Vision. Should get results similar to this:
記事全体を表示
Requirements: PC machine with telnet client (for Windows you can use Putty - Download PuTTY - a free SSH and telnet client for Windows ) DHCP server running on your PC machine or network connection with DHCP server How to install DHCP server on Linux https://www.ostechnix.com/install-dhcp-server-in-ubuntu-16-04/  DHCP server for Windows - Open DHCP Server download | SourceForge.net      S32 debug probe connected to network (with DHCP server) and visible for your PC machine   separate network using static IP addresses (or direct connection between PC and S32 debug probe). The scenario is similar like on this picture:  Procedure:   Connect power to S32 debug probe with already connected ethernet cable and wait until green LED (RX/TX) starts blink.Connect to S32 debug probe by telnet client. You can use default domain name FSLXXYYZZ where XXYYZZ are last 6 digits from S32 debug probe MAC address or assigned IP address: Static IP address can be set by netparam static_ip_address ADDRESS:NETMASK command. Make sure that you are choosing IP address from range of your Embedded network. My network uses standard 192.168.1.xxx here is mt setings:  netparam static_ip_address 192.168.1.100:255.255.255.0 You also need to set boot config from DHCP to Static: netparam bootconfig static Turn OFF and ON again S32 debug probe and check the settings by telnet with static IP address - in my case 192.168.1.100: We are done. 
記事全体を表示
This document details the steps to program external EEPROM with the 32 reset configuration bits in support of the 'Boot from serial RCON' method detailed in the device reference manual. The Python scripts used for this task are designed and tested to work on the EVBs, where EEPROM hardware is connected via I2C.(Serial EEPROM is not implemented on all boards).   The RCON can be set by the following:    Fuses (internal to the device)  Parallel (GPIO pins/DIP Switches on EVB)  Serial (EEPROM connected via I2C)    The Serial option can be programmed using a debug probe connected via JTAG. This enables the RCON to be controlled remotely, assuming the debug probe is setup to allow remote connections.  The images shown throughout this document are of the S32G274A device implementation and are provided for illustration purposes.               Preparation    Install S32 Design Studio IDE  Use the S32DS Extensions and Updates menu to install the Development Package for the device subject to debugging. This is important as the Development Packages add the S32 Debugger support which provides access to the EEPROM programming capabilities via I2C of the S32 Debug Probe.  Connect the S32 Debug Probe to the EVB and the host PC containing S32 Design Studio installation.  Set BOOTMOD pins to boot from RCON    Set BOOT_CFG[8]=1 on the EVB, for serial RCON mode   Procedure    Depending on the way the device used and how the {device name}_i2c_RCON.py is edited, user must use the old procedure on the new one. Both detailed below. To choose between the Old procedure and the new procedure, you must check in the {device_name}_i2c_RCON.py if variables like “INTERACTIVE_MODE” and “RCON_DATA” exist. The {device_name}_i2c_RCON.py can be found in: {INSTALL_DIR}…S32DS/tools/S32Debugger/Debugger/scripts/{device_name}/ {device_name_part_name}_i2c_RCON.py If the variables exist, please use the old procedure. If the variables were removed, please use the new procedure. I.  Old procedure ( If “INTERACTIVE_MODE” variable still exists)   Open cmd window to the S32 Debugger folder where the device-specific scripts are located. ../S32Debugger/Debugger/Scripts/{device_name/part_number} Set Python path so correct version is used (if not already set in env vars)   set PYTHONPATH=C:\NXP\S32DS.3.5\S32DS\build_tools\msys32\mingw32\lib\python2.7;C:\N XP\S32DS.3.5\S32DS\build_tools\msys32\mingw32\lib\python2.7\site-packages   Edit the python script to adjust the value to be programmed to RCON, {device_name}_i2c_RCON.py. Note: The listed examples show only the minimum values required to configure each of the external memory types. Additional settings may be required for your specific application.   Adjust RCON_DATA for the configuration you wish to program. Do not adjust RCON_ADDR. Adjust S32DBG_IP for the IP address of your S32 Debug Probe. Adjust INTERACTIVE_MODE i. Set True, if desired to be prompted in the command window to enter RCON_DATA      ii. Set False, if desried to have script automatically enter RCON_DATA, based on the value set     within the file. Adjust _SOC_NAME as appropriate for the specific device you are using. The valid options are defined in {device_name}_context.py Enter the command to start GDB, passing in the RCON Python script:   Windows OS: ../ S32DS\tools\gdb-arm\arm32-eabi\bin/arm-none-eabi-gdb-py.exe -x {device_name}_i2c_RCON.py OR ../ S32DS\tools\gdb-arm\arm64-eabi\bin/arm-none-eabi-gdb-py.exe -x {device_name}_i2c_RCON.py Linux OS: arm-none-eabi-gdb-py -x {device_name}_i2c_RCON.py   If everything worked properly, then the value you programmed will be displated to the screen.   To exit GDB, enter ‘quit’. II.  New Procedure ( If “INTERACTIVE_MODE” variable was deleted)   Set Python path so correct version is used (if not already set in env vars)  set PYTHONPATH=C:\NXP\S32DS.3.5\S32DS\build_tools\msys32\mingw32\lib\python2.7;C:\N XP\S32DS.3.5\S32DS\build_tools\msys32\mingw32\lib\python2.7\site-packages  Start GDB Server. (…\S32Debugger\Debugger\Server\gta\gta.exe)   Start Command Prompt and enter the command to start GDB with python: Example:   C:\NXP\S32DS.3.5_230912_devpck\S32DS\tools\gdb-arm\arm32eabi\bin\arm-none-eabi-gdb-py.exe Linux OS: arm-none-eabi-gdb-py     In s32rcon.py ( C:\NXP\S32DS.3.5_230912_devpck\S32DS\tools\S32Debugger\Deb ugger\scripts\gdb_extensions\rcon\s32rcon.py😞 Edit connection parameters (Probe IP, GDB server port, JTAG speed, etc.) Edit _RCON_SCRIPT parameter with absolute path to the desired I2C RCON script for the desired board: Example: _RCON_SCRIPT = " C:/NXP/S32DS.3.5_230912_devpck/S32DS/tools/S32Debugger/Deb ugger/scripts/s32g2xx/ s32g274a_i2c_RCON.py"      c. Source s32rcon.py in GDB. Example: source C:/NXP/S32DS.3.5_230912_devpck/S32DS/tools/S32Debugger/Deb ugger/scripts/gdb_extensions/rcon/s32rcon.py     d. Run command py rcon() in GDB. OBS:  Steps a, b can be done after c directly from GDB, using GDB py commands: Examples:  py _GDB_SERVER_PORT=45000  py _RCON_SCRIPT="C:/NXP/S32DS.3.5_230912_devpck/S32DS/tools/S32Debugger/Debu gger/scripts/s32g2xx/ s32g274a_i2c_RCON.py"   User can now use the available commands, like rcon_help, rcon_read, rcon_write to interact with the EEPROM.   User can write [command] -h for more information and mandatory parameters of the command.   User can write ‘quit’ to exit the S32 RCON services.
記事全体を表示
Hi,     With S32DS and multilink, you can try the follow steps to dump flash or RAM data into file.  1. Attach    (https://community.nxp.com/t5/S32-Design-Studio/How-attach-to-running-program/m-p/1030375) 2. Export the data which you need    (https://community.nxp.com/t5/S32-Design-Studio/S32DS-how-to-properly-dump-RAM-in-debug-session/m-p/649974#M1089) Cheers! Oliver
記事全体を表示
The S32 Design Studio for S32 Platform supports the S32R45 device with the S32 Debugger. This document provides the details on how to setup and begin a debugging session on the S32R45 evaluation board.   Preparation Setup the software tools Install S32 Design Studio IDE   Use the Extensions and Updates menu within S32 Design Studio for S32 Platform to add the S32R4xx Development Package.   Setup the hardware Confirm the setup of the S32R45 evaluation board.  Configure the JTAG. The S32R45 evaluation board supports both 10- and 20- pin JTAG connections. The default board configuration is set to 20-pin, change the position of the jumper J59 from 2-3(default)  to 1-2, if you are using the 10 Pin JTAG interface. Both are supported by the S32 Debugger and S32 Debug Probe. Connect the power supply cable Setup the S32 Debug Probe Connect the S32 Debug Probe to the evaluation board via JTAG cable. Refer to the S32 Debug Probe User Manual for installation instructions. Use the JTAG connection as was confirmed in the previous step. Connect the S32 Debug Probe to the host PC via USB OR via Ethernet (via LAN or directly connected, and configured for static IP address) and power supply connected to USB port. Launch S32 Design Studio for S32 Platform Create new or open existing project and check that it successfully builds. If creating a new project, be sure the S32 Debugger is selected in the New Project Wizard.     Procedure Open the Debug Configurations menu, then follow the steps depending on whether an S32 Debugger configuration exists for your project. If the project was created using the New Project Wizard in S32 Design Studio for S32 Platform, and the S32 Debugger was selected as the debugger, then it likely has existing debug configuration(s).       S32 Debugger Configuration(s) Exist If existing S32 Debugger configuration, proceed with probe configuration. Otherwise, skip to the next section. Below is shown the debug configuration which appears for the provided SDK example project 'hello_world_s32r45'. The suffixes 'debug', 'ram', and 's32debugger' refer to how the project was built and the debugger the configuration is for. Select the debug configuration which corresponds to the project, build type debug, and primary core (if a multicore project) Select the Debugger tab Select the Interface (Ethernet/USB) by which the S32 Debug Probe is connected. If connected via USB and this option is selected for interface, then the COM port will be detected automatically (in the rare event where 2 or more S32 Debug Probes are connected via USB to the host PC, then it may be necessary to select which COM port is correct for the probe which is connected to the EVB) If connected via Ethernet, enter the IP address of the probe. See the S32 Debug Probe User Manual for ways to determine the IP address.   S32 Debugger Configuration(s) Do Not Exist There might be no existing debug configuration if the project is being ported from another IDE or was created to use another debugger. Select the S32 Debugger heading and click New Launch configuration (or double click on the S32 Debugger heading, or right click on the S32 Debugger heading and select New from the context menu) A new debug configuration appears with the name set to the name of the active project in the Project Explorer window(this can be set by opening a file from the project or selecting an already opened file from the project in the editor), and the build type which was used to build it. If this is not matching your intended project then it can either be modified to match or deleted and recreated after the active project has been changed to the desired project. Adjust the name of the project as desired. From the Main tab, check that the Project field is set to the correct project name, as listed in the Project Explorer, and that the C/C++ Application is set to the ELF file which was built. The name of the project can be customized, but '_' must be used instead of spaces. If the Project field is not set or incorrect, click Browse... and then select the correct project name from the list. If more than one project is open in the workspace, then each will be listed. This shows how, regardless of which project is active in the C/C++ perspective, any available workspace project could be associated. This can be useful when reusing a debug configuration from one project in another. If the C/C++ Application is not set or incorrect, click Search Project... and then select the correct binary file (will only work if Project field is correct and project was successfully built). Switch to the Debugger tab, Click 'Select device and core' and then select the correct core from the list. In this case, the M7_0 core is correct. If this is not the primary core, then uncheck the box next to 'Initial core'. This is done only for multi-core projects for the non-boot cores. This causes the scripts to skip the initialization of the core as the boot core will launch the other cores so additional initialization will not be required. Select the Interface (Ethernet/USB) by which the S32 Debug Probe is connected. If connected via USB and this option is selected for interface, then the COM port will be detected automatically (in the rare event where 2 or more S32 Debug Probes are connected to the host PC, then it may be necessary to select which COM port is correct for the probe which is connected to the EVB) If connected via Ethernet, enter the IP address of the probe. See the S32 Debug Probe User Manual for ways to determine the IP address. Click Apply Click Debug. This will launch the S32 Debugger. When the debugger has been successfully started, the Debug perspective is opened and the application is executed until a breakpoint is reached on the first line in main().  
記事全体を表示
Product Release Announcement Analog & Automotive Embedded Systems S32 Design Studio 3.6.5   The Analog & Automotive Embedded Systems (AAES) - Software Development Tools Engineering Team at NXP Semiconductors is pleased to announce the release of the S32 Design Studio 3.6.5 with support for: AMCU AP RAS APN S32K3 Family S32G Family S32R41 Family S32J Family S32K1 Family S32ZE Family S32R45 Family   S32M2 Family S32N Family S32R47 Family       SAF8xxx Family     Major Features for S32 Design Studio 3.6.5 Installer S32 Design Studio 3.6.5 is delivered with all public NPI's in a single 2.63GB installer to improve first time user experience. Additional packages for alpha customers are available based on Flexera entitlement and can be installed on top of S32 Design Studio 3.6.5 using Extension and Updates.   Installer will require admin rights only when the user chooses to install components which need elevation (Visual Studio Redistributable or debugger drivers). If a user chooses a custom installation only with S32DS IDE and its components (no drivers) the installation will finish without admin rights.   Platform IDE and UI Integrated Cody, the open-source Eclipse plugin from Sourcegraph, into S32 Design Studio. This plugin is installed by default, allowing users with a valid Cody license to log in directly within S32DS and access Generative AI features. Note: Users must agree to the Sourcegraph Terms of Service before using Cody. Enabled integration with the NXP Application Code Hub, allowing users to browse available examples and import them directly from the hub page into S32 Design Studio. Note: the application examples will be published soon on the Application Code Hub URL. Note: This image is taken from internal sources. The illustrated examples are currently under development and will be available soon. Extended the Quick Fix mechanism for the missing NPI and Real Time Drivers packages. Basically, an error message displays in the Problems view whenever the IDE identifies a missing package (build tool, NPI, RTD) associated with the current project. The Quick Fix automatically installs the missing package if it is available in the configured Update Sites. Note: not all scenarios are covered, there may be cases where the tool cannot determine if a package is missing. A new Recent tab has been added in S32DS Extensions and Updates to display the latest installed packages, providing a clear history of user actions related to package installations. In addition, the default sorting was changed in All tab to bring greater visibility to NXP packages. Added support for drag-and-drop of S32 Design Studio p2 update sites / installable packages into the S32DS Extensions & Updates window. Users can now simply drag the ZIP file into the window, and the package will be automatically inserted and selected, requiring only a click on Next to complete the installation. Significant improvements to Secure Debugging:  Added a dedicated Debug Card view that allows users to generate debug card binaries based on custom input. Implemented Challenge & Response functionality for Linux environment.  Enabled Secure Registry Key view for managing secure registry keys on Linux.  UI is aligned to the secure debugging functionality latest changes introduced by HSE2. Extended the S32 Debugger OS awareness support with FreeRTOS. OS threads are now visible in S32 Design Studio and user will be able to individually debug them. Extended the command line support to display OS threads and objects. Enable debug in low power mode with S32 Debugger for S32K3xx devices:  The debug session will recover after core exits low power or standby mode, allowing the user to continue application debugging. Debugging from the first instruction after low power exit is now possible by using this configuration command when starting the debug session: monitor template config :ccs:S32K3XX:SoC#0 6 1 Expanded the S32Trace debug-info parser to fully support DWARF-5, adding compatibility with projects using GCC 11.4 and newer.   Major Features for NPIs S32N Family S32Flash Programmer improvements for erase and verify write operations on S32N5. S32G2/G3, S32J100, and SAF8xxx Families S32J100 development package is now public and delivered inside S32DS installer. Enabled debugging support for S32G2 devices on VDK R10. S32Flash Programmer enhancements for erase and verify write operations. Various bug fixes and improvements for arm cores and accelerators.   This release is available for download on: S32 Design Studio 3.6.5 can be found on  nxp.com  Flexera catalogue S32 Design Studio for S32 Platform v.3.6   Target Audience: S32 Design Studio 3.6.5 and bundled NPIs releases are targeted for public audience.   The Installation Procedure for Packages: Download S32 Design Studio v3.6.5, available on nxp.com and in Flexera catalogue S32 Design Studio for S32 Platform v.3.6. If you have any local admin restrictions(ex. Admin by Request) the installer will request elevation, alternatively you can use “Run as Administrator” to run the installer. Download any additional packages if it’s required. Start S32 Design Studio v3.6.5 and install the desired package. Go to  Help > S32DS Extensions and Updates. For additional packages, in the S32DS Extensions and Updates dialog box, drag the ZIP file into the window, and the package will be automatically inserted and selected, requiring only a click on Next to complete the installation, or click Add Update Sites. Navigate to the directory with the downloaded ZIP file. Choose it and click Open, then click OK. You will get back to S32DS Extensions and Updates and can use this dialog to select desired packages.​​   Technical Support: Please use the public community for general questions: https://community.nxp.com/community/s32/s32ds For internal packages please use INTERNAL S32DS NXP Community space:https://community.nxp.com/groups/internals32ds  
記事全体を表示
This document shows the step-by-step process to create a simple blinking LED application for the S32R41 family using the S32 RTD AUTOSAR drivers. This example used for the S32R41 EVB, connected via ethernet connection through S32 Debugger. Preparation Setup the software tools Install S32 Design Studio for S32 Platform Install the S32R41 development package and the S32R41 RTD AUTOSAR 4.4. Both of these are required for the S32 Configuration Tools. Launch S32 Design Studio for S32 Platform Procedure New S32DS Project OR Provide a name for the project, for example 'Blinking_LED_RTD_With_AUTOSAR'. The name must be entered with no space characters. Expand Family S32R41, Select S32R418AB Cortex-M7  Click Next Click '…' button next to SDKs   Check box next to PlatformSDK_SAF85_S32R41_2022_08_S32R418AB _M7_0. Click OK And also, uncheck the other core Cortex_M7_1 Click Finish. Wait for project generation wizard to complete, then expand the project within the Project Explorer view to show the contents. To control the LED on the board, some configuration needs to be performed within the Pins Tool. There are several ways to do this. One simple way by double-click on the MEX file. Select the overview tab and disable Pins tool. Make sure to overview tab windows shows settings shown as below.  Here, we are disabling pin tools and using MCAL driver from peripheral tools for using AUTOSAR drivers. Now from Overview menu, select peripheral tools and double click to open it. In the driver sections, “Siul2_Port_1 driver” is the non-AUTOSAR version driver and so it must be replaced. Right click on ‘Siul2_Port_1’ and remove it. Keep BaseNXP driver as it is. Click on the ‘+’ next to the MCAL box. Locate and then select the ‘Dem’ component from the list and click OK. Click on the ‘+’ next to the MCAL box again, and Locate and then select the ‘Dio’ component from the list and click OK. Click on the ‘+’ next to the MCAL box again, and Locate and then select the ‘Mcu’ component from the list and click OK. Click on the ‘+’ next to the MCAL box again, and Locate and then select the ‘Port’ component from the list and click OK. Now components tab should show like below : Now we required to configure the different MCAL drivers that we added. Starting with Dio configuration, open the Dio configuration. No change is required for Dem configuration. Now, open the ‘DioGeneral’ tab, and select checkmark as per shown below: Now, open the ”DioConfig” tab. In that Select  “+” sign adjacent to Dio Channel. Then Edit Name to “Digital_Output_LED_0” and Dio Channel Id to ‘4’ instead of ‘0’. From the schematic for S32R41 EVB, checking for signal line for the user LED, channel 4 is connected to user LED signal, so we use channel 4 for signal line for user LED on the chip. So, we select the signal line for Dio channel Id 4 for the LED connected on the S32R41 EVB. Now Select Port tab for Port configuration. And open the Port Configuration tab, and from that open “PortConfigSet” tab. Change the PortPin Mscr to 36 , PortPin Direction to PORT_PIN_INOUT as shown below: Now, at the bottom you will find the “UnTouchedPortPin ’’ . Click on “+’’ and add PortPins. Now add port pins 0, 1, 2, 3,4 as per below configuration Now configure MCU component. Select Mcu component in MCAL, and then open the Mcu configuration. In Mcu configuration click MCUModuleConfiguration and then select  “McuModesettingConf” from the dropdown menu as shown below. From McuModeSettingConf select McuPartitionConfiguration Now open “McuPartition0Config” tab. And under the McuCore0Configuration for “McuCoreClockEnable” select checkbox and for “McuCoreResetEnable” uncheck  the checkbox. Similarly, And under the McuCore1Configuration for “McuCoreClockEnable” select checkbox and for “McuCoreResetEnable” uncheck  the checkbox. After modification it should be as shown below: Now open the “McuPartition1Config” tab. for "McuPartitionClockEnable" select checkmark to true and for "McuPartitionResetEnable" uncheck  the checkmark   And under McuCore0Configuration for "McuCoreClockEnable"  select checkmark to true and for "McuCoreResetEnable" uncheck  the checkmark After modification it should be as shown below: Now, click on global setting icon as shown below: And, Confirm that ComponentGenerationMethod is set to “FunctionalGroups” Now the device configurations are complete and the RTD configuration code can be generated. Click ‘Update Code’ from the menu bar. To control the output pin which was just configured, some application code will need to be written. Return to the ‘C/C++’ perspective. If not already open, in the project window click the ‘>’ next to the ‘src’ folder to show the contents, then double click ‘main.c’ file to open it. This is where the application code will be added. Before anything else is done, Initialize the clock tree and apply PLL as system clock, Apply a mode configuration, Initialize all pins using the Port driver by adding – editing code before write code here comment in main function.        /* Initialize the Mcu driver */        Mcu_Init(&Mcu_Config_BOARD_InitPeripherals);        /* Initialize the clock tree and apply PLL as system clock */        Mcu_InitClock(McuClockSettingConfig_0);        /* Apply a mode configuration */        Mcu_SetMode(McuModeSettingConf_0);        /* Initialize all pins using the Port driver */        Port_Init(NULL_PTR); Now replace the logic of for loop as shown below code section, which will enable the LED blinking for 10 times: You also need to declare and initialize the loop variable: uint8 i = 0U; Then replace the code as below after write your code comment: /*Logic for blinking LED 10 times*/ while (i++ < 10) {       /* Get input level of channels */       Dio_WriteChannel(DioConf_DioChannel_Digital_Output_LED_0, STD_HIGH);       TestDelay(3000000);       Dio_WriteChannel(DioConf_DioChannel_Digital_Output_LED_0, STD_LOW);       TestDelay(3000000); } Before the 'main' function, add a delay function as follows: void TestDelay(uint32 delay); void TestDelay(uint32 delay) {     static volatile uint32 DelayTimer = 0;     while(DelayTimer<delay)     {         DelayTimer++;     }     DelayTimer=0; } Update the includes lines at the top of the main.c file to include the headers for the drivers used in the application: Add #include "Mcu.h" #include "Port.h" #include "Dio.h" Now, in open peripheral tools again by clicking on icon as shown below. And then click on global setting icon as shown below: And, Confirm that ComponentGenerationMethod is set to “FunctionalGroups” Build 'Blinking_LED_RTD_AUTOSAR'. Select the project name in 'C/C++ Projects' view and then press 'Build'. After the build completes, check that there are no errors. Open Debug Configurations and select 'Blinking_LED_RTD_with_AUTOSAR_Debug_RAM'. Make sure to select the configuration which matches the build type performed, otherwise it may report an error if the build output doesn’t exist. And make selection as shown in screenshot below. You need to select the ethernet connection for S32 debugger and provide its IP address Click Debug To see the LED blink, click ‘Resume' This code as it will blink the LED 10 times, you can make changes in for loop condition to blink it infinitely.
記事全体を表示
Product Release Announcement Analog & Automotive Embedded Systems S32 Design Studio 3.6.2   The Analog & Automotive Embedded Systems (AAES) - Software Development Tools Engineering Team at NXP Semiconductors is pleased to announce the release of the S32 Design Studio 3.6.2 with support for: AMCU AP RAS S32K3 Family S32G Family S32R41 Family S32K1 Family S32ZE Family S32R45 Family S32M2 Family       Major Features for S32 Design Studio 3.6.2 Installer S32 Design Studio 3.6.2 is delivered with all public NPI's in a single 3GB installer to improve first time user experience. Additional packages for alpha customers are available based on Flexera entitlement and can be installed on top of S32 Design Studio 3.6.2 using Extension and Updates.     Platform IDE and UI   Enhanced debugging efficiency by at least 20%. It applies to the entire debug session initialization pipeline and was measured from the moment Debug is pressed until the main() is reached. Live view mechanism was introduced in Memory Spaces and Global Variables views when target is running in non-stop mode. Users can observe real-time changes to memory addresses and variables, improving visibility into the runtime behavior. A configurable refresh rate allows tunning the update frequency based on performance needs. A new entry named assigned core was added in the Task List (FreeRTOS) view, it targets SMP cases. Expressions with global scope can now be added straight from the Global Variables panel, without needing to switch to a separate view. Added option to export registers description during data export from the Watch Registers view.  Find & Paste functions were enabled in Memory Management Unit (MMU) view. Added support for Enable auto build in S32 Debugger configuration. Enabled support for Additional Images in S32 Debugger configuration, for cases when additional source objects are loaded in the Flash memory. Enabled Advanced Settings to set the CCS IP and Port for S32 Debugger Flash Programmer debug configurations.   3 rd Party Solutions  Update of 3rd Party Debug support: Segger J-Link v8.28 PEmicro v6.0.2 TASKING v9.21.333   Major Features for NPIs S32K3 Family Merged  S32K389 into S32K3xx development pack to be available for all customers with S32DS 3.6.2 installer file. Enabled Wind River Diab 7.0.6 and IAR 8.50.10 compilers for S32K389. Enabled PEmicro v6.0.2 and IAR 8.50.10 debuggers for S32K389. Extended IAR and Segger debugging support for S32K36x, S32K37x, S32K39x, S32K341, S32K342 and S32K322 derivatives. Enhanced S32Flash programmer over JTAG to detect the presence of the HSE FW and adapt the flash operations considering HSE FW reserved flash addresses.   This release is available for download on: S32 Design Studio 3.6.2 can be found on:  nxp.com  Flexera catalogue S32 Design Studio for S32 Platform v.3.6  Automotive Software Package Manager   Target Audience: S32 Design Studio 3.6.2 and bundled NPIs releases are targeted for public audience.   The Installation Procedure for Packages: Download S32 Design Studio v3.6.2, available on nxp.com, in Flexera catalogue S32 Design Studio for S32 Platform v.3.6, and in Automotive Software Package Manager. If you have any local admin restrictions(ex. Admin by Request) the installer will request elevation, alternatively you can use “Run as Administrator” to run the installer. Download any additional packages if it’s required. Start S32 Design Studio v3.6.2 and install the desired package. Go to  Help > S32DS Extensions and Updates. For additional packages, in the S32DS Extensions and Updates dialog box, click Add Update Sites. Navigate to the directory with the downloaded ZIP file. Choose it and click Open, then click OK. You will get back to S32DS Extensions and Updates and can use this dialog to select desired packages.​​   Technical Support: Please use the public community for general questions: https://community.nxp.com/community/s32/s32ds For internal packages please use INTERNAL S32DS NXP Community space:https://community.nxp.com/groups/internals32ds  
記事全体を表示
Project created by S32 Design Studio (S32DS) new project wizard typically contains the debugger configurations to load  and debug the project into the code memory (Flash/RAM). However there might be situations that require also to load a content/data (e.g. calibration values) into a special on-chip memory (such as shadow flash, data flash, utest flash...) or an external memory (QSPI). This document describes how to program multiple memory types (using different programming algorithms) just by single click on the debug button. The decription applies to PEMICRO probes (Multilink Universal, Multilink FX or OpenSDA) anyway a similar approach might be applicable for other vendor probes. The process can be splitted into two steps: 1. create a separate debugger configurations to program a specific memory modules(QSPI,  data flash,..) 2. associate the program and debug configurations into the single launch group  - this alows to execute multiple actions by invoking the single debug launch . Let's demonstrate this on MPC5744P and program code and data flash memory using S32DS for Power v2.1 (similar approach can be applied also to other architectures/versions of S32DS). •  Create a new empty project for MPC5744P. Such a project typically contains Debug/Debug_RAM debugger configuration. First we will add a dummy code  (see below) that creates a record to be stored into the data flash memory (different to code flash memory block). • The project linker file (MPC57xx_flash.ld) should have the data flash memory block and a linker section associated with data flash (.dflash) defined: MEMORY { dflash : org = 0x00800000, len = 0x1F /* not entire dflash - just for test*/ flash_rchw : org = 0x00FA0000, len = 0x4 cpu0_reset_vec : org = 0x00FA0004, len = 0x4 m_text : org = 0x1000000, len = 2048K m_data : org = 0x40000000, len = 384K local_dmem : org = 0x50800000, len = 64K } SECTIONS { .dflash : { KEEP(*(.dflash)) } > dflash … •Add a test code into main.c that results in creating a dummy data record in data flash memory (0x0800000) __attribute__((section(".dflash"))) volatile char dflash_data[]="DTEST String"; // place the string into .dflash segment int main(void) { volatile int counter = 0; volatile char test_str[10]; test_str[0] = dflash_data[0]; // use DFLASH data (to avoid deadstripping) /* Loop forever */ for(;;) { counter++; } } Now if you build the project you can see the data that belong to dflash and code flash in the .map or srec file. If you debug the project using the default debug configuration data flash (DFLASH) memory is not programmed. To program DFLASH you should create another debug configuration simply by duplicating the existing one and changing the programming algorithm to dflash one: nxp_mpc5744p_1x32x20k_dflash.pcp. Note: There are many flash programming algorithms available in PEMICRO eclipse plugin folder typically located here (version of plugin may vary): "C:\NXP\S32DS_Power_v2.1\eclipse\plugins\com.pemicro.debug.gdbjtag.ppc_2.0.2.202005132054\win32\gdi\P&E\" S32DS: Duplicate Debug Configuration S32DS: Load parameters S32DS: Choose alternative programming algorithmNow the new debug configuration (MPC5744P_code_dflash_Debug_DFLASH) is able to program data flash memory. The final step is to create a launch group configuration and associate it with all the programming/debugging configurations that should be executed once debug is started. Add the debug configuration used just for programming purpose as flash type and code debug configuration as debug type. In order to avoid interference between programming of various memories select post launch action -> "Wait until terminated" Finally as soon as the debug session is established by launching the launch group created above - all the memories are programmed and you can debug the code. Note: There is an information about executed flash configurations in the debug context view. Since the programming has alredy finished the thread is terminated and could be cleared by double cross icon. Enjoy single click programming&debugging in S32 Design Studio!
記事全体を表示
        Product Release Announcement Automotive Microcontrollers and Processors S32 Design Studio v3.3 Vision Extension Package for S32V234 1.2.0          What is new? Integrated VSDK 1.6.0   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 S32 Platform 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 '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.
記事全体を表示