Connecting LCD_PAR_S035 to the U-blox IRIS-W1 EVK Using the 8080 8-bit Interface The LCD_PAR_S035 can be interfaced with the U-blox IRIS-W1 EVK using the 8080 8-bit parallel interface. Enabling this configuration requires a combination of GPIO routing, jumper wiring, and two resistor population changes on the EVK. The reason for this additional wiring is that the signals required by the LCD's 8080 interface are distributed across multiple expansion connectors on the EVK. Additionally, the CS (Chip Select) and DC (Data/Command) signals are not routed by default to the required GPIOs and must be reassigned through resistor rework. Without these modifications, the LCD controller cannot be properly controlled by the IRIS-W1 device when operating in 8080 parallel mode.   Signal Mapping The following GPIO assignments have been verified for operation with the LCD_PAR_S035:   GPIO56 -> CS Available on J48 after removing R263 and populating R264 GPIO57 -> DC Available on J48 after removing R265 and populating R266 GPIO54 -> WR Available on J43 by default GPIO48 -> RD Available on J44 by default GPIO44 -> RST Available on J3 by default GPIO45 -> TE Available on J4 by default GPIO53 -> D7 Available on J43 by default GPIO52 -> D6 Available on J44 by default GPIO51 -> D5 Available on J43 by default GPIO49 -> D4 Available on J43 by default GPIO47 -> D3 Available on J43 by default GPIO46 -> D2 Available on J48 by default GPIO43 -> D1 Available on J4 by default GPIO42 -> D0 Available on J3 by default GPIO17 -> I2C_SCL Available on J47 by default GPIO16 -> I2C_SDA Available on J10 by default Required Hardware Rework Two routing modifications are required to expose the LCD control signals through the desired GPIOs: CS Signal Routing:   Remove : R263 Populate : R264  DC Signal Routing: Remove : R265 Populate : R266 Populate:   Remove: LCD Configuration The LCD module must be configured for 8080 8-bit parallel mode before power-up. The interface selection switch located on the back of the LCD_PAR_S035 should be set to: 110     Incorrect switch settings will prevent communication between the display controller and the IRIS-W1. Software Configuration After completing the hardware setup, any compatible LVGL example from the SDK can be used as a starting point. The selected project must use a flash configuration that matches the flash device populated on the target hardware. Reference flash configurations are available in the following repository: https://github.com/u-blox/u-blox-sho-OpenCPU/tree/master/MCUXpresso/IRIS-W1/sw_config/flash_config Reference Design Files Additional information regarding connector locations, GPIO routing, resistor options, and board-level implementation can be found in the EVK design package: https://github.com/u-blox/evk_designs_sho_altium/tree/main/EVK-IRIS-W10/Deliverables Summary Enabling the LCD_PAR_S035 on the U-blox IRIS-W1 EVK through the 8080 8-bit interface requires: Configuring the display for 8080 8-bit mode (switch setting 110 ). Reworking resistor populations for CS and DC routing. Connecting the LCD control and data signals according to the GPIO mapping listed above. Selecting the appropriate flash configuration for the target hardware. Using an LVGL-based application to validate display operation. This configuration provides direct access to the LCD through the parallel interface and serves as a useful reference for graphics evaluations and GUI development on the IRIS-W1 platform. Results: FRDM-RW612

8MNANOLPD4-EVK 的 Altium 文件或 MIMX8MN6CVTIZAA 的原理图符号/封装 您好， 我能否获得最新的 Altium 项目文件，或者可以导入 Altium 的格式文件？ 顺祝商祺！ 8MNANOLPD4-EVK MIMX8MN6CVTIZAA Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA 你好，以色列， 我可以获取可导入到 Altium 的电路板文件吗？ 此致， 糟糕。 Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA 你好@Stefano_Allegri ， 您应该提交一个工单，请使用以下链接： https://support.nxp.com 此致， 以色列。 Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA 你好，以色列， 我将开发一款新板，并以 8MNANOLPD4-EVK 作为参考设计，请问如何获取该板的 Altium 文件（原理图和布局图）？ Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA 嗨@Sal2020 ， 我已将文件直接发送到您的邮箱。 此致， 以色列。

RW612 的 32.768kHz 晶体 你好， 我目前正在进行一个PCB设计项目，其中包括来自u-blox的IRIS-W10模块，该模块内部有一个RW612芯片。这是我第一个使用恩智浦MCU的设计。 我不太确定应该如何设计RTC外部晶振的电路。根据其他MCU（例如STM32）的经验，我知道它们需要在晶振的两个引脚上都连接一个外部负载电容。但对于 NXP MCU 来说，似乎有些型号具有内部可配置的负载电容。在 RW612 寄存器列表中，我偶然发现了 RTC CTRL 寄存器，特别是字段 RTC_OSC_LOADCAP。在我看来，这表明该 MCU 实际上具有内部负载电容，但我找不到任何关于此领域的文档。 所以我的问题是：要在该寄存器中设置一个特定的电容值，位格式是什么？ 产品：WiFi RW6XX

工具在 VS Code 中安装失败 您好，NXP， 我尝试在 VS Code 中安装配置工具和安全配置工具，但都失败了。 您能帮忙检查一下并提供一些修复建议吗？ 非常感谢。 VS Code 版本：1.120.0 回复： Tools are failed to install in VS Code 嗨，哈里， 知道了。 谢谢 。 回复： Tools are failed to install in VS Code 嗨@jimmyli 作为替代方案，我建议分别下载并安装 MCUXpresso 配置工具和 MCUXpresso 安全配置工具。 请使用Windows系统的默认安装路径安装这两个工具。安装完成后，重启 VS Code。这样一来，MCUXpresso for VS Code 扩展程序应该能够自动检测已安装的工具，从而有助于避免您目前遇到的安装/检测错误。 MCUXpresso 配置工具 | 面向恩智浦微控制器 (MCU) 的软件开发 | 恩智浦半导体 MCUXpresso 安全配置工具 | 恩智浦半导体 BR 哈里

QEMU support for S32 series boards I am looking to use qemu to speed up ci/cd and testing for S32 automotive processors for a project. I am having trouble getting the SDK access.  2 questions: 1. is this allowed? I can't figure out if they want me to sign NDAs or whats the process. 2. whether its allowed or not how can I get an SDK? seems to be public but also blocked?? which seems counter intuitive to getting a hassle for the process of making accounts to acess this and won't tell me what I need. Re: QEMU support for S32 series boards Hello, @enough_ahnaf  Thanks for your reply. I have the following suggestions for your issue: 1. If you have any contact information with NXP repsentative,  you can reach out to them to request access 2. If not, you may create a support case via support.nxp.com to obtain further support. BR Chenyin Re: QEMU support for S32 series boards I don't even have that category. That's what I have been wanting to find out why? Seems its different access not public? Re: QEMU support for S32 series boards Hello, @enough_ahnaf  Thanks for your reply. You may try applying S32N5 SDK via the following URL BR Chenyin Re: QEMU support for S32 series boards S32 N5 SDK Re: QEMU support for S32 series boards Hello, @enough_ahnaf  Thanks for the post. May I know which SDK you were referring to? S32G or other SOC? BR Chenyin

Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA Hi, Could I get the last Altium project files or the files in a format importable into Altium? Best Regards, 8MNANOLPD4-EVK MIMX8MN6CVTIZAA Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA Hi Israel, Can i get the files of the board that is importable to altium. Regards, Dangy. Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA Hi @Stefano_Allegri, You should open a ticket use the next ticket: https://support.nxp.com Regards, Israel. Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA Hi Israel, i will developper a new board and i will use 8MNANOLPD4-EVK for referance designe, how can i get the altium files of the board (schematics and layout)? Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA Hi @Sal2020, I sent you the files directly to your mail. Regards, Israel.

QEMU对S32系列板卡的支持 我正在考虑使用 qemu 来加速 S32 汽车处理器的 CI/CD 和测试，用于一个项目。我无法获取SDK访问权限。 两个问题： 1. 这样做可以吗？我搞不清楚他们是不是要我签保密协议，也不知道具体流程是什么。 2. 无论是否允许，我该如何获取 SDK？它似乎是公开的，但又被屏蔽了？这似乎与创建帐户以访问它的过程相矛盾，而且它也不告诉我需要什么。 Re: QEMU support for S32 series boards 你好， @enough_ahnaf 谢谢你的回复。 针对您的问题，我有以下建议： 1.如果您有恩智浦代表的联系方式，您可以联系他们申请访问权限。 2. 如果以上方法均无效，您可以通过 support.nxp.com 创建支持案例以获得进一步支持。 BR 陈银 Re: QEMU support for S32 series boards 我甚至没有这个类别。我一直想知道为什么？似乎访问权限不一样，不是公开的？ Re: QEMU support for S32 series boards 你好， @enough_ahnaf 感谢您的回复。 您可以尝试通过以下URL应用 S32N5 SDK BR 陈银 Re: QEMU support for S32 series boards S32 N5 SDK Re: QEMU support for S32 series boards 你好， @enough_ahnaf 感谢分享。 请问您指的是哪个SDK？S32G 或其他 SoC？ BR 陈银

RW612用32.768kHz水晶発振子 こんにちは、 現在、u-bloxのIRIS-W10モジュールにRW612を内蔵したPCB設計プロジェクトに取り組んでいます。これはNXP MCUを使った初めてのデザインです。 RTC外部クリスタルの回路設計方法が迷っています。STM32などの他のMCUでは、水晶発振器のピン両方に外部負荷コンデンサが必要であることがわかっています。しかし、NXPのMCUの中には、内部で設定可能な負荷容量を備えているものもあるようだ。RW612レジスタリストで、RTC CTRLレジスタ、特にRTC_OSC_LOADCAPフィールドを見つけました。これはこのMCUに内部負荷上限があることを示していますが、この分野に関するドキュメントは見つかりませんでした。 SO 質問ですが、このレジスタで特定のコンデンサ値を設定するためのビットフォーマットは何でしょうか? 製品: WiFi RW6XX

32.768kHz Crystal for RW612 Hello, I'm currently working on a PCB design project that includes an IRIS-W10 module from u-blox with an RW612 inside. This is my first design with an NXP MCU. I'm unsure, how I should design the circuit for the RTC external crystal. From other MCUs like STM32 I know they need an external load capacitor on both of the crystal pins. But for NXP MCUs it seems that some have internal configurable load caps. In the RW612 register list I stumbled upon the RTC CTRL register and in particular the field RTC_OSC_LOADCAP. To me this indicates that this MCU has in fact internal load caps, but I couldn't find any documentation on this field. So my question is: What is the bit-format to set a specific capacitor value in this register? Product: WiFi RW6XX

S32シリーズボードに対するQEMUサポート プロジェクトのために、S32 車載プロセッサのCI/CDやテストを高速化するためにQEMUを利用したいと考えています。SDKへのアクセスに問題があります。 2つの質問： 1. これは許可されていますか？NDAにサインしてほしいのか、それとも手続きがどうなのか分かりません。 2. 許可されているかどうかは、どうやってSDKを入手すればいいのか?公開されているのにブロックされているように見えます。これはアカウント作成の手続きに面倒がかかるのは直感に反しているように思えますし、必要なものも教えてくれません。 Re: QEMU support for S32 series boards こんにちは、 @enough_ahnaf ご返信ありがとうございます。 あなたの問題に対して、以下の提案があります。 1.もしNXP担当者のお問い合わせをお持ちであれば、アクセスを申請するために連絡を取ることができます 2. そうでない場合は、support.NXP.com を通じてサポートCASEを作成し、さらなるサポートを得ることができます。 BR チェイン Re: QEMU support for S32 series boards 私にはそのカテゴリーすらありません。それがずっと知りたかったことだよ、なぜ?アクセスが違うみたいで、公開されていない? Re: QEMU support for S32 series boards こんにちは、 @enough_ahnaf ご返信ありがとうございます。 以下のURLからS32N5 SDKを適用してみてください BR チェイン Re: QEMU support for S32 series boards S32 N5 SDK Re: QEMU support for S32 series boards こんにちは、 @enough_ahnaf 投稿ありがとうございます。 どのSDKsのことを言っているのか教えてもらえますか?S32Gまたは他のSoC？ BR チェイン

8MNANOLPD4-EVK の Altium ファイル、または MIMX8MN6CVTIZAA の回路図シンボル/フットプリント こんにちは、 最後のAltiumプロジェクトのファイルや、Altiumにインポート可能な形式のファイルを入手できますか? よろしくお願いいたします。 8MNANOLPD4-EVK MIMX8MN6CVTIZAA Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA こんにちは、イスラエルさん。 Altiumにインポート可能なボードのファイルを入手できますか? よろしくお願いいたします。 危険だ。 Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA こんにちは、 @Stefano_Allegri さん。 チケットを開いてください。次のチケットを使用してください： https://support.nxp.com よろしくお願いいたします。 イスラエル。 Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA こんにちは、イスラエルさん。 新しい基板を開発し、参照設計に8MNANOLPD4-EVKを使う予定ですが、基板のAltiumファイル(回路図とレイアウト)はどうやって入手できますか? Re: Altium files for 8MNANOLPD4-EVK or Schematic Symbol/Footprint for MIMX8MN6CVTIZAA こんにちは、 @Sal2020 さん。 ファイルを直接あなたのメールアドレスに送信しました。 よろしくお願いいたします。 イスラエル。

Tools are failed to install in VS Code Hi NXP,       I am trying to install config tool and secure provisioning tool in VS Code, but they are all failed.       Can you help to check and provide some tips to fix ?       Thanks very much.       VS Code ver: 1.120.0 回复： Tools are failed to install in VS Code Hi Harry,       Got it.       Thanks . 回复： Tools are failed to install in VS Code Hi @jimmyli  As a workaround, I would suggest downloading and installing the MCUXpresso Config Tools and MCUXpresso Secure Provisioning Tool separately. Please install both tools using their default installation paths on Windows. After the installation is complete, restart VS Code. The MCUXpresso for VS Code extension should then be able to detect the installed tools automatically, which should help avoid the installation/detection errors you are currently seeing. MCUXpresso Config Tools | Software Development for NXP Microcontrollers (MCUs) | NXP Semiconductors MCUXpresso Secure Provisioning Tool | NXP Semiconductors BR Harry

VS Code でツールのインストールに失敗しました こんにちは、NXPさん。 VS Code に構成ツールとセキュアプロビジョニングツールをインストールしようとしていますが、どちらも失敗します。 チェックを手伝って、修正するためのコツを教えてもらえますか? ありがとうございました。 VS Code バージョン: 1.120.0 回复： Tools are failed to install in VS Code こんにちは、ハリーさん。 わかった。 ありがとう 。 回复： Tools are failed to install in VS Code こんにちは、 @jimmyli 回避策として、MCUXpresso Config ToolsとMCUXpresso Secure Provisioning Toolをそれぞれ個別にダウンロードしてインストールすることをお勧めします。 Windowsでは、両方のツールをデフォルトのインストールパスを使用してインストールしてください。インストールが完了したら、VS Codeを再起動してください。MCUXpresso for VS Code拡張機能はインストール済みのツールを自動的に検出できるはずで、現在見ているインストールや検出エラーを避けるのに役立ちます。 MCUXpresso Config Tools | NXPマイクロコントローラ (MCU) 向けソフトウェア開発 | NXP Semiconductors MCUXpressoセキュアプロビジョニングツール |NXPセミコンダクターズ BR ハリー

S32 Design Studio: Import and Build an Application Code Hub Project using AI Introduction This tutorial shows how an AI agent, together with S32 Design Studio AI Support, can run a complete S32 Design Studio workflow from one natural-language prompt. The workflow covers importing an NXP Application Code Hub example, generating configuration code, building the project, and running it on hardware. Instead of clicking through wizards, configuration views, and debug settings, you describe the result you want in plain language. The agent then uses S32 Design Studio AI Support's MCP tools to carry out each step. In this scenario, you ask the agent to complete an end-to-end task: Start S32 Design Studio with a dedicated workspace. Import the GPIO Blinking LED Demo from the NXP Application Code Hub. Target the FRDM-A-S32K312 board. Generate code for Pins, Clocks, and Peripherals using S32 Configuration Tools. Build the project with zero errors. Flash and run the firmware on the connected board. The agent breaks this request into a sequence of tool calls. It starts the IDE, searches the Application Code Hub, imports the demo, runs code generation, builds the project, and flashes the board.  Estimated time: ~20 minutes. System Architecture GPIO Blinking LED Demo — FRDM-A-S32K312 – system architecture overview   The components involved are:   FRDM-A-S32K312 – Target evaluation board. Runs the GPIO Blinking LED Demo firmware. Host PC – Runs S32 Design Studio and the S32 Design Studio AI Support. Imports the project, generates code, builds, and flashes the firmware over USB. Prerequisites   What you need before starting Download and install the FRDM Automotive S32K3 + S32M27 Board Installation Package from the Automotive Package Manager – LINK Update S32 Design Studio to v3.6.11 or later using the S32 Design Studio Platform package available in the Extensions and Updates panel Install the S32 Design Studio MCP REST Server (bundled with S32 Design Studio 3.6.11+ or available for installation via Extensions and Updates in older versions starting with 3.6.5) One FRDM-A-S32K312 evaluation board + USB cable Download, install and configure your agent to use the S32 Design Studio AI Support from Installation & Usage Guide  Note: This tutorial uses these paths: Installation: C:\NXP\2026\K3_kit\S32DS_3.6.8 Workspace: C:\NXP\2026\K3_kit\workspace_S32DS_3.6.8_K3_kit 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 before starting. The AI will detect the board automatically through the MCP server. Steps   Send the following prompt to your AI assistant. It is a complete, self-contained instruction that drives the demo.   Step 1 – Import GPIO Blinking LED Demo & build You are a software developer that needs to use S32K312 FRDM board, start S32DS that is installed at C:\NXP\2026\K3_kit\S32DS_3.6.8, import the GPIO Blinking LED Demo for FRDM-A-S32K312 from the NXP Application Code Hub into S32 Design Studio IDE. After importing, run S32 Configuration Tools to generate code (Pins, Clocks, Peripherals), build and run the project. Use s32ds-agentic-ai MCP server and if the server disconnects, stop and notify the user. AI will:   Start S32 Design Studio from C:\NXP\2026\K3_kit\S32DS_3.6.8 Search NXP Application Code Hub for GPIO Blinking LED Demo for FRDM-A-S32K312 and import it into S32DS Open S32 Configuration Tools and click Generate Code (Pins, Clocks, Peripherals) Trigger a full build and confirm zero errors Flash and run the project on the board Stop and notify the user if the s32ds-agentic-ai server disconnects Verifying the Result   Work through this final check to confirm that the prompt completed successfully.   Final check The project is imported and visible in the S32DS Project Explorer. S32 Configuration Tools ran successfully – Pins, Clocks, and Peripherals code was generated with no errors. Build completes with zero errors. Firmware is flashed and running on the FRDM-A-S32K312 board. The onboard LED should toggle with a 500ms cadence (500ms on, 500ms off). Troubleshooting   Symptom Fix Project not found in Application Code Hub Confirm the search term is GPIO Blinking LED Demo for FRDM-A-S32K312. Check that the s32ds-agentic-ai is connected and the ACH tool is available. Import fails or project does not appear in Project Explorer Try File › Import › Existing Projects into Workspace manually. Confirm the workspace path is C:\NXP\2026\K3_kit\workspace_S32DS_3.6.8_K3_kit. S32 Configuration Tools does not open Double-click the .mex file in the project root. Ensure the S32K3 SDK is installed and the project SDK is correctly configured. Generate Code produces errors Check the Pins, Clocks, and Peripherals tabs for validation errors (red markers). Resolve conflicts before regenerating. Build errors after Generate Code Ensure the generated src/ folder is included in the build path. Try Project › Clean then rebuild. Flash / debug fails Ensure the board is powered via USB and the J-Link / OpenSDA debugger is recognised. Try Run › Debug Configurations and re-select the correct debug probe. LED does not blink after flashing Confirm the correct binary was flashed. Check that the debug session started and the program counter advanced past main(). s32ds-agentic-ai server disconnects Stop immediately and restart the MCP server following the setup instructions. Do not continue until the server is confirmed connected. File Reference   File Step Description src/main.c 1 Main firmware entry point — GPIO LED blinking loop *.mex 1 S32 Configuration Tools project file (Pins, Clocks, Peripherals) generate/src/ 1 Auto-generated peripheral initialization source files generate/include/ 1 Auto-generated peripheral configuration headers   Import the demo, generate the configuration code and flash it – your first Application Code Hub project running on the FRDM-A-S32K312 in about 20 minutes. Examples

S32 Design Studio: Import, Build, and Monitor a Motor Control Project using AI Introduction This tutorial demonstrates an end-to-end, AI-assisted motor control workflow using S32 Design Studio AI Support. You'll find a motor control application for the FRDM-A-S32K312 on the NXP Application Code Hub, import it into S32 Design Studio, generate code, build and flash the project, and then create a FreeMASTER dashboard with motor controls, speed selection, and live parameter monitoring. The tutorial uses the NXP PMSM Low Voltage Motor Control Accessory Kit as the motor hardware.   Everything is done through two prompts – jump straight to the steps if you already have the tools installed.   Estimated time: ~35 minutes. System Architecture S32K312 Motor Control + FreeMASTER – system architecture overview   The components involved are:   Motor – NXP PMSM Low Voltage Motor Control Accessory Kit is connected to the FRDM-A-S32K312 board. The Motor is driven by PWM output from the MCU. FRDM-A-S32K312 – Runs motor control firmware with FreeMASTER TSA enabled. Streams live data to the host PC over USB (UART). Host PC – Runs FreeMASTER Lite (fmlite.exe) on COM#, 115200 baud, port 51234. Serves the HTML5 dashboard to the browser. Prerequisites   What you need before starting   Download and install the FRDM Automotive S32K3 + S32M27 Board Installation Package from the Automotive Package Manager – LINK Update S32 Design Studio to v3.6.11 or later using the S32 Design Studio Platform package available in the Extensions and Updates panel Install the S32 Design Studio MCP REST Server (bundled with S32 Design Studio 3.6.11+ or available for installation via Extensions and Updates in older versions starting with 3.6.5) Install the AMMCLIB for S32K3xx/S32M27x (Automotive Math and Motor Control Library) using S32DS Extensions and Updates required by the motor control demo Install the NXP GCC for Arm Embedded Processors v10.2 toolchain using S32DS Extensions and Updates — this is the toolchain used to build the motor control example Install FreeMASTER Lite into your working directory – download from LINK One FRDM-A-S32K312 evaluation board + USB cable One NXP PMSM Low Voltage Motor Control Accessory Kit (motor and driver hardware for the FRDM-A-S32K312) Connect the board to the PC via USB and find out which COM port it was assigned — open Device Manager → Ports (COM & LPT) and note the port of the board's USB-serial interface (it can be any COMx ). You will hand this value to the AI agent, which uses it for the FreeMASTER Lite serial connection Any modern browser (Chrome / Edge / Firefox) Download, install and configure your agent to use the S32 Design Studio AI Support following the 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 before starting, then tell the agent the COM port of the board — for example: "the board is connected on COM7, use it for FreeMASTER Lite". Everywhere this tutorial shows COMx , replace it with your own port number. The AI will search the Application Code Hub and select the most suitable motor control demo automatically. Steps   Send the following prompts to your AI assistant in order. Each is a complete, self-contained instruction.   Step 1 – Import motor control demo, build and run You are a software developer that needs to use S32K312 FRDM board to control a motor. I have the NXP PMSM Low Voltage Motor Control Accessory Kit available for my application. Check NXP Application Code Hub for an application that can be used and import the selected application into S32 Design Studio IDE. S32DS is installed at C:\NXP\2026\K3_kit\S32DS_3.6.8. Run S32 Configuration Tools to generate code, build it, load into the flash memory and run the project. Use the s32ds-agentic-ai MCP server; if the MCP server disconnects at any point, stop immediately and notify user. AI will:   Search NXP Application Code Hub for a motor control application suitable for the FRDM-A-S32K312 and compatible with the NXP PMSM Low Voltage Motor Control Accessory Kit Import the selected project into S32 Design Studio at C:\NXP\2026\K3_kit\S32DS_3.6.8 Open S32 Configuration Tools and click Generate Code (Pins, Clocks, Peripherals) Build the project and confirm zero errors Flash the .elf binary into the board's flash memory and run the project Stop and notify the user immediately if the s32ds-agentic-ai MCP server disconnects   Step 2 – Create FreeMASTER dashboard and run it 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 define and connect all the variables for the 4 panels and contained components: - top panel: contains the controls for the board serial connection, default: connection name "S32K312 Board", COM#, 115200 baud, 8 data bits, no parity, 1 stop bit - left panel: contains the motor control panel: motor state (on/off), actual RPM and desired RPM, slider for selecting the RPMs in both directions, a 0 RPM button, and +- 10/100 RPMs buttons - middle panel: contains a graphical representation of the motor, spinning the NXP logo in sync with the motor actual speed - right panel: contains all the board\motor parameters that you can find relevant Start FreeMaster server and run the dashboard at the end Once the JS client confirms that the board is connected it should start reading desired and actual RPMs Use the s32ds-agentic-ai MCP server; if the MCP server disconnects at any point, stop immediately and notify user. AI will:   Create a FreeMASTER configuration file in the project subfolder dashboard/: COM#, 115200 baud, 8 data bits, no parity, 1 stop bit, connection name "S32K312 Board" Generate a self-contained HTML5 dashboard saved to the project subfolder dashboard/ with all FreeMASTER variables defined, organised in four panels Once the JS client confirms the board is connected, automatically start reading desired and actual RPMs Start the FreeMASTER server and open the dashboard in the browser Stop and notify the user immediately if the s32ds-agentic-ai MCP server disconnects   Verifying the Result   Work through this final check to confirm that both prompts completed successfully.   Final check Motor control project imported and visible in S32DS Project Explorer. S32 Configuration Tools ran – code generated with no errors. Build completes with zero errors. Firmware flashed and running – motor responds as expected. PMSM kit connected and motor responds to commands from the dashboard. FreeMASTER configuration file created in dashboard/: COM#, 115200 baud, 8 data bits, no parity, 1 stop bit, connection name "S32K312 Board". FreeMASTER server is running. Dashboard opens in browser – all four panels visible. Once connected, the dashboard automatically starts reading desired and actual RPMs. Left panel shows motor on/off state, actual and desired RPM, slider for both directions, 0 RPM button, and ±10/100 RPM buttons. Middle panel shows the NXP logo spinning in sync with the actual motor speed. Right panel shows all relevant board/motor parameters updating in real time. Troubleshooting   Symptom Fix No motor control demo found on ACH Try broader search terms such as "motor", "PWM", or "BLDC". Confirm the s32ds-agentic-ai server is connected. Import fails or project missing from Project Explorer Try File › Import › Existing Projects into Workspace manually. Confirm S32DS path is C:\NXP\2026\K3_kit\S32DS_3.6.8. S32 Configuration Tools does not open Double-click the .mex file. Ensure the S32K3 SDK is installed and the project SDK is correctly configured. Generate Code produces errors Check Pins, Clocks, and Peripherals tabs for red validation markers. Resolve conflicts before regenerating. Build errors after Generate Code Ensure the generated src/ folder is in the build path. Try Project › Clean then rebuild. Motor does not respond after flashing Check hardware connections between board and motor driver. Verify correct PWM output pins per the demo schematic. FreeMASTER dashboard does not connect Confirm the FreeMASTER server is running and COM# / 115200 baud / port 51234 match the configuration file. Check that the board is powered and running. Dashboard does not auto-read RPMs after connect Check the JS connect callback in the dashboard HTML. Ensure the ReadVariable calls for desired and actual RPM are triggered after the WebSocket StartComm response confirms success. Actual/desired RPM shows 0 or stale Verify the variable names match those in the FreeMASTER project. Check that FMSTR_Poll() is called in the main loop and TSA is enabled. Right panel parameters not updating Verify FreeMASTER TSA is enabled (FMSTR_USE_TSA 1) and FMSTR_Poll() is called in the main loop. s32ds-agentic-ai MCP server disconnects Stop immediately and restart the MCP server following the Installation & Usage Guide. File Reference   File Step Description src/main.c 1 Main firmware – motor control loop with FreeMASTER TSA *.mex 1 S32 Configuration Tools project file (Pins, Clocks, Peripherals) generate/src/ 1 Auto-generated peripheral initialisation source files generate/include/ 1 Auto-generated peripheral configuration headers dashboard/board_115200.fmcfg 2 FreeMASTER server configuration: COM#, 115200 baud, 8 data bits, no parity, 1 stop bit, "S32K312 Board" dashboard/motor_dashboard.html 2 Self-contained HTML5 dashboard with all FreeMASTER variables, 4 panels (top: serial connection; left: motor control with slider, 0 RPM button, ±10/100 RPM buttons; middle: NXP logo spinning in sync with actual speed; right: board/motor parameters), auto-read on connect   Import the demo, build it and let your AI assistant generate the FreeMASTER dashboard – a complete motor control setup in about 35 minutes. Examples

FRDM-KL25Z 卡在 OpenSDA Bootloader v1.09 — LASTSTAT.TXT 卡在“正在编程...”处 你好， 我的FRDM-KL25Z卡在OpenSDA Bootloader v1.09版本（绿色LED灯持续闪烁）。 当我将匹配的固件（MSD-DEBUG-FRDM-KL25Z_Pemicro_v118.SDA）复制到引导加载程序驱动器时： 1. LASTSTAT.TXT 无限期地显示“编程中...”。 2. 卸载并重启电源（不按住 Reset 键）后，电路板不会启动到应用程序——它会直接重启到 BOOTLOADER 模式。 3. 在 Windows 和 Linux 上测试，结果完全相同。 如何才能让 Bootloader v1.09 成功完成固件的写入和刷写？     谢谢您！ Kinetis L系列MCU Re: FRDM-KL25Z stuck in OpenSDA Bootloader v1.09 — LASTSTAT.TXT hangs on "Programming..." 是的，我也遇到了同样的问题，lastat.txt 一直处于编程状态。

JTAG on FRDM iMX95 Hi all,  I just bought FRDM iMX95 recently, i am curious about how to use JTAG to debug this board  As check in schematic it has JTAG exposed at 6 test point pin here  At board layout it here  How should i connect jtag to it, do i need any rework ? And does this JTAG support to debug all A55, M33, and M7 core ?  Which device should i use here, it seem we have 6 pin needle but it 2x3 not 1x6  I would appreciate any guide or docment to set up JTAG  Thank you !!   Linux Re: JTAG on FRDM iMX95 Hello, Your understanding is correct. As you can see in schematic is needed to add the DNP resistors and a connector for the debugger. Best regards. Re: JTAG on FRDM iMX95 Hello, Thank you for your confirmation @JorgeCas  Summary : Please help with JTAG problem ""DAP: Could not power-up system power domain."" I have done the rework for 3 resistor and measure the pin, it successfully pull up. One note that to enable JTAG, i need to disable LPUART5 in device tree  because it use the same pin (i follow the same modify as imx95-19x19-jtag.dtb ) or else TMS (Test point 49) will always LOW) diff --git a/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts b/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts index c45f28efb568..598e16af0ebd 100644 --- a/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts +++ b/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts @@ -520,7 +520,7 @@ &lpuart5 { /* BT */ pinctrl-names = "default"; pinctrl-0 = <&pinctrl_uart5>; - status = "okay"; + status = "disabled"; bluetooth { compatible = "nxp,88w8987-bt"; After this i need to find the connector with 1.27mm pin. It take me some time to find this pcb test by pogo pin, it has 6 pin, perfectly fit.  Here is my current setup  It seem a mess but the connection is not problem, i check the HWStatus and it look good  J-Link>ShowHWStatus VTref=3.324V ITarget=0mA TCK=1 TDI=1 TDO=0 TMS=0 TRES=1 TRST=1 Supported target interface speeds: - 120 MHz/n, (n>=8). => 15000kHz, 13333kHz, 12000kHz, ... - Adaptive clocking I try connect it by these 2 command for A55 and M33 but same issue show is "DAP: Could not power-up system power domain." zk47@ltu:~$ JLinkExe -device MIMX9516_M33 -if JTAG -speed 200 SEGGER J-Link Commander V9.42 (Compiled May 6 2026 12:36:02) DLL version V9.42, compiled May 6 2026 12:35:00 zk47@ltu:~$ JLinkExe -device MIMX9516_A55 -if JTAG -speed 200 What could i do wrong here ? Maybe it fall to my JLink device is not good, can MCU-Link Pro replace it ? Can MCU-Link Pro debug both A55 and M core ?  I would still prefer do the debug through JTAG because i already had it. Please help  If you guy plan to add document guide for JTAG on FRDM iMX95, please update it soon like FRDM iMX93.   Re: JTAG on FRDM iMX95 Dear @JorgeCas  Any update ? Can i use MCU-Link Pro to debug all core A55, M33 and M7 core ?  Re: JTAG on FRDM iMX95 Hello, I apologize for the delay. We suggest you any debugger from MACRAIGOR Systems, Wind River or any of ARM. NXP team uses Lauterbach Trace32 as debugger tool for Cortex-A cores, J-link is for Cortex-M cores. In the case of i.MX95, as prerequisite to use the CM7 or CA55 scripts the SM should be already running on the i.MX device. it has the CM33 for resource management and security reasons, it's open source, it's compliant to a HW resource management standard by ARM, and its code it's meant (between a lot of them) to partition hardware, assign resources to either Cortex-A or Cortex-M7. You can use this document as reference. Debugging Cortex-M with VS Code on i.MX 8M, i.MX 8ULP, and i.MX 9 If you still having issues after this considerations, please look for hardware issues in your adapter. Best regards.  Re: JTAG on FRDM iMX95 Dear @JorgeCas  Thank you for your reply.  Okay so the hardware could be the problem, but i am still wonder these thing  Can i have a picture for your setup debug ? I am not sure what is the official way to connect to these test point. does we need to use kind of this  2. The docs only for Debug core M, not core A. Can you give me more guide for "Debug core A linux using Trace32 or JLink or MACRAIGOR " as you said ?  3. Not relate to this thread, but can i have the estimated release date for FRDM iMX95 Pro ?  Re: JTAG on FRDM iMX95 Hello, 1. Our available boards for testing are not modified since if JTAG is needed, we use EVK instead FRDM boards. The recommended approach is use shorter wires as possible between the boards and debugger to warranty a good connection and signal integrity. As you can see in this post, the issue was solved with shorter cables soldered to the board. 2.  This information is in probe manual since each manufacturer uses their process and scripts to connect with the processor. There is no documentation in our side regarding these probes connection. 3. Unfortunately we do not have this information, I suggest you check our official web site for further updates. Best regards. Re: JTAG on FRDM iMX95 @Zk47T Hi, I was wondering if you managed to succeed in debugging the cortex cores on the board, and if you have any advice that you're able to share with me. I'm currently facing the same issues trying to debug the M7 core, and any help would be appreciated. Thanks Re: JTAG on FRDM iMX95 Dear @bbggl  I still can't make it work on FRDM iMX95 board. And as i upgrade to FRDM iMX95 Pro which even have more mess up pin layout. I don't pursue the JTAG on these board any more  As suggest by @JorgeCas , you should ask the author on this thread  as they say they successfully make it work.  Re: JTAG on FRDM iMX95 Thanks you for the reply, I have reached out to the other author. What did you decide on for your debugging setup? Is there another device like the MCU link or EVK board that works better, or have you used alternate methods? Re: JTAG on FRDM iMX95 Hi,  After all, seem like it really the wire issue. I solder directly jumper with copper wire to the JTAG test point, then connect from CH347F module and it did work. I can even able to get some ETM trace here 

How can I download QCVS for QorlQ? Dear Manager, I'm using T2080 QorlQ CPU and want to create RCW file. I knew that the RCW file can make using QCVS or CodeWarrior Develpment Studio. I was installed the CodeWarrior ver 10.5.1  but I can't found the QCVS. Question. 1. Please let me know how can I download QCVS?   (I'm using WIndows 10, 64bit) 2. How can I make RCW using Codewarrior? Regards Daejin Re: How can I download QCVS for QorlQ? Please reinstall CodeWarrior for PA 10.5.1, then install QCVS on top of it. Please open CodeWarrior in a new workspace, then install QCVS. If your problem persists, please address it in a new thread. Re: How can I download QCVS for QorlQ? The link provided in the solution no longer works. However, I have been able to download the QCVS offline installation packages for CodeWarrior for Power Architectures Rev 4.5, but when I try to install using the add archive, I get the following error near the end of the installation process   Re: How can I download QCVS for QorlQ? Thanks for your reply. Re: How can I download QCVS for QorlQ? Please download QCVS for PA 4.5 installation file from  the following link. https://support.nxp.com/s/case/500Tg00000FpCkuIAF/community-how-can-i-download-qcvs-for-qorlq?language=en_US Please install CodeWarrior for PA 10.5.1 first, then open CodeWarrior IDE and install QCVS for PA 4.5 from Help->Install New Software->Add->Archive. Please create a QCVS PBL project from File->New->QorIQ Configuration Project, then double click “PBL:PBL” under Components to edit Properties panel, generate the binary file from Project->Generate Processor Expert Code and get PBL.bin under Generated_Code in the project. Re: How can I download QCVS for QorlQ? Hello Yiping, I'm in the same situation of OP, could you please share the file with me? The link you posted doesn't seem to work, at least for me. Best regards, Gab

Rt1176_evkb 以太网 OTA 我正在使用 rt1176 evkb，我们可以使用 j-link 和串行链接器进行代码转储和调试，如果我想通过以太网应用 OTA，这怎么可能呢？ @nxp#NXPAnalogComp FRDM 培训 动手实践培训 i.MX RT102x i.MX RT105x Re: Rt1176_evkb OTA Via Ethernet 你好，拉维拉基 以下主题可能会有所帮助： 已解决：需要 RT1170 FOTA 示例 - NXP 社区 已解决：RT1170 - 现场固件更新 - NXP 社区 敬上， Gustavo Re: Rt1176_evkb OTA Via Ethernet 你好， 我正在开发 i.MX RT1176 EVKB，正在探索实现 OTA（空中）更新的选项。我想知道是否有可能在不使用轻量级 IP（LWIP）协议栈的情况下，通过以太网直接进行MAC 对 MAC通信（即使用原始以太网帧）来执行 OTA 更新。 是否有任何示例、SDK 支持或推荐的方法可以纯粹在 MAC 层处理 OTA（绕过 LWIP）？ 还是说 LWIP（或其他 IP 栈）是 OTA 实施的强制性要求？ 谢谢。 - Raviraj Re: Rt1176_evkb OTA Via Ethernet 您好， 通过以太网实施 OTA 是一项常见要求。通常的方法是在您的设备上运行一个可以处理文件上传的简单网络服务器。 为此，您可以使用Mongoose 网络库。它是嵌入式系统的轻量级库，提供 HTTP、MQTT、WebSockets 等多种网络协议。一项关键功能是其强大的 HTTP 服务器，该服务器内置支持处理大文件上传，使其成为空中 (OTA) 固件更新的理想之选，Mongoose 通过易于使用的 API 支持这种更新。该库有据可查，旨在便于在不同平台上移植，包括裸机和 RTOS 环境，如 RT1170 板上的环境。 为了给您提供一个实用的起点，我为 RT1170 设计了一个简单的 MCUXpresso 项目，演示如何使用 Mongoose 实现 OTA。您可以直接导入，看看它是如何工作的。 请注意：我是 Mongoose 开发团队的一员。希望这能帮助你开始工作。 Re: Rt1176_evkb OTA Via Ethernet 通常的实现方式是使用 TFTP。它是一种基于 UDP 的简单文件传输协议，通常用于实现固件 OTA 更新。UDP协议非常简单，可以直接在以太网驱动程序之上实现。 能否详细说明一下，您为什么想要避免使用 TCP/IP 协议栈，您的使用场景是什么？

Display not working on IMX 93 FRDM board Hi, I am using an i.MX 93 FRDM board with Linux version 6.6.36 (Scarthgap), the fsl-imx-wayland distribution, and the core-image-weston image. However, the display is not working, and the screen remains blank. The system detects both the display and the HDMI interface, but no output is shown on the screen. Could you please help me identify the possible cause of this issue and suggest steps to troubleshoot it?.