S32K ナレッジベース

ディスカッション

******************************************************************************** Detailed Description: Configures the FlexCAN 0 to transmit and receive a CAN message Baudrate to is set to 500kbps. In this config, RXFIFO is used to receive a messages. 16 filter elements are defined in the RXFIFO table. Both standard and extended IDs are used. DMA is enabled in component inspector to read RXFIFO. MB10 is moreover used to receive a message with given standard ID and MB11 is used to transmit a message upon button press. The callback function is installed as well and is it called each time message is received in MB10, RXFIFO or message is transmitted. Note: EVB must be powered by 12V to have SBC's CAN transceiver active * ------------------------------------------------------------------------------ * Test HW: S32K144EVB-Q100 * MCU: FS32K144UAVLL 0N57U * Target: Debug_FLASH * EVB connection: PCAN-View with PCAN-USB Pro connected to CAN port J13 * Compiler: S32DS.ARM.2018.R1 * SDK release: S32SDK_S32K1xx_RTM_3.0.0 * Debugger: Lauterbach Trace32 ******************************************************************************** Revision History: Ver Date Author Description of Changes 0.1 Apr-04-2019 Petr Stancik Initial version *******************************************************************************/

/******************************************************************************** Detailed Description: Example shows possible implementation of multiple ADC conversions using SDK. Here 25 channels are sampled periodically. 2 ADC modules and 2 PDBs are used. ADC0 is configured to sample 16 channels, ADC1 9 channels. PDBs are set to back-to-back mode to perform chain conversion. Within ADC component you need to select ADC input to be measured for each item in configuration list. For ADC0 channels ADC ch12 is selected, as it is connected to trimmer on the EVB. DMA is used to read result into single buffer, and DMA callbacks are issued to indicate end of transfer for each ADC module. Within those callbacks PTE14 and PTE15 is toggled. PDB0 output pulse is generated on the PTE16 to indicate start of ADC measurement. This is done periodically at LPIT ch0 rate, which is set to 30us. The ADC0 ch0 result is used to dim LEDs. * ------------------------------------------------------------------------------ * Test HW: S32K144EVB-Q100 * MCU: FS32K144UAVLL 0N57U * Target: Debug_FLASH * EVB connection: * Compiler: S32DS.ARM.2018.R1 * SDK release: S32SDK_S32K1xx_RTM_3.0.0 * Debugger: Lauterbach Trace32 ******************************************************************************** Revision History: Ver Date Author Description of Changes 0.1 May-04-2019 Petr Stancik Initial version *******************************************************************************/

Hello, NXP does a big change on document structure. Generally, you can find pin assignment table, interrupt mapping and memory map table in RM. But now, these information change to Excel files and attached in RM. For example on S32K. You will find the words in RM, like 'For reset values per port, see IO Signal Description Input Multiplexing sheet(s) attached to the Reference Manual.' Then, please go to attachment tab of your PDF file viewer, like Adobe Acrobat Reader DC. These steps are also fit for MPC57xx , S32R family. Cheers! Oliver

******************************************************************************** Detailed Description: Example shows how to use FlexCAN 0 Pretended networking mode to allow FlexCAN module to wake up MCU from STOP mode using SDK. Wake up by Timeout and wake up by Match events are enabled. Also pin interrupt can be used to exit STOP mode. So MCU enters STOP mode by pressing SW3 button. MCU exits STOP mode when one of following happens: - no CAN message comes in 8sec (CAN PN timeout event) - message with standard ID 0x554 or 0x555 comes (CAN PN match event) - SW2 button is pressed (PTC12 interrupt) In run mode blue LED is dimming and the rate is different for each wakeup event ------------------------------------------------------------------------------ Test HW: S32K116EVB-Q48 MCU: PS32K116LAM 0N96V Compiler: S32DS.ARM.2.2 SDK release: S32SDK_S32K1xx_RTM_3.0.0 Debugger: Lauterbach, OpenSDA Target: internal_FLASH ********************************************************************************

******************************************************************************************************* Detailed Description: Configures the MCU to run system clock from XOSC. LPUART1 is set to respond to LIN header sent from master. Based on ID received the LPUART1 either receive frame's data and compare checksum or publish requested data with calculated checksum. Enhanced checksum is used. Interrupt is used for RX and TX operation and 2 versions of interrupt routine are available. VER 1 ... during response transmission receiver disabled and transmit interrupt enabled VER 2 ... during response transmission receiver is kept enabled ------------------------------------------------------------------------------ Test HW: S32K116 EVB-Q048 MCU: PS32K116LAM 0N96V Fsys: 40MHz Debugger: Lauterbach Target: internal_FLASH ******************************************************************************************************

******************************************************************************** Detailed Description: Example shows how to use FlexCAN 0 Pretended networking mode to allow FlexCAN module to wake up MCU from STOP mode. Wake up by Timeout and wake up by Match events are enabled. Also pin interrupt can be used to exit STOP mode. So MCU enters STOP mode by pressing SW3 button. MCU exits STOP mode when one of following happens: - no CAN message comes in 8sec (CAN PN timeout event) - message with standard ID 0x554 or 0x555 comes (CAN PN match event) - SW2 button is pressed (PTC12 interrupt) In run mode blue LED is dimming and the rate is different for each wakeup event ------------------------------------------------------------------------------ Test HW: S32K144 EVB-Q100 MCU: FS32K144UAVLL 0N57U Fsys: 160MHz Debugger: Lauterbach, OpenSDA Target: internal_FLASH ********************************************************************************

Dear all, I'd like to share some useful tips about S32DS for ARM v2018.R1 IDE and S32K1xx development in Chinese as below: 《S32DS使用Tips--SDK使用常见问题(FAQ)答疑》；《S32K SDK使用详解之S32 SDK软件编程思想详解》；《S32K SDK使用详解之S32 SDK软件架构详解》；《 S32K1xx系列MCU使用Tips--功能介绍及软件开发和硬件设计FAQ》；《 S32K1xx系列MCU使用Tips--Flash加密后不断复位无法连接调试器的问题解决》；《S32DS使用Tips--S32DS for Power V1.2 链接文件和启动过程详解》；《S32K1xx系列MCU使用Tips之SDK软件架构和使用详解》；《S32DS使用Tips--SDK使用常见问题(FAQ)答疑》；《S32DS IDE使用Tips--应用工程调试常见问题(FAQ)答疑》；《 S32DS 使用Tips之S32DS for Power不同版本之间的GNU工具链差异与外设寄存器位域访问问题总结》；《 S32DS使用Tips之S32DS for Power v1.1应用工程升级到v1.2重新编译运行程序跑飞问题解决》；《S32DS 使用tips--S32DS for ARM v1.3工程到S32DS for ARM V2.0迁移升级方法和注意事项》；《 S32DS 使用 tips--工程属性配置(编译选项和C编译器、汇编器及链接器设置)》；《 S32DS使用Tips--如何编译生成和调用静态库》；《S32DS使用Tips--如何通过创建新的编译目标(Build Target)在同一个S32DS工程中同时编译静态库和应用程序》；《 S32DS使用Tips--如何配置和使能Attach功能定位软件程序bug和完成bootloader与应用程序工程的联合调试》；《 CodeWarrior与S32DS IDE使用 Tips之如何在应用工程中保留定义但未使用的全局常量、变量(用于参数标定)》；《 S32DS 使用 tips--使用Flash from file下载S19或elf文件》；《S32DS for ARM v2018.R1安装IAR Eclipse插件调用IAR工具链开发S32K系列MCU应用程序详解》 For more contents, please follow below link: “汽车电子expert成长之路”微信公众号最新最全原创技术分享文章列表 ; Hope this can help you and have a nice day~! Best regard, Enwei Hu(胡恩伟)

******************************************************************************** Detailed Description: Configures the FlexCAN 0 to transmit and receive message into RXFIFO. LOOPBACK mode is enabled. Two IDs are set into RXFIFO ID table. DMA is configured to read the message from RXFIFO. Within DMA major interrupt the new message is send according to which Identifier Acceptance Filter was hit. ------------------------------------------------------------------------------ Test HW: S32K144 EVB-Q100 MCU: PS32K144HFVLL 0N77P Fsys: 160MHz Debugger: Lauterbach Target: internal_FLASH ******************************************************************************** Revision History: 1.0 Sep-4-2017 Petr Stancik Initial Version *******************************************************************************

To accelerate S32K demand creation and support urgent evaluation requriement in Great China, we build one batch boards locally. These boards will only be given out to our potential opportunities for free. The boards are made by China local partner and verified by AE and FAE team. if you have any question on this kind of board, please go to China Auto CAS or Auto MCU marketing for support. 1. Board overview 2. Pinout 3. Test point 4. Block diagram 3. The main difference between NXP official S32K EVB and this FRDM-S32K144 board are OpenSDA firmware and CAN PHY The original OpenSDA firmware in this board is from MBED which is not supported by S32DS, thus we need to change to PEmicro OpenSDA firmware, and then we can use S32DS for development. Unplug the USB cable (if attached). Press and hold the Reset button. Plug in a USB cable from a USB Host to the OpenSDA USB port. Release the RESET/Bootloader button. A removable drive will be visible in the host file system with a volume label of BOOTLOADER. Drag/drop or copy/paste attached firmware “DEBUG-FRDM-K64F_Pemicro_v108a_for_OpenSDA_v2.0.bin” into the removable drive. Unplug the USB cable and plug it in again. The OpenSDA application should now be running. The CAN physical is different. This board used standalone CAN PHY but not CAN SBC. Please refer SCH file for debug. Original Attachment has been moved to: dmeo2.rar

******************************************************************************** * Detailed Description: * * This example shows how to use the back-to-back mode of the PDB to trigger * sequence of ADC channels conversion. 4 PDB channel pre-triggers/triggers are * generated upon single PDB SW trigger. The first trigger is started by the PDB, * no delay is used. Next 3 triggers start after corresponding acknowledgment is * received from ADC. * * DMA is configured to read the ADC result registers. * Within DMA major interrupt the new conversion scan is started via PDB SW request. * * Converted data is used to change color of the EVB led based on Trimmer position. * * ------------------------------------------------------------------------------ * Test HW: FRDM-S32K144 * MCU: PS32K144HFVLL 0N77P * Fsys: 160MHz * Debugger: S32DS * Target: internal_FLASH * ********************************************************************************

******************************************************************************** * Detailed Description: * * This example shows how to init DMA for simple memory to memory copy. * Eight 16-bit values are copied upon SW start. * * ------------------------------------------------------------------------------ * Test HW: FRDM-S32K144 * MCU: PS32K144HFVLL 0N77P * Fsys: default * Debugger: S32DS * Target: internal_FLASH * ******************************************************************************** Original Attachment has been moved to: Example-S32K144-DMA-RAM2RAM-test-v1_0-S32DS.zip

******************************************************************************** * Detailed Description: * This simple example shows how to force function to RAM memory in S32 Design * Studio and how to perform flash functions (Erase flash sector and Program * phrase command in this case). * * ------------------------------------------------------------------------------ * Test HW: FRDM-S32K144 * MCU: PS32K144HFVLL 0N77P * Fsys: default * Debugger: Lauterbach Trace32 * Target: internal_FLASH * ********************************************************************************

特集記事

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 complient 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 complient 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 S32K144 FlexCAN RXFIFO DMA S32DS.ARM.2018.R1

Example S32K144 PDB ADC DMA S32DS.ARM.2018.R1

How to get pin assignment, interrupt mapping and memory map details

Example S32K116 FlexCAN PN STOP S32DS.ARM.2.2

Example S32K116 LPUART LIN Slave TXRX ISR S32DS.ARM.2.2

Example S32K144 FlexCAN Pretended Networking STOP mode test S32DS.ARM.2.2

S32K LPUART hardware flow control

some useful tips about S32DS for ARM v2018.R1 IDE and S32K1xx development

Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13

Using S32K CMSIS-SVD Files in EmbSysRegView Eclipse Plugin

FRDM-S32K144 EVB

Example S32K144 PDB ADC trigger DMA ISR S32DS

Example S32K144 DMA memory copy test S32DS

Example S32K144 Flash RW simple

S32K3 Motor control SW examples