Zephyr 外围设备和驱动程序资源 如果您对这些资源有任何疑问或问题，请 提出新问题，恩智浦支持团队将为您解答。 开发人员选择Zephyr的一个重要原因是它提供了大量驱动程序和外围设备支持。 要查找硬件平台支持的最新驱动程序和功能，最佳位置是电路板的文档页面。 例如，此支持功能表列出了FRDM-MCXN947电路板的最新支持。 以下是所有支持Zephyr的电路板的页面链接。 NXP的硬件抽象层（HAL）基于MCUXpresso SDK驱动。 要了解更多信息，请参阅博客Zephyr软件代码与NXP MCUXpresso SDK重用。 大多数用户希望在他们的应用程序中使用Zephyr 驱动程序API以实现可移植性。 但是，如果平台不支持Zephyr驱动程序，或者硬件外设没有Zephyr驱动程序，另一种选择是在Zephyr应用程序中使用MCUXpresso SDK驱动程序。 外设时钟：NXP 拥有丰富的电路板产品组合，支持不同的SoC，提供多种外设选项和多个外设实例。 在为电路板添加Zephyr支持时，许多此类情况无法轻易测试。 从长远来看，NXP希望通过时钟管理子系统来启用和配置时钟，但这尚未被采用。 大多数外设时钟在SOC或电路板源文档中启用。 Zephyr用户在启用或添加板载外设实例时，常见的问题是该实例未正确配置时钟。 通常情况下，一旦知道这一点，启用外设时钟就很简单了 较新的电路板可在board.c文档中启用这些时钟。 例如，frdm_mcxn947_init()为FRDM-MCXN947电路板启用这些时钟。一些较旧的SOC在soc.c中启用时钟。例如，clock_init()为i.MX RT10xx SOC启用这些时钟。 以下是一些针对特定外设和驱动程序的有用资源： 加速器和协处理器 PowerQuad Appnote AN13970在Cadence Tensilica HiFi 4 DSP上运行Zephyr RTOS 模数转换器(ADC) Zephyr样本die_temp_polling用于测量温度 显示器 在Zephyr中，大多数显示器作为子卡启用，这些子卡是附加的硬件模块。 查看Zephyr的子卡列表。 通常来说，电路板页面会记录已测试的显示器子卡。 例如，FRDM-MCXN947电路板页面包括LCD_PAR_S035显示器子卡。 子卡页面说明了如何将该子卡集成至构建系统，并添加到应用程序中。 例如，请参阅LCD_PAR_S035子卡页面。 如果使用VS Code构建，请参阅CMake wiki。  Zephyr有几个使用显示器的示例，包括显示器驱动程序示例和LVGL演示。 直接存储器访问(DMA) 在使用DMA时，请注意缓存一致性，并确保DMA访问的缓冲区不在可缓存存储器中。 这包括使用其他使用DMA的驱动程序，如I2S、SPI、UART等。 spi_loopback测试是在不可缓存存储器中放置缓冲器的良好参考。 内部集成电路音频 (I2S) I2S驱动程序通过Zephyr的i2s_speed测试进行测试。这是一种环回测试，有些电路板需要更改信号连接才能通过测试，请参阅自述文件。 网络 包括以太网 MIMXRT1170-EVK Zephyr 网络性能 串行外设接口(SPI) SPI驱动程序通过Zephyr的spi_loopback测试进行测试。此测试也是一个很好的参考，说明了将DMA缓冲区放置在不可缓存存储器中的选项，请参见上文的DMA。 借助Zephyr的SPI驱动程序，SPI控制器可以通过硬件外设或驱动程序中的软件使用GPIO来驱动芯片选择信号。 要了解更多信息，请参阅硬件芯片选择与GPIO。有一些简单的SPI示例可以说明这一点，请参阅LPSPI硬件片选示例，以及LPSPI GPIO片选示例。 SPI时序参数可以在设备树中配置，请参见LPSPI时序参数示例。 通用串行总线(USB) USB主机 截至2024年5月12日：Zephyr目前不支持USB主机。 USB维护者有此RFC跟踪器，用于计划中的增强，以添加USB主机支持。 但目前只有实验性的Host API。 USB主机堆栈尚未实现，目前也不支持任何USB设备类。 可以按照此RFC跟踪进度和状态。  支持USB设备，Zephyr提供了多个示例应用 返回Zephyr知识中心

MCX W23 Knowledge Hub The MCX W23 is a family of devices. All devices are Arm Cortex®-M33 based wireless microcontrollers for embedded applications supporting Bluetooth Low Energy 5.3. It can be used to develop IoT solutions. MCX W23xA supports LV_SM mode. MCX W23xB supports HV_SM and XR_SM mode. Building on NXP's strong history of providing industrial edge solutions, the MCX W series offers a wide operating temperature range from -40 °C to 125 °C. The Arm Cortex-M33 provides a security foundation, offering isolation to protect valuable IP and data with Trust Zone technology. It simplifies the design and software development of digital signal control systems with the integrated digital signal processing (DSP) instructions. To support security requirements, the MCX W23 also offers support for SHA-1, SHA2-256, AES, RSA, ECC, UUID, dynamic encryption, and decryption of the flash data using a PRINCE engine, debug authentication, and TBSA-M compliance. neidys_vargas_1-1760378278216.png   Documents Reference Manual Fact sheet Data Sheet Errata for MCX W23xUIK MCX W23 Hardware Design Guide Secure Reference manual** European Union Declaration of Conformity for FRDM-MCXW23 FRDM-MCXW23 Board User Manual Bluetooth Specifications The MCX W23 is compatible with the Bluetooth Low Energy 5.3 specification: – Bluetooth Low Energy 5.3 controller subsystem (QDID 200592) – Bluetooth Low Energy 5.3 host subsystem (QDID 226395) – Includes a 48-bit unique Bluetooth device address – Up to 4 simultaneous connections supported The MCX W23 supports the following Bluetooth Low Energy features: – Device privacy and network privacy modes (version 5.0) – Advertising extension PDUs (version 5.0) – Anonymous device address type (version 5.0) – Up to 2 Mbps data rate (version 5.0) – Long range (version 5.0) – High-duty cycle, Non connectable advertising (version 5.0) – Channel selection algorithm #2 (version 5.0) – High output power (version 5.0) – Advertising channel index (version 5.1) – Periodic advertising sync transfer (PAST) (version 5.1) – Supports LE power control feature (version 5.2) RF antenna: 50 Ω single-ended RF receiver characteristics: – Sensitivity −94 dBm in Bluetooth Low Energy 2 Mbps – Sensitivity −97 dBm in Bluetooth Low Energy 1 Mbps – Sensitivity −100 dBm in Bluetooth Low Energy 500 kbps – Sensitivity −102 dBm in Bluetooth Low Energy 125 kbps – Accurate RSSI measurement with ±3 dB accuracy Flexible RF transmitter level configurability: – TX mode 1 (TXM1): Range from −31 dBm to +2 dBm when VDD_RF exceeds 1.1 V – TX mode 2 (TXM2): Range from −28 dBm to +6 dBm when VDD_RF exceeds 1.7   Bluetooth_5.0_Feature_Overview Bluetooth_5.1_Feature_Overview  Bluetooth_5.2_Feature_Overview Bluetooth_5.3_Feature_Overview   Training MCX W Series Training - NXP Community   Equipment Wireless Equipment: This article provides the links to the Equipment that helps to the project development    Application Notes Power Management: AN14660: Power Management for MCX W23: This App Note provides information about the power manager software component. The application uses this component and the operating system to achieve optimal low-power states, based on the requirements of the application. RF: AN14575: MCX W23 Health Care IoT Peripheral Software Architecture: This App Note provides an overview of the software architecture for the MCX W23 Health care IoT Peripheral application. Designed as a model implementation, this application showcases the key features of the MCX W23 platform and serves as a foundation for developing product-quality applications. AN14659: MCX W23 Bluetooth Low Energy Power Consumption Analysis: This App Note describes the power consumption of the MCX W23 Bluetooth Low Energy (LE) device and the procedure to measure the current consumption using the MCXW23_EVK_BB and MCXW236B_RDM boards. AN2731: Compact Planar Antennas for 2.4 GHz Communication: This App Note is not an exhaustive inquiry into antenna design. It is instead focused on helping the customers understand enough board layout and antenna basics to select a correct antenna type for their application, as well as avoiding typical layout mistakes that cause performance issues that lead to delays Security: AN14657: Getting Started with Secure Boot on MCX W23: This application note covers the design of the bootloader ROM code that NXP has developed on the MCX W23, and how to use all its features. Useful Links Bluetooth LE FSCI Host Application running on FRDM-MCXN947 and MCXW23B-Click Board: The Bluetooth LE FSCI Host application demonstrates a host-side implementation for the Health Thermometer use case. It is designed to work alongside the FSCI Blackbox application, which runs on platforms such as the MCXW236 Click Board, FRDM-MCXW236, or other compatible Bluetooth LE wireless MCUs. Transmitter Maximum Output Power Override Application Note Kinetis (../45/47/43;MCX W71/72/70) & MCX W23 Power Profile Tools (including Localization):  This page is dedicated to the Kinetis (KW35/KW38/KW45/KW47/KW43) and MCX W7x (MCX W71/W72/W70) Power Profile Tools. It will help you to estimate the power consumption in your application (Automotive or IIoT) and evaluate the battery lifetime of your solution. Development Tools  VSCode: MCUXpresso for Visual Studio Code (VS Code) provides an optimized embedded developer experience for code editing and development. Zephyr RTOs  NXP Application Code Hub: Application Code Hub (ACH) repository enables engineers to easily find microcontroller software examples, code snippets, application software packs and demos developed by our in-house experts. This space provides a quick, easy and consistent way to find microcontroller applications. NXP SPSDK: Is a unified, reliable, and easy to use Python SDK library working across the NXP MCU portfolio providing a strong foundation from quick customer prototyping up to production deployment. NXP SEC Tool: The MCUXpresso Secure Provisioning Tool us a GUI-based application provided to simplify generation and provisioning of bootable executables on NCP MCU devices. NXP OTAP Tool: Is an application that helps the user to perform an over the air firmware update of an NXP development board. FRDM-RW612

CodeWarrior for StarCore:プロファイリングおよび分析ツール <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> CodeWarrior Development Studioは、アプリケーションの開発、デバッグ、および分析のための共通のインターフェイスを提供します。プロジェクト指向のワークベンチ ウィンドウには、メニューやツール バーに表示されるビュー、エディター、コントロールなど、さまざまなパースペクティブが用意されています。プロジェクトを作成したら、アプリケーションをビルドし、起動構成を定義してから、データ収集とデータ表示を待ちます。   CodeWarrior プロファイリングおよび分析ツールは 、シミュレータとハードウェア上で実行されるアプリケーションを可視化します。この可視性は、アプリケーションの実行方法を理解し、運用上の問題を特定するのに役立ちます。   Freescale StarCore DSPプロセッサ用のソフトウェアを開発するためのCodeWarriorプロファイリングおよび分析ツール・セットを使用すると、データの収集が容易になります。このツールの基本機能は次のとおりです。   • 基本設定は、デバッグ起動設定の「トレースとプロファイル」タブを使用して実行できます •詳細設定は、詳細設定パネルを使用して実行できます。デバッグおよびプロファイリング・ユニット(DPU)、仮想トレース・バッファ(VTB)、およびオンチップ・エミュレータ(OCE)に対して複雑な構成を定義できます •データファイルはチーム間で共有できます HSST(High Speed Simultaneous Transfer)およびSmartDSP HEAT(Host Exchange over Asynchronous Transfer)による高速トレース収集 • トレースバッファの内容を「プロセスにアタッチ」で表示します • そして多くのm a n y more! このガイドの最新情報は こちらから入手してください! 全般

Compile MCU's firmware by yourself Our debug firmware is generally downloaded from the official website of nxp. nxp.com/opensda. But sometimes we want to modify the source code of bootloader and firmware according to our own requirements. So we introduce the open source project daplink. Arm Mbed DAPLink is an open source software project that can program and debug application software running on the Arm Cortex CPU. DAPLink is usually called interface firmware, and it runs on the auxiliary MCU connected to the SWD or JTAG port of the application MCU. It provides k20 bootloader and interface firmware and k26 bootloader and interface firmware. Many frdm boards use k20 as a debugger, and a few boards use k26 as a debugger. board：FRDM-K64 OS：WIN10   steps： 1.Install git, python2.7.11 or above, add these two software to the computer system environment variables (required), it is best to add the scripts folder under python to the environment variables, and install keil.  DAPlink currently only supports IDE keil. 2.Use python to install pip, you can search for tutorials online 3.Install virtualenv, use powershell (hold down shift and click the right mouse button), Input ‘pip install virtualenv’ 4.After that, the commands are all completed under powershell. Get the source code. Input ‘git clone https://github.com/mbedmicro/DAPLink’ Note: You must use git to download the code, or you will fail at compiling the code. It Will generate a DAPLink folder in your current directory 5.Enter the directory. Input ‘cd DAPLink’， The docs/DEVELOPERS-GUIDE.md under this folder is more detailed how to use this DAPLink 6.Create a virtual environment，Input ’virtualenv venv’ 7.Input ‘venv/Scripts/activate.bat’ to active the virtual environment 8.Install necessary tools，’pip install -r requirements.txt’ 9.Generate keil project, input ‘progen generate -t uvision’ It will generate projectfiles/uvision, enter the folder and you will find various bootloader and firmware. The name with ‘bl’ is the bootloader, and the name with ‘if’ is the interface firmware, which is to be dragged into the mcu. Open the first project about k20. After compilation, a bin file will be generated. The bin file with crc is what we want to burn or drag. For the name ‘if’ is the same. The git command will be called during compilation. If you do not add this command to the environment variable, the compilation will fail. This is the bootloader source code Bin file This is interface firmware. The generated bin file with ‘0x’ is firmware address. Generally, the default firmware address of the DAPLink bootloader is 0x8000. As you can see from the above figure, this macro defines DAPLINK_ROM_IF_START, so the file we want to drag is the file with the name ‘0x8000’. If the firmware start address is modified in the bootloader, the interface firmware should also be modified accordingly Burn the bootloader into k20, then drag the interface firmware into k20 to see this result.  

AMF-DES-T2352 - 使用适用于 i.MX 应用处理器的全新“引脚工具” <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Pins Tool 使得引脚的配置、复用和布线变得非常容易和快捷。它提供冲突的实时反馈，并提供具有多种视图的直观图形界面。该工具生成可直接集成到 C/C++ 应用程序中的设备树和源文件。本次培训将提供使用 i.MX 应用处理器开始新项目的解释和演示。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Pins Tool 使得引脚的配置、复用和布线变得非常容易和快捷。它提供冲突的实时反馈，并提供具有多种视图的直观图形界面。该工具生成可直接集成到 C/C++ 应用程序中的设备树和源文件。本次培训将提供使用 i.MX 应用处理器开始新项目的解释和演示。

UC Berkeley Team 9 Freescale Cup technical report

Kinetis V as inverter for Micro turbine? Man powers his home from local stream with DIY micro-hydro plant - StumbleUpon The above project is amazing. Imagine a Kinetis V as the inverter for a micro-turbine based on a PMSM or BLDC ?? Re: Kinetis V as inverter for Micro turbine? Cool!

How to quickly develop i.MX25 products Computer On Module • Processor i.MX25, 400 MHz • RAM 64/128 MB mDDR • ROM up to 2 GB NAND Flash • Power supply Single 3.0V to 5.5V • Size 42.2mm SO-DIMM200 • Temp.-Range -40°C..85°C Key Features • 10/100Mbps Ethernet • High-Speed USB 2.0 OTG • Full-Speed USB 2.0 Host • LCD controller • Still-picture camera interface • Several peripheral interfaces: UART, SD-CARD, I2C, PWM, 1-wire, Keypad, Digital Audio (AC97/I2S), Configurable serial peripheral interface, 4 wire Touchscreen, CAN OS Support • Windows Embedded CE 6.0 • Linux 2.6.35 Application：POS, handheld terminals, building security, anti-theft devices for e-commerce, smart meters and access control For more information, please see Attachment We can provide a complete solution Computer On Module • Processor i.MX25, 400 MHz • RAM 64/128 MB mDDR • ROM up to 2 GB NAND Flash • Power supply Single 3.0V to 5.5V • Size 42.2mm SO-DIMM200 • Temp.-Range -40°C..85°C Key Features • 10/100Mbps Ethernet • High-Speed USB 2.0 OTG • Full-Speed USB 2.0 Host • LCD controller • Still-picture camera interface • Several peripheral interfaces: UART, SD-CARD, I2C, PWM, 1-wire, Keypad, Digital Audio (AC97/I2S), Configurable serial peripheral interface, 4 wire Touchscreen, CAN OS Support • Windows Embedded CE 6.0 • Linux 2.6.35 Application：POS, handheld terminals, building security, anti-theft devices for e-commerce, smart meters and access control For more information, please see Attachment We can provide a complete solution

MPC8541イーサネット(eTSEC)固有のFAQ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> MPC8541イーサネット入力クロックが実際には2クロック(eTSECごとに1つ、名前はTSECn_GTX_CLK125/GPIOm)であることを確認していただけますか?MPC8541 ballmap スプレッドシートには gtx_clk125 ピン (8536 など) が 1 つしか表示されませんが、現在のデータシート (リビジョン E) には 2 つあることが示されています。 ボールマップには、ピンの主要な機能のみが表示されます。デフォルトでは、両方のeTSECは同じクロック、つまりTSEC1_GTX_CLK125 @Y29を共有します。必要に応じて、ユーザーはeTSEC2に別のクロックを使用することを選択できます。eTSEC2 の個別のクロックは TSEC_1588_TRIG_IN1@AH27 で多重化され、PMUXCR[6:7] を使用して構成できます。 イーサネット

HDMI 加密狗 JB4.2.2_1.1.0-GA 补丁发布以修复 Wifi 问题 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 此补丁修复了 HDMI 加密狗 JB4.2.2_1.1.0-GA 中的问题发布 wifi((STA+P2P)/AP) 无法正常启用。 在Android源代码的根目录中，使用以下命令应用补丁： $ git 应用hdmi_dongle_wifi_jb4.2.2_1.1.0.patch 回复：HDMI 加密狗 JB4.2.2_1.1.0-GA 补丁发布以修复 Wifi 问题 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 此补丁在jb4.2.2_1.1.0-ga上失败最新的源代码。有很多文件丢失，有什么解决方法吗？我按照上述说明进行操作。hdmi_dongle_wifi 补丁均不起作用。

Kinetis L MCU Challenge México 2013 CONVOCATORIA Freescale Semiconductor, Inc. Convoca al primer concurso de proyectos “Kinetis L MCU Challenge México” “Kinetis L MCU Challenge México” es una competencia de proyectos tecnológicos basado en la herramienta de desarrollo Kinetis Freedom en la cual el participante construye una aplicación alineada a una de las futuras tres tendencias Salud y Seguridad, Efecto Net o Going Green. Los proyectos finalistas serán presentados durante la final del Freescale Cup 2013 el día 7 de Diciembre, a las 9:00hrs en el Centro de Congresos del Tecnológico de Monterrey Campus Guadalajara.  Si resultas ganador, viajarás con todos los gastos pagados al Freescale Technology Forum (FTF) en Dallas, Texas. ¿Cómo puedo participar? Regístrate en Kinetis Challenge antes del 15 de Noviembre de 2013 Crea una aplicación utilizando la herramienta de desarrollo Freedom (en caso de no contar con ella, puedes adquirirla a través de Element 14 (entrega al siguiente día laborable), Mouser (entrega en 4 semanas), o Digikey (entrega de 3 a 5 días hábiles) . Tienes hasta el 15 de Noviembre para subir la información de tu aplicación a la comunidad de Freescale (es necesario hacer log in con tu cuenta en www.freescale.com😞 Nombre de la aplicación 1 párrafo descriptivo de la aplicación Un video descriptivo de hasta 2 minutos El código fuente en formato .zip Subir el proyecto como documento en la sección de Kinetis Microcontrollers en el siguiente formato:  https://community.freescale.com/docs/DOC-94067 El proyecto deberá contener el tag: "Kinetis L MCU Challenge México" para ser identificado como proyecto participante del concurso. Freescale seleccionará 10 proyectos finalistas basándose en los criterios descritos en la convocatoria. Éstos se presentarán en el evento Freescale Cup 2013 el próximo 7 de Diciembre de 2013. Para conocer a los finalistas ingresa aquí. El proyecto ganador, será elegido durante el evento Freescale Cup 2013 por los asistentes al evento, a través de la comunidad Freescale y redes sociales, basándose en los criterios descritos en la convocatoria. El anuncio del proyecto ganador y la entrega de certificados será el  día del evento. La elección del ganador está en tus manos, sigue las instrucciones aquí. ¡Descubre quién es el ganador aquí! Links de interés: Acerca de Otros Recursos Registro Freedom Development Platform Ejemplos de proyectos con Kinetis www.electronicosonline.net/kinetischallenge FRDM-KL25Z Compra de FRDM-KL25Z en Element14 Kinetis L Microcontrollers Compra de FRDM-KL25Z en Mouser Freescale Cup 2013 Compra de FRDM-KL25Z en Digikey FTF Americas 2014 Cómo subir tu proyecto

NXP Model-Based Design Toolbox for LAX v1.2.0 - Product Release Announcement Product Release Announcement Automotive Embedded Systems NXP Model-Based Design Toolbox for LAX – version 1.2.0 RTM paulvlase_7-1715174465762.png The Automotive Embedded Systems, Model-Based Design Tools Team at NXP Semiconductors, is pleased to announce the release of the Model-Based Design Toolbox for LAX version 1.2.0 RTM. This release supports automatic code generation for ARM Cortex-A53 and NXP LAX Accelerator cores from MATLAB for NXP S32R45 Automotive Microprocessors. This release adds support for RSDK 1.2.0, improves to code generation and Radar processing demo, and adds support for new trigonometric LAX kernels. The product comes with 60 examples, covering the supported RSDK LAX Kernels by MATLAB API and demonstrating the programming of the LAX accelerator from MATLAB environment. Target audience: This product is part of the Automotive SW – Model-Based Design Toolbox.   FlexNet Location: https://nxp.flexnetoperations.com/control/frse/download?element=3983168   Technical Support: NXP Model-Based Design Toolbox for LAX issues will be tracked through the NXP Model-Based Design Tools Community space. https://community.nxp.com/community/mbdt   Release Content: Automatic C code generation from MATLAB® for NXP S32R45: ARM Cortex-A53 NXP LAX Accelerator Support Linux application build and run NXP Auto Linux BSP 37.0 for S32R45 Includes MATLAB API for additional RSDK LAX Kernels highly optimized for LAX accelerator add, sub, mul, div, times, cT, inv abs, abs2, sqrtAbs ¸conj, norm, norm2 diag, eye, zeros, ones, find, sort cospi, sinpi, tanpi, cispi, sincpi acospi, asinpi, atanpi, atan2pi Improved code generation and reduced memory usage Support for Radar SDK version 1.2.0 Support for MATLAB versions: R2021a R2021b R2022a R2022b R2023a R2023b R2024a More than 60 examples showcasing the supported functionalities: Cholesky Gauss-Newton Eigen (new) Kalman Filter Linear Regression Navier-Stokes QR Factorization (updated) MUSIC DoA (updated) Radar processing demo (updated) Range FFT, Doppler FFT, and Non-Coherent Combining offloaded to NXP SPT accelerator MUSIC DoA offloaded to NXP LAX accelerator paulvlase_4-1715173953567.png For more details, features, and how to use the new functionalities, please refer to the Release Notes and Quick Start Guides documents attached. MATLAB® Integration: The NXP Model-Based Design Toolbox extends the MATLAB® experience by allowing customers to evaluate and use NXP LAX Accelerator from NXP’s S32R45 MPU and evaluation board solutions out-of-the-box. NXP Model-Based Design Toolbox for LAX version 1.2.0 is fully integrated with MATLAB® environment. paulvlase_5-1715173953597.png   Target Audience: This release (1.2.0 RTM) is intended for technology demonstration, evaluation purposes, and prototyping on NXP S32R45 MCUs and Evaluation Boards.   Useful Resources: Examples, Trainings, and Support: https://community.nxp.com/community/mbdt paulvlase_6-1715173953613.png

Example S32K144 CMP Windowed Mode use PDB S32DS3.4 RTM4.0.3 *************************************************************************************************************** Detailed Description: Example shows implementation of Analog Comparator ‘45.7.5 Windowed mode (#s 5A & 5B)’ of S32K1XXRM using S32 SDK API. The Comparator is configured to compare analog input 0(AIN0) with half the reference voltage generated with the internal DAC. PDB is used to generate pulse output which is used as sampling windows of CMP block via TRGMUX. PDB period is 5ms, the first 2.5ms WINDOW=1 and the next 2.5ms WINDOW=0. Pdb0PulseOut not only be TRGMUX to Cmp0Sample but also to TrgmuxOut0, so that we are able to observe WINDOW at TRGMUX_OUT0(PTA1) pin. Based on the input from CMP0_IN0 (1kHz external triangle wave) the LEDs light by the following rules: 1) Vin < DAC voltage : RED on, GREEN off 2) Vin > DAC voltage : RED off, GREEN on 3) Unknown state : RED on, GREEN on EVB connection: Signal Function pin S32K144EVB-Q100 WINDOW TRGMUX_OUT0 PTA1 J5.5 2.5ms WINDOW=1 and 2.5ms WINDOW=0 Plus input CMP0_IN0 PTA0 J5.7 Need to connect external 1khz triangle wave COUTA CMP0_OUT PTE3 J1.16 square wave PTC1 PTC1 J5.13 If there is no external triangle wave, a square wave(PTC1) is generated and output to CMP0 (PTA1) * * ------------------------------------------------------------------------------------------------------------------------ * Test HW: S32K144EVB-Q100 * MCU: S32K144UAVLL 0N47T * Target: Debug_FLASH * Compiler: S32DS3.4 * SDK release: S32SDK_S32K1XX_RTM_4.0.3 * Debugger: PEMicro OpenSDA * ------------------------------------------------------------------------------------------------------------------------ Revision History: Ver   Date              Author            Description of Changes 1.0   Nov-9-2023   Robin Shen    Initial version, based on cmp_dac_s32k144 and pdb_periodic_interrupt_s32k144 ***************************************************************************************************************

Energy Efficiency - Kinetis vs. Competitors - Demo Demo Owner: Eduardo Montanez   Watch how Kinetis K Series and Kinetis L Series MCUs beat out the competition.     Features Latest Kinetis K2 microcontrollers running a CoreMark benchmark from EEMBC 4 different Microcontrollers are put to the test. Running all the same iteration benchmark with same capacity for all of the products Featured NXP Products K22F KL02 Links Kinetis MCUs|ARM® Cortex®-M Cores|NXP Kinetis L Series MCUs: Energy-Efficiency Benchmark Demo Kinetis L Series MCUs Energy Efficiency Benchmark - YouTube   Industrial

i.MX Wiki This section for all Freescale i.MX users ranging from customers to designers to help provide the best solution to the most frequently encountered questions related to Freescale i.MX products. Products Below are links to pages containing links to documentation related to that product. i.MX Family i.MX6 Multimedia Applications Processors i.MX53 Multimedia Applications Processors i.MX51 Multimedia Applications Processors i.MX35 Multimedia Applications Processors i.MX31 Multimedia Applications Processors i.MX28 Multimedia Applications Processors i.MX27 Multimedia Applications Processors i.MX25 Multimedia Applications Processors i.MX21 Multimedia Applications Processors Topics Below are links to pages containing links to documentation related to that topic. 19-iMX_Serial_Download_Protocol.py All Boards 2D/3D Graphics All Boards Accessing Registers All Boards Audio All Boards Bluetooth Dongle All Boards Compiling RedBoot All Boards Configuring RedBoot All Boards Creating App Video All Boards Deploy NFS All Boards DirectFB All Boards FlexCAN All Boards Hardware Software All Boards How To Convert RVICE CP15 To OpenOCD All Boards How To Understand JTAG BSDL All Boards I2C-tools All Boards Java All Boards JTAG All Boards LTIB All Boards LTIB Config Ubuntu All Boards LTIB Creating Uimage Uboot All Boards NFS on Fedora All Boards NFS on Slackware All Boards NFS on Ubuntu All Boards OpenEmbedded All Boards Pdfreader All Boards PMIC Registers All Boards Qtopia All Boards Qtopia on Ubuntu All Boards Qt v2 All Boards RedBoot All Boards Serial Console All Boards TCP All Boards Tethering All Boards TFTP All Boards TFTP Fedora All Boards TFTP on OpenSuse All Boards TFTP on Ubuntu All Boards Theora Encoder All Boards Transfer Serial RedBoot All Boards U-boot All Boards Updating RedBoot Through RedBoot All Boards Video All Boards Video Host All Boards VMWare All Boards Wi-Fi All Boards X11 Android Demonstration Platform Exercising the i.MX Serial Download Protocol with a Python Script Gstreamer GTK How to Enable Second Display Showing Different Things on JB4.2.2 SabreSD How to Measure Signal Frequency by Using the Camera Sensor Interface of an i.MX i.MX as a USB Playback/Capture Device on One OTG Port i.MX Bootlets (i.MX233 EVK) i.MX USB Loader i.MXS Development Kit InternalI2C Linux Kernel Mxuart patch New Release of the i.MX OTP Tools V1.3.3 NFS OpenEmbedded Redboot Running ATK on Linux Script to Flash a Linux System into a SD card U-Boot Yoctoproject

Example MPC5746C eMIOS Shifted PWM GHS716 * Example of eMIOS configuration for shifted PWM mode ******************************************************************************** * Test HW: MPC5746C minimodule + MPC57xx Motherboard * Maskset: 1N06M * Target : Internal Flash * Fsys: 160 MHz PLL * ******************************************************************************** Revision History: 1.0 Oct-29-2014 b21190(Vlna Peter) Initial Version 1.1 Nov-20-2014 b21190(Vlna Peter) Modified for Cut2.0 1.2 Apr-23-2015 b21190(Vlna Peter) Added INTC driver and PIT ISR 1.3 May-14-2015 b21190(Vlna Peter) Dissabling SWT in Startup code 1.4 Jun-06-2017 b21190(Vlna Peter) ported for MPC5746C 1.5 Jun-06-2017 b21190(Vlna Peter) eMIOS example with shifter PWM *******************************************************************************/ test

传感器工具箱 GUI 安装程序 Rev.4.2.0.8 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这是传感器工具箱 GUI 修订版 4.2.0.8 的安装程序文件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 这是传感器工具箱 GUI 修订版 4.2.0.8 的安装程序文件 加速度传感器 压力传感器 触摸传感器

KDS Debug Configurations (OpenOCD, P&E, Segger) NOTE: the screenshots below are for KDS V1.0.1-beta!   After creating a new debug configuration is simple: Select either 'GDB OpenOCD Debugging', 'GDB PEMicro Interface Debugging' or 'GDB SEGGER J-Link Debugging' and use the 'new' button: Verify the project and application settings:   After that, there are a few settings to be checked or set, depending on your connection.   OpenOCD with CMSIS-DAP Make sure '-f kinetis.cfg' is specified as 'Other Options':   P&E with OpenSDA or Multilink Select your Interface, Port and Device Name:   Segger J-Link Make sure you use the correct device name (link to Segger web page (scroll there down!) lists all supported devices). OpenSDAv1 and OpenSDAv2 is using SWD. Disable SWO if not supported by your connection: General Re: KDS Debug Configurations (OpenOCD, P&E, Segger) I am using KDS 3.2.0 by selecting PnE as debug option on the FDRM-KE06Z board. I follow the steps above to configure the Debug configurations. But an error message keeps popping-up: "Launching xxx_Debug_PnE' has encountered a problem. Error in services launch sequence Details>> Error in services launch sequence PEmicro GDB Launch Failure : Another GDB Server debug session is alreadyusing the same Server Port number. To run simultaneous debug sessions, please specify a unique Server Port and GDBMI Port in the Debug Configuration for each project. If another session is not running simultaneously, make sure that the pegdbserver_console and the arm-none-eabi-gdb processes have terminated. May i know what's wrong with my PnE configuration on Server Port number? I just have a project file open and build in my project explorer for this time being? Re: KDS Debug Configurations (OpenOCD, P&E, Segger) In case this is helpful: here is how to reprogram the Hexiwear docking station bootloader and firmware: Reprogramming the Mikroelektronika Hexiwear Dockingstation | MCU on Eclipse  I hope this helps, Erich Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Hi Jaime, OpenOCD only supports a limited number of Kinetis devices, and if I'm not mistaken, the KW40 is not supported. I have not used it for the KW40 and used P&E and Segger instead. I can look into how to re-program the K20 on the docking station with the DAPLink bootloader, but for this you will need an external probe in any case. Erich Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Hello! Thanks for your quick response. Heres an image of my debug configuration  The OpenOCD .exe exists on that path. My Hexiwear docking station has Switch 5, (OpenSDA pin) up and both Switches 3 and 4 up to target the KW40Z MCU.  More information that could be helpfull; when i run the openocd.exe from the command line, i get the following text: Thank you very much for your help Jaime Re: KDS Debug Configurations (OpenOCD, P&E, Segger) It would be helpful if you could post screenshots of your debug launch configuration settings. It basically means the GDB client cannot connect to the OpenOCD server (see the same message for Segger J-Link: Fix for GDB and “The system tried to join a drive to a directory on a joined drive”). Can you check that: - openOCD binary is properly referenced in your settings (${openocd_path}/${openocd_executable}) - OpenOCD binary actually exists on that path - Start OpenOCD locally is checked - Your Hexiwear docking station has the properl OpenOCD/CMSIS-DAP firmware loaded ? I hope this helps, Erich Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Hello!  I get this error when trying to program the Hexiwear device with OpenOCD. Error in final launch sequence Failed to execute MI command: -target-select remote localhost:3333 Error message from debugger back end: localhost:3333:The system tried to join a drive to a directory on a joined drive. Any idea on how to fix it? Thanks Re: KDS Debug Configurations (OpenOCD, P&E, Segger) Please, give an example of setting a debug session for OpenOCD FTDI debug interface for K60 Re: KDS Debug Configurations (OpenOCD, P&E, Segger) thanks for a very helpful page! The setup options in KDS are different (more complex) than CW, and I was scratching my head regarding what to do with my j-link (segger).  Lifesaver once again Erich!

视频教程：使用 FRDM-KL25Z 创建和调试项目 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDS V1.0.1（测试版）带有 FRDM-KL25Z 板，其中已加载 P&E OpenSDA 作为固件。 显示的步骤包括创建项目、创建连接和设备的调试配置，然后进行调试。 （在 “我的视频” 中查看） 概述

S32 Design Studio for Power Architecture v2.1 - Update 1 available!       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. General SDKs