Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
AMF-DES-T2360 - EMI Made Simple: It's All About the Space! Signal integrity, EMI, RFI...They are all the result of how well you manage the Electromagnetic fields in your designs. EM fields live in spaces, not conductors. The material presented focuses on the basic physics of electromagnetic energy, presented in an entertaining and easy-to-understand format with plenty of diagrams. Attendees will discover how understanding the behavior of EM fields can help them to design PCBs that will be more robust and have better EMC performance. This is not rocket science, but an easy-to-understand application of PCB geometry. Signal integrity, EMI, RFI...They are all the result of how well you manage the Electromagnetic fields in your designs. EM fields live in spaces, not conductors. The material presented focuses on the basic physics of electromagnetic energy, presented in an entertaining and easy-to-understand format with plenty of diagrams. Attendees will discover how understanding the behavior of EM fields can help them to design PCBs that will be more robust and have better EMC performance. This is not rocket science, but an easy-to-understand application of PCB geometry.
View full article
使用 blhost 编程/擦除 LPC54(S)0xx 闪存 注意:本文档提供了简单的描述,有关 flashloader 的详细信息可以在 SDK_2.5.0_LPCXpresso54S018\middleware\mcu-boot\doc 中的 LPC540xx Flashloader 用户指南入门.pdf 中找到 下载LPC54S0xx SDK。 编译flashloader工程,生成flashloader.bin 该项目位于sdk\boards \lpcxpresso54s018\bootloader_examples\flashloader 使用 dfu-util.exe 或 IDE 将 flashloader.bin 加载到 RAM 中。 dfu-util 可以从http://dfu-util.sourceforge.net/releases/下载 配置ISP引脚,然后复位芯片,使芯片进入USB1 DFU启动模式。 Boot mode ISP2 PIO0_6引脚 ISP1 PIO0_5引脚 ISP0 PIO0_4引脚 描述 USB1 DFU启动 低 低 高 USB DFU 类用于通过 USB1 高速端口将图像下载到 SRAM 中。 将LPC54S0xx设备USB1高速口与PC通过USB连接。以下是加载flashloader.bin的命令行: $ dfu-util.exe –D flashloader.bin   使用 blhost 编程/擦除 LPC540xxM/LPC54S0xxM 闪存 一旦下载了闪存加载程序二进制文件并在 LPC54S0xx 平台上开始执行,并且 LPC54S0xx 平台USB1(高速)和主机之间仍然保持物理 USB 连接,闪存加载程序将准备好接收命令。 blhost -u 0x1fc9,0x01a2 --获取属性 12 blhost -u 0x1fc9,0x01a2 --填充内存0x2000d000 4 0xc0000004 blhost -u 0x1fc9,0x01a2 --配置内存 0xa 0x2000d000 blhost -u 0x1fc9,0x01a2 --获取属性 25 0xa blhost -u 0x1fc9,0x01a2 -t 100000 --闪存擦除区域 0x10000000 0x100000 blhost -u 0x1fc9,0x01a2 -t 100000 --写入内存 0x10000000 xxx.bin 注: xxx.bin为需要下载到flash中的目标文件。 作者:刘浩 感谢刘浩。
View full article
示例 MPC5777M MCAN 简单 TX/RX GHS614 ******************************************************************************** * 详细说明: * * 配置 MCAN 来传输和接收 CAN 消息。 * * 在此配置中,MCAN_1 传输一条消息。MCAN_2接收消息。 * * MCAN_1 每 1 秒发送一次消息。该间隔由 PIT 生成。 * 单个 TX 缓冲区用于发送 n 个字节。每次 * 传播。发送两个标准 ID 和 2 个扩展 ID。 * * MCAN_2 配置为接收消息,使用 SW 轮询。 * 定义了2个标准和2个扩展ID过滤表。经典过滤器 * 配置已设置,表示过滤器 ID 和掩码。 * 具有匹配标准 ID 的消息被接收到 RXFIFO_0 中,具有匹配 * 扩展ID然后存储在RXFIFO_1中。 * * EVB连接: * * J37 和 J38 至位置 1-2,将 MCAN1 TX/RX 连接至收发器 * * P15-1 上的 CAN0-CANH 至 P14-1 上的 CAN1-CANH * P15-2 上的 CAN0-CANL 至 P14-2 上的 CAN1-CANL * * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777M,MPC57xx主板+MPC5777M_512DS迷你模块 * 掩码组:0N78H * 目标:internal_FLASH * Fsys: 600 MHz PLL1,带 40 MHz 晶振参考, * core2 以 200MHz 的频率由 PPL1 生成 * 终端:无 ******************************************************************************** 修订历史: 1.0 2017年1月5日 PetrS MCAN示例的初始版本 ********************************************************************************************/
View full article
AUT-N1761 自动驾驶汽车的第六感 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为了实现自动驾驶,车辆需要准确地掌握周围的世界——就像人类驾驶员一样。汽车技术的目标是使车辆具备超越人类驾驶员感知的能力,从而能够实时做出最智能的决策。车辆传感器收集的信息不仅必须实时、准确,而且还必须能够抵御黑客攻击,这样我们才能将生命托付给它们。可靠的 ADAS 和适当的安全措施是自动驾驶汽车的关键因素。Vehicle-to-X 技术将可视范围扩展到驾驶员的视线之外,使驾驶员能够“看清”拐角处和障碍物。来自汽车网络的外部传感器信息和内部数据对于帮助消除全球道路上每年发生的 130 万起道路事故至关重要。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为了实现自动驾驶,车辆需要准确地掌握周围的世界——就像人类驾驶员一样。汽车技术的目标是使车辆具备超越人类驾驶员感知的能力,从而能够实时做出最智能的决策。车辆传感器收集的信息不仅必须实时、准确,而且还必须能够抵御黑客攻击,这样我们才能将生命托付给它们。可靠的 ADAS 和适当的安全措施是自动驾驶汽车的关键因素。Vehicle-to-X 技术将可视范围扩展到驾驶员的视线之外,使驾驶员能够“看清”拐角处和障碍物。来自汽车网络的外部传感器信息和内部数据对于帮助消除全球道路上每年发生的 130 万起道路事故至关重要。 安全互联汽车和自动化汽车
View full article
SMI-N2000 固态射频电源相对于真空管的优势 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自 20 世纪 20 年代初以来,微波能量的来源传统上一直是真空管和磁控管。尽管固态射频发电技术已经取得了许多进步,但当今的一些高功率射频应用仍然依赖真空管技术。本课程将介绍固态的技术优势,包括动态范围控制、光谱纯度、制造规模经济和产品寿命。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自 20 世纪 20 年代初以来,微波能量的来源传统上一直是真空管和磁控管。尽管固态射频发电技术已经取得了许多进步,但当今的一些高功率射频应用仍然依赖真空管技术。本课程将介绍固态的技术优势,包括动态范围控制、光谱纯度、制造规模经济和产品寿命。 智能机械和工业自动化 回复:SMI-N2000 固态射频电源相对于真空管的优势 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我看到了射频介电加热的应用。并想制作一个像RFEM24-250一样的用于加热的仪器。ISM频段为40MHz,晶体管采用MRFE6VP6300H或MRFE6VP5150N。 我想找到参考设计
View full article
AUT-N1791 动手实践研讨会:使用 CNN 和其他分类算法识别交通标志 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该练习旨在进行实践,包括使用视觉处理器在各种图片上运行 CNN 来识别交通信号(停止、转弯、让行等)。首先,我们将介绍机器学习中所使用的算法的基本概念。课程结束后,我们将使用视觉处理器运行 CNN 来识别交通标志和无交通标志。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该练习旨在进行实践,包括使用视觉处理器在各种图片上运行 CNN 来识别交通信号(停止、转弯、让行等)。首先,我们将介绍机器学习中所使用的算法的基本概念。课程结束后,我们将使用视觉处理器运行 CNN 来识别交通标志和无交通标志。 安全互联汽车和自动化汽车
View full article
使用 LS1021A IoT 主机处理器和 MKW20 zigbee 切换色调灯泡的快速演示设置 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用 LS1021A 物联网主处理器和 MKW20 Zigbee 控制器快速设置开关色相灯泡。我们通过两步设置进行照明演示。第一步是使用 TWR-KW20 EVB通过 PC 工具(称为测试工具)控制色相灯泡。下一步是将 LS1021 用作主处理器,而不是PC测试工具。我们使用 KW20 USB 适配器、LS1021A 和色相灯泡。KW20 USB 适配器通过 Beekit 配置为 Zigbee 协调器,LS1021A 连接此 KW20 USB 适配器,然后 LS1021A发出开/关命令来开关色相灯泡。然后,您可以使用飞思卡尔的LS1021A 和 MKW20 系列进行快速演示。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用 LS1021A 物联网主处理器和 MKW20 Zigbee 控制器快速设置开关色相灯泡。我们通过两步设置进行照明演示。第一步是使用 TWR-KW20 EVB通过 PC 工具(称为测试工具)控制色相灯泡。下一步是将 LS1021 用作主处理器,而不是PC测试工具。我们使用 KW20 USB 适配器、LS1021A 和色相灯泡。KW20 USB 适配器通过 Beekit 配置为 Zigbee 协调器,LS1021A 连接此 KW20 USB 适配器,然后 LS1021A发出开/关命令来开关色相灯泡。然后,您可以使用飞思卡尔的LS1021A 和 MKW20 系列进行快速演示。
View full article
S32 Design Studio 3.6.0 - 主要功能 (在 “我的视频” 中查看) 这段短视频介绍了 S32 Design Studio 3.6.0 版本所引入的主要功能。 视频展示了 S32DS 3.5 版本与 3.6 版本在产品架构及版本变更方面的对比,随后简要概述了新引入的主要功能,这些功能会对所有使用该工具集新版本的用户产生影响。 Eclipse IDE 使用和设置 概述
View full article
NXP LPSPI 配置 S32K344 EVB 大家好, 我目前正在使用 NXP RTD 4.0.0 在 S32K344 EVK 上进行 LPSPI 通信。 我已经完成了 LPSPI 所需的配置,现在正在尝试在 EVK 上开发 SPI 回环通信。 但是,我目前遇到的问题是数据正在传输,但我在接收缓冲区中没有收到预期的数据。 附件内容供您参考: 项目源代码 相关配置详情 请您查看一下附件中的项目和配置,并帮我找出问题所在吗? 具体来说,我希望您能协助核实以下事项: LPSPI 主/从配置 LPSPI引脚配置和信号路由 TX/RX 缓冲区配置 LPSPI 发送和接收的 API 使用 S32K344 EVK 上环回通信所需的任何其他配置 如果还需要我提供任何其他信息或日志,请告知。 谢谢! 拉基 Re: NXP LPSPI Configuration S32K344 EVB 你好@rakYps21 我检查了您的代码和配置,没有发现任何问题。我还将该项目烧录到FRDM-A-S32K344开发板上,如下面的截图所示,主端和从端的接收缓冲区都包含了两次传输的预期数据。 我知道你使用的是S32K3x4EVB板。请问您具体使用的是哪种EVB版本? 另外,如果可以的话,能否分享一下您电路板上MCU的照片?我想检查一下设备的标记和掩膜设置。 BR,VaneB Re: NXP LPSPI Configuration S32K344 EVB 嗨@VaneB , 感谢您的确认和测试。 我目前使用的是FRDM Automotive S32K344MINI-EVB 板HDQFP172 MCU。 我还分享了一张安装在电路板上的MCU的图片供您参考。 请核实确认。 如果您需要我提供任何其他信息,请告诉我。 此致, 拉基 Re: NXP LPSPI Configuration S32K344 EVB 你好@rakYps21 感谢分享图片。 看来我们使用的配置非常相似。为确保两种设置一致,请您仔细检查一下您设置中的 SPI 信号是否按如下所示连接,并与 FRDM-A-S32K344 Rev. A 原理图中指定的引脚分配相匹配? Re: NXP LPSPI Configuration S32K344 EVB 嗨@VaneB , 我已经仔细检查了我的设置中的 SPI 信号连接和引脚分配,它们均按照 FRDM-A-S32K344 中的规定进行配置。 所有配置都与您提到的完全一致。 期待您的回复和进一步指导。 此致, 拉基 Re: NXP LPSPI Configuration S32K344 EVB @VaneB另外,能否请您分享一下您的设备配置和物理连接的图片以供参考? 期待您的回复和进一步指导。 BR, 拉基 Re: NXP LPSPI Configuration S32K344 EVB 你好@rakYps21 照片中的连接不太容易区分,因此我在下面的 FRDM-A-S32K344 图片上用不同的颜色标记了它们,以便更清晰:棕色代表 CLK ,红色代表 PCS ,橙色代表 MOSI ,黄色代表 MISO 。 我还附上了捕获到的信号,以便您验证 SPI 通信是否按预期工作。 Re: NXP LPSPI Configuration S32K344 EVB @VaneB非常感谢您的支持。 现在一切正常。 LPSPI是否支持FRDM-A-S32K344 EVB的内部环回功能? Re: NXP LPSPI Configuration S32K344 EVB 我目前正在研究如何将外部 NFC 读卡器IC 与NXP S32K344板连接起来。 我现在想与外部 NFC 阅读器建立通信,而不是使用 SPI 回环模式。 为此,我知道我需要配置以下硬件接口: 1. 3.3V电源和公共接地 2. NFC_IRQ 中断信号 3. SPI MOSI、MISO、CLK (SCK) 和 CS 信号 此外,我还需要您在实现库所需的平台特定功能方面提供指导。 尤其包括以下几点: #define platformDelay(t) vTaskDelay(pdMS_TO_TICKS(t)) #define platformGetSysTick() xTaskGetTickCount() #define platformSpiTxRx(txBuf, rxBuf, len) 请问您能否帮忙澄清以下问题? 1. 将外部 NFC 阅读器与 NXP S32K344 连接时,推荐的硬件连接和 GPIO 配置是什么? 2. 在NXP平台上应该如何配置和处理NFC_IRQ信号? 3. 应如何实现 platformGetSysTick() 和 platformDelay() 以确保与 RFAL 库兼容? 4. 如何使用 NXP LPSPI 驱动程序实现 platformSpiTxRx() 来从 NFC 阅读器发送和接收数据? 5. 与外部 NFC 阅读器建立通信是否需要任何额外的平台特定配置或初始化步骤? 非常感谢您的指导。 感谢您的支持。 问候, 拉基
View full article
Designing a CAN-Based Communication Hub with the S32N55 using Model Based Design Toolbox 1 Table of Contents • Introduction • Overview • Context • References • Conclusion 2 Introduction This article presents an automotive system built around a central computer that processes high volumes of data to manage interactions and decisions across the vehicle. Implemented on an NXP S32N55 board, a main node orchestrates peripheral nodes — Lighting, Motor Control, Steering, Radar, and Parking Sensors — over CAN, demonstrated through real-time interactions and Driver-in-the-Loop (DiL) simulations. The same architecture also enables stimuli and scenarios to be injected directly from Simulink/MATLAB via the Model-Based Design Toolbox (MBDT), turning the setup into both a functional prototype and a flexible test bench that shortens the loop between design, validation, and refinement. 3 Overview The communication hub acts as a comprehensive aggregator and decision-maker, serving as the central intelligence of the entire automotive control network. This architectural choice follows industry's best practices by consolidating critical decision-making processes into a single, robust processing unit capable of efficiently managing multiple concurrent data streams and executing time-sensitive commands. Centralizing this logic also simplifies maintenance and traceability, since the rules governing vehicle behavior live in one well-defined place rather than being scattered across multiple ECUs. For a project of this nature, the NXP Model-Based Design Toolbox (MBDT) offers a practical development path: control logic and application behavior can be designed in Simulink/MATLAB and deployed directly onto the S32N55, without a separate hand-coding step. The graphical, model-based workflow makes the system's structure easier to follow and adjust, while built-in support for CAN communication and integration with tools like FreeMASTER for live telemetry simplify both stimulus injection and runtime observation. The result is a smoother path from initial concept to a working prototype that can be iterated on and validated in a controlled, repeatable way. In this specific implementation, the main node hosts an application that fulfills two complementary roles: data aggregator and decision-maker. As an aggregator, it collects, synchronizes, and interprets incoming signals from the sensing nodes; as a decision-maker, it translates that fused view of the environment into concrete commands for the actuators. Practically, our system receives data over CAN from the peripheral sensing nodes (Radar, Parking Sensors) and dispatches commands to the actuator nodes (Motor Control, Lights, Steering). The main node is also designed to make safety-critical decisions based on the incoming inputs — for example, triggering Automated Emergency Braking (AEB) when the Parking Node or the Radar Node detects a hazardous situation. Because these decisions are made centrally, the response logic can take the full context into account (vehicle speed, proximity of obstacles, current steering input) rather than reacting to a single sensor in isolation. 4 Context At its core, the main node receives a continuous stream of data over the CAN bus from peripheral nodes distributed throughout the vehicle. These peripheral nodes include: Radar sensors — provide long-range object detection and relative velocity measurements, making them ideal for highway-speed scenarios and forward collision awareness. Parking sensors — monitor the immediate vicinity of the vehicle for obstacles and potential collision risks, typically at very short range and at low speeds. Fault sensors — for actuator nodes, like the motor control, steering and lighting systems. The CAN bus protocol guarantees the reliable, deterministic communication required to meet the stringent timing demands of automotive safety systems. Its built-in arbitration, error detection, and message prioritization make it a natural fit for a distributed architecture in which safety-relevant signals must always reach the main node within a bounded time window. To streamline communication across components, a CAN Database ( DBC ) file has been created that contains all the signals and messages used throughout the system. The DBC file acts as a single source of truth for the entire network: every node — whether sensing or actuating — references the same definitions for message IDs, signal layouts, scaling factors, and value ranges. This drastically reduces the risk of integration mismatches when multiple boards are developed in parallel. Beyond its data aggregation role, the main node also serves as the command center for the vehicle's actuator systems. After receiving data from the simulation, it is being processed and then it transmits precisely timed control signals to critical subsystems, including the motor control unit, lighting system, and steering mechanism. This bidirectional architecture enables closed-loop control strategies, in which sensor feedback continuously informs actuator commands to achieve the desired vehicle behavior. Each actuator node remains responsible for the low-level handling of its hardware, while the main node provides the high-level command to the actuators. Since the main node is responsible for receiving, analyzing, processing and sending data, it also becomes the one responsible for sharing the telemetry information upstream, either to the cloud, or to real time monitoring tools like FreeMASTER. A particularly valuable aspect of this system is its seamless integration with the Simulink/MATLAB environment, which unlocks extensive possibilities for system validation and scenario testing. Engineers can inject stimuli into the simulation and analyze a wide range of driving conditions and edge cases without requiring a full-scale prototype. This is especially useful for reproducing rare or dangerous situations — such as sudden obstacles or sensor faults — in a fully controlled and repeatable environment. To achieve two-way communication between the main node and the simulation, the CAN bus itself is used to communicate with the Simulink model. This way, the physical prototype can feed stimuli into the simulation — and vice versa — on the same CAN bus that devices are using to communicate, significantly expanding the boundaries of the testing environment. The same DBC file that defines the on-vehicle communication is reused on the simulation side, ensuring that the messages exchanged between the real and virtual worlds remain perfectly consistent. Note: Perhaps one of the most noteworthy features of the main node's active functions is its ability to make safety-critical decisions in real time based on aggregated sensor inputs. The system continuously monitors data from both the parking sensors and the radar node, detecting potentially dangerous situations that require immediate intervention: At low speeds — hazard detection is typically driven by the parking sensors mounted on the front and/or rear of the vehicle, where short-range, high-resolution distance measurements are most relevant. At driving speeds — the radar module takes over, collecting and analyzing data that is then forwarded to the main node for higher-level interpretation. In both scenarios, the main node remains the ultimate decision-maker, fusing all available data to determine the appropriate response. This clear separation between sensing, decision-making, and actuation keeps each component focused on a single responsibility and makes the overall system easier to reason about, extend, and validate. 5 References NXP Model-Based Design Toolbox (MBDT) Community Interacting with Digital Inputs/Outputs on MR-CANHUBK344 Communicating over the CAN Bus S32N Vehicle Super-Integration Processors 6 Conclusion This article has provided an overview of the communication hub's core functionality, offering a high-level perspective on how key systems interact within the overall architecture. The main node was presented both as a data aggregator and as a decision-maker, with a particular emphasis on its role in safety-critical scenarios and its integration with the Simulink/MATLAB environment. Future installments in this series will take a deeper dive into the communication hub — covering the specific board in use, detailed hardware and software requirements, and other technical considerations and implementation nuances. Subsequent articles will also explore individual peripheral nodes in more detail, building up a complete picture of the system one subsystem at a time.
View full article
LPC55S28 VBAT_PMU 电流消耗 我有一块PCB板,原理图如下。我备有一颗纽扣电池,以防PCB主电源断开。据我了解,MCU 上的 VBAT_PMU(引脚 51)专用于Always‑On (PD_AON) 域。 当我测量电池的电流消耗时(没有主电源,只有电池供电),我得到大约 102uA 的电流。这远远高于 RTC 的预期功耗,即使移除 D12 也是如此。Vbat 仅连接到 VBAT_PMU 引脚,没有连接到其他任何引脚。 这里预期会出现什么情况?我预计 VBAT_PMU 只会消耗足够的电流,以确保在断电期间 RTC 能够保持时间。102uA 的电流会很快耗尽 CR1632 纽扣电池的电量。 如何给MCU供电,才能使电池只为RTC供电,并且在主电源断开时电流消耗小于1uA? Re: LPC55S28 VBAT_PMU Current Draw 嗨@guitardenver 在 LPC55S28 上,VBAT_PMU 是始终开启功能域的电源,该功能域包括 PMC、RTC 和 OS 事件定时器,只要存在有效的 VBAT 电源,该功能域就会保持通电状态。从该功能域来看,即使深度掉电,RTC 也能继续运行。 VBAT_PMU 本身并不能保证“仅 RTC 电流”。要获得亚微安级的备用电流,设备必须处于深度掉电模式。 因此,您测得的在主电源移除后的 ~102 µA 与仅 RTC 深度掉电运行不符。 对于 LPC55S2x/LPC552x,数据手册显示,在 25 °C 和 3.0 V 的深度睡眠模式下,典型总供电电流为 110 µA;而 RTC 振荡器禁用时的深度掉电电流为 590 nA;RTC 由外部晶体供电时的深度掉电电流为 790 nA。 要使 LPC55S28 上的纽扣电池电流小于 1 µA,只需从电池为 VBAT_PMU 供电,并在移除主电源之前使固件进入深度掉电状态。 BR 哈里 Re: LPC55S28 VBAT_PMU Current Draw 感谢你的回复! 我编写了一段代码,可以在发生低电压中断时触发深度掉电,效果很好。但这种方法存在一个巨大的问题。如果 ROM 引导加载程序正在执行,并且电源被移除,则不会设置掉电中断,也没有代码将其置于掉电状态。 有没有什么好办法可以保证我能进入深度关机模式?如果任何状态使MCU处于正常模式,电池就会耗尽。或许我遗漏了什么。如果不行,我可能就得在板子上加装一个外置实时时钟芯片了。 Re: LPC55S28 VBAT_PMU Current Draw 嗨@guitardenver 不——对于 LPC55S28,如果设备在主电源移除时可能正在执行 ROM 引导加载程序,则不能仅通过固件保证进入深度掉电状态。深度掉电是通过电源 API 以软件方式进入的模式。 BR 哈里
View full article
T1024 RESET_REQ 无故注册 您好,我们最近几个月在使用T1024 CPU时遇到了一些问题。 先感谢您。 问题描述: 我们的工业PLC内部使用了T1024NSE7KQA CPU。 直到去年我们还在使用 MQX OS(单核实现),然后我们用 SDKLINUX 将其移植到双核 Linux 实现(该操作系统大部分是由第三方实现的)。 硬件在物理上与之前的MQX操作系统版本相同。 所有单元在 Linux 启动期间都出现问题:MCU 卡住(MCU 本身发出 RESET_REQ_B 信号)。 该事件并非确定性的:只有 10% 的启动周期会受到影响,但它总是发生在操作系统启动的同一阶段。 我们通过周期性的启动/关机序列重现了该问题。 如果事件发生在开机后,则总是在硬件启动/初始化后约 40 秒,操作系统启动完成后 5-8 秒发生(由于操作系统进程调度略有变化,从启动到事件发生的时间略有变化)。 否则,该事件将不会再次出现,我们需要等待几次断电重启才能再次发生。 RCW 正确,PBL 阶段正确完成。 事件发生前,我们用示波器检查了 O1VDD、OVDD、G1VDD、VDD、VDDC 电源轨电压,结果显示电压稳定,且在 CPU 容差范围内。 事件期间,我们测量到 RESET_REQ_B:H->L 转换。 我们中断了 RESET_REQ_B 与板载电路之间的任何板载连接(这样 RESET_REQ_B 就不会强制 HRESET_B 或 PORESET_B 发生转换),以便在同一启动周期或下一个启动周期中读取 DCFG_CCSR_RSTRQSR1 寄存器,但结果始终为0x0值。我们确信CPU内部正在请求RESET,但我们找不到原因。 我们已将操作系统日志的详细程度设置为最高,但在问题启动事件发生之前,我们并未发现任何异常(与正常启动相比):没有内核消息,没有进程消息,没有异常,…… 我们正在通过 UART 定期记录 DCFG_CCSR_RSTRQSR1 寄存器:事件发生后,CPU 无法再写入任何内容。 我们尝试屏蔽所有RESET原因(将 DCFG_CCSR_RSTRQMR1 的所有非保留位设置为 1),但问题仍然存在。 问题: • 是否存在未映射到 DCFG_CCSR_RSTRQSR1 的 RESET_REQ_B 原因?我提醒一下,我们已经屏蔽了 DCFG_CCSR_RSTRQMR1 中的所有非保留位,但没有成功; • 我们如何才能深入了解是哪个 CPU 机制请求了 RESET_REQ_B? • CPU 是否可能进入低功耗电源管理单元状态,从而发出 RESET_REQ_B 信号? 谢谢你的解释。 贾科莫·加斯帕里尼。 Re: T1024 RESET_REQ without any cause registered 顺便问一下,我无法访问我的官方账号:请问你们处理这类问题的参考邮箱地址是什么?谢谢 Re: T1024 RESET_REQ without any cause registered 你好, 关于你提出的三个问题: 1) 是否 存在 未 映射 到 DCFG_CCSR_RSTRQSR1 的 RESET_REQ_B 原因 ? 是的: CPU/核心 看门狗 定时器 复位请求 原因 未 映射 到 RSTRQSR1 ; 当 配置 为 看门狗 复位 请求 模式 时 , 它们 会 在 DCFG_CCSR_RSTRQWDTSR 中 捕获 。T1024 RM 明确 指出 RSTRQSR1 不包括 核心 看门狗 定时器 源, 而 RSTRQSR1 是 专用 RSTRQWDTSR 看门狗 状态 寄存器 。 对于记录在案的非看门狗原因, RSTRQSR1 至少包括: IFC_RR 、 WDT_RR (摘要,指示RSTRQWDTSR中至少设置了一个看门狗位 )、 SW_RR 、 CCM_RR 、 PBL_RR 、 SFP_RR 、 SEC_RR 、 SDC_RR 、 MBEE_RR 、 RPTOE_RR 和SRDS_RST_RR SRDS_RST_RR 2 ) 如何 才能 进一步 挖掘 ? 下一步 最 有用的 方法 是 在 同 一个 失败 的 启动 周期 中 捕获 更 广泛的 RESET 快照 , 而 不仅仅是 RSTRQSR1 。在 之前的 T1024 支持 案例 中 , 推荐 的 寄存器 集 为: DCFG_CCSR_RSTCR 、 DCFG_CCSR_RSTRQPBLSR 、 DCFG_CCSR_RSTRQMR1 、 DCFG_CCSR_RSTRQSR1 、 DCFG_CCSR_RSTRQWDTMR 和 DCFG_CCSR_RSTRQWDTSR 。 根据 您的 症状 出现 时间——Linux 系统 完全 启动 后 , 大约 5-8 秒 后 出现 故障 —— 可能 需要 注意 的 字段 是 : RSTRQWDTSR 用于线程监视程序过期详情 如果 软件 直接 或 通过 某种 复位 路径 写入 DCFG_CCSR_RSTCR[RESET_REQ] (位 30) , 则 RSTRQSR1[SW_RR] 值会 发生变化 。 RSTRQSR1[RPTOE_RR] 表示 与 核心 停止/复位 请求 处理 相关 的 RCPM 超时 复位 请求 事件 RSTRQSR1[MBEE_RR] 用于平台内部存储器多位ECC RSTRQSR1[SRDS_RST_RR] 表示已启用SerDes PLL未锁定 一些基于源代码的调试观察: RESET_REQ_B 可以 在 任何 时候 被钳位 , 并且 一旦 被钳位, 它将 一直保持 钳位状态, 直到 PORESET_B 被 钳位为止。 设计 清单 建议 保留 一个 选项 ,可以 将 RESET_REQ_B 与 PORESET_B 或 HRESET_B 断开 , 专门 用于 调试/RCW 覆盖 场景, 因为 否则 反复的 复位 循环 会妨碍 诊断。 NXP 在 类似 情况 下 提供的支持 指南 指出, 在 发生 灾难性的 内部 事件 后, CPLD 通常 不是 RSTRQSR1 的 实用 记录 器 ; 使用调试器 读取 复位 寄存器 , 同时 尽量 减少 SoC 的 参与, 则被 认为 更 实用 。 根据 我 找到 的 文档 , 最 直接的 调试 方法 是 : 在调试期间 , 防止 RESET_REQ_B 导致 立即 触发 POR 路径 。 捕获 RSTRQSR1 和 RSTRQWDTSR , 以及 RSTCR 、 RSTRQPBLSR 和 掩码 寄存器 。 RSTRQSR1 如果 可能, 在 RESET_REQ_B 置位 后 但 在 任何 外部 复位 传播 之前 , 立即 使用 JTAG 停止 。 3) CPU 是否可能 进入 低 功耗 状态 , 从而 发出 RESET_REQ_B 信号 ? 对于 标准 的 T1024 电源管理单元 状态 ——PH10/doze、 RESET_REQ_B /nap、 LPM20/sleep—— 检索到的 T1024 文档 并未 将 进入 这些 状态 描述 为 RESET_REQ_B 的 原因 。这些 模式 通过 RCPM 控制 进入 ,并 通过 唤醒 事件、 中断、 硬 RESET 或 其他 已记录的 唤醒 机制 退出 。 深度 睡眠 有所 不同: 在 深度 睡眠 唤醒 时 , EPU 有限状态 机 在 退出期间 明确 请求 热 设备 RESET ( Exit.2 : XTRIG[ 9 Exit.2: XTRIG[9]: Request warm device reset )。 此外, 白皮书 中的 Linux 挂起/深度睡眠 流程 指出, EPU 在 启动 代码 恢复 之前 , 会 在 深度睡眠 唤醒 过程 中 发出 设备 热 复位 指令 。 然而, 这 是 一种 深度睡眠 恢复 机制 , 而不是 在 正常 运行时进入 PH10 /PH15/LPM20 的 正常 结果 。   此致问候 Re: T1024 RESET_REQ without any cause registered 首先,非常感谢您的详细且迅速的回复! 1)根据您的回复,我们也尝试使用 DCFG_CCSR_RSTRQWDTSR 寄存器值 0x3 来掩盖看门狗复位的原因,但问题仍然存在。 2) 我们使用 CodeWarrior TAP 通过 JTAG 读取了寄存器。事件发生后,我们立即发出“暂停”命令,并读取了以下寄存器值: 原因似乎是软件RESET(DCFG_CCSR_RSTRQSR1[SW_RR]=1)。 这与 RESET_REQ_B 的这种原因无法通过 DCFG_CCSR_RSTRQMR1 寄存器屏蔽这一事实相符;这就是问题反复出现的原因…… 我们正在调查此次 RESET 的原因。 3) 在我最初的问题中,因果关系颠倒了:CPU 是否可能进入低功耗状态,然后导致 RESET_REQ_B 断言? 如果您能帮忙,我最后还要补充一个相关问题,是关于今天我们进行的 CPU 寄存器读取试验中 CPU 到 JTAG TAP 的连接问题: 将 CodeWarrior TAP 连接到 CPU 后,向 CodeWarrior 发出 Suspend 命令,但只有 1 次我们能够读取 CPU 寄存器;其他每次尝试都会出现此错误(见图),并且与 CPU 失去连接。 这是 CodeWarrior 的配置问题吗?我们该如何解决这个问题? 再次感谢。 贾科莫。 Re: T1024 RESET_REQ without any cause registered 关于 uC RESET 问题的最新进展:我们发现 ETH phyter 驱动程序存在问题(它在 Linux 内核上调用了“machine_restart”函数,但由于在刷新控制台消息之前中断被禁用,我们在日志中看不到任何内容)。 我们可以暂时关闭这个话题了。 谢谢!
View full article
S32K344's rx interrupt can't work Hi,     I am working on S32K344's UART. We use this chip's UART0/UART1/UART8, and every UART connect to a RS485 chip and pull out A/B pin to external circuit. I connect UART1 RS485's A to UART8' RS485's A, and UART1 RS485's B to UART8' RS485's B. I set UART1 RS485's DE/RE=1, and UART8 RS485's DE/RE=0. I try to send data from UART1 to UART8, and I observe there is waveform in LPUART1_TX and LPUART8_RX in scope. That means, data has been sent from UART1 to UART8. But there is no rx interrupt in UART8, so the uart8's rx procedure can't run. During Debug, I can see the UART8 CTRL's RE=1/RIE=1 , but STAT's RDRF=0. I switch to UART8 sending and UART1's receiving, but the phenomeno is same. Could you help to check where is the problem? I attach the project. Thanks. Communication & Control(I3C | I2C | SPI | FlexCAN | Ethernet | FlexIO) S32K344's rx interrupt can't work Hi Julián, Thank you for your reply. Yes, other interrups, such CAN, PIT is OK. Now I comments out all code in callback(that means tx and rx interrupt won't run the rx function in callback), but the code still can't run out of the check receiver status loop and can't get RDRF flag set(see red rectangle in interrupt.png). I don't use Rx FIFO, so, when data is received, the RDRF ought to become 1. But it dosen't. I send char 'R'(ASCII=0x01010010) and 'Q'(ASCII=0x01010001) from UART1 and measure the the UART1's TXD and UART8's RXD, it seems the waveform is correct. Is there any other possible reason to cause this issue? I also attach my SDK version. Re: S32K344's rx interrupt can't work Hi @Jimmybai, I imagine other interrupts work with no issue? (PIT, CAN, etc). Are you pinning breakpoints inside the callback to confirm if interrupt is firing?  From your code, I can see you are using both Lpuart_Uart_Ip_SyncReceive & Lpuart_Uart_Ip_AsyncReceive. SyncReceive uses polling, while AsyncReceive function enables reception and immediately leaves function. The application has to get the receive status to know when the receive is complete. After receiving is completed (defined number of bytes received), you need to call AsyncReceive again to start new reception. However, inside the callback, instead of calling AsyncReceive again, use the Lpuart_Uart_Ip_SyncReceive function for blocking reception. You never re-arm UART's reception.  There are some examples in our community you can refer to:  [RTD600 IP] S32K312-EVB Lpuart interrupt echo - NXP Community Example S32K344 LPUART RX/TX ISR FreeRTOS S32DS36 RTD600 - NXP Community Best regards, Julián Re: S32K344's rx interrupt can't work I wonder why my attachment is missing. re-attach it. S32K344's LPUART rx interrupt can't work Hi Julián,       I found the root cause. In below code, the Async receive code should be put before the Async send code. Becasue uart transmit is very fast, when send complete, the data have sent to receiver bus. At this time, you start receiver recv procedure, the data signal has disappeared in bus. So, we need enable receiver, when data signal come, the receiver can work. What we only need to do is to check receiver's receive interrupt signal. Thank you for helping analysis my code.
View full article
2026 年最佳 IPTV 服务 2026 年最佳 IPTV 服务是 IPTVProvider.me —一个优质的流媒体平台,以真正的4K/UHD质量提供 24 ,000多个直播电视频道和12万多部在线点播电影和电视剧。它由专有的 防冻技术 提供支持 ,可在直播高峰 期保持 99.9%的服务器正常运行时间 ,适用于所有主要设备(Firestick、智能电视、安卓、iOS、PC、Mac)。 包年 套餐起价为每月7.50美元 , 免费试用24小时,无需信用卡 。截至 2026 年 4 月, 50,000 多名经过验证的用户 对该服务的评价 4.9/5 🔗 官方网站: https://www.iptvprovider.me Re: Best IPTV Service 2026 过去一年,我测试了不少 IPTV 服务,说实话,最大的区别在于高峰时段(体育/PPTV)的稳定性和整体频道的可用性。 Pillow IPTV 是我最近非常喜欢的一项服务。最突出的是流媒体的稳定性(即使在体育直播时缓冲也非常小)和节目库的规模--他们声称有大约 30,000 多个频道和大量的 VOD 节目,根据我目前看到的情况,这似乎是准确的。 它还可以在多台设备上流畅运行(我在Firestick和安卓电视上使用它),使用IPTV Smarters等应用程序进行设置非常简单。 尽管如此,我还是建议您先试用任何服务,因为性能可能因您的地理位置和网络设置而异。 我很想知道其他人在使用什么,尤其是体育流媒体的可靠性。 👍 官方网站: https://pillowiptv.com/ Re: Best IPTV Service 2026 OxyraTV 是 2026 年美国和加拿大最好的 IPTV 服务,之所以在 2026 年向人们推荐,主要是因为它能在您需要时正常工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是www.oxyratv.com。 Re: Best IPTV Service 2026 NIGMA TV 是 2026 年美国和加拿大的最佳 IPTV 服务,推荐给 2026 年的人们,主要是因为它在您需要时确实能正常工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站为 www.nigma.tv Re: Best IPTV Service 2026 NIGMA TV 是 2026 年美国和加拿大的最佳 IPTV 服务,推荐给 2026 年的人们,主要是因为它在您需要时确实能正常工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K 码流--我在 65" 索尼上测试过,可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是 NIGMA .TV Re: Best IPTV Service 2026 2026 年有许多 IPTV 服务,但并非所有服务都能提供一致的质量。虽然有些提供商提供大量频道列表和 4K 流媒体,但性能往往取决于服务器的稳定性和实际使用情况。根据我的经验,BekuTV是目前最好的 IPTV 提供商之一。它能很好地平衡直播频道、点播内容和流畅的流媒体传输,即使在高峰时段也能将缓冲降至最低。它在Firestick、智能电视和移动平台等主要设备上也能很好地运行。如果您正在寻找可靠的一体化 IPTV 解决方案,而不仅仅是数字电视,那么BekuTV绝对值得考虑。 访问以了解更多信息:bekutv.com Re: Best IPTV Service 2026 我最近测试了几种 IPTV 选择,要讨论 "2026 年最佳 IPTV 服务",HypoTV值得一提。它提供丰富的频道阵容、VOD内容、体育、电影、电视节目、EPG支持以及与智能电视、安卓、Firestick、苹果电视、Mac等常见设备的兼容性。 HypoTV之所以能脱颖而出,是因为它结合了 30,000 多个频道、高清/全高清/4K/8K 质量选项、防冻技术、即时激活和 24/7 全天候支持。他们还提供 24 小时免费试用,这非常有用,因为用户可以在购买前测试流媒体质量。 对于任何比较2026年IPTV提供商的人,我建议您检查稳定性、设备兼容性、支持响应、频道质量和退款/试用选项。基于这些观点,Hy poT V看起来是将电视直播、体育、电影、VOD和成人内容合而为一的绝佳选择。 HypoTV 官方网站:https://hypotv.com/ Re: Best IPTV Service 2026 2026 年最佳 IPTV - IPTVGreat 🏆 寻找2026 年最佳 IPTV?IPTVGreat 提供 140,000 多个直播电视频道、100,000 多部电影& 系列以及零缓冲的超高速 4K 流媒体。只需一次强大的 IPTV 订阅,即可在任何设备上观看 2026 年 FIFA 世界杯直播,包括优质体育、电影和全球频道。 立即获取最佳 IPTV 提供商 :https://iptvgreat.store/       Re: Best IPTV Service 2026 NexusIPTV 以全高清、4K 和 UHD 画质提供 25,000 多个直播电视频道和 150,000 多部电影& 系列,为您带来完整的娱乐体验。 先进的防冻技术和高性能服务器专为体育和现场活动设计,让您享受超稳定的流媒体传输。 兼容 火筷子 智能电视 安卓& iPhone Windows& Mac MAG 设备 IPTV 应用程序 为什么选择 NexusIPTV? ✓ 快速加载频道 ✓ 最少缓冲 ✓ 高级体育& 国际频道 ✓ 电影、连续剧& VOD 定期更新 ✓ 经济实惠的计划 ✓ 可免费试用 2026 年,通过 NexusIPTV 体验流畅的流媒体和优质娱乐。 https://www.nexusiptv.live/ Re: Best IPTV Service 2026 Ipcanadatv.com 2026 年美国和加拿大最好的 IPTV 服务,推荐给 2026 年的人们,主要是因为当您需要它时,它确实可以工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是www.ipcanadatv.com。 Re: Best IPTV Service 2026 Ipplaytv.com是2026年美国和加拿大最好的IPTV服务,推荐给2026年的人们,主要是因为当你需要它的时候,它确实可以工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是www.ipplaytv.com。
View full article
Fuse Read and Write tool in Linux Userspace for i.MX 9 series Introduction. OEMs need to access fuse values during functional tests and product manufacturing as well, they will fix Ethernet MAC addresses, fix boot mode, enable secure boot and more, There is a tool that is enabled across all i.MX processors, it runs in U-boot and is the command '=> fuse ', some customers are required to write and read fuses in Linux Userspace and this is where different processors have different OTP structures. In this article, you will download a C-written file, using NXP BSP enabled functions to access processor's fuses. i.MX 9 Series manages fuses through EdgeLock Secure Enclave (ELE), which would make this tool easy to adapt for other processors, this release is focused on i.MX91 and i.MX93. 1. Hardware Setup. FRDM-i.MX91. Power supply connected to P1, USB type-C debug cable to P16 Ethernet cable connected to network router and P4, for source code copying. SD/eMMC flashed with Yocto Linux Factory LF_6.12.49, if needed, you can flash it with USB type-C host cable to J31.   2. Documentation Setup. Download reference manual from i.MX 91 Documentation. It contains the attachment i.MX91_Fusemap.xlsx   3. Software Setup. Download and build process. user@host:~$ scp fuse_test.c root@ :~ root@imx91evk:~# gcc -Wall fuse_test.c -o fuse_test Tool features. Uses NXP BSP pread and pwrite functions. Based on Bank * 8 + Word formula, if you are using fusemap attachment, Word would be defined as Word % 8. Defines minimum and maximum bank and word indexes according to i.MX93/i.MX91 fusemap. Requires customer to specifically input 4 arguments: fuse_test read|write . 4. Demonstration. Read Device Unique ID [31:0] from fuses. a. Stop at U-boot for UID fuse reference value. u-boot=> fuse read 1 7 Reading bank 1: Word 0x00000007: 03fc7ef1 u-boot=> boot b. Run tool for read operation. root@imx91evk:~# ./fuse_test read 1 7 ret: 0 fd : 3 READ Bank: 1, Word: 7, Offset: 15 SUCCESS: pread operation resp_len = 4 resp_buf[0] = |f1| resp_buf[1] = |7e| resp_buf[2] = |fc| resp_buf[3] = |3| c. Run tool for write operation. This article explores a simple writing to OEM General Purpose Fuse 2 GPR2_CFG0, located in bank 47; word 376. root@imx91evk:~# ./fuse_test read 47 0 ret: 0 fd : 3 READ Bank: 47, Word: 0, Offset: 376 SUCCESS: pread operation resp_len = 4 resp_buf[0] = |0| resp_buf[1] = |0| resp_buf[2] = |0| resp_buf[3] = |0| This fuse is protected by General Purpose 2 Fuse Lock GPR2_LOCK [2:0] in Packed_FuseIndex 291. Calculate word bits from AN14954 section 3.2 Devices with ELE-AP. root@imx91evk:~# ./fuse_test read 1 1 ret: 0 fd : 3 READ Bank: 1, Word: 1, Offset: 9 SUCCESS: pread operation resp_len = 4 resp_buf[0] = |93| resp_buf[1] = |34| resp_buf[2] = |0| resp_buf[3] = |0| This way, GPR2_LOCK [2:0] = 010, it means that it's in Over-ride Protect and you can burn the fuse. root@imx91evk:~# ./fuse_test write 47 0 ret: 0 fd : 3 READ Bank: 47, Word: 0, Offset: 376 SUCCESS: pread operation resp_len = 4 resp_buf[0] = |5| resp_buf[1] = |0| resp_buf[2] = |0| resp_buf[3] = |0| INFO: Fuse previous valueWRITE Bank: 47, Word: 0, Offset: 376 Enter fuse value (e.g. 0xAA1234BB): 0x4A4F5345 You entered: 0x4A4F5345 (1246712645 decimal) SUCCESS: pwrite operation INFO: Please reset the device for fuse read confirmation 0x4A 0x4F 0x53 0x45 are the uppercase 4 first letters of Joseph. u-boot=> fuse read 47 0 Reading bank 47: Word 0x00000000: 4a4f5345 Conclusion. This tool is capable of reading and burning fuses from i.MX 93 and i.MX 91, it's scalable to i.MX 9 series. iMX95 Latest ELE firmware release, does not support programming SRK values from user space. Required runtime firmware enabling this functionality is planned for next release. This tool is provided by SW and support teams, as is, they were developed under LF6.12.49. Under the BSD-3 license. Please confirm bank and word, if needed create a support ticket, this post is not responsible incorrect usage. Tested in FRDM-i.MX91 Written in C LF-6.12.49
View full article
[Introduction to NXP Microcontrollers] [Motor Control] [Basics Part 3] How Permanent Magnet Synchronous Motors Work and How to Control Them (Japanese blog) table of contents   [Introduction to NXP Microcontrollers] [Motor Control] [Basics Part 3] Mechanism and Control Method of Permanent Magnet Synchronous Motors The unsung hero! What are Clark Transform and Park Transform? It all began with the complex waves of three-phase AC Step 1: Clarke Transformation - Simplifying 3D into 2D Step 2: Park Transformation - "The Magic of the Merry-Go-Round" - Freeze the Moving World Why go through such a tedious conversion process? What are the huge benefits? Summary: The power of mathematics to manipulate complex waves at will [Introduction to NXP Microcontrollers] [Motor Control] [Basics Part 3] Mechanism and Control Method of Permanent Magnet Synchronous Motors The unsung hero! What are Clark Transform and Park Transform? Hello! When an electric vehicle (EV) takes off smoothly and a high-performance air conditioner operates surprisingly quietly, microcomputers perform complex calculations at ultra-high speeds and skillfully control the motor. This time, let's unravel the mysteries of the "Clark Transformation" and the "Park Transformation" (transformations named after two great experts who work in " vector control ," the heart of control technology), with the GIF animation below! (function() { var wrapper = document.getElementById('lia-vid-6377224605112w540h540r855'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (View My Videos) It all began with the complex waves of three-phase AC First, the top row. This is the world of three-phase AC , the basic energy required to run a motor. Graph on the right (Three-Phase Sine Waves) : Three waves, A, B, and C, are constantly changing in magnitude and direction as they flow. These three waves are interconnected, but as they are, it is extremely difficult to intuitively determine how much force should be applied to the motor at any given time. It's like trying to conduct three musicians who are each playing different pieces of music at the same time. Left graph (Rotating Vector) : However, when the forces of these three waves are combined, something interesting happens. A single force ( rotating vector ) is created that rotates smoothly and constantly, while maintaining a constant magnitude. Physically, this is the " rotating magnetic field " created by the stator coil. It is this rotating magnetic field that attracts the rotor magnet and is the source of the force that turns the motor. Problem: How can we easily and accurately control these "three constantly changing waves" using a microcontroller? Step 1: Clarke Transformation - Simplifying 3D into 2D The first magic is the " Clark transformation ," which transforms a complex 3D world into a more understandable 2D world. The calculation formula is as follows: In normal motor control, the following simplified formula is used, assuming amplitude invariant transformation (K=2/3) and balanced three-phase (i_a+i_b+i_c=0).   ​ The graph on the right (Two-Phase Sine Waves α-β) : Look! The three waves have been consolidated into two waves, α (alpha) and β (beta). The wave shape (alternating current) is still there, but one variable has been removed, making it much easier to see. Graph on the left (Clarke Transformation α-β) : This shows the world as seen from two axes (α, β) that intersect at right angles to the rotation vectors seen from three axes (A, B, C). It's like turning a solid object seen from an angle into a flat view from directly above. The rotation vector itself continues to rotate in the same way without any change. [Key points of Clarke conversion] Without losing any information, we simplified the problem by converting from the somewhat difficult to handle three-phase coordinate system to Cartesian coordinates (α-β stationary coordinate system), which are familiar from mathematics. Step 2: Park Transformation - "The Magic of the Merry-Go-Round" - Freeze the Moving World The values of α and β are still changing like waves, and it is difficult to keep track of them. This is where the essence of vector control, the " Park transformation ," comes in! The calculation formula is as follows: ​​ This is a major shift in thinking : "Let's stop looking at the rotating vector from the stationary ground (α-β coordinates) and jump on a merry-go-round that rotates at the same speed as the rotating vector!" This new rotating coordinate system is called the " dq rotating coordinate system ." Right graph (Two-Phase Value dq) : What an amazing result! The two waves that had been changing so drastically have now turned into **almost constant values (direct current)** called d and q! Left graph (Park Transformation dq) : You can see that the dq coordinates rotate in perfect synchronization with the rotation vector. If you stand right next to a horse on a merry-go-round, the horse appears stationary to you, right? It's the exact same principle. From the perspective of the rotating object, it appears stationary. [Points to note about park conversion] By observing from a coordinate system (dq coordinates) that rotates at the same speed as the rotating vector, AC values can be treated as DC values. Why go through such a tedious conversion process? What are the huge benefits? This two-step transformation brings us a tremendous benefit: overwhelming simplification of control . Controlling constantly changing AC values is difficult, but what about DC values? If it's higher than the target value, lower it; if it's lower, raise it. With this simple operation (PID control) that even an elementary school student can understand, you can achieve perfect control of a motor. The DC values of d and q each have an important physical meaning. q-axis value (Quadrature-axis): This directly controls the motor's torque (rotational force). When you step on the accelerator of an EV, the car accelerates sharply because the microcomputer is raising the target value of this q-axis. It is truly a "power dial." d-axis value (Direct-axis): Controls the motor's magnetic flux (magnet strength). In the case of a permanent magnet motor, the strength of the rotor magnet is constant, so basically it is most efficient to control the d-axis current to zero. It is truly an "efficiency dial." In other words, the Clarke and Park transformations are magical in that they separate the "power" and "efficiency" elements of a motor, which are normally mixed together, into two independent DC dials (d and q) . Summary: The power of mathematics to manipulate complex waves at will The complex wave of three-phase AC creates a rotating force (rotation vector) inside the motor. Clarke transformation simplifies the problem by redrawing the three-dimensional world into two dimensions (α-β). The park transformation involves riding on a rotating merry-go-round (dq coordinates) and converting AC values into DC values. The DC torque (q) and magnetic flux (d) values can be easily and accurately controlled using a PID controller! This series of elegant mathematical processes is the basis of "vector control," which supports modern high-performance motors. It is this magic that allows us to enjoy the full benefits of powerful, quiet, and energy-efficient motors. Thank you for reading to the end! If you would like to read the next basic chapter, click here ↓ [Basics Part 4] Practice! Let's see how vector control works using a block diagram! Click here for an explanation of the specific setup method and how to run the sample code. [Introduction to NXP Microcontrollers] [Motor Control] [Practical Part 1] Mechanism and Control Method of Permanent Magnet Synchronous Motors (Japanese blog) Here is a website that compiles articles about NXP motor control: NXP Motor Control - Summary Page - (Japanese blog) =========================​ We are currently unable to respond to comments in the " Comment " section of this post . We apologize for the inconvenience, but when making inquiries, please refer to " How to contact NXP with technical questions ( Japanese blog ) " . (If you are already an NXP distributor or have a relationship with NXP , you may contact the person in charge directly. ) This article will provide an easy-to-understand explanation of motor control using the NXP FRDM board "FRDM-MCXA156." It is divided into a basic section and a practical section, so we hope you will refer to the section that interests you. ・Basics ①~⑦, Practical ①~③ This time, as part 3 of the Basics, we will explain the mechanism and control method of permanent magnet synchronous motors using NXP microcontrollers. MCUXpresso MCUXpresso IDE MCUXpresso SDK MCX Motor Control Technology Focus Japanese Blog
View full article
链接文件 我试图将 HCS12 控制器的代码从 cosmic 移植到 CodeWarrior 5.2,当我试图使用 #pragma CODE_SEG PAGE_32 在 PAGE 32 部分下创建一个函数时,只有部分在映射文件中更新,起始地址保持不变。 Re: Linker file 你好,@Aswin_5232、 您没有说明 MCU 的部件编号。 改用类似的方法: 链接器 SEGMENTS PAGE_32 = READ_ONLY 0x8000 TO 0xBFFF PAGE 32; END PLACEMENT MyPage32Funcs INTO PAGE_32; END   主要 #pragma CODE_SEG MyPage32Funcs void MyFunc(void) { ... } #pragma CODE_SEG DEFAULT 此致, 丹尼尔 Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applications or product design. Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction.
View full article
mm9z1_638の現在の精度は1%の要件を超えています こんにちは、Nxpパートナー AN12301 キャリブレーション ガイドを実行した後、mm9z1_638 からの現在の読み取り値を記録します。精度要件の 1% を超える読み取りが 3 ~ 5 件あることがわかりました。ソフトウェアまたはハードウェアのローパス フィルターはありますか?ローパス係数をどのように決定しますか?ガイドラインを参照しますか? Re: mm9z1_638 current accuracy is out of 1% requirement こんにちは、トーマス ありがとうございます。別の電流源を変更します。失敗条件が修正されました。 しかし、6Aの精度は+/-1%を満たすことができず、ノイズは約100mAです。100mA のノイズを減らすための提案はありますか?または 100mA のノイズは許容できます。 Br、 マイク・リャン Re: mm9z1_638 current accuracy is out of 1% requirement こんにちは、Mikeさん データを見ると、定期的に低い数値が出ているようですが、これはどこから来ているのでしょうか?これはテスト機器またはソフトウェアからのものでしょうか? この定期的なイベントが問題を引き起こしているようです。 よろしくお願いいたします。 トーマス
View full article
MPX5100 Voltage pins - Vout, V1, V2, Vex Hi there, I have been trying to test a few MPX5100DP units I received for calculating air flow. With a similar differential sensor I am able to see the expected pressure values. However, I cannot get Vout to change from its base voltage of 185/200mV. What is the purpose of V1, V2 and Vex and what do they correspond to? I'm sorry to ask, but I could not find an explanation for those pins in the datasheet or various application notes I found. Thank you for your help. Pressure Sensors Re: MPX5100 Voltage pins - Vout, V1, V2, Vex Hello Andrew, Thank you for writing. In this case, V1, V2 and VEX pins are used for factory trimming and it is recommended to leave these pins unconnected. Can you please share your schematic? How are you connecting the MPX5100DP device? Regards, David
View full article
speed I am using rw612, is it possible to send udp packet every 1ms? after about 20 seconds i cannot send and should wait. I increased all buffers but it did not work. I receive MEM Error after that Re: speed /*  *  Copyright 2020-2022 NXP  *  All rights reserved.  *  *  SPDX-License-Identifier: BSD-3-Clause  */ #ifndef _WIFI_CONFIG_H_ #define _WIFI_CONFIG_H_ #include "wifi_bt_module_config.h" #define OVERRIDE_CALIBRATION_DATA "wifi_cal_data_override.h" #define CONFIG_IPV6 0 #define CONFIG_MAX_IPV6_ADDRESSES 0 #define CONFIG_RF_TEST_MODE 0 #define CONFIG_MAX_RESCAN_LIMIT 30 #define CONFIG_WIFI_AUTO_POWER_SAVE 0 #define CONFIG_TURBO_MODE 0 #define CONFIG_WIFI_TX_PER_TRACK 1 #define CONFIG_WIFI_TX_BUFF 1 #define CONFIG_WIFI_FEATURES 1 // #define CONFIG_HOST_SLEEP 0 #define CONFIG_POWER_MANAGER 0 // #define CONFIG_MEF_CFG 0 /** If define CONFIG_TX_RX_ZERO_COPY 1, please make sure  *  #define PBUF_POOL_BUFSIZE 1752  *  in lwipopts.h  */ #define CONFIG_TX_RX_ZERO_COPY 1 // #define CONFIG_ANT_DETECT 1 #define CONFIG_11AX 0 // #define CONFIG_11AC 0 /* WLCMGR debug */ #define CONFIG_WLCMGR_DEBUG 0 /*  * Wifi extra debug options  */ #define CONFIG_WIFI_EXTRA_DEBUG 0 #define CONFIG_WIFI_EVENTS_DEBUG 0 #define CONFIG_WIFI_CMD_RESP_DEBUG 0 #define CONFIG_WIFI_PKT_DEBUG 0 #define CONFIG_WIFI_SCAN_DEBUG 0 #define CONFIG_WIFI_IO_INFO_DUMP 0 #define CONFIG_WIFI_IO_DEBUG 0 #define CONFIG_WIFI_IO_DUMP 0 #define CONFIG_WIFI_MEM_DEBUG 0 #define CONFIG_WIFI_AMPDU_DEBUG 0 #define CONFIG_WIFI_TIMER_DEBUG 0 #define CONFIG_WIFI_SDIO_DEBUG 0 #define CONFIG_WIFI_FW_DEBUG 0 #define CONFIG_WIFI_UAP_DEBUG 0 #define CONFIG_WPS_DEBUG 0 #define CONFIG_FW_VDLL_DEBUG 0 #define CONFIG_DHCP_SERVER_DEBUG 0 #define CONFIG_FWDNLD_IO_DEBUG 0 /*  * Heap debug options  */ #define CONFIG_HEAP_DEBUG 0 #define CONFIG_HEAP_STAT 0 #endif /* _WIFI_CONFIG_H_ */ Re: speed Thanks for your answer. VS code, SDK 25.09. Freertos. I want to send every 1ms a udp packet to an AP, (rw612 to rw612) on receiver side (AP), i fixed the problem, it seems can receive. but on transmitter after ~20 second, i got error -1 from udp_send function and after a second it works again for some seconds and again. I increased many values on TCP/IP config library but no effect. Re: speed Hello @gtecaskari, hope you are doing well. To better analyze the issue, could you please share more details about your test scenario? Information such as the board you are using, the IDE (MCUXpresso or MCUXpresso for Visual Studio Code), SDK version, whether you are working with FreeRTOS or Zephyr, and the specific example you are running would be very helpful. Re: speed Hi @gtecaskari. Thanks for sharing your environment, although it would be very helpful if you could provide more details on your application and clarify if it is an example from the SDK or a custom project. If it is an example from the SDK please share with me the example and the steps that you are following so I can be able to replicate your issue and try to get to the root cause. Re: speed Hi.a custom project.  and i have another question. when we are using freertos, why the wifi interrupt priority still 0, it should be bigger than 2 ( freertos config). judt i want to know is it possible send continues udp packet every 1 ms? when i am sending every 2 ms it is working. and another problem, when i am using wifi6, i have many packet loss by shaking my device. ( also without shaking but less).  when i disable AX, it is working much better, maybe 1 packet loss every 1 hour.  Re: speed Hello @gtecaskari. Is your custom project based on any of our SDK demos? If so, could you please specify which example it is derived from? Additionally, could you clarify where you are viewing the priority configuration? The FreeRTOS configuration file only defines general OS parameters such as the tick rate and the maximum number of available priorities. Any task‑specific priority values (or changes to them) must be configured within the application itself. Re: speed Hi, I have selected httpsrv example and changed.  my last configs: priorities: in "lwipopts.h", #define TCPIP_THREAD_PRIO      (configMAX_PRIORITIES - 1) in "wifi_config.h" #define CONFIG_WIFI_MAX_PRIO (configMAX_PRIORITIES - 2) And please answer why when wifi6 (11AX) is enabled, when I shake the board, a lot of packets are lost? when i use "#define CONFIG_11AX 0" , it is working. And I could not find any document about TURBO MODE. What is the parameter 0~3. Why you dont have a good document for your product.  and my last result, I can send 128 byte packet every 1 ms, but cannot send 256 bytes (error after a while) Re: speed Hello @gtecaskari. Could you please confirm that the "CONFIG_WIFI_MAX_PRIO" macro has been added by you as a part of your custom modifications? Also please clarify on what are you referring on the turbo mode issue? Re: speed Hello @gtecaskari. I'm checking internally the issue about the turbo mode documentation, I will let you know upon any update on this regard. Regarding your Wi-Fi 6 data loss, since this might be related to your setup, therefore I'm not able to replicate your issue as I cannot replicate your exact test scenario. Re: speed dear @RomanVR , I fixed speed problem, Please answer these 2 questions. what it does wlan_set_turbo_mode function, the input is 0 to 3. and why when I am using wifi6, i have data loss when shaking the board, but it is working with WIFI5 and 4 Re: speed Hello @gtecaskari, sorry for the late response. The wlan_set_turbo_mode function allows the user to configure WMM performance optimization levels for a Wi-Fi connection. Regarding the parameters that this function receives: - 0: Standard mode (required for WFA certification) - 3: Enhanced performance. The usage of the function would be "int wlan_set_turbo_mode(t_u8 mode);" and it would return WM_SUCCESS on success setup and WM_FAILURE on failure. Please let me know if this information clears out your doubts.
View full article