S32K ナレッジベース

ディスカッション

/******************************************************************************** Detailed Description: Example shows possible implementation of multiple ADC conversions using SDK. Here 7 channels are sampled periodically. 2 ADC modules and 2 PDBs are used. ADC0 is configured to sample 3 channels, ADC1 4 channels. PDBs are set to back-to-back mode to perform chain conversion as shown in RM's Figure 46-3. PDB back-to-back chain forming PDB0-PDB1 ring. Within ADC component you need to select ADC input to be measured for each item in configuration list. For ADC0 ch5 External input channel 28 is selected, as it is connected to potentiometer on the EVB. PDB0 is triggered by LPIT ch0 at 500ms rate. * ------------------------------------------------------------------------------ * Test HW: S32K148EVB-Q144 * MCU: FS32K144UAVLQ 0N20V * Target: Debug_FLASH * EVB connection: UART terminal 115200, 8N1 * Compiler: S32DS.ARM.3.4 * SDK release: S32SDK_S32K1XX_RTM_4.0.3 * Debugger: S32DS ******************************************************************************** Revision History: Ver Date Author Description of Changes 1.0 Jan-26-2023 Petr Stancik Initial version, based on adc_hwtrigger_s32k148 *******************************************************************************/

------------------------------------------------------------------------------ * Test HW: S32K31XEVB-Q100 * MCU: S32K311 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE Micro * Target: internal_FLASH ******************************************************************************** S32K31XEVB-Q100 :-- S32K31XEVB-Q100 Evaluation Board for Automotive General Purpose | NXP Semiconductors S32K312 UART Transmit & Receive Using DMA :-- S32K311 UART Transmit & Receive Using DMA - NXP Community S32K311 UART Idle state Interrupt :-- S32K311 UART Idle state Interrupt - NXP Community

******************************************************************************* The purpose of this demo application is to present a usage of the EMIOS IP Driver in Interrupt mode for the S32K3xx MCU. The example use to :-- EMIOS-1 - ch-0 --> PTC24 --> Generate the PWM EMIOS-1 - ch-1 --> PTC25 --> is the ICU channel to measure the duty Pins used :-- Dinesh_Guleria_0-1733896956186.png Dinesh_Guleria_4-1733897197653.png Dinesh_Guleria_5-1733897299281.jpeg This example is tested for SAIC & IPWM mode both. You can change the mode by this setting in MEX file :-- Dinesh_Guleria_6-1733897383718.png Difference between SAIC & IPWM, ICU Driver User Manual :-- Dinesh_Guleria_2-1733897086528.png These Two Macro :-- SAIC_MODE --> this maco will enable variables to store for SAIC mode CUSTOM_IRQ --> this MACRO will enable customized IRQ or RTD available IRQ Dinesh_Guleria_8-1733897822913.png Result :-- Dinesh_Guleria_7-1733897734611.png ------------------------------------------------------------------------------ * Test HW: S32K3X2EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ********************************************************************************

******************************************************************************* The purpose of this demo application is to present a usage of the EMIOS IP Driver for the S32K3xx MCU. This example uses the custom IRQ. The example uses:-- EMIOS-1 - ch-0 --> PTC24 --> Generate the PWM EMIOS-1 - ch-1 --> PTC25 --> is the ICU channel to measure the duty Dinesh_Guleria_2-1733220197914.png Dinesh_Guleria_1-1733220169992.png Result :-- Dinesh_Guleria_0-1733220161435.png ------------------------------------------------------------------------------ * Test HW: S32K3X2EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ********************************************************************************

******************************************************************************* The purpose of this demo application is to present a usage of the ICU & PWM MCAL Driver for the S32K3xx MCU. This example uses the custom IRQ. The example uses:-- EMIOS-1 - ch-0 --> PTC24 --> Generate the PWM EMIOS-1 - ch-1 --> PTC25 --> is the ICU channel to measure the duty Dinesh_Guleria_0-1733220239428.png Dinesh_Guleria_1-1733220247864.png Result :-- Dinesh_Guleria_2-1733220259942.png ------------------------------------------------------------------------------ * Test HW: S32K3X2EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ********************************************************************************

ADC Module clock is ideally the CORE clock :-- Dinesh_Guleria_0-1732083693587.png Dinesh_Guleria_1-1732083711398.png Prescaler In S32DS is this MCR[ADCLKSEL]) :-- Dinesh_Guleria_2-1732083809064.png See below snippet from specs for calculation of ADC conversion clock :-- ADC is controlled by one clock signal, the module clock. Internally, the conversion circuit is controlled by the conversion clock, which is derived from the module clock. You must configure the ADC conversion clock divider (MCR[ADCLKSEL]) so that the frequency of the conversion clock is within allowed limits. Dinesh_Guleria_3-1732083835789.png Dinesh_Guleria_4-1732083835803.png S32K3 Datasheet, ADC MAX MIN clock limit :-- Dinesh_Guleria_5-1732083946772.png

******************************************************************************* The purpose of this demo application is to present a usage of the SWT IP Driver for the S32K3xx MCU. ------------------------------------------------------------------------------ * Test HW: S32K3X2EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ******************************************************************************** With S32K312 device take care, HSE clock AIPS_SLOW_CLOCK ratio, kept 1:2 :-- Dinesh_Guleria_0-1706855323004.png The example we use to trigger the SWT once & go to while(1) loop. This will trigger the watchdog RESET. Dinesh_Guleria_1-1706855535347.png Then After RESET from SWT we will check at starting of main function, if RESET reason is SWT, then glow LED and wait in while(1) loop :-- Dinesh_Guleria_2-1706855589096.png

**************************************************************************************************** Detailed Description: The current RTD RTM 2.0.0 does not support overflow notification if EMIOS ICU is used in the Edge Detect mode. Workaround is to use another channel in ECU mode clocked by the same counter bus as the ICU channel. Emios_0 input clock: 48MHz CORE_CLK MCL EMIOS_0_Ch_23 (BUS_A) Global clock devider: 48 MCB prescaler: 1 MCB clock: 1MHz MCB tick: 1us MCB period: 65_535 ticks Both OCU (Emios_0_Ch0) and ICU (Emios_0_ch3) use the same BUS_A counter clock. GPIO generated PWM period: ~0.5s That's 500_000 ticks ICU routed to PTB0 GPIO PWM to PTB1 ----------------------------------------------------------------------------------------------- Test HW: S32K3X4EVB-Q172 MCU: S32K344 Debugger: S32DS 3.4, PEMicro Multilink rev.C Target: internal_FLASH ****************************************************************************************************

******************************************************************************* The purpose of this demo application is to present a usage of the LPI2C-0 as MASTER and LPI2C-1 Slave, using DMA for TX & RX for the S32K324 MCU. ------------------------------------------------------------------------------ * Test HW: S32K3X4EVB-Q257 * MCU: S32K324 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ******************************************************************************** Dinesh_Guleria_0-1709199728594.png Dinesh_Guleria_1-1709199772913.png

******************************************************************************* The purpose of this demo application is to present a usage of the LPSPI IP Driver for the S32K3xx MCU. The example uses LPSPI2 for transmit & receive Twelve bytes using the SPI Interrupt Lpspi_Ip_AsyncTransmit() method . MOSI MISO connected on Hardware in loopback. ------------------------------------------------------------------------------ * Test HW: S32K3X2EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ******************************************************************************** Interrupt Triggered :-- Dinesh_Guleria_0-1733909921359.png Async callback triggered at the end of transfer/reception :-- Lpspi_Ip_AsyncTransmit(&MASTER_EXTERNAL_DEVICE, txBuffer, rxBuffer, numberOfBytes, lpspi_callback_int); Dinesh_Guleria_1-1733909974233.png Dinesh_Guleria_0-1733909770614.png

******************************************************************************************************* * Detailed Description: The purpose of this demo application is to present some usage modes of the eMIOS for the S32K3xx MCU. The application uses the eMios_Pwm driver as OPWMCB ( Center aligned Output PWM Buffered with dead time), OPWMB (Output Pulse Width Modulation Buffered) and OPWMT (Output Pulse Width Modulation Trigger) to generate waveforms. PWM signal generated by EMIOS 0 CH 1 (OPWMCB mode), EMIOS 0 CH 2 (OPWMCB mode), EMIOS 0 CH 3 (OPWMB mode) and EMIOS 0 CH 4 (OPWMT mode). VaneB_1-1731363332793.png Each waveform was manipulated to demonstrate a capability (dead time insertion and phase shift) of the configured mode. VaneB_2-1731363543100.png VaneB_3-1731363559820.png VaneB_4-1731363572325.png VaneB_5-1731363591320.png The application also uses the eMios_Icu driver as ICU_MODE_SIGNAL_MEASUREMENT in SAIC (Single Action Input Capture) mode with interrupts and IPWM (Input Pulse Width Measurement) mode without interrupts to obtain the duty cycle of the captured signal. PWM signal generated by EMIOS 2 CH 8 (OPWMB mode) measured by EMIOS 1 CH 5 (SAIC mode) AND CH 6 (IPWM mode). * Test HW: S32K3X4EVB-T172 * MCU: S32K344 * Debugger: S32DS 3.5, OpenSDA * Target: internal_FLASH *******************************************************************************************************

******************************************************************************* The purpose of this demo application is to present a usage of the MEM_InFls MCAL Driver for the S32K3xx MCU. The example uses MEM_InFls driver to write 128 bytes to FLASH memory address 0x50_0000 . ------------------------------------------------------------------------------ * Test HW: S32K3X2EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ******************************************************************************** Dinesh_Guleria_0-1715852390344.png Results :-- Dinesh_Guleria_1-1715852435648.png Ram location where FLASH writing erase code is placed :-- I placed the code at 256 byte below the MAX address of the RAM size 0x20417DAA = 541162922 Dinesh_Guleria_4-1715852864835.png Dinesh_Guleria_3-1715852777286.png Size of RAM need to save the flashing routine, as per the MAP & linker file :-- 0x00407e64 - 0x00407e38 = 44 bytes Dinesh_Guleria_2-1715852737622.png Dinesh_Guleria_5-1715852986217.png S32K3 FLASH Memory Terminology :-- Dinesh_Guleria_0-1715853503848.png Dinesh_Guleria_2-1715853660788.png Dinesh_Guleria_3-1715853699814.png

******************************************************************************* The purpose of this demo application is to present a usage of the UART IP Driver for the S32K3xx MCU. The example uses LPUART0 for transmit 20 packets with each packet of 21 bytes using the Interrupt in cyclic order. Also when receiving UART packet generate Idle interrupt when variable length of data is received. I used coolterm tool to send the string of data. If Data send by cool term is less than 20 bytes which is set by API call Lpuart_Uart_Ip_AsyncReceive(), then Ideal interrupt is received RTD driver modified in RTD --> Lpuart_Uart_Ip.c. Baudrate : 921600 ------------------------------------------------------------------------------ * Test HW: S32K31XEVB-Q100 * MCU: S32K311 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ******************************************************************************** Terminal Used :-- CoolTerm User can also use following terminal :-- Hercules uart terminal Dinesh_Guleria_0-1713853153843.png Idle Interrupt received :-- Dinesh_Guleria_1-1713853788454.png

Question As we know, the TPPSDK supports S32K144 MCU and various Kinetis MCUs to initialize GD3000 in NXP MC solutions. Because of the release of S32K3 and related SW RTD, it’s necessary to expand the capability of TPPSDK to support S32K3 MC based RTD LLD driver or MCAL driver. Unfortunately, the AA team will not maintain the TPPSDK anymore. How could we configure the GD3000 chip for S32K3 platform? JoaquinL_0-1662367122679.png Answer I took some time to finish this work. Here I'd like to share you the The Expanded TPPSDK Based on S32K3 RTD that is suitable for S32K3 MC application. You can find the Application Note, the source code of new TPPSDK (GD3000 driver), two examples in the attachment. I hope these materials can help you get start with the expanded TPPSDK on S32K3.

******************************************************************************************************** Detailed Description: LPUART1 echoes RX signal at 115200 bps When an 's' char is received, the MCU enters VLPS. A falling edge of the RX signal brings the MCU from VLPS via LPUART RXEDGIF interrupt. BUS_CLK can be monitored at CLKOUT PTD14. In VLPS, BUS_CLK is gated off. -------------------------------------------------------------------------------------------------------------------------- Test HW: S32K144EVB-Q100 MCU: S32K 0N57U Debugger: S32DS_ARM_2.2, OpenSDA Target: internal_FLASH ******************************************************************************************************** danielmartynek_0-1605283306283.png danielmartynek_2-1605283434147.png

------------------------------------------------------------------------------ * Test HW: S32K3 T-BOX * MCU: S32K324 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE Micro * Target: internal_FLASH ******************************************************************************** The purpose of this demo application is to present a usage of the SPI-HAP of S32K3xx MCU to download firmware to SJA1110. SPI using Interrupt working code :-- S32K324_SPI_DMA_SJA1110_Load_firmware__Working__SPI__Interrupt.zip SPI using DMA working code :-- S32K324_SPI_DMA_SJA1110_Load_firmware__SPI_DMA_not_working.zip Firmware image of the SJA1110 is stored inside the S32K3 flash memory.. See the linker file of S32K3, we specify the location where the firmware image is present. Dinesh_Guleria_0-1724463137478.png This this firmware attached to be loaded to SJA1110, any one of the firmware can be selected and renamed to flash_image.bin :-- 1> flash_image.bin --> Green LED blink on SJA1110 2> flash_image_RED.bin --> Green LED blink on SJA1110 If you use your proprietary SJA1110 binary firmware, then this example to work, you have to change this MACO, in SJA1110_APP.h file :-- Dinesh_Guleria_1-1724750091671.png You can get the size of the SJA1110 image from the MAP file of the attached project. Check for this __sja1110_BIN_SIZE, Symbol in MAP file :-- Dinesh_Guleria_2-1724750222059.png Switch connection to S32K3 SPI pins :-- Dinesh_Guleria_0-1724421673930.png LED connected to these pins of SJA1110, on T-BOX hardware :--- Dinesh_Guleria_1-1724421742999.png

特集記事

The S32K3 family of 32-bit AEC-Q100 qualified MCUs combines a scalable family of Arm® Cortex-M7-based microcontrollers built on long-lasting features with a comprehensive suite of production-grade tools. S32K3 MCUs are included in NXP’s Product Longevity Program, guaranteeing a minimum of 15 years of assured supply. The S32K3 offers dedicated peripherals set for rapid motor control loop implementation: enhanced Modular IO Subsystem(eMIOS), Logic Control Unit (LCU), TRGMUX, BodyCross-triggering Unit (BCTU), Analog to Digital Converter(ADC), and Analog Comparator (CMP). The comprehensive motor control ecosystem based on Automotive Math and Motor Control Library(AMMCLib) set, FreeMASTER with Motor Control ApplicationTuning (MCAT) tool and Model-Based Design Toolbox (MBDT) helps to enable S32K3 MCU in wide range of motor control use cases. The table below points to the articles with more detailed description each of S32K3 motor control use cases, hardware description, links to appropriate application notes and their addendums, and software repositories. Device HW Article S32K344 MCSPTE1AK344 12 V development kit engineered for 3-phase PMSM and BLDC motor control applications FOC with dual shunt current measurement Article focuses on solution based Field Oriented Control (FOC) technique (typically used for 3-phase PMSM motors) with dual shunt current measurement and without any position sensor (sensorless). The Encoder sensor is supported by SW option, but missing on HW kit. The available example codes covers both ANSI-C and Matlab Simulink approaches and uses RTD drivers with high-level Autosar compliant API or low-level non-Autosar API. FOC with single shunt current measurement Article focuses on solution based Field Oriented Control (FOC) technique (typically used for 3-phase PMSM motors) with single shunt current measurement and without any position sensor (sensorless). The Encoder sensor is supported by SW option, but missing on HW kit. The single shunt current measurement is advanced technique that allows decrese the cost of Bill of Material (BOM). The available example codes covers both ANSI-C and Matlab Simulink approaches and uses RTD drivers with high-level Autosar compliant API or low-level non-Autosar API. FOC integrated with FreeRTOS Article focuses on integration of motor control software (based on FOC with dual shunt current measurement) and Real Time Operating System (FreeRTOS). The available example code is based ANSI-C code and uses RTD drivers with low-level non-Autosar API. Six-step commutation control. Article focuses on solution based Six-step commutation (6-step) technique (typically used for 3-phase BLDC motors) with Hall position sensor and without any position sensor (sensorless). The available example codes covers both ANSI-C and Matlab Simulink approaches and uses RTD drivers with low-level non-Autosar API. Note: the list of use cases cannot cover all combinations of MCU, current measurement scenario, control technique and sensor inputs, but should work as a base reference for most common configurations. This list is not final, please follow this acticle to be notified about updates with new use cases.

S32K ナレッジベース

S32K Knowledge Base

ディスカッション

Example S32K148 PDB0-PDB1 ring S32DS3.4 RTM4.0.3

S32K144 ISELED + Touch Sensor Demo

All Example S32K311 DS3.5 RTD-3.0.0

S32M2xx - Motor control use cases

Example IP S32K312 EMIO PWM Generation & Duty capture using Interrupt DS3.5 RTD300

Example IP S32K312 PWM ICU using EMIOS DS3.5 RTD300

Example MCAL S32K312 PWM ICU using EMIOS DS3.5 RTD300

S32K312 : ADC Clock selection

Example S32K312 SWT DS3.5 RTD300

S32K344_Example_Ocu_Overflow_Icu_Edge_S32DS34_RTD200_v2

Example S32K324 I2C Transmit & Receive Using DMA DS3.5 RTD300

Example S32K312 SPI Transmit & Receive Using Interrupt DS3.5 RTD300

Example S32K344 eMIOS DS3.5 RTD500

Example MCAL S32K312 MEM_InFls DS3.5 RTD300

S32K311 UART Idle state Interrupt

S32K311 UART Transmit & Receive Using DMA

The new TPPSDK (GD3000 driver) based on RTD for S32K3

Example S32K144 LPUART RXEDGIF VLPS

SENT receiver for S32K118 Design Studio

S32K3 T-BOX : SJA1110 Firmware update using SPI HAP : S32DS-3.5 : RTD-3.0.0

S32K3 Motor control SW examples