HOWTO: Create a Blinking LED application project for S32Z27x using S32 RTD No AUTOSAR

[#1]

This document shows the step-by-step process for creating a simple blinking LED application for the S32Z27x family using the S32 RTD non-AUTOSAR drivers. This example used for the S32Z27x-DC EVB, which is connected via an Ethernet connection through the S32 Debugger.  

Preparation 

1. Setup the software tools 
   1. Install S32 Design Studio for S32 Platform  
   2. Install the S32Z2/E2 development package and the S32ZE RTD AUTOSAR R21-11 Version 0.9.0 P01 Both of these are required for the S32 Configuration Tools. 

DanielBarbu_0-1729770950096.png

2. Launch S32 Design Studio for S32 Platform 

Procedure 

1. New S32DS Project 

DanielBarbu_1-1729770996860.png

OR  

DanielBarbu_2-1729771028823.png

2. Provide a name for the project, for example 'Blinking_LED_RTD_No_AUTOSAR'. The name must be entered with no space characters.  

3. Expand the Family ‘S32Z27x’, and Select ‘S32Z270 (Boot core_ R52_0_0)’ 

DanielBarbu_3-1729771054158.png

4. Click '…' button next to SDKs 

DanielBarbu_5-1729771121264.png

5. Check box next to PlatformSDK_S32ZE_2022_10_S32Z270_R52_0_0_LS (or whichever latest SDK for the S32M27x is installed). Click OK  

DanielBarbu_6-1729771153344.png

6. Click "Finish" and wait for the project generation wizard to complete. Then, expand the project within the "Project Explorer" view to show its contents. 

DanielBarbu_0-1729773632866.png

7. 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 is to double-click on the .MEX file. 

DanielBarbu_1-1729773653875.png

8. By default, the Pins Tool will be presented. The S32Z27x DC EVB has user D12 LED connected to the PA_01 pin on the S32Z270 device. 

To configure this pin, select the "Peripheral Signals" tab to the left of the Pins Tool perspective layout. Locate and open the SIUL2_0 from the peripheral signals tab, and from the drop-down menu, select the "gpio,1 PA_01" option as shown in the following image. 

We are using Siul2_0 for GPIO usage, so we are routing the gpio,1 –> PA_01 GPIO signal to this pin. 

DanielBarbu_2-1729773702826.png

   The Direction required! menu will appear. Select Output then OK. 

DanielBarbu_3-1729773749749.png

9. In Routing Details view, notice a new line has been added and highlighted in yellow. 

DanielBarbu_4-1729773779967.png

10. Add ‘LED’ to the Label and Identifier columns for the Siul2_0, gpio-1 pin. 

DanielBarbu_5-1729773841359.png

11. Code Preview 

DanielBarbu_6-1729774044873.pngDanielBarbu_7-1729774152124.png

12. Go to Peripherals tool and add Gpio_Dio to enable LED blinking, it adjacent to the user LED on S32Z270 EVB. 

1. Click on the Peripherals Tool icon in the Eclipse Perspective navigation bar. 
   DanielBarbu_8-1729774246191.png
2. In the Components view, click on the ‘Add a new configuration component…' button in the Drivers category. This will bring up a list of all configuration components. 
   DanielBarbu_10-1729774311323.png
3. Locate and select the 'Siul2_Dio' component from the list and click OK. Don't worry about the warning message – it's only indicating that the driver isn't already part of the current project. The associated driver package will be added automatically.  

Note: it may be necessary to change the selection at the top from 'Present in the toolchain project' to 'All'. 

The Siul2_Dio driver provides services for reading and writing to/from DIO Channels.  

DanielBarbu_11-1729774351169.png

13. Now, form the toolbar selection menu at the top, select and double click on the symbol as shown as below:  

DanielBarbu_12-1729774374958.png

Then, from the global settings window, for ComponentGenerationMethod from the drop down menu select “FunctionalGroups” from the drop down menu as shown below:  

DanielBarbu_13-1729774390991.png

14. The Siul2_Dio driver requires no further configuration. Click Save to store all changes to the .MEX file. 

DanielBarbu_14-1729774409193.png

15. Now. click ‘Update Code’ from the menu bar. 

Now the device configurations are complete and the RTD configuration code can be generated. Click ‘Update Code’ from the menu bar.  

DanielBarbu_15-1729774461735.png

16. To control the output pin which was just configured, some application code will need to be written. Return to the ‘C/C++’ perspective. 

DanielBarbu_16-1729774493201.png

17. If the 'src' folder is not already open in the project window, click the '>' symbol next to it to show its contents. Then, double-click the 'main.c' file to open it. This is where you will add the application code. 

DanielBarbu_17-1729774508583.png

18. To control the pin, it needs to be 'initialized' using the configuration information generated from the S32 Configuration tools. To do this, add the following line to the 'main' function after the comment 'Write your code here': 

    /* Initialize all pins using the Port driver */  

    Siul2_Port_Ip_Init(NUM_OF_CONFIGURED_PINS0, g_pin_mux_InitConfigArr0);  

DanielBarbu_18-1729774561333.png

19. Now, add logic to turn the LED on and off with some delays in between to make it visible blinking. Make sure the delays are long enough to be perceptible.  

1. Add line to initialize variable uint8 i = 0; 
2. Add line to declare variable level:
   volatile uint8 level; 
3. Change the code within the provided for loop, and add the following lines:   

 /*logic for blinking LED 10 times*/     for (; i<10; i++)  

    {  

        Siul2_Dio_Ip_WritePin(LED_PORT, LED_PIN, 1U);         level = Siul2_Dio_Ip_ReadPin(LED_PORT, LED_PIN);  

        TestDelay(480000);  

        Siul2_Dio_Ip_WritePin(LED_PORT, LED_PIN, 0U);         level = Siul2_Dio_Ip_ReadPin(LED_PORT, LED_PIN);  

        TestDelay(480000);  

    }  

DanielBarbu_19-1729774770933.png

20. 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;  

}  

DanielBarbu_20-1729775004705.png

21. Update the includes lines at the top of the main.c file to include the headers for the drivers used in the application: 

Remove   #include

"Mcal.h" 

Add  

#include "Siul2_Port_Ip.h"  

#include "Siul2_Dio_Ip.h"  

DanielBarbu_21-1729775154749.png

22. Build 'Blinking_LED_RTD_No_AUTOSAR'. Select the project name in 'C/C++ Projects' view and then press 'Build'. 

DanielBarbu_22-1729775270319.png

23. After the build completes, check that there are no errors. 

DanielBarbu_23-1729775288288.png

24. Open Debug Configurations and select 'Blinking_LED_RTD_No_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. 

DanielBarbu_24-1729775320447.png

25. Now, you need to Select the Interface (Ethernet or USB) by which the S32 Debug Probe is connected.  

DanielBarbu_26-1729775403585.png

1. 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) 
   DanielBarbu_27-1729775489556.png
2. 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. 
   DanielBarbu_28-1729775575202.png
   
   
3. Click apply and Debug 

26. To see the LED blink, click ‘Resume'.  

DanielBarbu_29-1729775613296.png

27. This code as it is will blink the LED 10 times, you can make changes in for loop condition to blink it infinitely.