恩智浦技术研讨会 - 工业系统的免提、低延迟、安全语音控制 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 查看网络研讨会录音 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 查看网络研讨会录音 i.MXRT 106x

示例 MPC5748G DPM 多核 GHS614 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明： * 此示例演示了如何使用 lauterbach 多核项目。 * 所有 MPC5748G 核心 (z4a、z4b、z2) 均处于活动状态。带有核心 z4a 的微型靴子。 * 在 z4a 上执行微配置，然后在 Core_Init(); 函数中执行 * 启动另外 2 个核心（z4b 和 z2）。 * 示例还包括 Lauterbach 多核 (多 powerview) 示例脚本 *+T32配置文件 * ---------------------------------------------------------------------------------------------- * 测试硬件：MPC57xx MB + * 面罩组：1N81M * 目标：SRAM * 系统频率：160 MHz PLL * ******************************************************************************** 修订历史： 1.0 2014年10月29日 b21190（Vlna Peter）初始版本 1.1 2014 年 11 月 20 日 b21190（Vlna Peter）针对 Cut2.0 进行了修改 1.2 2014 年 11 月 20 日 b21190（Vlna Peter）添加了在启动时禁用 SWT_0 1.3 2016 年 2 月 12 日 b21190（Vlna Peter）针对多核项目进行了修改 ********************************************************************************************/ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明： * 此示例演示了如何使用 lauterbach 多核项目。 * 所有 MPC5748G 核心 (z4a、z4b、z2) 均处于活动状态。带有核心 z4a 的微型靴子。 * 在 z4a 上执行微配置，然后在 Core_Init(); 函数中执行 * 启动另外 2 个核心（z4b 和 z2）。 * 示例还包括 Lauterbach 多核 (多 powerview) 示例脚本 *+T32配置文件 * ---------------------------------------------------------------------------------------------- * 测试硬件：MPC57xx MB + * 面罩组：1N81M * 目标：SRAM * 系统频率：160 MHz PLL * ******************************************************************************** 修订历史： 1.0 2014年10月29日 b21190（Vlna Peter）初始版本 1.1 2014 年 11 月 20 日 b21190（Vlna Peter）针对 Cut2.0 进行了修改 1.2 2014 年 11 月 20 日 b21190（Vlna Peter）添加了在启动时禁用 SWT_0 1.3 2016 年 2 月 12 日 b21190（Vlna Peter）针对多核项目进行了修改 ********************************************************************************************/

JustInTime_Milestone_3 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我们已经在 bitbucket 上上传的 JustInTime_Milestone_3.doc 文件中描述了此视频中发生的事情 （在 “我的视频” 中查看）

AMF-INS-T2024 - 半導体 101/102: 集積回路の機能と製造 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エレクトロニクス業界に携わる多くの人々は、製造サイクルタイム、半導体ファブの集約、故障解析結果などの問題を理解するために、半導体部品に関する基本的な知識を必要としています。このセッションは、技術者以外の聴衆を対象としており、半導体デバイスとその製造方法の概要を説明します。講義は、半導体デバイスの仕組みについて簡単に説明するところから始まります。プレゼンテーションの大部分は、使用される機器/設備の複雑さと必要なプロセス時間に重点を置いて、半導体デバイスの一般的な製造フローについて説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エレクトロニクス業界に携わる多くの人々は、製造サイクルタイム、半導体ファブの集約、故障解析結果などの問題を理解するために、半導体部品に関する基本的な知識を必要としています。このセッションは、技術者以外の聴衆を対象としており、半導体デバイスとその製造方法の概要を説明します。講義は、半導体デバイスの仕組みについて簡単に説明するところから始まります。プレゼンテーションの大部分は、使用される機器/設備の複雑さと必要なプロセス時間に重点を置いて、半導体デバイスの一般的な製造フローについて説明します。

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

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 应用处理器开始新项目的解释和演示。

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 ***************************************************************************************************************

PCT2075 - Temperature data streaming using UTICK timer on the LPC55S06-EVK Hi Everyone, In this document I would like to present a very simple example code I created for the PCT2075. This I2C digital temperature sensor offers a resolution of 0.125°C with an accuracy of ±1°C over -25°C to 100°C range. It operates with a single supply from 2.7V to 5.5V and has three address pins, allowing up to 27 devices to operate on a single I2C bus without address collisions. The device also includes an open-drain output (OS) which becomes active when the temperature exceeds the programmed limits. NXP offers the PCT2075DP Arduino Shield and GUI for easy evaluation of this temperature sensor. However, I have decided to pair this demo board with the LPC55S06-EVK and create a simple example code in the MCUXpresso IDE using Config tools (Pins, Clocks and Peripherals). The connection is very straightforward. The PCT2075DP-ARD daughter board is inserted to J9, J10, J12 and J13 connectors located on LPC55S06-EVK development board. Both SDA pin (J1-5) and SCL (J1-6) lines are connected through the on-board 5.6K pull-up resistors to the FlexComm1 SDA (PIO0_13, J13_9) and SCL (PIO0_14, J13_11) pins on the LPC55S06-EVK board. The VCC pin (J6-4) is connected to the 3.3V supply voltage and the GND pin to common ground. The address select pins A0, A1 and A2 are connected to GND using jumpers between pins 2 and 3 of J7, J8 and J9, resulting in a 7-bit I2C slave address of 0x48. I created a new project in MCUXpresso IDE v11.3.0 based on SDK_2.8.2_LPCXpresso55S06 using the New project wizard: Capture 1.JPG It was not necessary to make any changes to the project and I named it LPC55S06 PCT2075 Temp reading using I2C in the wizard: Capture 2.JPG Let’s start with the Pins Config tool...: Open Pins.JPG ...to configure PIO0_13 and PIO0_14 for their I2C functions (I2C_SDA and I2C_SCL, respectively). Simply search for each pad in the Pins view: Capture 3.JPG In the diagram above, I already have PIO0_13 routed for I2C function (it is showing green). However, you may want to check the checkbox in the first column to mark the pin for routing. A dialog pops up, offering you all the possible pin multiplex functions for the pad. Scroll down through the list and select FlexComm1’s SDA function: Capture 4.JPG When you put a checkmark (“tick”) in the FC1_CTS_SDA row, the Pins Config tool routes the pad and you will see a new entry (in yellow) in the Routed Details view at the bottom of the perspective: Capture 5.JPG Follow the same procedure to route PIO0_14 for function FC1_SCL. That is already done in the screen-grab above, so I am ready to move to the Peripherals Config tool.  Use the Peripherals icon to switch to the Peripherals perspective: Capture 6.JPG The Peripherals Config tool identifies that I have set up the pads/pins for FlexComm1 to be used as I2C. But I have not yet set up the I2C peripheral, and so the tool reports a Warning: Capture 7.JPG There is a very simple fix, proposed by the tool. Select the FLEXCOMM1 warning line, and right-click to bring up a context menu: Capture 8.JPG Selecting “Initialize FLEXCOMM1 peripheral” opens a dialog where I can select the desired function for FlexComm1… in this case I want I2C configuration. So I select I2C and click [OK]: Capture 9.JPG The Peripherals Config tool displays the Flexcomm Interface I2C configuration screen. This shows all of the ‘top level’ settings for the I2C module. I configured it as follows: Capture 10.JPG As the PCT2075 does not have a data ready interrupt, I use the MicroTick (UTICK0) timer to read the Temp register periodically at a fixed rate of about 10Hz since the temp-to-digital conversion is executed every 100 ms. The UTICK0 is configured in the Peripherals Config tool as follows: Capture 11.JPG I am ready to move to the final, Clocks Config tool: Capture 12.JPG I chose to use the BOARD_BootClockFRO12M() functional group: Capture 13.JPG Then I enabled the clock to FlexComm1, since this is the FlexComm module that I use for I2C. I used the fro_12m as the clock source for FlexComm1 I2C: Capture 14.JPG Finally I enabled the fro_1m and attached the fro_1m to the UTICK timer: Capture 15.JPG All the configuration is now complete. I can click “Update Code” at the top of the screen to generate all of the necessary configuration code, accept the changes, and return to the C/C++ Develop perspective. In the UTICK0_Callback function, the Temp register is read and then the real temperature in °C is calculated as shown below. For more information on how to convert the raw values from the Temp register to real values in °C, please refer to the PCT2075 data sheet (Chapter 7.4.3). Capture 16_1.JPG This screenshot shows the two bytes read of the Temp register (0x00).  Traffic.JPG The calculated temperature can be watched either in the "Global Variables" window on the top right of the Debug perspective...: Temp 3.JPG ...or in the Console window: Temp Console.JPG Attached you can find the complete project developed in the MCUXpresso IDE v11.3.0. If there are any questions regarding this simple application, please feel free to ask below. Regards, Tomas

传感器工具箱 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 的安装程序文件 加速度传感器 压力传感器 触摸传感器

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

Activating multiple Tags using NFC Reader Library Hello NFC enthusiasts,   In the NFC communication protocol, when a device acts as a NFC reader (it provides its own field), it is waiting for a tag to approach. When this occurs, the reader energizes the tag and depending on the application, it can read from or write to a tag.   When multiple tags are in the field, the power decreases according to the number of tags being energized, for which the tag operations will not work properly. For this, there is a process called anti-collision, in which the reader decides, from the detected tags, one to work with.   The purpose of this document is to demonstrate the activation of each tag at a given index.   This demonstration is going to be made with two NTAG 216.     This demonstration is based on NXP NFC Reader Library v05.02.00, NfcrdlibEx3_NFCForum project for PNEV7462B, in which some modifications are going to be made in order to carry this out. These tags are compliant with NFC Forum Type 2 Tag and ISO/IEC14443 Type A specifications.    In phacDiscLoop.h modify the max number of cards supported (two cards for this demonstration):   #define PHAC_DISCLOOP_CFG_MAX_CARDS_SUPPORTED 0x02U      In NfcrdlibEx3_NFCForum.c add the following code in LoadDiscoveryConfiguration():   static phStatus_t LoadDiscoveryConfiguration() { ... /*Passive max typea devices*/ status = phacDiscLoop_SetConfig(pDiscLoop, PHAC_DISCLOOP_CONFIG_TYPEA_DEVICE_LIMIT, 2); CHECK_STATUS(status); }   A fix to the SW stack has to be made (Fix will be implemented in the next release): open "phacDiscLoop_Sw_Int_A.c", line 511, change if statement as below.     if((pDataParams->sTypeATargetInfo.bTotalTagsFound > 1) && ((bTypeATagIdx) < pDataParams->sTypeATargetInfo.bTotalTagsFound))     Until now, the reader is able to detect a maximum of two tags and work with up to two type A devices.   The activation of a tag at a given index is possible to the phacDiscLoop_ActivateCard() function.   Once this function is called, it will receive the discovery loop data parameters, the type of tag and the index of a tag to be activated.   The code will be added after knowing that multiple tags are detected and resolved in the NfcrdlibEx3_NFCForum.c file.   else if((status & PH_ERR_MASK) == PHAC_DISCLOOP_MULTI_DEVICES_RESOLVED) { /* * Multiple cards resolved. It enters here if DEVICE LIMIT > 1 and more than one devices are * detected and resolved. */ DEBUG_PRINTF (" \n Multiple cards resolved: \n"); /* Get detected technology type */ status = phacDiscLoop_GetConfig(pDiscLoop, PHAC_DISCLOOP_CONFIG_TECH_DETECTED, &wTagsDetected); CHECK_STATUS(status); /* Get number of tags detected */ status = phacDiscLoop_GetConfig(pDiscLoop, PHAC_DISCLOOP_CONFIG_NR_TAGS_FOUND, &wNumberOfTags); CHECK_STATUS(status); DEBUG_PRINTF ("\tNumber of tags: %d \n",wNumberOfTags); /* Code */ ... } Note: The code to be inserted in the comment /* Code */ is below in the Code section of this document.   The demonstration will be as simple as activating one tag, read its NDEF message, activate the second tag and read its NDEF message as well so that we make sure the activation process is performed correctly.   Each tag was previously written with a text NDEF message respectively.   Tag 1: Text: Hallo! Language: de   Tag 2: Text: ¡Hola! Language: es   Writing to a tag can be done by making use of our TagWriter app available in the play store: NFC TagWriter by NXP - Aplicaciones de Android en Google Play    Code section:   uint8_t bTagState1; /* Tag 1 */ /* Activate tag at index 0 */ status = phacDiscLoop_ActivateCard(pDataParams, PHAC_DISCLOOP_TECH_TYPE_A, 0x00); /* Check for NDEF presence */ status = phalTop_CheckNdef(palTop, &bTagState1); /* Read NDEF message */ status = ReadNdefMessage(PHAL_TOP_TAG_TYPE_T2T_TAG); DEBUG_ERROR_PRINT(status); /* Tag 2 */ /* Activate tag at index 1 */ status = phacDiscLoop_ActivateCard(pDataParams, PHAC_DISCLOOP_TECH_TYPE_A, 0x01); /* Check for NDEF presence */ status = phalTop_CheckNdef(palTop, &bTagState1); /* Read NDEF message */ status = ReadNdefMessage(PHAL_TOP_TAG_TYPE_T2T_TAG); DEBUG_ERROR_PRINT(status);   Behavior shown in the console monitor:   NFC Forum Example:       This implementation demonstrated the activation of two type A tags at a given index. I hope this is of great help!   Best regards, Ivan. Original Attachment has been moved to: Project-files.zip

OpenCV 3.1 支持 mx6q 板 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> OpenCV（开源计算机视觉库）是在 BSD 许可下发布的，因此对于学术和商业用途都是免费的。它具有 C++、C、Python 和 Java 接口，并支持 Windows、Linux、Mac OS、iOS 和 Android。OpenCV 的设计注重计算效率，并重点关注实时应用。该库采用优化的 C/C++ 编写，可以利用多核处理的优势。通过 OpenCL 的支持，它可以利用底层异构计算平台的硬件加速 在当前的bsp中，支持opencv 2.4，但是有些客户想要使用opencv 3.1，那么可以使用morty yocto bsp来安装opencv。 步骤1： 有关如何在 ubuntu 上安装软件包以及如何构建环境，请参阅 bsp 用户指南，有关如何构建分支 morty，请尝试使用以下命令： 机器=imx6qsabresd源fsl-setup-release.sh-b build_qt5-e fb 第 2 步： 关于如何启用 opencv，请在 local.conf 中添加以下命令，路径为 fsl-release-bsp/build/conf， "CORE_IMAGE_EXTRA_INSTALL += "libopencv-core-dev libopencv-highgui-dev libopencv-imgproc-dev libopencv-objdetect-dev libopencv-ml-dev" CORE_IMAGE_EXTRA_INSTALL += “opencv-应用程序 opencv-dev python-opencv python-模块”” 然后通过 bitbake 再次构建。 然后您可以在 fsl-release-bsp/build/tmp/deploy/images/im6qsabresd/ 中找到该图像，提取 rootfs 文件时可以找到 opencv 库 步骤3： 然后您可以使用 dd 命令或 mfgtool 将图像文件下载到板上并使用 opencv 库文件。 其他用法： 可以安装 populate_sdk 来构建源代码，对于 opencv 3.1，也许你会发现一些需要修复的 g++ 问题，所以只需简单介绍一下 使用命令：bitbake -c populate_sdk fsl-image-gui（例如） 然后您可以在fsl-release-bsp/build_x11/tmp/deploy/sdk中找到sdk安装文件，运行安装文件，在/opt/poky中设置安装文件，安装成功后您可以在/opt/poky中找到工具链。

Program the firmware to PNEV5180B board When the PNEV5180B cannot work with the Cockpit, you can re-program the firmware to the board. Below are the steps show you how to program the firmware to the board again. 1. If you don't have the MCUXpresso, please download the MCUXpresso from the NXP web first. MCUXpresso Software and Tools for ARM® Cortex®-M cores|NXP  2. Install the MCUXpresso IDE v10.0.0 to your PC. 3. Configure PNEV5180 board to use external power supply J101, and then power up the board. There is 10-pin ARM Cortex header on the PNEV5180B , connect  LPC-Link2 debug probe to it (J7) by using flat cable and also connect debug probe to the PC host over USB mini cable - both jumper on debug probe are open (JP1 and JP2). 4. Start MCUXpresso IDE and import any LPC1769 project from filesystem. For example: SW3522.zip. This is important to give programmer right definitions. SW3522 can be downloaded from here : NFC Reader Library v4.040.05.011646 R1 for PNEV5180B including all software examples  5. After import the SW3522, you can try to build the example and run the example on your board. e.g. NfcrdlibEx1_BasicDiscoveryLoop. Click LinkServer GUI Flash programmer icon on the main menu. When started programmer tool will check if LPC-Link2 debug probe is attached. 6. Browse to the C:\nxp\NxpNfcCockpit_v4.0.0.0\firmware\Secondary_PN5180\BootLoader_And_Nfcrdlib_SimplifiedAPI_EMVCo_Secondary.bin. Set the Base address to 0x0. 7. Flash Write Done. 8. After this, reset the board and to start NFCCockpit v4.0.0.0. The board will be recognized. P.S. The board is connected to PC via VCOM. If there is any driver issue, please try to re-install the VCOM driver and restart the PC. The VCOM driver can be found in the C:\nxp\NxpNfcCockpit_v4.0.0.0\VCOM. Re: Program the firmware to PNEV5180B board Your content helped me a lot to take my doubts, thank you very much...  9apps

Ment_Milestone_4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我们翻唱了深紫乐队的《水上烟雾》。 （在 “我的视频” 中查看） 2017 年 Linux 嵌入式挑战赛 回复：Ment_Milestone_4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 超级皮重！