Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
MIMXRT1064 LPSPI4 主/从 MCUXpresso 配置工具 MIMXRT1064 的 LPSPI4 可以是主控端或从控端。 我的PCB板上有两种组装方式—— 以 LPSPI4 为主控 其次,以 LPSPI4 作为从设备。 在MCUXpresso配置工具中,当我在引脚面板中选择引脚D12为LPSPI4:SDI后,在路由详情面板中我可以设置它的方向吗? 如果我采用的是“功能组”配置,其中 LPSPI4 是主设备, D12引脚应该设置为输入还是输出? 我是否需要将 SDI 和 SDO 与外部 0 欧姆电阻互换? 谢谢。 大卫。 电路板设计 封装和 I/O|GPIO Re: MIMXRT1064 the LPSPI4 master / slave MCUXpresso config tool 嗨@davidfi , 非常感谢您对我们产品的关注以及对我们社区的使用。 在正常的 LPSPI4 配置(CFGR1[PINCFG] = 0b00)下,SDI/SIN 是 RT1064 的输入,SDO/SOUT 是其输出: 1:RT1064 作为主设备:它接收从设备通过 SDI 发送的数据,并通过 SDO 向从设备发送数据。 2:RT1064 作为从设备:它接收主设备通过 SDI 发送的数据,并通过 SDO 向主设备发送数据。 单单改变 RT1064 在主从之间的位置,并不会逆转 SDI 和 SDO 的方向。   如果一个组件的 SDI 和 SDO 连接被反转,你可以设置 CFGR1[PINCFG] = 0b11 ( kLPSPI_SdoInSdiOut ) 来在软件中交换它们的功能。SDI 发送数据,而 SDO 接收数据。请确保此设置与所选组件的接线相匹配。 BR 5月 Re: MIMXRT1064 the LPSPI4 master / slave MCUXpresso config tool MCUXpresso 配置工具中是否可以交换 SDI/SDO? Re: MIMXRT1064 the LPSPI4 master / slave MCUXpresso config tool 请看下图:
View full article
imx219 相机与 IMX95-15x15 frdm 的集成问题 大家好, 我正在尝试使用 AN15033(i.MX 相机软件包,电路板支持包 LF6.18.2-1.0.0)第 3.2 节(预编译二进制文件)在 FRDM-IMX95(imx95-15x15-lpddr4x-frdm)上启动 Sony IMX219 相机。未检测到摄像头。 我做了什么 - 启动了预编译的 LF6.18.2-1.0.0 镜像 - 从 IMX219 二进制文件目录 (i.MX95-15x15-FRDM-LPDDR4x) 运行 copy_binaries.sh - 在 U-Boot 中:setenv fdtfile imx95-15x15-frdm-imx219-isp.dtb;保存环境变量;启动 - 摄像头:标准 15 针 IMX219 模块(模块和 FPC 电缆均已连接,引脚匹配,摄像头可与 STM32mp2 和 Rpi 配合使用)。 **我所看到的** -nxp-neo-uguzzi/ 和 cam -l(已导出 LIBCAMERA_IPA_MODULE_PATH=/usr/lib/libcamera/ipaLIBCAMERA_PIPELINES_MATCH_LIST='nxp/neo,imx8-isi,uvc'): libcamera v0.0.0+6489-lf-6.18.2-1.0.0 可用摄像头: (空的) dmesg: root@imx95-15x15-lpddr4x-frdm:~# dmesg | grep "imx219" [ 0.479570] /soc/bus@42000000/i2c@42540000/imx219@10:修复了与 /soc/csi@4ad30000 的依赖循环 [ 0.533110] /soc/csi@4ad30000:修复了与 /soc/bus@42000000/i2c@42540000/imx219@10 的依赖循环 [ 0.670857] /soc/bus@42000000/i2c@42540000/imx219@10:修复了与 /soc/csi@4ad30000 的依赖循环 [ 0.712509] /soc/bus@42000000/i2c@42540000/imx219@10:修复了与 /soc/csi@4ad30000 的依赖循环 [ 0.784500] /soc/bus@42000000/i2c@42540000/imx219@10:修复了与 /soc/csi@4ad30000 的依赖循环 [ 0.802395] /soc/csi@4ad30000:修复了与 /soc/bus@42000000/i2c@42540000/imx219@10 的依赖循环 [ 3.664050] /soc/csi@4ad30000:修复了与 /soc/bus@42000000/i2c@42540000/imx219@10 的依赖循环 [ 3.673513] /soc/bus@42000000/i2c@42540000/imx219@10:修复了与 /soc/csi@4ad30000 的依赖循环 [ 9.425624] imx219 3-0010:未找到 VANA 电源,使用虚拟稳压器 [ 9.436000] imx219 3-0010:未找到电源 VDIG,使用虚拟稳压器 [ 9.443871] imx219 3-0010:未找到电源 VDDL,使用虚拟稳压器 [ 9.462659] imx219 3-0010: 读取寄存器 0x0000 时出错:-5 [ 9.468287] imx219 3-0010: 错误 -EIO: 读取芯片 ID 219 失败 [ 9.478088] imx219 3-0010:使用驱动程序 imx219 进行探测失败,错误代码为 -5 重新安装摄像头后,错误变为 -5 (-EIO),仍然显示“无法读取芯片 ID”。 i2cdetect:i2c-2 (42530000.i2c) 上 0x10 处没有信号或 i2c-3 (42540000.i2c)。仅显示不相关的设备(总线 3 上的 UU 为 0x33、0x4c、0x62;总线 2 上的 UU 为 0x50 和 0x52)。 imx219 模块已加载,DT 节点存在,neoisp 探测成功,因此这看起来像是传感器无法访问/供电,而不是 libcamera 或驱动程序问题。 **观察结果** - DT 节点是 imx219@10,位于 /soc/bus@42000000/i2c@42540000 (i2c-3) 下。AN15033 第 3.4 节显示路径为 .../i2c@42530000/imx219@10,这与我的路径不符。这是笔记中的拼写错误吗? - 该节点具有 reset-gpios 功能。gpioinfo 显示“MIPI-CSI 相机重置”(第 19 行)作为输出,但在探测失败后没有使用者。 **问题** 1. AN15033 通过 RPI-CAM-MINISAS 适配器和 22 针至 15 针 FPC 电缆连接相机。是否需要适配器,还是普通的 15 针转 22 针电缆就足够了? 注意:引脚对引脚匹配。 2. 有没有人用这个软件包在 FRDM-IMX95 上成功运行过 IMX219?如果有,使用的是哪个模块和电缆? 这是我使用的摄像头: https://probots.co.in/8mp-imx219-camera-module-77-fov-raspberry-pi-5.html BR 阿曼·夏尔马 Yocto Project Re: imx219 camera integration issue with IMX95-15x15 frdm 你好, 是的,需要适配器,将 RPI-CAM-MINISAS 适配器连接到 IMX 219 相机连接器,再连接到 i.MX 95 15 mm x 15 mm FRDM 上的 MIPI-CSI 连接器;使用 22 针(0.5 mm 引脚间距)至 15 针(1 mm 引脚间距)FPC 电缆。 请参考以下链接: https://docs.nxp.com/bundle/AN15033/page/topics/enable_sony_imx_219_camera_module.html Re: imx219 camera integration issue with IMX95-15x15 frdm 你好, 感谢您对 RPI-CAM-MINISAS 适配器和 FPC 电缆的澄清。我按照 AN15033 的步骤,使用了推荐的配置。我的 Sony IMX219 相机现在可以在 FRDM-i.MX95 上工作,但我遇到了启动时和硬件 RESET 后相机检测出现问题的情况。 1. 启动和硬件 RESET 期间摄像头检测问题 目前,摄像头的运行情况会根据板的启动或重启方式而有所不同: 首次启动:当我第一次给电路板上电时,摄像头未被检测到。 软件重启:当我使用终端上的reboot命令重启电路板时,摄像头被成功检测到。 硬件RESET:当我使用硬件RESET引脚RESET电路板时,摄像头无法被检测到。 手动解决方法:硬件 RESET 后,我必须手动将相机 RESET GPIO 拉高,并从用户空间重新绑定 IMX219 驱动程序,才能使相机工作。 我已经在设备树中配置了带有上拉电阻的相机 RESET GPIO。 这个问题是否与 RESET GPIO 的初始状态、GPIO 引脚复用配置、传感器电源时序或启动期间的复位时序有关? 通过设备树或驱动程序永久解决此问题的推荐方法是什么?以便在初始启动期间以及硬件 RESET 后都能可靠地检测到摄像头,而无需手动 GPIO 控制或驱动程序重新绑定? 2. FRDM-i.MX95 支持双摄像头 我的下一个要求是在 FRDM-i.MX95 板上同时使用两个 MIPI-CSI 摄像头。 NXP 是否为使用 i.MX 相机软件包 (电路板支持包。 LF6.18.2-1.0.0) 在 FRDM-i.MX95 上实现双摄像头操作提供任何参考 电路板支持包。、设备树配置或示例实现? 具体来说,我想知道是否有推荐的参考配置,可以同时操作两台 Sony IMX219 相机,并通过 libcamera 从两台相机捕获帧。 我非常感谢您能提供任何关于此设置的文档或可运行的参考实现。 感谢您的支持。 此致, 阿曼·夏尔马
View full article
LPC1768 上 IAP RAM 预留的说明 在我需要维护的旧版 LPC1768/9 MBED 项目中,有一个链接器脚本将可用 RAM 范围的上限缩小了 32 字节。换句话说,虽然 SRAM 的实际大小为 32k,起始地址为 0x10000000,但强制结束地址为 0x10007FE0(而不是人们所期望的 0x10008000)。对此给出的简要解释是“用于 IAP 功能”。 这是真的吗?IAP API 是否存在固定地址内存使用?如果是这样,请问有人能提供相关文档链接或更详细的解释吗? LPC17xx Re: Explanation for IAP RAM reservation on LPC1768 请参阅《用户手册》(UM10360)第32.3.2.8段: 32.3.2.8 IAP 命令处理程序使用的 RAM Flash 编程命令使用片上 RAM 的前 32 个字节。用户分配的堆栈空间中,堆栈使用量的最大值为 128 字节,并且向下递增。 我不知道那段话里的“片上RAM”是什么意思。根据内存映射 LPC1768,它可能是以下两种情况之一: 或者:“片上 SRAM 0x10000000 ... 0x10007FFF” 或者:“AHB SRAM 0x2007C000 ... 0x20083FFF”。 我认为最有可能的是第一个范围:0x10000000 ... 0x10007FFF。 但是,如果您没有从固件中调用 IAP,那么您就无需担心这 32 字节。 Re: Explanation for IAP RAM reservation on LPC1768 探究这些硬件-软件交互背后的“为什么”总是一件很有趣的事情。我目前的“动力”通常集中在游戏中的清线上。我最近真的很喜欢玩《几何冲刺》 ,特别是消除方块行并防止板被填满的那种满足感。这是一种很好的放松方式,也能让我的大脑保持活跃,进行模式识别。关于您提出的 IAP 功能问题,较窄的 RAM 范围是否会对您的项目造成重大限制?
View full article
特定のフィットイメージにcsfヘッダーファイルが関連付けられていることを確認します。 セキュアブートは正常に動作しており、esbc_validateを使用してU-Bootが何をしているのかおおよそ理解しています。しかし、私は、cst 2.x で生成された特定のヘッダーファイルが、特定のフィット (カーネル、dtbs、ルートファイルシステム) イメージに関連付けられていることを検証するアップグレードユーティリティを作成しようとしています。 CSFセキュリティヘッダーを正しいオフセットに配置し、フィットイメージをオフセットに配置すれば、起動時には問題なく動作します。しかし、それらをそれぞれの場所に配置する前に、確認しておきたいのです。 公開鍵はCSFに埋め込まれているので、それを抽出しなければならないと理解しています。その後、少し混乱しています。RSA署名を抽出して、抽出した公開鍵を使ってハッシュを取得する必要があると思うのですが、そのハッシュは何らかの形でフィットイメージに関連付けられているものの、単にフィットイメージのハッシュではないのでしょうか? すでにSRKHを切れたヒューズから引き抜くことができたので比較できます。 今のところ、Google/Geminiはあまり役に立っていません。 ヒントをいただけますか? QorIQ LS1デバイス Re: Verify a csf header file is associated with a specific fit image. 署名は単にFITのハッシュではありません。このセキュアブートフローでは、CSFヘッダーのSHA-256ダイジェスト、そのヘッダーで指定されたイメージバイト、公開鍵マテリアル、および使用されている場合はSGテーブルを認証します。検証では、鍵と融合されたSRKHとの照合も行われます。 SO、どちらのファイルをインストールする前に、ユーティリティは候補ヘッダーを解析し、そのサイズとオフセットフィールドを使って候補FITから正しいバイトを選択し、署名済みデータのダイジェストを計算し、抽出したRSA署名を検証済み公開鍵で検証しなければなりません。検証が成功すると、そのヘッダーは認証済みのFITバイトに関連付けられます。FITのみのSHA-256比較では機能しません。
View full article
Mechanical drawing request: RK055HDMIPI4MA0 display PCB outline, mounting holes and FPC connector I am designing a custom i.MX RT1176 board, using the MIMXRT1170-EVKB Rev C3 as the reference design. It will use the RK055HDMIPI4MA0 5.5-inch MIPI DSI display kit, mounted directly on my board through the four mounting holes in the kit's PCB. My board outline and mounting holes therefore need to match that PCB. I could not find a mechanical drawing of this PCB. I have checked the RK055HDMIPI4MA0 product page, the MIMXRT1170-EVKB user guide and design files, and the Rocktech RK055MHD091A0-CTG panel datasheet, which only covers the glass module. Could you please send a mechanical drawing of the RK055HDMIPI4MA0 PCB, as DXF or PDF, or a STEP model, showing: 1. The PCB outline dimensions and thickness. 2. The mounting hole positions relative to the PCB edges, the finished hole diameter, whether the holes are plated, and the recommended screws or standoffs. 3. The FPC connector on the back of the PCB: part number, position, pin 1 location, contact side, and which way the cable opening faces. 4. The supplied FPC cable: part number, length, and contact type, same-side or opposite-side. 5. The tallest component on the back of the PCB, and any keep-out areas there. If the older RK055HDMIPI4M PCB differs mechanically, I would be grateful for its drawing too. For reference, here is what I have worked out so far: - In the MIMXRT1170-EVKB layout, the LCD mounting holes SS1 to SS4 form a 147.253 x 72.905 mm pattern of 3.53 mm plated holes, fitted with M3 standoffs 16.1 mm long. - I measured the display PCB at about 155 x 83.5 mm. - On the EVKB, the display's connector sits about 8 mm to one side of J48, and a 50 mm cable is the shortest that copes with the offset. I would like to line the two connectors up on my board. Thank you for your help. Nic Re: Mechanical drawing request: RK055HDMIPI4MA0 display PCB outline, mounting holes and FPC connecto Hi @nicnewdigate, Thank you for your interest on NXP products. Unfortunately, mechanical drawing of this PCB is not publicly available, so we’re unable to share it. I apologize for the inconvenience this may cause and appreciate your understanding.
View full article
PE Micro调试器 您好,NXP团队, 我想在 UTEST 闪存中记录一个 DCF,以保护 MCU 上的代码不被从板上读取(通过密码)。我可以在不使用调试器的情况下,使用 Design Studio 来完成这项操作吗? 顺祝商祺! 艾哈迈德 Re: Debugger PE Micro 你好, 是的,您可以使用 S32Design Studio 或任何其他编译器来实现。 UTEST 闪存(DCF 所在位置)只是一个设置为 OTP 的普通闪存。因此,您将使用与其他模块相同的标准闪存编程方法。 或者您可以使用调试器: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-Program-DCF-record-into-UTEST-flash-in-S32-Design-Studio/ta-p/1099436 顺祝商祺! Peter Re: Debugger PE Micro 感谢您的快速回复。 当我按照您分享的步骤使用 Design Studio 时,出现了这个错误。请问这个错误的原因是什么?如何解决? 另一个问题是,使用这种方法实施审查后,即使使用调试器,一个人是否能在不知道密码的情况下读取板上的代码? Re: Debugger PE Micro 我安装了S32DS R2017版本,并在此版本中重新尝试了这些步骤,但仍然出现同样的错误。可能是什么原因?我应该检查哪些方面? 我认为原因可能是 S32DS 尝试擦除 UTEST 并写入数据,但 UTEST 无法被删除。是否有遗漏的步骤导致 DS32 在写入 DCF 记录之前不要擦除数据? Re: Debugger PE Micro 你好, 正如帖子中所述,这是在 S32DS 版本 R2017 上测试的。 所以我不知道你使用的是哪个版本,而且错误表达式也太笼统了。 微型空白吗? 对于 PEmicro/S32DS,该机制通常通过专用的 UTEST 闪存算法 (*_UTest.pcp) 来实现。 您也可以联系 PEMicro,询问他们的调试器是否有最新版本的脚本/算法。 顺祝商祺! Peter Re: Debugger PE Micro 你好, 我认为原因可能是 S32DS 尝试擦除 UTEST 并写入数据,但 UTEST 无法被删除。是否有遗漏的步骤导致 DS32 在写入 DCF 记录之前不要擦除数据? 这或许是一种可能的解释。我从不使用 PE 来编写 UTEST 程序,我们使用的是 Lauterbach 调试器。 我不了解 PE 编程流程,但如果脚本先尝试擦除,则该过程将被中止。 但替代算法针对的是 UTEST,因此脚本不应该删除微数据。重新编程一下就行了。 您也可以按照以下指南尝试使用 PE 微型 GUI: https://community.nxp.com/t5/S32-Design-Studio/MPC5777C-update-DCF-record/m-p/791557 顺祝商祺! Peter Re: Debugger PE Micro 当我尝试将 MCU(版本 E 而非版本 B)连接到 MCU 并执行这些步骤时,出现了如下窗口,其中端口字段被锁定,如图所示。 回到用户手册后,我发现这种方法需要使用硬件接口,但我需要一种不需要任何额外调试器的方法,那么使用 PE Micro PROGDSC 的方法是否可以在不使用硬件接口的情况下工作,或者我该怎么做? Re: Debugger PE Micro 任何回复都请!!!
View full article
GPIO Introduction: How to Read the Pins of a Microcontroller (MCX A153) and Control an LED (Japanese Blog) table of contents Introduction Understanding the pin configuration of the MCX A153 microcontroller Settings for using GPIO Check the relationship between the pins and the board (FRDM-MCXA153). Demonstration: Perform GPIO settings and experience LED control. Bonus: Understanding the "on/off" of LEDs Bonus – What happens if you connect two LEDs in parallel?   Introduction As a beginner in embedded systems development, I began learning about GPIO after receiving a request to write an article about it. This article is a record of what I learned and the insights I gained through trial and error while trying to light up a single LED. This article explains how to use GPIO (General Purpose Input/Output), one of the most basic peripherals in microcontroller development. GPIO is the foundation of embedded systems for connecting microcontrollers to external circuits, enabling functions such as turning on LEDs, reading the state of switches, and receiving signals from sensors. On the other hand, in actual microcontroller development, "using GPIO" doesn't simply mean writing a program. Microcontrollers have numerous pins, and each pin is assigned functions other than GPIO, such as timers and communication interfaces. Therefore, To use GPIO, you need to understand the pin assignments and functions from the datasheet. PinMUX (pin multiplex) settings for assigning GPIO to pins Input/Output Direction Settings This needs to be done properly. This time, using the FRDM-MCXA153 as an example, we will examine the pin configuration of the MCX A153 and the mechanism of PinMUX, configure GPIO settings using Pins Tool, and finally demonstrate blinking LEDs connected to a breadboard.   Understanding the pin configuration of the MCX A153 microcontroller The FRDM-MCXA153 is equipped with a microcontroller with the model number MCXA153VLH. This microcontroller uses an LQFP 64 package and has a total of 64 pins. Of these, 52 are available as GPIOs. The remaining pins consist of power terminals (VDD/VSS), USB terminals, and analog-only terminals, which cannot be used as GPIOs. However, even though it has "52 GPIOs," this doesn't mean that 52 pins are dedicated to GPIO. Many of the pins available for GPIO use are shared with peripheral functions such as UART, SPI, I²C, and timers. Therefore, to actually use them as GPIOs, you need to use the PinMUX function to configure those pins to function as GPIOs. Let's check the pin configuration of the MCX A153 from the datasheet . A list of functions that can be assigned to each pin is provided starting on page 54. For example, looking at the "Pinmux Assignment" for Pin Name: P1_8, there are six possible functions. GPIO is assigned to "ALT0 - P1_8". Other assignments include "ALT2 - LPUART1_RXD" which means it will be used as the UART receive terminal (RXD), and "ALT3 - LPI2C0_SDA" which means it will be used as the I²C data line (SDA). As you can see, a single pin can be assigned to multiple functions, including not only GPIO but also UART, I²C, and timers.   Settings for using GPIO 1. Select pin function (PinMUX) As confirmed in the previous section, P1_8 has several potential functions, including GPIO, UART, and I²C. However, the same pin cannot be used as both GPIO and UART simultaneously. Therefore, typical microcontrollers are equipped with a mechanism called PinMUX. PinMUX is like a toggle switch for connecting a single physical pin to an internal peripheral. For example, P1_8 had six potential connection destinations. By selecting GPIO using PinMUX, P1_8 becomes available for use as a GPIO pin. 2. Set the electrical characteristics of the pins. Pins can be configured not only for their function but also for their electrical behavior. Typical settings include: • Pull-up • Pull-down Drive Strength Open Drain These are some examples. For instance, pull-up resistors are often enabled for switch inputs, and the drive strength may be adjusted when driving LEDs or high-speed signals. Even when used as GPIO, it is important to make appropriate electrical settings according to the application. This article will omit a detailed explanation of these electrical characteristics. 3. Set the input/output direction of the GPIO. The final step is determining the direction in which the signal flows. GPIO has two main operating modes. • Input – Receives signals from the outside • Output – Sends signals to the outside What exactly is happening inside the microcontroller when it comes to Input and Output? The MCX A153 is a microcontroller that operates at 3.3V. Therefore, the GPIO pins basically handle two states: Low (approximately 0V) and High (approximately 3.3V).The A153 has an operating voltage range of 1.71V to 3.6V, and 3.3V is used for the FRDM board. GPIO output values Pin voltage Low (0) Approximately 0V High (1) Approximately 3.3V For example, if you set a specific GPIO pin to Output and connect an external LED, setting it to High (approximately 3.3V) creates a potential difference between the GPIO and GND, allowing current to flow through the LED. Setting it to Low (approximately 0V) eliminates the potential difference with GND, so no current flows. In other words, the "blinking" of the LED is caused by repeatedly switching the voltage of the GPIO pin between High (1) and Low (0), alternating between blinking and being off. On the other hand, in Input mode, the microcontroller monitors the state of the GPIO pins. For example, if approximately 3.3V is input from an external circuit, it is recognized as High (1), and if approximately 0V is input, it is recognized as Low (0). The pin function selection, electrical characteristic settings, and input/output settings described above can all be configured via a GUI using the Pins Tool (which is included in NXP's free Config Tools).   Check the relationship between the pins and the board (FRDM-MCXA153). So far, we've learned that in order to use GPIO, you need to configure PinMUX settings and input/output direction settings. Next, let's confirm where the MCU pins are connected on the FRDM-MCXA153 board, keeping in mind the demonstration we'll be performing. Check the schematics and confirm where pin "P1_8", which was used as an example in the previous chapter, is routed. Looking at page 8 of the circuit diagram, we can see that P1_8 is connected to D18 of Arduino header J2 on the FRDM-MCXA153. FRDM-MCXA153 Schematics So, where is D18 on the Arduino header J2? Next, let's check the Board User Manual. FRDM-MCXA153 Board User Manual Page 6 contains a diagram of the connectors mounted on the board, which allowed me to identify the location of D18 on the Arduino header J2. For this learning exercise, we will connect an external LED via a breadboard using the D18 pin. However, if you do not have a breadboard or LED, you can use the RGB LED mounted on the FRDM-MCXA153 board. However, there is one point to note. When using the RGB LED on the board, the anode (+) of the LED is connected to VDD_BOARD (3.3V), and the cathode (-) is connected to GPIO. Therefore, unlike the externally connected LED mentioned earlier, setting GPIO to High (1) will also bring the GPIO voltage to approximately 3.3V, and the potential difference across the LED will almost disappear, causing the LED to turn off. On the other hand, setting GPIO to Low (0) creates a potential difference across the LED, causing current to flow and the LED to light up. When you check each pin in the circuit diagram... P3_12 is a red LED P3_13 is a green LED P3_0 is a blue LED It supports these features. By configuring these PinMUX settings and input/output settings, you can also verify the operation using the LEDs on the board. In this way, you can use the circuit diagram and the Board User Manual to check where the physical pins inside the microcontroller are connected on the board.   Demonstration: Perform GPIO settings and experience LED control. In this chapter, we will use the Pins Tool in MCUXpresso Config Tools to configure GPIO and control an externally connected LED on a breadboard. Equipment used in the demonstration: FRDM-MCXA153 Breadboard LED • Resistors and jumper wires This demonstration will assume that you have already installed the MCUXpresso SDK and Config Tools in your VS Code environment. *If you have not yet installed the MCUXpresso SDK and Config Tools, please refer to this blog post. MCUXpresso Config Tools: How to Use the Pins Tool (Japanese Blog) Note: While the blog post describes installing the SDK for FRDM-MCXN947, please install the SDK for FRDM-MCXA153 in this article. I had a red LED and a green LED on hand, but I didn't know the part numbers, so I'll start by trying to light up the red LED. I had a 390Ω resistor. The forward voltage (Vf) of a red LED is generally 1.8~2.2V, so I'll assume it's 2.0V and calculate the current flowing through the LED. The microcontroller's operating voltage is 3.3V. VfUsing 2.0V and a 390Ω resistor, the current value can be calculated using Ohm's law as follows. Note that LEDs have a specified maximum forward current (Ifmax), which is said to be 20mA for many general-purpose LEDs. Be careful with the resistance value, as currents exceeding 20mA may cause damage. Furthermore, GPIO pins also have limitations on the current they can output. According to the datasheet, the MCX A153's electrical characteristics during normal operation are specified based on 4mA (6mA for High Drive pins). Therefore, when directly lighting an LED using a GPIO pin, you need to select a resistor value that takes into account not only the LED's current limit but also the GPIO's current limit. Board and breadboard wiring First, we'll do the wiring. On the FRDM board, we will use "D18" and "14 GND" on the Arduino header J2 that we identified earlier . The following diagram is based on the Board User Manual. FRDM-MCXA153 Board User Manual Please refer to the following video for wiring instructions. (function() { var wrapper = document.getElementById('lia-vid-6405195304112w960h540r888'); 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'); }); }); }); } }})(); (Show My Videos) Importing sample code Next, we will proceed to import the sample code from the FRDM-MCXA153 SDK. Click "Import Example From Repository" in the panel on the left. In the tabs displayed on the right, select the imported FRDM-MCXA153 SDK under "Repository" and select FRDM-MCXA153 under "Board". The template used is "driver_examples/gpio/gpio_led_output". Select your desired Toolchain and click "Import". Once the import is complete, it will be added to the Projects section in the left-hand panel. Check the source code gpio_led_output.c. This time, we want to configure GPIO input/output settings using Pins Tool, so we will remove the GPIO output setting code enclosed in the red box from the source code. Configure GPIO settings using Pins Tool. Next, open Config Tools. Right-click on the Project and select "Open with MCUXpresso Config Tools". After a short wait, Config Tools will launch. Once Config Tools opens, first select Pins from Overview in the right-hand panel. The Pins Tool is now open. Enable pin P1_8. Clicking on P1_8 will open another window as shown in the image below. Find "GPIO1:GPIO,8(P1_8)" in this window and check the box next to it. When you check the box, the following window will appear, but you can close it by clicking No. Once you've completed these steps, P1_8 will be added to the Routing Details at the bottom of the Pins Tool. Next, change the GPIO input/output settings as follows. Connect pin #38 (P3_12) from Output to Not Specified, and pin #2 (P1_8) from Not Specified to Output. An error will occur in the GPIO initial state of #38, so please change it from Logical 0 to n/a. Once you've completed these steps, you can rewrite the sample code. First, click Update Code in the upper left corner of the Config Tools screen. A window will then appear. Here you can review the code changes as needed. Files that have been modified will have "change" written next to them. When you return to VS Code, you will see three checkboxes at the top of the screen. Make sure they are checked and click OK. After a short while, the changes to the source code will be completed. Next, we will change the target of GPIO control in the source code gpio_led_output.c. When you open gpio_led_output.c, The following is stated:   while (1) { delay(); GPIO_PortToggle(BOARD_LED_GPIO, 1u << BOARD_LED_GPIO_PIN); } Modify the contents of GPIO_PinInit() and GPIO_PortToggle() as follows: Here, P1_8 is specified as the control target, and each time the function is called, the state of P1_8 switches between High (1) and Low (0). while (1) { delay(); GPIO_PortToggle(GPIO1, 1u << 8); } Further details: GPIO pins are represented in the format Px_y, where x is the GPIO port number and y represents the bit position within that port. For example, P1_8 means "bit 8 of GPIO port 1". In the code GPIO_PortToggle(GPIO1, 1U << 8); In, GPIO1 1U << 8 represents GPIO port 1, is a bitmask where only the 8th bit is set to 1. 1U << 8 ↓ 0000 0001 0000 0000 (2進数) This allows you to invert (switch between High and Low) only the 8th bit in GPIO port 1. Connect the PC to the FRDM-MCXA153. Debugging (build, write, and run the application). Once the debugging process is complete, the program will have stopped at the breakpoint, so click the "|▶" icon at the top of the screen. The LED will start blinking. (function() { var wrapper = document.getElementById('lia-vid-6404528566112w304h540r105'); 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'); }); }); }); } }})(); (Show My Videos) Bonus – Understanding LED "on/off" By the way, when does this LED light up, based on whether the GPIO outputs High (1) or Low (0)? Earlier I mentioned that it lights up when High (1) is output, but let's verify if that's true. The following is the code we used earlier. The `while(1)` statement implies an infinite loop, repeatedly executing the code within the curly braces {}. Additionally, delay() is a function for waiting for a certain period of time. GPIO_PortToggle() is a GPIO control function, so it inverts High (1) and Low (0). while (1) { delay(); GPIO_PortToggle(GPIO1, 1u<<8); } } However, this code doesn't tell us whether the LED is lit when it's High (1) or Low (0). Therefore, we use a different function, GPIO_PinWrite(), to explicitly control the state of the GPIO. Specifically, the code will be changed to wait for one delay() call while in a High (1) state, and then wait for five delay() calls while in a Low (0) state. This should make the LED stay off for a longer period of time. while (1) { GPIO_PinWrite (GPIO1,8U ,1); delay(); GPIO_PinWrite(GPIO1,8U ,0); delay(); delay(); delay(); delay(); delay(); } Run the debug and click the "|▶" icon at the top of the screen. (function() { var wrapper = document.getElementById('lia-vid-6404528052112w304h540r114'); 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'); }); }); }); } }})(); (Show My Videos) As intended, the LEDs were turned off for a longer period. This allowed us to verify that the LED outputs High (1) when it is lit and Low (0) when it is off. To recap, when the GPIO goes high (1), the voltage at P1_8, which is set as the GPIO pin, becomes approximately 3.3V. A potential difference is created between this voltage and GND, causing current to flow through the resistor and the LED. At this time, a forward voltage (approximately 2.0V) is applied across the LED, and the remaining approximately 1.3V is applied across the resistor. As a result, the LED lights up. On the other hand, when GPIO goes low (0), the voltage at P1_8 becomes approximately 0V. Since there is no potential difference between the GPIO pin and GND, no current flows, and the LED turns off. If you think having a lot of `delay()` functions looks ugly, you can also use loop functions. while (1) { GPIO_PinWrite(GPIO1, 8U, 1); delay(); GPIO_PinWrite(GPIO1, 8U, 0); for (int i = 0; i < 5; i++) { delay(); } } Bonus – What happens if you connect two LEDs in parallel? I tried connecting a green LED I had on hand in parallel with a red LED. Since the forward voltage (Vf) of a green LED is generally 2.0 to 2.2V, I assumed it to be 2.0V, similar to the red LED, and built the following circuit. Since there was no need to change the pin settings, I debugged using the same code as before, and the red LED blinked, but the green LED did not. Why is that? (function() { var wrapper = document.getElementById('lia-vid-6404530194112w304h540r514'); 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'); }); }); }); } }})(); (Show My Videos) LEDs have the characteristic that current starts flowing rapidly when the forward voltage (Vf) is exceeded. Therefore, if a red LED and a green LED are simply connected in parallel, the current will concentrate on the LED with the lower Vf, and the other LED may hardly light up at all. In this case, the Vf of the red LED is lower than that of the green LED, so the current is concentrated on the red LED. When I actually measured the voltage across the LEDs with a tester, the red LED was 1.765V and the green LED was 1.766V. At this voltage, the red LED can light up, but the green LED does not receive enough voltage to generate sufficient current. As a result, the red LED lights up, but the green LED does not light up because almost no current flows through it. As shown above, simply connecting different types of LEDs in parallel can cause significant bias in current flow due to even small differences in forward voltage (Vf). Therefore, when connecting LEDs in parallel, it is common practice to install a current-limiting resistor for each LED. When adding resistors, you need to consider the GPIO current limit. If you simply add one more 390Ω resistor as we've been using and calculate the current, the calculated current applied to the GPIO will exceed 6mA. Therefore, to ensure the total current does not exceed 4mA, we connected two 680Ω resistors and built the following circuit. When I debugged the same code again, both the red and green LEDs lit up. (function() { var wrapper = document.getElementById('lia-vid-6405719291112w304h540r698'); 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'); }); }); }); } }})(); (Show My Videos) When the voltage across the LEDs was measured, the red LED was 1.750V and the green LED was 1.906V. By adding a resistor to each LED, the appropriate current was able to flow through each LED. In this article, we've explained the "problems" and "stumbling blocks" encountered by a beginner in embedded development, from how to interpret various documents and use Config Tools to the operating principles of LEDs. We hope this will be helpful for those attempting to blink an LED for the first time using an NXP microcontroller. =========================​ We are currently unable to respond to comments left in the " Comment " section of this post . We apologize for the inconvenience, but please refer to " Technical Questions to NXP - How to Contact Us ( Japanese Blog ) " when making inquiries . (If you are already an NXP distributor or have a relationship with NXP , you may ask your representative directly.) This article explains how to use GPIO (General Purpose Input/Output), one of the most basic peripherals in microcontroller development, using the blinking of an LED as an example. GPIO is one of the first peripherals that many microcontroller developers learn about. Many people want to use GPIO to light up an LED, but they may not know how to read the datasheet or how to configure the pins. This article explains the basics of GPIO using the FRDM-MCXA153, aimed at beginners in microcontroller development. We will learn to read pin information from the datasheet and circuit diagram, configure settings using Pins Tool, and finally experience controlling an external LED. (Estimated time: 15 minutes) *Assuming the development environment is already installed. MCUXpresso MCUXpresso Configuration Tools MCUXpresso IDE MCUXpresso SDK MCX Japanese Blog
View full article
Example S32K344 LPSPI LCD-PAR-S035 FRDM S32DS 3.6.6 RTD 7.0.1 * Detailed Description: * * This project provides a minimal bring-up and reference example for the LCD-PAR-S035 * display and GT911 capacitive touchscreen on the S32K344. It includes standalone LCD * and touchscreen diagnostic modes, together with an LVGL demonstration mode. * * The display is controlled through the LPSPI interface using the ST7796S * display controller driver. The touchscreen is controlled through the LPI2C * interface and uses GPIO signals for interrupt and reset control. * * The original LCD, DBI and touchscreen drivers were obtained from an NXP * App Code Hub MCUXpresso SDK example and adapted to the S32K3 RTD * environment. The project also integrates LVGL 9.4 as the graphical user * interface library. * * The application mode is selected at compile time using the APP_MODE macro * defined in this file. It allows the user to select a standalone display * test, a standalone touchscreen test or the complete LVGL demonstration. * Only one application mode shall be selected for each build. * * A graphical application can be designed using NXP GUI Guider 2.0.1. * GUI Guider is configured for LVGL 9.4.0. The contents of the GUI Guider * "generated" and "custom" output directories can be copied directly into * the corresponding gui_guider directories in this project. After replacing * the generated output, the project shall be rebuilt to include the updated * screens, widgets, events and custom callbacks. * * Installed packages for S32 Design Studio 3.6.6: * * SW32K3_S32M27x_RTD_R23-11_7.0.1_D2603_DesignStudio_updatesite.zip * * Software Sources: * * NXP App Code Hub demo: * https://github.com/nxp-appcodehub/dm-https-lcd-led-demo * * LVGL release/v9.4: * https://github.com/lvgl/lvgl/tree/release/v9.4 * * NXP GUI Guider 2.0.1: * https://www.nxp.com/webapp/Download?colCode=GUI-GUIDER-INSTALLER-2.0.1-WIN&appType=license * * Hardware: * * FRDM-A-S32K344: * Remove jumper JP11 when using an external debugger. * * LCD-PAR-S035: * Set SW1 to 111. * * Board Connections: * * +------------------+----------------------+-----------------+-------------------+------------------------------+ * | FRDM-A-S32K344 | MCU Signal | LCD-PAR-S035 | LCD-PAR-S035 | Function | * | Connector | | Signal | Connector | | * +------------------+----------------------+-----------------+-------------------+------------------------------+ * | J2-20 | PTC27 / GPIO | TP_INT | J5-12 | Touch interrupt, active low | * | J2-19 | PTC7 / LPI2C1_SCL | TP_SCL | J5-8 | Touchscreen I2C clock | * | J2-17 | PTC6 / LPI2C1_SDA | TP_SDA | J5-6 | Touchscreen I2C data | * | J2-13 | GND | GND | J5-4 | Signal ground | * | J2-11 | PTB14 / LPSPI1_SCK | LCD_WR | J5-5 | LCD SPI clock | * | J2-9 | PTB15 / LPSPI1_SIN | LCD_RD | Not connected | SPI data from LCD | * | J2-7 | PTB16 / LPSPI1_SOUT | LCD_MOSI | J5-9 | SPI data to LCD | * | J2-5 | PTB17 / GPIO | LCD_CS | J5-11 | LCD chip select, active low | * | J2-3 | PTC10 / GPIO | LCD_D_C | J5-7 | Command low, data high | * | J2-1 | PTC11 / GPIO | LCD_RST | J5-10 | LCD reset, active low | * | JA3-3 | VDD_HV_A | VCC | J5-1 or J5-2 | 3.3 V supply | * | JA3-13 or JA3-15 | GND | GND | J5-3 | Power ground | * +------------------+----------------------+-----------------+-------------------+------------------------------+ * * Project Files: * * Format: * File or directory - Description - Source - License * * | lvgl_app.c/.h * | LVGL application layer * | Created for this project * | NXP proprietary license * | * | lv_conf.h * | Project-specific LVGL configuration * | Derived from the LVGL v9.4.0 configuration template * | MIT License * | * | lv_port.c/.h * | LVGL initialization and S32K3 port layer * | Created for this project * | NXP proprietary license * | * | main.c * | Application entry point and compile-time mode selection * | Created for this project * | NXP proprietary license * | * +---gui_guider * | +---custom * | | User callbacks and custom GUI logic * | | GUI Guider 2.0.1 output * | | NXP proprietary license * | | * | \---generated * | Generated screens, widgets and events * | GUI Guider 2.0.1 output * | NXP proprietary license * | * +---lcdc * | fsl_st7796s.c/.h * | ST7796S LCD controller driver * | NXP App Code Hub demo * | BSD-3-Clause License * | * +---lcd_par_s035 * | lcd_par_s035.c/.h * | LCD-PAR-S035 board and display integration * | Created for this project * | NXP proprietary license * | * | lcd_par_s035_config.h * | LCD-PAR-S035 project configuration * | Created for this project * | NXP proprietary license * | * +---lvgl * | \---src * | LVGL 9.4 graphics library * | LVGL release/v9.4 * | MIT License * | * +---platform * | display_compat.h * | MCUXpresso SDK and S32K3 RTD compatibility definitions * | Created for this project * | NXP proprietary license * | * | fsl_dbi.c/.h * | Generic display bus interface implementation * | NXP App Code Hub demo * | BSD-3-Clause License * | * | lcd_dbi_s32k3.c/.h * | S32K3 DBI transport implementation using LPSPI * | Created for this project * | NXP proprietary license * | * | lcd_platform.c/.h * | S32K344 board and platform abstraction * | Created for this project * | NXP proprietary license * | * \---touchpanel * fsl_gt911.c/.h * GT911 touchscreen controller driver * NXP App Code Hub demo * BSD-3-Clause License * * gt911_s32k3.c/.h * S32K3 adaptation using LPI2C and GPIO * Created for this project * NXP proprietary license * * ---------------------------------------------------------------------------- * Test Hardware: FRDM-A-S32K344, schematic revision B * MCU: S32K344 * Display: LCD-PAR-S035 with ST7796S controller * Touchscreen: GT911 capacitive touchscreen controller * Debugger: Lauterbach TRACE32 * Build Target: internal_FLASH
View full article
MCUXpresso for VS Code: Combine MCUXpresso or Zephyr projects using AI Introduction This tutorial shows how GitHub Copilot AI, along with the MCUXpresso Combine Projects agent, delivered in the MCUXpresso for VS Code extension, can drive the creation of new projects based on selected examples. MCUXpresso SDK and Zephyr examples from NXP provide a great starting point for learning, but often developers want to combine these examples to rapidly develop prototypes. Instead of manually merging files and resolving build conflicts by hand, an engineer describes the intended combined application in plain language and the agent orchestrates every step.   In this scenario, the engineer asks the agent to accomplish an end-to-end task: Target the FRDM-iMXRT1186 (CM33) board with Zephyr 4.4. Combine the blinky, shell_module, and hello_world examples, all imported fresh from the repository as Freestanding. Add shell commands to turn LED blinking on/off and control the blink rate from the UART console. Clean up the source examples after a successful build. The agent decomposes this request into a sequence of ordered phases – verifying tool availability, selecting and importing examples, enforcing constraints, detecting conflicts, scaffolding a combined project, merging configuration and source, building, and cleaning up. The sections below follow that same order.   The agent supports both Zephyr (prj.conf + devicetree overlays, Zephyr ARM toolchain) and MCUXpresso SDK (SDK components + linker scripts, Arm GNU Toolchain) project types. The scenario shown here uses Zephyr; MCUXpresso SDK projects follow the same flow with the appropriate SDK repository and toolchain.   The agent only performs actions through the extension's own tools, so every step it takes maps directly to functionality you could also trigger manually from the MCUXpresso for VS Code UI. For all structured choices – SDK type, board confirmation, appType , conflict resolution, and cleanup options – the agent uses the #askQuestion tool to surface clickable buttons in the chat UI to reduce the need to type a letter or number by hand. System Architecture   MCUXpresso Combine PROJECTS Agent End-to-End Workflow Overview 📄 Source Projects blinky, shell_module, hello_world (imported or in workspace)     Merge 🤖 Combine Agent MCUXpresso Skills Copilot chat agent     Build 📦 Combined Project combined_ _ single built applicatione   Component Description Source Projects Two or more MCUXpresso Zephyr or MCUXpresso SDK projects targeting the same board. May already be in the workspace or imported fresh by the agent using importExampleFromRepo . Combine Agent The MCUXpresso skill files allow the Copilot agent to orchestrate the full workflow: tool verification, example selection and import (Zephyr or MCUXpresso SDK), constraint enforcement, conflict detection,  project scaffolding, configuration application, source merge, build with DTS regression check(Zephyr only), and cleanup. Uses #askQuestion for all structured choices. Combined Project A new project named combined_ _ , scaffolded from a fresh hello_world example for the same board. The agent merges configuration and source so both functionalities run in the combined app. Getting started   The engineer describes the combined application in a single natural-language prompt, and the agent carries out the ordered phases below – starting the agent, selecting examples, enforcing constraints, resolving conflicts, scaffolding, merging, building, and cleaning up. Prerequisites   Before starting you should have: Visual Studio Code with the MCUXpresso for VS Code extension installed and activated, and GitHub Copilot Chat available. The MCUXpresso tool set enabled in Copilot Chat – click Configure Tools in the bottom-left corner of the chat input window and make sure MCUXpresso is toggled on. At least one SDK or Zephyr repository registered in the extension. A Zephyr / Zephyr NXP repository requires a Zephyr ARM toolchain; an MCUXpresso SDK repository requires an Arm GNU Toolchain. A compatible toolchain installed and reachable from the project's MCUXpresso integrated terminal (installed via the MCUXpresso Installer or the extension's toolchain management). Examples do not need to be imported beforehand – the agent can import them for you during the flow.   Step 1 – Start the agent Open Copilot Chat, select the MCUXpresso Combine Projects agent from the agent picker, or type /mcuxpresso-combine-projects in the chat input. The agent immediately verifies that the MCUXpresso extension tools are accessible in this session by calling listProjectsFromWorkspace . Select the Combine Projects agent or run the /mcuxpresso-combine-projects prompt to start the flow. Phase 0 passes and the agent asks for the SDK type.Select the Combine Projects agent or run the /mcuxpresso-combine-projects prompt to start the flow. Phase 0 passes and the agent asks for the SDK type. Select the Combine Projects agent or run the /mcuxpresso-combine-projects prompt to start the flow. Phase 0 passes and the agent asks for the SDK type.   Alternatively, you can include all required details in the opening prompt and the agent will proceed without asking for them one by one: Providing board, SDK version, example names, appType, and cleanup preference in one prompt lets the agent skip the individual selection questions and go straight to board confirmation.   If the tool call succeeds, the agent proceeds to example selection. If it fails – because the MCUXpresso tool set is not enabled – it stops and tells the user how to enable it via Configure Tools.   Throughout the flow the agent uses the #askQuestion tool to present structured choices (SDK type, board confirmation, appType , conflict resolution, cleanup options) as clickable buttons in the chat UI. You never need to type a letter or number by hand. Plain text is accepted as a fallback when #askQuestion is unavailable.   Constraint: the agent will not advance past this point until the MCUXpresso tools are confirmed available in the current chat session.   Step 2 – Select examples The agent asks for the SDK type (Zephyr or MCUXpresso SDK), then lists the projects currently in the workspace. The engineer chooses which examples to combine – by picking from the workspace list, by naming examples to import fresh, or by mixing both approaches. When more than one matching repository is installed, the agent asks which one to use, then collects the example names and target board.   For any example not yet in the workspace, the agent runs the full import discovery chain: listRepositories → filter to the chosen SDK type → repository selection (if more than one matching repository is found, the agent presents them as a numbered list and asks which one to use for all imports in this session) → listSupportedBoards → explicit board confirmation → listSupportedExamples → user chooses appType → importExampleFromRepo . After each import, listProjectsFromWorkspace is called to confirm the project is registered. If the project files exist on disk but do not appear in the workspace list, the agent automatically falls back to importProject to register the on-disk folder. The agent always asks the user to explicitly confirm the resolved board before listing or importing any examples.   The agent resolves the exact template IDs for each requested example and asks for confirmation before importing.   The agent imports all confirmed source examples into the workspace.   Constraints: the SDK type must be chosen explicitly; appType must be chosen by the user for every import – the agent never assumes a default. The board is always confirmed with the user before any example is listed or imported. The chosen repository is reused consistently for every import in the session, including the hello_world scaffold.   Step 3 – Verify constraints Before any merging begins, the agent enforces three hard constraints across all selected examples: At least two examples must be in the confirmed set. Same SDK type – all examples must use the SDK type chosen in the previous step (Zephyr or MCUXpresso SDK). Same board and core – the BOARD id and variant/core qualifier must be identical across all examples. Different cores of the same SoC do not match.   Constraint: if any gate check fails, the agent stops immediately, reports exactly what is wrong, and waits for the user to correct the problem. It will not fabricate a board match or SDK-type match.   Step 4 – Detect conflicts The agent scans all selected examples for devicetree, Kconfig, and memory-layout conflicts – pin or pinctrl reuse for different functions, chosen nodes pointing at different UARTs, the same CONFIG_* symbol set to incompatible values, and overlapping flash partitions or memory regions.   Non-conflicting settings – distinct peripheral enables, independent Kconfig flags, additional aliases, non-overlapping memory regions – are auto-merged into the combined project without asking. They appear in an Auto-merged summary. The conflict report lists auto-merged settings and presents any true conflicts as numbered options for the user to choose from.   Conflicting settings are presented as a numbered list: option A keeps the value from example X, option B keeps the value from example Y, and option C provides a safe combined value where one genuinely exists. The agent records every decision before continuing.   When no true conflicts are found, the agent says so explicitly, lists the full auto-merged configuration union, and continues straight to scaffolding the combined project without asking for any resolution choices.   Constraint: the agent never resolves a conflict silently – every conflict requires an explicit user choice. Non-conflicting settings are always auto-merged without prompting. Step 5 – Create the combined project The agent imports a fresh hello_world example for the same board – following the same import discovery chain and asking the user for appType – and uses it as the scaffold for the combined application. The default name is combined_ _ ; the user can accept the default or provide a custom name. The agent asks for both the project name and the appType for the scaffold before importing it. The agent confirms the combined project name and appType, then imports the fresh hello_world scaffold as the base for the merge.   The agent then applies the conflict resolutions chosen in the previous phase and auto-includes all non-conflicting configuration from every source example – every peripheral enable, Kconfig flag, alias, and memory region that was listed as auto-merged is added without further prompting.   Constraint: the agent never silently drops a setting a source example needed, and never adds settings that were not present in at least one source example. Step 6 – Merge sources The agent merges the application source from every example into the combined project so both functionalities run. It inventories each example's source files and CMakeLists.txt entries, then: Copies source and header files into the combined project, renaming collisions (e.g. main.c → app_blinky.c ) and prefixing any clashing symbols. Refactors each example's main() into a callable init/run function. Writes a combined main() that runs both workloads – using separate Zephyr threads if either example blocks or loops forever, cooperative calls if both are short. Merges CMakeLists.txt source lists, component dependencies, include directories, and linked libraries, removing duplicates. The merged main.c combines both workloads; prj.conf reflects the union of all required Kconfig settings.   Shared resources – console, GPIO, timers – are reconciled according to the conflict-resolution decisions from the previous phase. Both examples' output is routed to the single chosen console.   Step 7 – Build and verify The agent builds the combined project using the MCUXpresso for VS Code extension build tools ( buildProject / rebuildProject ). It monitors compile and link errors, iterates on fixes, and reports the final FLASH and RAM usage from the build output.   Build restriction: the agent never invokes cmake , ninja , make , or west build directly in a terminal. All builds, cleans, and rebuilds go exclusively through the MCUXpresso extension tools ( #buildProject , #cleanProject , #rebuildProject ). Running build commands in a raw terminal bypasses the extension's environment and toolchain configuration and will produce incorrect results.   After a successful build the agent provides a full summary: what was combined, the conflicts and their resolutions, the new project name and location, and how to flash the firmware to the target board.   Step 8 – Clean up Once the build succeeds, the agent asks what to do with the source examples used for combining. It never touches the combined project itself: A. Keep all source examples in the workspace. B. Remove all source examples from the workspace (with a separate confirmation for disk deletion). C. Choose per example – the agent asks about each one individually. The agent offers three cleanup options for the source examples and asks for explicit confirmation before any disk deletion.   For any removal the agent calls removeProject , asks a follow-up question confirming whether the files should also be deleted from disk, and then re-checks the workspace list to confirm the cleanup is complete.   Constraint: the agent never deletes files from disk without explicit user confirmation. The combined project is never offered for removal. Verifying the Result   The workflow is successful when all of the following hold: The verification gate passed: at least two examples, all sharing the same SDK type and the same board and core. All conflicts were resolved by explicit user choice; all non-conflicting settings were auto-merged. The combined project (e.g. combined_blinky_shell_module_hello_world ) appears in the workspace (confirm with listProjectsFromWorkspace ). The build completed without errors and produced a firmware artifact. The build summary reports the expected FLASH and RAM usage for both combined workloads. Source examples were handled per your chosen cleanup option Troubleshooting   Most issues fall into one of the categories below.   Symptom Likely cause Suggested action MCUXpresso tools not available The MCUXpresso tool set is not enabled in Copilot Chat Click Configure Tools in the bottom-left corner of the chat input, enable the MCUXpresso tool set, then restart the conversation. Verification gate fails – board mismatch Selected examples target different boards or core variants Re-import the mismatched example targeting the correct board, or replace it with a compatible one. Import did not register in workspace importExampleFromRepo succeeded but the project is not listed by listProjectsFromWorkspace The agent automatically falls back to importProject to register the on-disk folder. If this also fails, manually add the project folder via the MCUXpresso Projects view. Configure fails after import Board revision in CMakePresets.json uses the wrong case (e.g. @b instead of @B ) The agent detects and corrects the board revision in CMakePresets.json , cleans the build directory, and re-runs configure and build automatically. Build fails with stale CMake cache A previous failed configure left a partial build directory The agent cleans the build/ directory and re-runs configure before rebuilding. You can also delete the build/ folder manually and run configure again from the MCUXpresso terminal.   Examples
View full article
S32 Design Studio: Add FreeMASTER Lite Configuration to Existing UART Project using AI Introduction In Tutorial 2, the application was extended to cycle the FRDM-A-S32K312 board's RGB LED through red, green, and blue, while sending corresponding status messages to a serial terminal. This third article shows how to add a FreeMASTER Lite server configuration using S32 Design Studio AI Support to an existing UART project on the FRDM-A-S32K312 board and create a browser dashboard that displays the current LED color – replacing the plain UART color echo.   Estimated time: ~20 minutes. System Architecture Add FreeMASTER to existing UART project – system architecture overview   The components involved are:   FRDM-A-S32K312 – Target evaluation board. Runs the existing UART project extended with FreeMASTER TSA, streaming the LED colour variable to the host over USB at 115200 baud. Host PC – Runs FreeMASTER Lite (fmlite.exe) on the board's COM port, 115200 baud, port 8090. Serves the LED colour dashboard to the browser. Prerequisites   What you need before starting   Tutorial 2 completed — the GPIO Blinking LED Demo with UART must already be imported and building in S32 Design Studio One FRDM-A-S32K312 evaluation board + USB cable Download and install FreeMASTER Lite (fmlite.exe) from LINK  Any modern browser (Chrome / Edge / Firefox) S32 Design Studio AI Support configured in your agent (download, install and configure it following the instruction from Installation & Usage Guide)    Note: This tutorial uses these paths: S32 Design Studio Installation: C:\NXP\2026\K3_kit\S32DS_3.6.8 Workspace: C:\NXP\2026\K3_kit\workspace_S32DS_3.6.8_K3_kit FreeMASTER Installation: C:\NXP\2026\K3_kit\FM_32 You can use any location. If you do, update the paths in the prompt to match. Connect the FRDM-A-S32K312 board to the PC via USB, open Device Manager → Ports (COM & LPT) and note the virtual COM port number. You must know this port before sending the prompt below — replace every COM# in the prompt with your own port (for example COM7), otherwise FreeMASTER Lite cannot open the serial connection to the board. Steps   Send the following prompt to your AI assistant. It is a complete, self-contained instruction. Replace COM# with the COM port of your board before sending.   Step 1 – Create FreeMaster Lite dashboard and server configuration Using FreeMaster Lite create a self contained web dashboard and the server configuration file in the project folder called dashboard. FreeMaster Lite is installed at c:\NXP\2026\K3_kit\FM_32\FreeMASTER Lite\fmlite.exe The dashboard should have a volatile variable that will be used to reflect the color of the RGB LED At the top should have the controls for the board serial connection, default: connection name "S32K312 RGB Board", COM#, 115200 baud, 8 data bits, no parity, 1 stop bit The board is connected on COM# - use this serial port for the FreeMaster Lite connection The project is a plain GPIO demo with no FreeMASTER driver - add whatever is needed on the target side so it can talk to FreeMaster Lite, then build and flash it in S32DS and confirm the color actually changes from the dashboard. Start FreeMaster server and run the dashboard at the end Use the s32ds-agentic-ai MCP server; if the MCP server disconnects at any point, stop immediately and notify user. AI will:   Create a self-contained web dashboard in the dashboard project folder Create a FreeMASTER Lite server configuration file in the same folder Add a volatile variable to reflect the RGB LED colour in the dashboard Add serial connection controls at the top (name: S32K312 RGB Board, COM#, 115200 baud, 8N1) Start the FreeMASTER Lite server and open the dashboard in the browser Stop and notify the user immediately if the s32ds-agentic-ai server disconnects Verifying the Result   Work through this final check to confirm that the prompt completed successfully.   Final check FreeMASTER Lite server is running with no errors. Open http://localhost:8090 in your browser. The LED colour dashboard loads and shows the current LED colour within ~5 seconds. The displayed colour changes in sync with the physical LED on the board. Troubleshooting   Symptom Fix ReadTSA returns count=0 TSA not enabled (FMSTR_USE_TSA 1) or FMSTR_Poll() missing. StartComm times out Wrong COM port in .fmcfg, baud mismatch, or board not powered. fmlite.exe exits immediately Activation code not entered, or path has spaces — wrap in quotes. LPUART0 baud rate wrong or peripheral not running Open Peripherals Tool. Verify LPUART0 is enabled and its clock source is set to AIPS_PLAT_CLK. Regenerate code if you change anything. LPUART0 absent at runtime Open Peripherals Tool › McuPartition. Enable LPUART0 in the partition configuration, then regenerate. FreeMASTER host times out or drops connection FMSTR_Poll() must be called frequently — place it in the main loop or a fast periodic task. The host requires low-latency responses. LPUART6 interrupts conflict with FreeMASTER Open Peripherals Tool (Platform). Disable LPUART6 interrupts — FreeMASTER operates in polling mode and does not use interrupt-driven UART. File Reference     File Step Description dashboard/led_color.html 1 LED colour dashboard dashboard/board_115200.fmcfg 1 FreeMASTER Lite server configuration src/main.c 1 Firmware with FreeMASTER TSA and LED colour variable   Add the FreeMASTER Lite configuration and dashboard – watch your board's LED colour live in the browser in about 20 minutes. Examples
View full article
Coupon not valid for FRDM-MCXN236 NXP website advertises this free board to get started. But the coupon code returns invalid when applying at checkout. I feel NXP should honor current advertisements, or, take them offline. Development Board FRDM-Training Re: Coupon not valid for FRDM-MCXN236 Glad to hear that! You can submit the request as a hobbyist. A Does the button appear greyed out? If yes, could you please try logging in using an Incognito window in Chrome, a Private window in Firefox, or a different browser? Sometimes browser cookies can prevent the login process from working correctly. Please also try clearing your browser cache and cookies, then attempt to log in again. Let me know if the issue persists, and I'll be happy to help further. Best regards,  Alondra Re: Coupon not valid for FRDM-MCXN236 Thank you for the quick fix! Coupon works now. However, the checkout stage has several form entries like company name, url etc. Since I am a inidividual and intend to use the board for self learning, I have marked NA for these fields. Unfortunately the next button at end of the form does not respond. Re: Coupon not valid for FRDM-MCXN236 Thank you for contacting us. Could you please try again? We have updated the coupon, and you should now be able to use it successfully. Please let me know if the issue persists, and I will be happy to assist further. Best regards, Alondra Olvera Re: Coupon not valid for FRDM-MCXN236   It's not working for me either, may I know if it's still available or is their any other coupon code for the same ? Regards, Anukul Anand Re: Coupon not valid for FRDM-MCXN236 Hi, I ran into a similar promo error on checkout when applying regional codes. Usually, promo vouchers like ADCWFBXT are restricted by geographical region or distributor inventory allocations. If you are ordering from certain regions—such as developers connected through fiwfans - asia (fiwfan. app) or other local tech hubs—the NXP direct cart often flags the voucher as invalid due to regional shipping rules. The best solution is to open a direct support ticket with NXP Customer Care or contact your local regional distributor. They can either manually issue a regional promo code or release the order allocation for your account. Re: Coupon not valid for FRDM-MCXN236 Now it's back to invalid coupon. Re: Coupon not valid for FRDM-MCXN236 Greetings,  I tried all the steps you mentioned above, cleared the cookies and logged in through an incognito window on Chrome, yet it shows invalid coupon.  Would be glad to use this for my upcoming project so need some help with this coupon thing Thanks Re: Coupon not valid for FRDM-MCXN236 still facing the same probleme with the code "ATWQBE0T" Re: Coupon not valid for FRDM-MCXN236 Unfortunately, this coupon has already reached its usage limit. We will be removing the coupon in the next couple of days. We appreciate your understanding regarding this matter Best regards,  Alondra Re: Coupon not valid for FRDM-MCXN236 Hi NXP Support / Community Team, I am currently trying to purchase the FRDM-MCXN236 development board ($20.00 USD) through the NXP e-commerce store, but I am encountering an issue at checkout.   When attempting to apply the promo code ADCWFBXT, the cart displays an error stating: "Coupon is not valid." Could you please verify if this coupon code is currently active or if there are specific terms/conditions required to apply it to this development board? Any help to resolve this would be greatly appreciated. Thank you!
View full article
CLEV6630B評価ボード(OM26630FDK) 評価ボード(OM26630FDK)のPDfファイルCLEV6630B入手しましたが、カスタム設計で使うために同じAltiumのPCBファイルを入手できますか? Re: CLEV6630B eval board(OM26630FDK) こんにちは、 @R_Tony さん。 あなたの調子が良いといいのですが。 申し訳ありませんが、このデバイスで利用可能な設計ファイルはPDF形式の CLRC6630B回路図とレイアウトのみです。 ご迷惑をおかけして申し訳ございません。 よろしくお願いいたします。 エドゥアルド。
View full article
i.MX RT1176 – FlexIO2 并行接收:可实现的最大时钟移位是多少?仅达到约 48 MSPS iMXR1176 SDK 25.09.00 清单 3.15.0 目标 我正在从 i.MX RT1176 上的 LTC2164 16 位 ADC 获取数据。数据路径为: LTC2164(全速率CMOS输出)→ FlexIO2(并行接收)→ eDMA → 外部同步动态随机存取存储器(SDRAM) 硬件设置 LTC2164 配置为全速率 CMOS 输出模式,由外部 100 MHz 振荡器提供时钟信号(即 100 MSPS,16 位并行)。 ADC 数据输出 D0–D15 连接到 GPIO_AD_00 … GPIO_AD_15。 ADC CLKOUT+ 连接到 GPIO_AD_30,用作 FlexIO 定时器时钟(外部引脚时钟源)。 软件设置 FlexIO2 配置为并行接收器,数据锁存到移位器 7;移位器 7->0 串联起来,以便在 DMA 请求钳位之前缓冲 32 字节。 eDMA 由 kDmaRequestMuxFlexIO2Request0Request1 触发,使用两个 TCD 以乒乓(分散/聚集)模式运行。每次主循环完成时都会引发中断,即每 16384 个样本一次。 FlexIO2 功能时钟:120 MHz。 总线时钟(eDMA / SEMC 侧):240 MHz。 问题 在 100 MSPS 下,采集 16384 个样本需要163.84 µs 。通过测量两个连续 DMA 中断之间的时间(GPIO 切换 + 示波器),我始终得到338 µs ,即 ~2.06 倍。 这相当于大约48 MSPS的有效持续速率,这表明瓶颈在于 FlexIO 端,而不是 ADC 或 SDRAM。 问题 RT1176 上 FlexIO 在并行接收模式下是否有记录在案的最大移位时钟频率?我在参考手册或数据表中都找不到这样的数据。 当定时器时钟源为外部引脚时,FlexIO 功能时钟与外部移位时钟之间所需的比率是多少?我的 FlexIO 时钟 (120 MHz) 只是输入 100 MHz 时钟的 1.2 倍——这足够吗?还是输入同步逻辑需要 2 倍或 4 倍? 鉴于我观察到的几乎精确的 ×2 比率,这是否可能是由于 FlexIO 定时器在时钟的两个边沿递减(TIMCMP 约定)造成的,这意味着我的定时器比较值实际上将吞吐量减半? 任何关于 FlexIO + eDMA 在此部分上的最大实际持续吞吐量的指导都将非常有帮助,因为这决定了我是否需要迁移到不同的外设或外部 FIFO。 先行致谢。 通信与控制(I3C | I2C | SPI | FlexCAN | 以太网 | FlexIO) Re: i.MX RT1176 – FlexIO2 parallel receive: maximum achievable shift clock? Only ~48 MSPS reached 您好,谢谢您的回复。我确实达到了预期的性能,但这仅仅是通过超过 Flexio 外设的最大推荐时钟频率来实现的;具体来说,要达到 100 MSps 的采集速率,需要将时钟频率配置为 200 MHz 以上,而不是 120 MHz,而 120 MHz 的配置会导致时钟边沿丢失。问题是,即使它在 200 MHz 下工作(尽管参考手册规定最大频率为 120 MHz),我也无法保证在不同的温度条件下或不同生产批次之间可靠运行。 Re: i.MX RT1176 – FlexIO2 parallel receive: maximum achievable shift clock? Only ~48 MSPS reached 你好@azed38 , 请注意,当使用外部引脚作为时钟源时,会引入较小的同步延迟。根据 RM 第 67.3.3.2 节,此延迟范围为 0.5 至 1.5 个 FlexIO 时钟周期: Habib_MS_1-1788818202534.pngHabib_MS_1-1788818202534.pngHabib_MS_1-1788818202534.png 关于 FlexIO 和 DMA 可达到的最大吞吐量,目前还没有针对 FlexIO 和 DMA 的性能测试。不过,您可能会发现AN12686很有用,因为它演示了使用 FlexIO 和 DMA 的并行通信实现,这可能会为您的用例提供相关指导。 BR 哈比卜 Re: i.MX RT1176 – FlexIO2 parallel receive: maximum achievable shift clock? Only ~48 MSPS reached 你好@azed38 , 我注意到您已经通过其他渠道获得了关于此主题的支持,因此我们将继续通过该渠道提供支持,以保持所有沟通的集中化。我只想补充一点,如果 FlexIO 的运行频率超过其最大规格,可能会导致意外行为,从而影响您的最终应用程序。根据 RM 表 15-4“时钟根”中提供的信息,我建议使用最大频率 120 MHz。 BR 哈比卜 Re: i.MX RT1176 – FlexIO2 parallel receive: maximum achievable shift clock? Only ~48 MSPS reached 您好, 这个问题很可能是由于第 67.3.3.2 节中描述的引脚同步延迟造成的。参考手册中的“引脚同步”部分。 考虑到前面提到的设置,问题的根本原因是输入数据频率与 FlexIO 上的工作时钟频率之间的比率,这是由于该模块前面提到的引脚同步延迟造成的。 例如,由于存在引脚同步延迟,FlexIO 模拟外设(如 SPI 主控)只能以 FlexIO 工作时钟频率的四分之一的最大波特率运行。如 RM 第 67.4.3 节所述:“由于同步延迟,串行输入数据的建立时间为 1.5 个 FlexIO 时钟周期,因此最大波特率除以 FlexIO 时钟频率的 4。” 在这种情况下,吞吐量预计会降低,而且由于引脚同步延迟是 FlexIO 模块固有的特性,因此没有解决办法。 因此,为了确保正常运行,FlexIO 模块的最大工作频率为 120MHz,RT1170 无法达到预期的 100MSPS。 BR 哈比卜 Re: i.MX RT1176 – FlexIO2 parallel receive: maximum achievable shift clock? Only ~48 MSPS reached 鉴于我观察到的几乎精确的 ×2 比率,这是否可能是由于 FlexIO 定时器在时钟的两个边沿递减(TIMCMP 约定)造成的,这意味着我的定时器比较值实际上使吞吐量减半? 我只是想提一下,是的,FlexIO 定时器在由引脚或触发信号驱动时,对双边沿敏感。因此,如果你的外部信号包含一个上升沿和一个下降沿,你的定时器就会对其比较值进行两次计数。 另外,根据我目前使用 FlexIO 的经验,我猜测你只能处理频率不超过 FlexIO 时钟频率一半的外部信号。除此之外,它还能如何感知双面边缘?为了检测边沿,它需要在每个时钟周期内对外部引脚进行两次采样。
View full article
定时器触发DMA传输 你好, 我目前正在使用MCXN947微控制器。 我尝试通过 CTIMER 匹配中断触发 DMA 数据传输到采样缓冲区。 其思路是通过 DMA 每隔 x 个定时器间隔(具体来说是每隔 10 微秒)将 GPIO 寄存器的状态(具体来说是某些引脚的输入值)写入采样缓冲区。 我可以确认我的GPIO引脚已正确配置为输入。 我可以确认我的计时器工作正常,每 10 微秒触发一次比赛。 我可以确认我的 DMA 传输工作正常,因为缓冲区会被值填满。 我可以确认源地址(GPIO PDIR 寄存器)在 DMA 配置中已正确设置。 我可以确认我的目标地址在 DMA 配置中也设置正确,因为它始终位于缓冲区起始地址和结束地址之间(这意味着它可以正确递增和循环)。 但不知何故,错误的值被复制到了缓冲区中。我在调试器中看到,我尝试传输的寄存器的值为0x00020000 (引脚 17 为高电平,其余引脚为低电平)。但是,我的缓冲区只填充了0秒。这是一个 uint32_t 类型的缓冲区,包含 512 个元素,全部初始化为0xFF 。随着 DMA 传输的增加,整个缓冲区逐渐被0x0填充,而不是预期的0x00020000值(该值永远不会改变 - 引脚 17 始终为高电平)。 你知道这是什么原因造成的吗?或者我可能遗漏了什么? 以下是我的驱动程序配置: 计时器: CTIMER0 kCTIMER_Match_1 CTIMER0_IRQn(中断触发回调是可选的,但我为了调试目的在我的代码中使用它) DMA: DMA0 kDma0RequestMuxCtimer0M1 kINPUTMUX_Ctimer0M1ToDma0Ch8Ena EDMA_0_CH8_IRQn(中断触发回调是可选的,但我为了调试目的在我的代码中使用它) GPIO: GPIO3 端口3 引脚 17 以下是开始采样之前寄存器的状态。 reg_gpio3.pngreg_gpio3.pngreg_gpio3.pngreg_gpio3.png reg_port3.pngreg_port3.pngreg_port3.pngreg_port3.png reg_edma0_ch8.pngreg_edma0_ch8.pngreg_edma0_ch8.pngreg_edma0_ch8.png reg_inputmux0_dma.pngreg_inputmux0_dma.pngreg_inputmux0_dma.pngreg_inputmux0_dma.png reg_inputmux0_timer.pngreg_inputmux0_timer.pngreg_inputmux0_timer.pngreg_inputmux0_timer.png reg_ctimer0.pngreg_ctimer0.pngreg_ctimer0.pngreg_ctimer0.png             MCX N Re: Timer triggers DMA transfer 你好, 由于IP限制,我无法将我的整个项目发送给您。不过,我可以给你一个包含我的设置的小应用程序的 c 文件。GPIO、DMA 和定时器配置与我这边的相同。文件已附上。 Re: Timer triggers DMA transfer 你好@jabitbe2_jcplc 您能否与我们分享一下您的项目?我想尝试重现这个问题,并在我这边进行调查。 谢谢! 此致, 爱丽丝 Re: Timer triggers DMA transfer 你好@jabitbe2_jcplc MCXN947 支持 TrustZone 和网络安全归因控制。 如果访问源自与引脚安全配置不匹配的安全域,则对相应 GPIO 寄存器的读写操作可能无效。 请您确认 GPIO3 引脚 17 对应的位是否配置为允许非安全访问,并再次进行测试? 如果该位当前配置为仅安全,则意外的 GPIO 行为可能与 TrustZone 安全设置有关。 谢谢! BR 爱丽丝
View full article
[i.MX8MM] DDR PHY 训练固件日志级别:“最大调试”值并集成到 U-Boot 中 尊敬的恩智浦技术支持团队: 我们目前正在使用 MSC DDR 工具/DDR 测试工具调试我们定制的 i.MX 8M Mini 平台上的 DDR 训练问题,并希望澄清 PHY 日志级别配置。 1. 关于配置值 在 DDR 工具 GUI 中, “PHY 日志级别”下拉菜单包含以下选项: 固件已完成 断言消息 阶段完成 粗略调试 详细调试 最大调试 我们检查生成的 .ds 文件。我们注意到脚本中包含一些关于 TrainInfo 设置的注释: # 以下内容仅供工厂内部使用,强烈建议不要更改。 ddrparam 设置 TrainInfo 0x04 # 0x05 = 详细调试(例如眼部延迟) # 0x0A = 粗略调试信息(例如排名信息) # 0xC8 = 阶段完成 # 0xC9 = 断言消息 # 0xFF = 固件完成 # 其他 = 已预留 我们希望直接在 U-Boot SPL 中配置此 PHY 日志详细程度,以便在启动初期通过 UART 捕获完整的训练日志。 2. 将 PHY 日志级别移植到 U-Boot / SPL (lpddr4_timing.c) TrainInfo 日志详细程度参数能否在 DDR 时序结构中定义(例如,在 lpddr4_timing.c 或 SPL 中的 DDR PHY 初始化序列中)? 如果可以,能否请您指导我们如何将 `ddrparam set TrainInfo 0x04` 正确地集成到我们的 U-Boot 代码库中?如果您能指出 lpddr4_timing.c (或 PHY 消息块)中应该映射此参数的具体结构或寄存器,我们将不胜感激。 谢谢你的帮助。 Re: [i.MX8MM] DDR PHY Training Firmware Log Level: Value for "Maximal Debug" and Integrati 你好, Train Info 是一个 PHY 固件参数,通常不是 LPDDR4 时序结构的一部分。我不会直接添加 0x04。 Re: [i.MX8MM] DDR PHY Training Firmware Log Level: Value for "Maximal Debug" and Integrati 你好, 感谢您的回复。 在最近的测试中,我们需要使用以下PHY固件参数启用DDR训练调试信息: ddrparam 设置 TrainInfo 0x04 能否指导我们如何将此命令转换为 U-Boot SDK 中的 C 代码或将其集成到 U-Boot SDK 中(例如,特定的驱动程序结构、API 或配置定义)? 多谢。
View full article
Regarding IMX-LVDS-HDMI Dear Technical Support Team, We are evaluating your IMX-LVDS-HDMI for use in a monitoring setup for a medical device. Our medical device uses an LCD panel with an LVDS interface. We would like to tap the LVDS signal and convert it to HDMI so that the display output can be monitored on a separate PC/monitor without affecting the original display operation. The LCD panel we are using is: Display: TDT25060AA00 Resolution: 1024 × 768 (XGA) LVDS: 1-port LVDS These parameters are taken from the attached display datasheet. Before purchasing and testing the converter, we would like to clarify whether your board is technically suitable for this application. Could you please confirm the following: LVDS input compatibility Does your converter support single-channel / 1-port LVDS, 1024×768, 8-bit RGB? Pixel-clock frequency Our display specifies an LVDS pixel clock of 52–71 MHz (65 MHz typical). Is this entire frequency range supported by your LVDS receiver? LVDS timing Can the converter correctly receive the following typical timing? H active: 1024 pixels H total: 1344 clocks V active: 768 lines V total: 806 lines Refresh rate: approximately 60 Hz Spread Spectrum Clocking (SSC) Does the LVDS receiver support an LVDS pixel clock with Spread Spectrum Clocking (SSC)? If yes, could you please specify the supported SSC modulation depth and frequency range? Recommended configuration If this converter is compatible with our display, could you please provide the recommended configuration/settings for: 1024×768 1-port LVDS VESA 8-bit RGB We would like to determine whether this converter can provide a stable and reliable HDMI representation of our 1024×768 LVDS display signal for monitoring on another PC, without changing the original display signal. The datasheet is attached for reference. Thank you in advance for your technical support. We would appreciate confirmation of compatibility before we proceed with purchasing and testing the board. Best Regards,  Re: Regarding IMX-LVDS-HDMI Hello there, Good morning. Thank you for the quick feedback. So if we replace the mini SAS connector at the front to one suitable to our board, it can be used to monitor LVDS signal on the PC using HDMI? Thank you Re: Regarding IMX-LVDS-HDMI Hello, Please note that this adapter card is meant to be used as an LVDS to HDMI connector for i.MX boards, since it uses a mini SAS connector on the LVDS Connector side, so please make sure that it is compatible with your board. Regarding all the other features one, can have a look to the actual chip being used as the converter: https://www.ite.com.tw/en/product/cate1/IT6263 Best regards/Saludos, Aldo. Re: Regarding IMX-LVDS-HDMI Hello, Is not as easy as a plug and play adapter, as the chip being used needs to be configured using I2C which is part of the bus in the mini SAS connector, and it must be defined on your device tree as well. it is not a convencional LVDS to HDMI converter, this I why I have shared the actual chip being used so you may have a look on how it works. Best regards/Saludos, Aldo.
View full article
S32K3 ADC 外部チャネルの利用 こんにちは。NXPチーム S32K3 ADCの外部チャネルの使い方 . Re: S32K3 ADC Use of external channels こんにちは、 @VaneBさん これに関して、追加の質問があります。 もし私のデザインにマルチマックスがなくても、例えばセンサ1にADC1_X[0]、センサ2にADC1_X[1]、そしてADC1_Xセンサ3にだけ使いたい場合は、MAピンをGPIO出力ピンなど他の用途で再利用してLEDを駆動することは可能でしょうか? 私のデザインはs32k344をベースにしています Re: S32K3 ADC Use of external channels NPXチームの皆様、こんにちは。 このトピックに関連して、以下の図のようなSCHを実装することが可能かどうか確認していただけますか? サポートありがとうございます。 Re: S32K3 ADC Use of external channels @VaneB ご協力いただき、誠にありがとうございました。 Re: S32K3 ADC Use of external channels こんにちは@Niuyanlin 各ADCは外部アナログ多重化器の8チャネル中1チャネルを選択するために使う3つの外部デコード信号(MA)を提供し、最大4つのマルチプレクサを設置して32の外部チャネルを接続できます。つまり、これら4つのマルチプレクサは同じMA信号を共有します。 ADCは変換対象の現在のチャネルに基づき、これらの外部アナログ多重化器を制御するよう自動設定します。マスクレジスタのビットに応じて、対応する「X」ピンがサンプリングされ、その結果が「MA」と「X」の組み合わせに対応する場所に格納されます。 当社の開発ボードには外部アナログ多重化装置が設計されていないため、そのような例は実装されていません。 Re: S32K3 ADC Use of external channels こんにちは。ヴェインB あなたのプロンプトによると、RTDで外部チャネルADCを使った例が見つかりません。もし対応するルーティンがあれば、ぜひ送っていただけると嬉しいです。どうもありがとうございます。 Re: S32K3 ADC Use of external channels こんにちは@Niuyanlin RTDで役立つかもしれないADCの実装例が見つかります。 BR VaneB
View full article
MC33774 Daisy Chain Dual Loop Connection HI. I'm currently using an AFE sampling system with MC33665A and MC33774 to form a double-chain loopback structure. The MC33665A's PORT0 and PORT1 are configured as MADD0 and MADD1 respectively, and all commands are currently sent via MADD0. When I only connect the daisy chain between PORT0 and DC1, my communication is normal. However, when I also connect the daisy chain between PORT1 and DC2, I find that the 33774 cannot reply with a response frame. Why is this? I have confirmed that the PORT configuration of the 33665 is correct and that SYS_TPL_CFG.RESPCFG in the 33774 is set to 00 SAME mode. I am currently using an AFE sampling system consisting of the MC33665A + MC33774 in a dual-ring loop configuration. I have configured PORT0 and PORT1 of the MC33665A as MADD0 and MADD1, respectively, and all commands are currently sent through MADD0. When I connect only the daisy chain between PORT0 and DC1, communication works correctly. However, after I also connect the daisy chain between PORT1 and DC2, the MC33774 no longer responds when I send requests to it. Why does this happen? I have read back and verified that the MC33665 PORT configuration is correct, and I have configured SYS_TPL_CFG.RESPCFG = 00 (SAME mode) in the MC33774. Re: MC33774 Daisy Chain Dual Loop Connection HI. 1. I want to know if it is necessary to reverse the allocation of DADD from the position where MADD=1? 2. My current SYS_PORT0_CFG configuration is TIMEOUT=0, CADD=1, MADD=0, PROTOCOL=1, ALLCHAINS=1, TERM=1, RX=1, EN=1 SYS_PORT1_CFG is configured with TIMEOUT=0, CADD=1, MADD=1, PROTOCOL=1, ALLCHAINS=1, TERM=1, RX=1, EN=1 Re: MC33774 Daisy Chain Dual Loop Connection Hello, According to the AN13910 TPL Loopback Recommendation, when two MC33665A TPL ports are connected as a loopback ring, there are several configuration requirements that may cause the behavior you are seeing. For a loopback configuration: We recommend assigning device addresses (DADD) in ascending order from one side of the ring and in reverse order from the loopback side (I do not see this in your image). If two ports are connected as loopback, one of the ports should have SYS_PORTx_CFG[RX] = 0 to avoid duplicate data entering the MC33665 buffer. In addition, one of the ports should have SYS_PORTx_CFG[ALLCHAINS] = 0. If both loopback ports accept ALLCHAINS commands, document states that this can cause signal conflicts and communication errors. Could you please share the values of SYS_PORT0_CFG and SYS_PORT1_CFG (especially EN, RX, ALLCHAINS, MADD, and CADD)? That would help determine whether the loopback ports are configured according to the AN13910 recommendations. Re: MC33774 Daisy Chain Dual Loop Connection Hello, According to AN13910 TPL Loopback Recommendation, the DADD assignment should be reversed from the MADD=1 side in a loopback topology. In addition, your current configuration has RX=1 and ALLCHAINS=1 on both ports. For a loopback connection, we recommend disabling RX and ALLCHAINS on one of the ports to avoid duplicate routing and communication conflicts.  Could you please try configuring one port with RX=0 and ALLCHAINS=0 (for example, PORT1) and verify whether the MC33774 starts returning response frames? Re: MC33774 Daisy Chain Dual Loop Connection This seems like a sub optimal solution. We would like to have a loop between the two ports on a 6402 with multiple 7418 CMUs and an 8420 BJB in the loop.  It would be nice to read the CMUs through port 0 and the BJB (and in extreme cases the higher CMUs) through port 1 with MADD=1.. if we need to reprogram the RX enables on both ports each time we want to read from the other end of the loop this seems rather inefficient.  Why can’t the MADD bit in the read request handle disabling the far side RX automatically?
View full article
FreeMASTER 3.2.7 Update - Release Announcement Version 3.2.7 of the NXP FreeMASTER tool has just been published online.  This version is backward compatible and fully replaces older 3.2.x releases (see previous announcements). It brings new features and bugfixes described below. The updated installer is available along with documentation and other resources at http://www.nxp.com/freemaster.   Release description FreeMASTER is a powerful data visualization tool developed and provided by NXP to help users monitor and control embedded applications running on NXP’s targets. It works with almost all NXP Arm ® Cortex®-M and other microcontrollers from both Edge Processing and Automotive business lines as well as with DSC and legacy Power Architecture, ColdFire and HCS12/Z platforms. Note that the license terms and conditions does not allow using FreeMASTER with non-authorized systems from other vendors. Version 3.2.7 is a minor update of the 3.2.x mainline release. It overwrites the previous 3.2 version installed on the host computer. Older 2.x, 3.0, and 3.1 versions are not removed; however, the communication plug-ins installed with the latest version are globally registered in the operating system and will also be used by older versions. This version is backward compatible with all previous versions. It supports variable monitoring, oscilloscope real-time graphs, fast transient recorder graphs, array-to-graph views, and connectivity to third-party applications. It includes two Chromium-based HTML rendering engines—CEF and Microsoft Edge WebView2—with full support for JSON-RPC, HTML5, and JavaScript to create custom dashboards and other user interfaces running inside FreeMASTER. The older Internet Explorer rendering engine, with the ActiveX interface and protocol defined for version 2.x, is also still supported. FreeMASTER Lite, which is part of the FreeMASTER installation package, provides the communication core for Windows and Linux systems. It is accessible similarly to the FreeMASTER desktop application over the JSON-RPC interface. FreeMASTER Lite also embeds the popular Node-RED framework for graphical programming and provides many examples of its use with the FreeMASTER tool. More information related to Node-RED can be found in the dedicated training video. FreeMASTER Node.js Installable Modules enable convenient use of the FreeMASTER JSON-RPC components in a Node.js applications managed by the ‘npm’ package manager. Version 3.2.7 contains FreeMASTER Lite and Node.JS modules internally referred as version 1.4. Installing FreeMASTER Lite will require you to enter an activation code generated for this version. Get your free code on the License Keys tab at the license information page. New Features Version 3.2.7 introduces the following new features: P&E Micro debugging probes support updated This version includes the latest update of P&E Micro drivers, enabling JTAG communication with the newest NXP microcontrollers. Chromium browser component updated The Chromium browser has been updated to the most recent version, addressing several incompatibility issues and re-enabling the JScript debugger and other DevTools within FreeMASTER. ELF/DWARF parser extended  ELF file parser has been extended to locate static variables inside C++ anonymous namespaces. Bugfixes and other extensions: FreeMASTER Fixed "Show-As" style of floating point variables generated automatically from ELF symbols. Fixed CAN communication plug-in issue in its Configuration dialog. Fixed PD-BDM communication plug-in timing during initial connection to target. Fixed ELF file selection after forcing its file path by external script SetProjectOptions(). Fixed CEF and Edge web browser components to enable cross-origin content loading from file: resources. Fixed project corruption when deleting variable assigned to X-Axis in an XY graph. Related Content NXP MCUXpresso SDK For consumer, industrial or IoT edge applications, the FreeMASTER communication driver is distributed as a "middleware" component of MCUXpresso SDK. The driver sources are publicly available on GitHub along with documentation. The most convenient way to get a full SDK package including FreeMASTER and other middleware components is via the MCUXpresso SDK Builder. The full SDK is also available on GitHub. S32 Design Studio for S32 Platform For automotive parts, the FreeMASTER communication driver is distributed as an eclipse update site for S32 Design Studio. Latest versions can be installed directly from within the IDE by accessing "S32DS Extension and Updates" from "Help" menu. Additionally, it can be downloaded both as eclipse update site and a stand-alone zip archive via the Flexera Links available on FreeMASTER's home page. The distribution already includes ready to use examples. More advanced applications and demos are available on NXP's Application Code Hub (ACH). Zephyr sample applications FreeMASTER sample applications for Zephyr demonstrate Zephyr logging and shell running over FreeMASTER pipe as well as runtime visualization of Zephyr thread information, CPU utilization and stack usage. Thread performance data can be displayed in common graphs with application-specific data making it great runtime tuning tool. Release target audience Both FreeMASTER and FreeMASTER Lite are primarily targeted to our customers, engineers and developers of NXP embedded applications from Industrial, IoT and Automotive areas who want to monitor and control their applications at runtime. FreeMASTER is also a strong framework which can be used to create interactive demos and user interfaces helping to use the embedded applications by yet wider target audience. Prerequisites FreeMASTER tools run on the host computer and communicates with the target microcontroller application using Serial, CAN, Ethernet/WiFi network, JTAG, BDM or other physical interface. The microcontroller communication drivers are available as part of MCUXpresso SDK, S32 Design Studio or as a standalone installation package. Get familiar with the communication protocol and the microcontroller driver API before using the FreeMASTER tool. License terms and conditions permit use of FreeMASTER solely with systems based on NXP microprocessor or microcontroller systems. Packages A single self-extracting installation package which contains both FreeMASTER desktop application and the new FreeMASTER Lite service is available for Windows platforms. JTAG/ BDM Serial CAN TCP/IP Segger RTT FreeMASTER Desktop app. x86 for Windows ✓ ✓ ✓ ✓ ✓ Separate packages are available for FreeMASTER Lite containing x64 binaries for Windows & Linux platforms with the following supported communication interfaces. JTAG/ BDM Serial CAN TCP/IP Segger RTT FreeMASTER Lite x64 for Windows ✓* ✓ ✓ ✓ ✓ FreeMASTER Lite x64 for Linux ✗ ✓ ✗ ✓ ✗ *Requires 64 bit version of the 3 rd  party library. Tested with Segger (JLink_x64.dll). Access the installation and documentation at the FreeMASTER home page at https://www.nxp.com/freemaster.
View full article
S32K388 LPSPIのSCKDIV計算に関する質問 - 1MHzのボーレートでSCKDIV=38になるのはなぜですか? こんにちは、NXPコミュニティの皆さん、 私はS32K388を使用してLPSPIのボーレートを設定しています。SCKDIVの値の計算について質問があります。 **私の理解:** S32K3xxリファレンスマニュアルによると、LPSPIのボーレートの公式は以下の通りです: ``` SCK = LPSPI_CLK / (PRESCALE_DIV × (SCKDIV + 1)) ``` **私の設定:** - LPSPIクロックソース:AIPS_SLOW_CLK = 40 MHz 目標ボーレート:1MHz - プリスケール = 0 (÷1) **私の計算:** 「`」 SCKDIV = (LPSPI_CLK / Baud) - 1 SCKDIV = (40 MHz / 1 MHz) - 1 = 39 「`」 **S32DS生成コード:** しかし、S32DSを使用して構成を生成すると、次のようになります。 「`c」 LPSPI_CCR_SCKDIV(38U) // SCKDIV = 38 「`」 **質問:** SCKDIV=38の場合、実際の除算係数は39となり、これは次のことを意味します。 「`」 実際のボーレート = 40 MHz / 39 = 1,025,641 Hz ≈ 1.026 MHz 「`」 これは目標値である1MHzから約2.56%の誤差がある。 S32DSはなぜSCKDIV=39ではなくSCKDIV=38を使用するのですか?S32DS構成では、異なるLPSPIクロック周波数が使用されているのでしょうか?それとも、この選択には別の理由があるのでしょうか? **追加の背景:** - 私はS32DS 3.5を使っています - S32K388リファレンス・マニュアル Rev. 6 - プロジェクトはデフォルトのクロック構成で作成されました ご説明いただければ幸いです。よろしくお願いいたします。 よろしくお願いいたします。 Re: S32K388 LPSPI SCKDIV calculation question - why SCKDIV=38 for 1MHz baud rate? こんにちは、 @xlele まず、S32K3xxリファレンスマニュアルの最新版はRev. 12であることにご注意ください。現在ご利用の改訂版には、S32K310、S32K311、およびS32K3x8デバイスに関する予備情報が含まれていますが、これらのデバイスは当該文書の発行時点ではまだリリースされていませんでした。したがって、RMの最新版をダウンロードして参照することをお勧めします。 LPSPIのボーレート計算に関して、クロック構成レジスタ(CCR)のSCKDIVフィールドの説明には次のように記載されています。 ボーレート = 機能クロック ÷ (2^PRESCALE × (SCKSET + SCKHLD + 2)) ここで、SCKSETとSCKHLDはSCKDIV÷2から導出される。 SCKDIV = 38 であることを考慮すると、次のようになります。 SCKSET = SCKHLD = 38 ÷ 2 = 19 ボーレート = 40 MHz ÷ (2^0 × (19 + 19 + 2)) = 1 MHz となり、これは期待値と一致します。 BR、VaneB
View full article