wxWidgets on i.MX Assemble wxWidgets version 2.8. TinyX used. Powered by touchscreens 4 "- 8".

Motor Control and Power Conversion Application Development with Kinetis V Series Microcontrollers based on ARM® Cortex®-M Core The new Kinetis V series of MCUs enables ARM® Cortex®-savvy developers to create advanced motor control and power conversion solutions with Cortex-M0+, Cortex-M4 and Cortex-M7 based devices, spanning a wide range of packages, pinouts and features for low-cost to high-performance applications. This class provides an overview of the trends, solutions and roadmaps offered by Freescale, details on the Kinetis V series product families, the available enablement hardware and software to jump-start your motor control system design. Presented by Lorenzo Daniele Presented at DwF Istanbul - May 12, 2015 Session ID: EUF-IND-T1473 The new Kinetis V series of MCUs enables ARM® Cortex®-savvy developers to create advanced motor control and power conversion solutions with Cortex-M0+, Cortex-M4 and Cortex-M7 based devices, spanning a wide range of packages, pinouts and features for low-cost to high-performance applications. This class provides an overview of the trends, solutions and roadmaps offered by Freescale, details on the Kinetis V series product families, the available enablement hardware and software to jump-start your motor control system design. Presented by Lorenzo Daniele Presented at DwF Istanbul - May 12, 2015 Session ID: EUF-IND-T1473 Kinetis Cortex®-M Microcontrollers

キネティス量産ノート <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Kinetis チップを大量生産する場合、以下の点に注意する必要があります。 1. 正しい電源投入シーケンスを確認してください。VDDは他のすべてのピンよりも先に電源投入する必要があります。VDDが電源投入される前にRESETピンがハイレベルになってはなりません。 2. RESET ピンに 10k のプルアップ抵抗を追加し、プログラマのリセット ピンから切断することをお勧めします。 3. プログラマから MCU までのリードはできる限り短く、できれば 15 cm 以内にする必要があります。 4. すべてのピンは、チップのマニュアルに指定されている最大電圧レベルを超えることはできません。 5. はんだ付け温度がチップのマニュアルに指定されている最高温度を超えないようにしてください。

Kinetis Bootloader 总结 Bootloader是一种面向用户应用程序的引导代码，可以在没有烧写器的情况下烧录用户程序，也可以用于在线更新程序。飞思卡尔提供了三种实现bootloader的方式，分别为： 1.预烧写在ROM中的bootloader     这种方式是MCU中内置了专用的ROM来存放bootloader，目前支持ROM型bootloader的Kinetis系列MCU包括KL03，KL17，KL27和KL43等。其中KL03和KL17的ROM bootloader包含SPI/UART/IIC三种接收方式，KL27和KL43还增加了USB的方式。 2.预烧写在FLASH中一次性bootloader     这种类型的bootloader在芯片出厂前预写在FLASH中，因此可以像ROM型bootloader一样直接使用。但与ROM型不同的是，上电后bootloader会从FLASH搬移到RAM 中运行，再将FLASH整片擦除并烧写用户程序，因此这种bootloader是一次性的。其优点是不需要片内ROM且方便量产烧写，缺点是无法支持以后的程序更新。目前支持预烧写在FLASH中一次性bootloader的Kinetis系列MCU包括K22、K24和KV3x等。 3.开放源码的bootloader     这种方式将FLASH空间分为两个部分，一部分用于存储bootloader代码；另一部分用于存储用户应用程序代码。这种方式的bootloader方便客户定制自己的代码。     目前飞思卡尔提供开放源代码的Kboot，支持UART/SPI/IIC/USB HID 几种接口方式，其网址链接为：     www.freescale.com/kboot     除了Kboot，还有以下独立版本的bootloader，包括：     1）AN2295（开发人员的串行引导加载程序）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN2295.pdf         代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN2295SW.zip        另外FAE Yang Liang 对其进行了移植，目前已经支持FRDM-KE02,KE06,KL25,KL26,KL43,KL46, TWR-K60, KV4x, KV10.下载地址为：Kinetis/AN2295_Bootloader · GitHub     2）AN4767 （Kinetis E 系列上的UART Boot Loader 设计）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/32bit/doc/app_note/AN4767.pdf         基于AN2295，没有提供代码。     3）AN4775 （Kinetis E 系列上的IIC Boot Loader设计）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/32bit/doc/app_note/AN4775.pdf         代码下载地址为：http://cache.freescale.com/files/32bit/doc/app_note/AN4775SW.zip     4）AN4368 （USB 大容量存储设备主机引导加载程序）          文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4368.pdf          代码下载地址为：GitHub - Wangwenxue/USB_MSD_Host_Bootloader_K60: This is usb msd Bootloader for K60 （For K60）                                        GitHub - Wangwenxue/USB_MSD_Host_Bootloader_K64: This USB MSD bootloader for K64 （For K64）     5）AN4379  （Freescale USB大容量存储设备引导加载程序）          文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4379.pdf          代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4379SW.zip     6）AN4764   （USB Human Interface Device Boot Loader for ColdFire Plus, Kinetis K, and Kinetis L MCUs）          文档下载地址为：http://cache.freescale.com/files/32bit/doc/app_note/AN4764.pdf          代码下载见附件     7）AN4370   （用于 MCU 的 USB DFU 引导加载程序）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4370.pdf         代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4370SW.zip       8）AN4367   （用于 MCU 的 以太网引导加载程序）         文档下载地址为：http://cache.freescale.com/zh-Hans/files/microcontrollers/doc/app_note/AN4367.pdf?fromsite=zh-Hans         代码下载地址为：http://cache.freescale.com/files/microcontrollers/doc/app_note/AN4367SW.zip         最新的代码请到FNET官网下载：http://fnet.sourceforge.net/    9）Kinetis Bootloader to Update Multiple Devices in a Network - for Cortex-M0+         代码及文档下载地址为：https://community.freescale.com/docs/DOC-328168             回复：Kinetis Bootloader 总结 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨文学 对 Kinetics 系列引导加载程序的总结做得很好。 我正在研究基于 K20d72m 的定制板，寻找从 PC 接收命令来校准板上的蓝牙芯片的解决方案。 您是否知道是否有一个演示引导加载程序同时支持 USB（虚拟 COM 连接到 PC）和 SPI 端口到外围芯片？我需要这样的裸机应用程序来进行电路板校准。 谢谢！ 回族 Re: Kinetis Bootloader 总结 谢谢，我一直在更新AN2295，目前支持FRDM-KE02，KE06，KL25，KL26，KL43，KL46. TWR-K60, KV4x, KV10，可以从下面这个地址获取： Kinetis/AN2295_Bootloader · GitHub Re: Kinetis Bootloader 总结 点赞,总结的非常好! Re: Kinetis Bootloader 总结 谢谢分享，非常感谢！ 希望能将KBoot如何通过命令行更新介绍的更详细些。 回复：Kinetis Bootloader 总结 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> HI，Liang Yang， 如何将 KE02/KE06 uart 引导加载程序移植到 FRDM-KE04Z 演示板？ 谢谢你？ 回复：Kinetis Bootloader 总结 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Hi hui， 我们没有可以满足您的要求的引导加载程序。您需要自己动手。 顺祝商祺！ Wenxue 发自我的 iPhone 在 2015年4月11日，0:20，"Hui Shao" > 写道： <> <> Kinetis 引导加载程序总结 Hui Shao 的新评论<>查看本文档的所有评论<>

uSDHC auto tuning and possible SDIO failures 1 - Introduction: The Ultra Secured Digital Host Controller (uSDHC) provides the interface between the host processor and the SD/SDIO/MMC cards. Most recent versions provides the ability to automatically select a quantized delay (in fractions of the clock period) regardless of on-chip variations such as process, voltage, and temperature (PVT). The auto tuning is performed during runtime at hardware level, no software enablement is needed to drive this feature. 2 - Failure description: SDIO cards can implement an optional feature that uses DATA[1] to signal the card's interrupt to the i.MX device, this feature can be enabled by the SDIO card device and does not depends on i.MX uSDHC driver configuration. NXP Linux BSP is enabling the auto tuning for high SDIO frequencies (SDR104 and SDR50). Out of reset uSDHC_VEND_SPEC2 register is configured to use DATA[3:0] for calibration, this setup can conflict with the SDIO interrupt as DATA[1] signal can be asserted asynchronously. SDIO failures can be observed when running SDIO applications that requires high usage of the SDIO interface (e.g Download of large files), SDIO controller cannot return an accurate DLL causing failures such as "CMD53 read error". Failure can be observed on i.MX8MM EVK and i.MX8MN EVK boards, both devices are running 88w8987 Wi-Fi chipset at 208Mhz (SDR104). Users can observe an SDIO crash followed by error message below at Linux Kernel level. [ 401.945627] cmd53 read error=-84 [ 401.974677] moal_read_data_sync: read registers failed 3 - Impacted devices: The following devices are impacted by this limitation. - i.MX6 Family:   i.MX6SL, i.MX6SLL, i.MX6SX, i.MX6UL, i.MX6ULZ and i.MX6ULL. - All i.MX7 and i.MX7ULP family:   i.MX7D, i.MX7S and i.MX7ULP. - All i.MX8M Family:   i.MX8MQuad, i.MX8M Mini, i.MX8M Nano, i.MX8M Nano UL and i.MX8M Plus. - All i.MX8/8X Family:   i.MX8DQXP, i.MX8DX and i.MX8QM. NXP Linux BSP is enabling the auto tuning for SDR104 and SDR50 modes. Other operation modes are not impacted by this limitation. Users can poll uSDHCx_CLK_TUNE_CTRL_STATUS register when running SDIO applications to confirm. TAP_SEL_PRE field is updated automatically during run time and constant variations can point to an incorrect delay cell calculated by the uSDHC controller. All NXP Wi-Fi chipsets are enabling SDIO interrupt during firmware load, failures can be observed with any Wi-Fi vendor enabling SDIO asynchronous interrupt. 4 - Software changes: Recommendation is to enable auto tuning for DATA[0] and CMD signals only, DATA[1] should not be used for auto calibration to avoid a possible conflict with SDIO interrupt. This setup can only be used if SDIO interface length are well matched. Software patches can be found at codeaurora.org. Fix is already included in L5.10.52-2.1.0 BSP, users can add fsl,sdio-interrupt-enabled property to uSDHC device tree node to enable SW workaround. https://github.com/nxp-imx/linux-imx/commit/3b3d6dec05277f7786d813592a31ea4a1ce60a74 https://github.com/nxp-imx/linux-imx/commit/b9b5a43df1d709809b2b654ad8f8181b00a4ee55 https://github.com/nxp-imx/linux-imx/commit/95a846af9f82dc6ea60064d9d12d5d2378e23941

Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK This document shows how to run the multicore communication examples from MCUXpresso SDK while running the Android BSP on Cortex-A7 on i.MX 7ULP-EVK. Though this document is focused on the multicore demos, similar procedures can be applied to run any other demo in the SDK. 1. Source code This document is based on the following releases: Board Android BSP MCUXpresso SDK imx7ulp-evk Android O8.1.0 for i.MX 7ULP GA SDK2.4 for i.MX 7ULP GA Download releases at i.MX Software. 2. Building the Cortex-M4 SDK There are at least two multicore demos in the SDK package, rpmsg_lite_pingpong_rtos and rpmsg_lite_str_echo_rtos. They are located at: /boards/evkmcimx7ulp/multicore_examples/ Build the rpmsg_lite_str_echo_rtos demo according to the SDK Getting Started Guide. Remember to also follow the Chapter 6, Step 4 of the document to generate the ram bootable image (sdk20-app.img). 3. Building the Android BSP 3.1. RPMsg kernel module Before building the BSP, add the following line to the BoardConfig.mk file ( /device/fsl/evk_7ulp/BoardConfig.mk): BOARD_VENDOR_KERNEL_MODULES += \    $(KERNEL_OUT)/drivers/net/wireless/qcacld-2.0/wlan.ko \ + $(KERNEL_OUT)/drivers/rpmsg/imx_rpmsg_tty.ko 3.2. Cortex-M4 image Copy the SDK image file (sdk20-app.img) to the following directory in the Android source code: $ cp /tools/imgutil/evkmcimx7ulp/sdk20-app.img \   /vendor/nxp/fsl-proprietary/mcu-sdk/7ulp/sdk20-app.img Change the BoardConfig.mk file accordingly: # Copy prebuilt M4 demo image: PRODUCT_COPY_FILES += \ - vendor/nxp/fsl-proprietary/mcu-sdk/7ulp/imx7ulp_m4_demo.img:imx7ulp_m4_demo.img + vendor/nxp/fsl-proprietary/mcu-sdk/7ulp/sdk20-app.img:imx7ulp_m4_demo.img After these changes, build and flash Android as described in the BSP User's Guide. 4. Enabling the multicore communication While booting, the SoC automatically loads the Cortex-M4 image. After complete booting, install the imx_rpmsg_tty.ko module to create the multicore communication channel: $ su $ insmod vendor/lib/modules/imx_rpmsg_tty.ko To send messages from Cortex-A7 to Cortex-M4, use the /dev/ttyRPMSG* channel: $ echo "MESSAGE" > /dev/ttyRPMSG* /dev/ttyRPMSG* refers to the RPMsg device created on the board, so change the number accordingly. Cortex-M4 will echo all messages received from Cortex-A7. This is a simple example on how to communicate different cores on i.MX using Android but it can be used as a starting point for Android multicore applications. i.MX7ULP Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Thanks for your help. I will try running it through Uboot. I appreciate your help Thanks, Anurag Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK 1. Should I boot an image of an RTOS on the M7 architecture before running the demo SDK? No need, the demo SDK already includes the RTOS code. 2. Also if the above is not true, the SDK says to just boot the device, use IAR IDE(build) and JLink debugger to check the output of a demo application, hello world. The Jlink debugger does not detect the board, though the Putty terminal detects it. What do you propose the issue for the same is? If Putty recognizes the devide, please try the Uboot approach to boot the M7 core instead of IAR's method. Thanks, Vanessa Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Ok thanks, I have a couple of questions 1. Should I boot an image of an RTOS on the M7 architecture before running the demo SDK? 2. Also if the above is not true, the SDK says to just boot the device, use IAR IDE(build) and JLink debugger to check the output of a demo application, hello world. The Jlink debugger does not detect the board, though the Putty terminal detects it. What do you propose the issue for the same is? Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Please refer to the SDK Getting Started Guide for all the supported ways to boot the M7 core. Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Hi Siva, Sorry, just checked and there's no M4 target in imx-mkimage for 8MM. Indeed you have to change your dtb file to the rpmsg one. To load M4 bin in the boot, you can add Uboot commands to load your binary from a FAT partition as described in the SDK Getting Started: Add the commands above to imx8mm_evk_android.h\configs\include - uboot-imx - i.MX U-Boot and make sure you copy your M4 bin to a FAT partition of the output image in evk_8mm.mk. I have not tested this procedure on iMX8* targets. Thanks, Vanessa Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Is there a way to boot the iMX 8 Nano evaluation board cores with FreeRTOS(M7) and Andorid OS(A53) separately? Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK could you provide me the procedure to embed the M4 bin image for iMX8MM? Also, don't i need to change the dtb image to support M4 to test this out? if so, that change is needed in BOARD_PREBUILT_DTBOIMAGE flag in BoardConfig.mk? Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK It should be a similar procedure for 8MM as well, but for iMX8* the M4 bin should be embedded in the boot image through imx-mkimage. Regarding the linux modules, please try the same with the imx_rpmsg_pingpong module. Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK is it the same procedure for i.MX8MM EVK? i made the changes to BoardConfig.mk to add the kernel objects, but it  wont show up in /vendor/lib/modules Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Thank you Vanessa Maegima Vinoth S, Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Hi vinothkumars‌, It should be a similar procedure but I have not tested Android Auto myself. I intend to take a look in the following weeks. Thanks, Vanessa Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Hi Vanessa Maegima , Will you please tell me. How we can achieve the same procedure for IMX8QM-MEK with Android 9 Automotive. Regards, Vinoth S, Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK Hi [email protected]‌, You can download the SDK source code and documentation at Welcome | MCUXpresso SDK Builder and follow the Getting Started Guide. You can also refer to How to build and flash a bootable image for Cortex-M4 on i.MX 7ULP - i.MXDev Blog . This document refers to an old SDK version but the procedure is pretty similar to the latest ones. Thanks, Vanessa Re: Using Cortex-M4 SDK to communicate with Cortex-A7 Android BSP on i.MX 7ULP-EVK "Build the rpmsg_lite_str_echo_rtos demo according to the SDK Getting Started Guide. Remember to also follow the Chapter 6, Step 4 of the document to generate the ram bootable image (sdk20-app.img)." could you please upload the guide. how to make a ram bootable image ?

S32G_LLCE_to_PFE_Demo Building(Chinese Version) 本文说明在S32G2 RDB2板上实现LLCE to PFE Demo的搭建过程。本Demo目前包括：  CANtoEth：CAN0发送，用硬件回环到 CAN1接收，然后通过PFE_EMAC1， 再通过RGMII接口发出。  CANtoEth：CAN0发送，用硬件回环到 CAN1接收，然后通过PFE_EMAC1， 再通过SGMII接口发出。  EthtoCAN：PC通过PFE_EMAC1的 RGMII发出，接收到CAN1，再硬件 回环到CAN0  CANtoCAN Logging to Eth: CAN0发 送，用硬件回环到CAN1接收，然后 通过PFE_EMAC1，再通过SGMII接 口发出,同时LLCE内部硬件把CAN1 再发送到CAN15_TX，再用硬件回环 到CAN14_RX 软件版本为 RTD3.0.0+LLCE1.0.3+PFE0.9.6/0.9.5。 Automotive

Installation steps for MCUXpresso for VS Code This article has been updated 6/29/2023 for 6th Beta Release: Latest Release Versions: MCUXpresso extension for VS Code v2023.07 (1.0.68) MCUXpresso Installer v2023.07 (v1.0.85) LinkServer v2023.07 (v1.2.45) Release information provided in Extension Overview in Visual Studio Code Visual Studio Code Installation Windows install Visual Studio Code Ubuntu install Visual Studio Code macOS install Visual Studio Code Extension Installation Steps Launch Visual Studio Code Click the Marketplace icon found in the main left navigation pane Search "NXP" in Marketplace search bar.  Click "MCUXpresso for VS Code" Click Install in the MCUXpresso for VS Code extension.  Installation includes other required extensions (i.e. C/C++ by Microsoft) Dependency Installation Steps Links for the MCUXpresso Installer are in Quickstart Panel added by Visual Studio Code extension. Click Open MCUXpresso Installer The Installer UI launches to assist in adding required software tools/settings. Select from "Software Kits", "Debug Probes", and "Individual Components" appropriate for your development. Click Install NOTE: Installer can Check that you have the latest installer by clicking Cloud icon Your system should now be ready to begin developing with NXP.  Please review included Walkthrough OR "Online Documentation" for further assistance. Please provide feedback on these instructions below. Re: Installation steps for MCUXpresso for VS Code Hello @vae, Could you please help us with more information? You can send us the log file -> in the top right corner of the menu, please select "open log folder" and send us the files to better understand what is happening on your setup. Regards, Lorena Lazar ([email protected]) Re: Installation steps for MCUXpresso for VS Code Is there a vscode development path using WSL ? Re: Installation steps for MCUXpresso for VS Code Hello @FengChendian, You are right, MCUXpresso Installer doesn't yet support arm64 packages on macOS. We plan to add arm64 support in a future release, we estimate that it will be available in the last quarter of the year. Best regards, Lorena Re: Installation steps for MCUXpresso for VS Code MCUXpresso Installer cannot download correct AArch64(Arm64) packages on MacOS. It will download amd64 or x86_64 package. Maybe it's because that there was no arm64 version before. Re: Installation steps for MCUXpresso for VS Code Hi @ThBer,  Could you please post this question on MCUXpresso SDK community:  https://community.nxp.com/t5/MCUXpresso-SDK/bd-p/mcuxpresso-sdk?   Maybe they will be able to help you with the eCos OS issue. Best regards, Dragos. Re: Installation steps for MCUXpresso for VS Code Regarding my question of using the eCos OS in combination with MCUXPresso. Is there any help that you can offer ? I think I am running into an issue with trying to use a board specific ecos with the board specific configuration in MCUXpresso provided in the hello world examples. For instance when trying to import the compiled ecos librarys I am running into an memory allocation error. If anyone has some experience in this topic, help would be greatly appreciated. Otherwise I need to contact the ecos guys. Thank you Re: Installation steps for MCUXpresso for VS Code Hi and thank you for your response. I was able to get the  i.MX RT1050-EVKB Board running and am also now able to compile and Debug SW for the Board. I had to select one of the following confiugrations : flexspi_nor_sdram_debug / flexspi_nor_sdram_release This takes care of the hello world application. May next challenge is to get a EcosPro OS compiled and running on the board. This would require me to include the OS into the build system and also encorperate the ecc file, that configured the ecos itself. Is this something that you guys have done before or can help me with ? Re: Installation steps for MCUXpresso for VS Code If the i.MX RT1050-EVKB board shows up in your Windows (assumed) explorer as a USB device, then the debug settings require a latency setting.  This is being added to the extension release next week. YOu can manually see if this fixes the issue where debug data is not reliable due to GDB server latency/timeouts. Open the launch.json file for the project. Paste the following command as shown in the image below: "setupCommands": [{"text":"set remotetimeout 60000"}], Note 1: you should also verify that you installed the LInkserver Debug Probe software in the installer.  The Linkserver software is used with the probe on the board.  HOwever, not having this software installed usually reports an error of missing software. Note 2: you should also verify that the board has core power.  Without the board showing up as a USB storage device indicates it is using J-Link or LPCLink debug firmware.  This can require 2 usb cables to provide power to the board if an external power supply is not connected to the barrel connector.  The USB cables should connect to the Debug USB port and the USB Device port.  Refer to the RT1050-EVK getting started page to verify you have power.  Note 3: You may also verify that it connects with MCUXpresso IDE to eliminate VS Code as the issue.  Please let us know if this helped with your issue.  Re: Installation steps for MCUXpresso for VS Code HI, I have just installed the Toolchain and try to run a the provided Hello World Programm on a IMXRT1050-EVKB Board. I can compile the programm but when connecting to the Board to Debug the result, I get an GDB Error Message saying that the connection can not be established. Is there anything that I still need to set up in order for the debug process to run ?

MPC5746Cは周囲温度115℃でハングアップする（起動せず、UARTも動作しない）。 パート: MPC5746C(Power Architecture Z4、SDK:NXP MPC57xxプラットフォームSDK) 周囲温度115℃での恒温槽試験中、当社のMPC5746Cベースのボードは起動時に完全に反応しなくなり、UARTコンソール出力が全くなくなります。この現象は、その温度での起動試行のたびに発生します。冷却後、部品は完全に回復するようです。室温で再フラッシュ/再起動すると、永続的な損傷なく正常な動作に戻ります。 興味深いことに、基板が115°Cの状態でもPEMicro JTAGデバッグプローブを使ってフラッシュを再プログラム することは可能です 。これは、温度でバージョンストリングをフラッシングし、冷却後に新しいバージョンを読み返すことで確認済みです。したがって、デバッグプローブのフラッシュ経路は115°Cで動作します。アプリケーションのブートパスだけがハング/悪い状態になります。 マニュアルにはMCUが最大125°Cまで持続できると書かれています。 問題の根本原因と解決方法を教えていただけませんか。 Re: MPC5746C hangs (no boot, no UART) at 115°C ambient こんにちは、 マニュアルにはMCUが最大125°Cまで持続できると書かれています。 はい、それは問題ありません。 問題の根本原因と解決方法を教えていただけませんか。 これはカスタムボードであり、冷却後に問題が解消されることから、私は次のことを疑っています。 1. 時計の起動に関する問題（最も可能性が高い） 115℃の場合： 外部水晶発振器（FXOSC）の起動時間が長くなります。 発振器のゲインマージンが減少する。 負荷コンデンサの値は温度によって変化する。 プリント基板からの漏洩電流が増加します。 デバッグロジックは独自のインフラストラクチャを利用し、アプリケーションがmain(に到達する)に依存しないため、デバッガーは部品にアクセスできます。 FXOSCステータスビット CMUクロックモニタの障害 FIRCのみのブート実験 FIRCから完全に実行し、外部水晶発振器を一時的に無効にする JTAGのプログラミングが115°Cで動作し続けていることは、コアインフラストラクチャがまだ生きており、故障がフラッシュアレイ自体ではなくアプリケーションのブートパスの非常に早い段階で起きていることを示す最も強い手がかりです よろしくお願いいたします。 ピーター Re: MPC5746C hangs (no boot, no UART) at 115°C ambient @petervlna さん、貴重なご意見ありがとうございます。 これを受けて、同僚の@mnargundと私はさらに調査を進め、MPC5746Cを115℃で正常に起動させることに成功しました。以下に、調査結果の概要を示します。 根本原因: 事前初期化時にシステムをFIRC、FXOSC、PLLを起動するように設定し、その後システムクロックをFIRCからPLLに切り替えました。続いて、DRUN モードへのモード遷移をトリガーしました（システムはデフォルトで既に DRUN モードでしたが、マニュアルに記載されているように、新しい設定を有効にするには同じモードへの遷移が必要です）。そして、MC_ME_GS.MTRANS をポーリングして遷移が完了するのを待ちました。 しかし、MC_ME_GS.MTRANSがクリアされた後でも、コードはIVOR1例外でエラーを起こしました。これは、実行が続行された時点で遷移が完全に安定していなかったことを示している可能性があります。高温（115℃）では、室温よりも遷移に時間がかかるようで、次の命令が実行されたときにシステムが不安定な状態になる。 回避策の適用例: MC_ME_GSの後に明示的なソフトウェア遅延を挿入しました。MTRANSのポーリングを行い、その後の初期化を進めます。500ミリ秒の遅延を設けると、115℃の環境下でも起動は安定して成功する。100ミリ秒の遅延もテストしましたが、私たちの環境では問題なく動作しました。 初期化のこの段階で安全に挿入できる最大推奨ソフトウェア遅延はありますか? 125℃までの全動作温度範囲において、動作前にクロックの安定性を確実に確保するための推奨手順はありますか？

RT1160 带有外部同步动态随机存取存储器(SDRAM)和 SRAM，以及等待引脚 我正在使用 RT1160，搭配外部 16 位 同步动态随机存取存储器(SDRAM) 和 16 位 SRAM（用于 FPGA 通信）。SRAM 接口配置为异步模式下的 SRAM 读/写操作，并带有等待引脚。我怀疑等待信号是否会与同步动态随机存取存储器(SDRAM)刷新时序冲突，从而导致一些问题。我们测试过，让代码在同步动态随机存取存储器(SDRAM)中运行，并在 SRAM 异步写入时让等待引脚保持低电平约 10 毫秒或更长时间，但有时会在大约 1 毫秒后结束，不知道为什么。 我们可以这样使用吗？或者说同时使用同步动态随机存取存储器(SDRAM)和SRAM设备会有一些限制吗？感谢您的帮助。 Re: RT1160 with external SDRAM and SRAM with wait pin 你好 你提到的“大约1毫秒后结束”指的是什么？SRAM 写入操作是返回错误，还是进入硬故障？这种情况发生的频率如何？ 请问您能帮我测试一下以下功能吗？ 1. 从内部存储器（不是 同步动态随机存取存储器(SDRAM)）运行代码，并重复长时间异步 SRAM 写入。 2. 在仍然从内部存储器执行代码的情况下，再次运行相同的测试，但这次启用同步动态随机存取存储器(SDRAM)但使其处于空闲状态。 3. 按照你最初提到的方法运行测试，但要保持 SRAM 等待信号处于激活状态。 此外，能否在这些测试期间（包括上述提到的测试）检查以下内容？ 能否在传输过程中监控 SRAM 信号？ 能否分享一下每次测试的 SEMC INTR 寄存器值？ 请告诉我你的结果。 此致， 巴勃罗

S32k328 HSE 域标识符 您好，恩智浦技术团队 我写这封信是为了询问如何准确验证 S32k328 功能域 ID。 我目前正在使用 S32k328 板和 HSE 固件。  - 环境设置：      我正在使用 HSE 固件镜像 s32k358_hse_fw_1.14.0_2.40.0_pb230807.bin。      我目前处于多核状态，并正在使用 RM 模块（仅使用 XRDC）。  - 问题： 在 HSE FW RM 中，S32k328 功能域 ID 设置为 2，如附件所示。 dpsdprtmvl_1-1781577003974.png 但是，在 S32K3xx RM 中的 S32K328 方框图中，HSE 设置为 MDAC3，MDAC3 的 DID（功能域 ID）输出为 3。 dpsdprtmvl_2-1781577150058.png    (1) 注册验证码：             uint32_t mda[8];             mda[0] = IP_XRDC->MDA_W0_0_DFMT0;             mda[1] = IP_XRDC->MDA_W0_1_DFMT1;             mda[2] = IP_XRDC->MDA_W0_2_DFMT1;             mda[3] = IP_XRDC->MDA_W0_3_DFMT0;             mda[4] = IP_XRDC->MDA_W0_4_DFMT0;             mda[5] = IP_XRDC->MDA_W0_5_DFMT1;             mda[6] = IP_XRDC->MDA_W0_6_DFMT0;             mda[7] = IP_XRDC->MDA_W0_7_DFMT1;             UART_Print("--- MDA 锁 ---\n");             用于 (uint32_t i = 0; i < 8; i++)             {                 uint32_t vld = (mda[i]>> 31)& 1U;                 uint32_t lk1 = (mda[i]>> 30)& 1U;                 uint32_t did = mda[i]& 0x3U;                 UART_Print("MDA%lu=0x%lx VLD=%lu DID=%lu LK1=%lu %s\n",(无符号 long)i, (无符号 long)mda[i],(无符号 long)vld, (无符号 long)did, (无符号 long)lk1,lk1 ？ "(已锁定)" : "");             } (2) 寄存器值：            MDA0=0x80000000 VLD=1 DID=0 LK1=0 MDA1=0x20000000 VLD=0 DID=0 LK1=0 MDA2=0x20000000 VLD=0 DID=0 LK1=0 MDA3=0xc0000003 VLD=1 DID=3 LK1=1 (已锁定) MDA4=0x80000001 VLD=1 DID=1 LK1=0 MDA5=0x20000000 VLD=0 DID=0 LK1=0 正确的 s32k328 功能域 ID 是什么？ Re: S32k328 HSE DomainID 你好@dpsdprtmvl  S32K328 有四个功能域 0-3，HSE 始终分配给最高可用功能域，在本例中分配给功能域 3： lukaszadrapa_0-1781608491449.png 这是固有的，无法更改。 表 136 有些令人困惑，因为它只列出了主要导数，而没有列出所有次导数。这意味着： 第二行中的“S32K32x”代表 S32K322 和 S32K324。 第三行中的 S32K35x 代表 S32K358、S32K356、S32K348、S32K338、S32K328 以及 S32K37x 和 S32K39x 的衍生型号。 此致， Lukas

Why model size is limited at 1 MB? I run model from sample tflm_cifar10 on MIMRT700 (NPU model). When building the program, I could see the model's size and correspond region size.  In many cases, the region size is 1 MB. As my understanding, the model's size is limited at 1 MB. Is that right? nnxxpp_0-1781495142659.png I did not understand this point. Here is information of MIMRT700 EVK. nnxxpp_2-1781495429888.png I don't know where model is saved on MIMRT700 EVK. And where is the 1 MB for region size? Is it actual limit of model size? Or we can increase model size by some methods. Do you have any comment for this problem? Because I try to deploy a larger model > 1 MB. I do wait for your response. Thank you. Re: Why model size is limited at 1 MB? @mayliu1  Thank you so much. Now I understood that we can increase the size of the model by setting region size. nnxxpp_0-1781514247437.png Or If I want to run larger model on external memory, I can follow this document https://docs.nxp.com/bundle/AN14700/page/topics/external_memory.html  Re: Why model size is limited at 1 MB? Hi @nnxxpp , Thank you so much for your interest in our products and for using our community. Q: I don't know where model is saved on MIMRT700 EVK. And where is the 1 MB for region size? Is it actual limit of model size? Or we can increase model size by some methods. Do you have any comment for this problem? Because I try to deploy a larger model > 1 MB. A: The 1 MB shown for modeldata is not a hardware limit of the RT700. It is only the default linker allocation used in the sample project. For larger models, this allocation can be adjusted in the project settings, and external XSPI flash can also be used if more storage is needed. For more detail information, you can refer to this AN14700. https://docs.nxp.com/bundle/AN14700/page/topics/introduction.html mayliu1_0-1781507645284.png So, the RT700 is not inherently limited to a 1 MB model. Larger NPU models are supported either by increasing the modeldata memory allocation or by placing the model in external XSPI flash with the appropriate conversion option.  Wish it helps you Best Regards May Liu Re: Why model size is limited at 1 MB? @mayliu1  I want to reopen this topic. Now i am trying to deploy larger model on RT700. The below image is captured when building the program with the small model. I see that there are 4 memory regions: - QSPI_flash: external memory - SRAM: I ask chatgpt and it is for data when running the program (like .data, .bss, stack, heap). Is that correct? - NCACHE_REGION: it is same ktensorArena (for inputs, intermediate outputs and output) -  modeldata: to save model weights I see in the memory configuration when I import SDK example. It means that SRAM, NCACHE_REGION and modeldata from SRAM (7.5 MB). NCACHE_REGION and modeldata should be located in  0x2000_0000 to 0x2058_0000 (5.5 MB) to get best perforemce (SRAM area that can be accessed by the NPU) But location of SRAM (named SRAM) is 0x20080000 (in the second image) ==> It is also in the range 0x2000_0000 to 0x2058_0000. And by default, it is set about 2.5 MB. It means that NCACHE_REGION + modeldata should be less than (5.5 - 2.5) = 3 MB. My model size is about 3.5 MB. Beside that I can locate my model on external memory (it results in larger inference time), how I can config memory to still locate my model (3.5 MB) on memory area that NPU can access? I am curious about whether we can shrink "SRAM" region (in the images 1, 2) or can I move it to another area of RAM (7.5 - 5.5 = 2 MB - the last region in the image 3)? And how I can estimate the size of "SRAM" region? In the below image, it is 15560 B. Sorry for my long questions. nnxxpp_0-1782205318606.png nnxxpp_1-1782205742121.png nnxxpp_2-1782206037185.png Re: Why model size is limited at 1 MB? @mayliu1  Good morning. Maybe you missed my new above questions.  Re: Why model size is limited at 1 MB? Hi @nnxxpp , Apologies for the delayed response. If you don’t mind, could you please create a new case for your new issue?  Thank you for your understanding and cooperation. Best Regards, May Re: Why model size is limited at 1 MB? @mayliu1  Yes, ok. Let me create new issue. Thank you. Re: Why model size is limited at 1 MB? @mayliu1  I have resolved my problem. We can locate SRAM outof 5.5 MB area for NPU. I locate modeldata and kTensorArena in area 5.5 MB and it worked. The inference time is good. But If you did not miss my questions, so I can finish soon my tasks. Thank you. Re: Why model size is limited at 1 MB? Yes. Have a nice day. Re: Why model size is limited at 1 MB? Glad to hear that your issue has been resolved. Apologies for the delayed response,   thank you for your understanding.

i.MX RT700 开发套件对 VIT 语音到意图（S2I）功能的支持 您好，NXP团队， 我正在评估 VIT 的语音到意图（S2I）解决方案，用于在 i.MX RT700 开发套件上实现自然语言语音控制。 在查看 VIT S2I 文档和支持的设备信息时，我注意到 i.MX RT700 没有明确列在 S2I 自然语言模型支持的设备/示例中。不过，RT700 搭载了 HiFi4 DSP 和 NPU，这两者似乎非常适合语音 AI 应用。 请问能否就以下问题进行说明？ i.MX RT700 EVK 是否正式支持 VIT 语音转意图 (S2I) 引擎？ 如果是，是否有适用于 RT700 的参考示例、SDK 包或移植指南？ 如果 RT700 目前不支持 S2I，未来是否有计划添加该功能？ 对于 i.MX RT700 平台，您会推荐哪些由 NXP 支持的自然语言理解（NLU）或语音转意图解决方案？ 目前，我可以看到VIT Wake Word和Voice Command技术支持多台i.MX RT设备，但我特别感兴趣的是基于自然语言/意图的语音控制，而不是固定命令识别。 感谢您的指导。 Re: VIT Speech-to-Intent (S2I) Support on i.MX RT700 EVK 你好@suhas1503， 对于语音转意图解决方案，推荐的软件包是 VIT。 有关支持的设备的更多信息以及有关VIT语音转意图的一般问题，请联系当地的恩智浦代表或发送电子邮件至 [email protected]。 顺祝商祺！ 巴勃罗

i.MXRT1176 DQSなしの最大NORフラッシュ速度 パフォーマンスの問題が発生しているため、FlexSPI2に接続されたシリアルNORの速度制限についてより深く理解しようとしています。 1060シリーズのナレッジベース記事によると、DQSピンを使用せずにFlexSPIを使用すると、serialClkFreqが60MHzに制限されるようです。 しかし、RT1176に関しては、SDRモードで100MHzのNORフラッシュを問題なく動作させることに成功したが、120MHzでは起動に失敗した。 同様に、DDRは50MHzでは動作するが、60MHzでは動作しない。 セクション「30.3.17.2 クロックソースの受信機能」では、DQSピンを使用しない場合の最大周波数は「最低」であるとだけ記載されています。 1060シリーズのナレッジベース記事に記載されているように、インターフェースは60MHzに制限されているのでしょうか？それとも、SDRモードで100MHzで動作させることは仕様の範囲内なのでしょうか？それとも、DDRモードを50MHzで動作させた方が良いのでしょうか？ DQSを使わずにパフォーマンスを最適化するためのヒントはありますか？ https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/Everything-you-need-to-know-about-DQS-pin-on-FlexSPI-and-SEMC/ta-p/1977399 Re: i.MXRT1176 Max NOR flash speed without DQS こんにちは、 @anbn さん。 NXP MIMXRTシリーズにご関心をお寄せいただきありがとうございます！ MCR0[RXCLKSRC]=0x0 が使用されている場合（内部ループバック、DQSピンは使用されていない）、データシートの制限はSDRモードで60MHz、DDRモードで30MHzです。したがって、このモードでは、100MHz SDRは公表されている仕様の範囲内ではありません。 リファレンスマニュアルでは、 RXCLKsrc=0x0 「最低」、 RXCLKsrc=0x1 「中」と表記していますが、実際の周波数制限値はデータシートに記載されています。データシートでは、 RXCLKsrc=0x0 には 60 MHz SDR / 30 MHz DDR、 RXCLKsrc=0x1 には 133 MHz SDR が指定されています。 FlexSPI2のセカンダリピングループを使用する場合、そのピングループにはDQSパッドが提供されないため、ROMブートは低速読み出しのみをサポートします。したがって、このピンオプションは高性能なXiP/ブート動作には適していません。 したがって、現在お使いのボード接続に利用可能なDQSパッドがない場合は、60MHz SDR / 30MHz DDRとして評価する必要があります。仕様内でより高い読み取り性能が必要な場合は、DQSが使用可能なピン グループを使用し、 RXCLKsrc=0x1 を構成することが推奨される方法です。 よろしくお願いします、 ギャビン

emiOS GPT 中断未触发（EDGE COUNTER + GPT 配置） 您好， 我正在使用 RTD 6.0.0 处理 S32K344。 我的要求是测量输入 PWM 频率（0 Hz 至 ~10 kHz），以便计算速度。 为此，我在 EDGE COUNTER 模式下使用 eMIOS ICU，以避免每个边沿中断并减少 CPU 负载，并将 eMIOS GPT 作为周期性定时器（100 毫秒或 1 秒），在 GPT 回调中读取边沿计数并计算频率，目的是只使用一个中断（GPT）。   但是，尽管 GPT 计时器似乎配置正确，但中断并未触发 —— emios0_0_irqHandler () 从未被调用，也没有执行 gpt_emiosNotification () 回调。 我附上我的配置以供参考。 能否请您帮忙找出可能遗漏或不正确的地方？   此外，如果能就如何在 S32K3 上精确测量 0-10 kHz 范围内的 PWM 频率（尤其是包括极低频）的最佳方法提出建议，我将不胜感激。 我已经尝试过其他模式，如 ICU_MODE_SIGNAL_MEASUREMENT、ICU_MODE_SIGNAL_EDGE_DETECT 和时间戳模式，但仍面临计数器溢出（16 位限制 ~65535）和极低频率下读数不准确等问题。 预先致谢 Re: eMIOS GPT interrupt not triggering (EDGE COUNTER + GPT configuration) 你好@kapidlitap 关于您的配置，我有几点看法： 您正在将 eMIOS0 通道 0 配置为 GPT。但是，在中断控制器 (intCtrl_IP) 中，你启用了 emios0_0_IRQN 并分配了处理程序 emios0_0_IRQHandler。这与配置通道相关的中断不一致。 根据 S32K344_COMMON.h 中定义的 Interrupt_vector_numbers，映射如下： EMIOS0_0_IRQn = 61, /**< Interrupt request 23,22,21,20 */ EMIOS0_1_IRQn = 62, /**< Interrupt request 19,18,17,16 */ EMIOS0_2_IRQn = 63, /**< Interrupt request 15,14,13,12 */ EMIOS0_3_IRQn = 64, /**< Interrupt request 11,10,9,8 */ EMIOS0_4_IRQn = 65, /**< Interrupt request 7,6,5,4 */ EMIOS0_5_IRQn = 66, /**< Interrupt request 3,2,1,0 */ 根据这一映射，eMIOS0 通道 0 属于中断组 EMIOS0_5_IRQn，而不是 EMIOS0_0_IRQn。因此，应使用正确的中断配置： IRQn：EMIOS0_5_IRQn 处理程序：EMIOS0_5_IRQHandler（请参阅 Emios_Mcl_Ip_Irq.c）。 关于输入捕获，有几个可用的示例。请查看并选择最符合您预期功能的选项。 使用 EMIOS DS3.5 RTD300 的 IP S32K312 PWM ICU 示例 示例：S32K312 EMIO PWM 生成及使用中断捕获占空比 (DS3.5 RTD300) 示例 IP S32K312 EMIO PWM Generation & 使用轮询进行占空捕获 DS3.5 RTD300 带 DMA S32DS 3.6.2 的 S32K344 eMIOS Icu 示例RTD 6.0.0 BR、VaneB

FRDM-IMX93 预制图像 大家好， 以下图片有何不同？我找不到更新日志文件。我需要将我的 FRDM-imx93 主板恢复为出厂设置。 谢谢！ Screenshot from 2026-06-10 15-52-23.png Re: FRDM-IMX93 prebuilt images 您好 ，它们之间的变化微乎其微，我建议您使用 Linux 电路板支持包 版本，因为 FRDM 版本是我们在集成之前获得的初始软件支持。 https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applications-processors:IMXLINUX 此致， 阿尔多。

请问guider的table控件怎样在guider软件里调整每个单元格的宽度？ 我在使用table控件时，在guider界面没找到调整每个单元格的宽度的按钮或输入框。请问应该怎样在设计时调整单元格宽度？ Re: 请问guider的table控件怎样在guider软件里调整每个单元格的宽度？ Hi @alen-liao  您好，您可以尝试修改这个参数。 Harry_Zhang_0-1781158999778.png BR Harry

IW611：无法设置 Linux 驱动程序 您好， 我正在尝试用 Linux 内核 4.19 启动 IW611。我使用的是 mwifiex 分支 if-6.12.49_2.20。 配置文件包含以下内容： SDIW612 = { cal_data_cfg=none hw_name=IW611 fw_name=nxp/sduart_nw61x_v1.bin drv_mode=0x1 auto_ds=2 pm_keep_power=1 cntry_txpwr=0 slew_rate=0 } 芯片被 MMC 总线驱动程序识别，nwifiex 驱动程序已加载。但当我尝试启动 mlan0 接口时，却出现了写入错误。谁能告诉我是什么地方配置错误或出错了？ 下面是我的 dmesg 输出： [8.423408] wlan：正在加载 MWLAN 驱动程序 [8.427639] 未指定模块参数 cfg 文件 [8.632441] wlan：注册到总线驱动程序... [8.666463] vendor=0x0471 device=0x0205 class=0 function=1 [8.711324] Attach moal handle ops，卡接口类型：0x109 [8.764392] SDIW612：来自用户的初始化模块参数 [8.769688] cal_data_cfggs：SDIW612，配置块：0 [8.774488] cal_data_cfggg =无 [8.777622] hw_name=iw611 [8.780414] fw_name=nexp/sduart_nw61x_v1.bin [ 8.784838] drv_mode = 1 [ 8.787512] auto_ds = 2 [ 8.790109] pm_keep_power on [ 8.793152] cntry_txpwr = 0 [ 8.796102] slew_rate = 0 [ 8.798916] SDIO: sdio_blk_size=256 max_blk_count=65535 max_segs=64 max_seg_size=65536 [ 8.807287] rx_work=0 cpu_num=1 [ 8.810624] Enable moal_recv_amsdu_packet [ 9.101160] Attach mlan adapter operations.card_type is 0x109. [ 9.118472] wlan：启用 TX SG 模式 [ 9.122181] wlan: mpa_tx.buf_size=65280 [ 9.126231] wlan：启用 RX SG 模式 [ 9.129954] wlan: mpa_rx.buf_size=65280 [ 9.261877] 请求固件：nxp/sduart_nw61x_v1.bin [ 10.067400] Wlan：FW 下载结束，firmwarelen=913892 已下载 837692 [ 10.467947] WLAN FW 处于活动状态 [ 10.471106] on_time is 10463342042 [ 10.494983] VDLL 映像：len=76200 [ 10.498741] fw_cap_info=0x487cff03, dev_cap_mask=0xffffffff [ 10.504665] uuid: e139b70377da5b6fbc71c709b955b9a7 [ 10.509761] max_p2p_conn = 8, max_sta_conn = 16 [ 10.529596] IOCTL failed: 1b0efb8f id=0x200000, sub_id=0x200046 action=1, status_code=0x3 [FW_CMDRESP] [ 10.544554] Register NXP 802.11 Adapter mlan0 [ 10.549385] wlan: version = SDIW612---18.99.2.p19.10-MM6X18540.p33-GPL-(FP92) [10.567328] 设置 REG 0x90002328：0x10d57 slew_rate=0 [10.576793] usbcore：注册了新的接口驱动程序 usbxxx [10.584854] wlan：注册到总线驱动程序完成 [10.589480] wlan：驱动程序已成功加载 这里我尝试启动 mlan0 [ 76.346952] cmd53 write error=-110 [ 76.353352] host_too_card, write iomem (1) failed: -1 [ 76.359014] write CFG reg failed [ 76.362560] cmd53 write error=-110 [ 76.366184] host_too_card, write iomem (2) 失败：-1 [ 76.371495] write CFG reg 失败 [ 76.374999] cmd53 write error=-110 [ 76.402254] host_too_card, write iomem (3) 失败：-1 [ 76.407537] write CFG reg 失败 [ 76.410971] Error: host_to_card failed: 0xFFFFFFFF [ 76.416043] DNLD_CMD: Host to Card Failed [ 76.420306] IOCTL failed: ef7a4e76 id=0x90000, sub_id=0x90001 action=1, status_code=0x80000006 [CMD_DNLD_FAIL] [ 76.430903] ------------Dump info----------- [ 76.435415] Command to card failure [ 76.439111] pending command id: 0x10 ioctl_buf= (null) [ 76.444634] pending command id: 0x28 ioctl_buf=a69aa9f8 [ 76.450155]没有待执行的扫描命令 [ 76.453847] CurCmd 空 [ 76.456521] mlan_processing =1 [ 76.459753] main_lock_flag =0 [ 76.462885] main_process_cnt =75 [ 76.466292] delay_task_flag =0 [ 76.469523] mlan_rx_processing =0 [ 76.473022] rx_pkts_queued=0 [ 76.476061] more_task_flag = 0 [ 76.479292] num_cmd_timeout = 0 [ 76.482607] last_cmd_index = 2 [ 76.485830] last_cmd_id = [ 76.485834] 0x27c [ 76.488698] 0x27c [ 76.490818] 0x243 [ 76.492938] 0xe4 [ 76.495058] 0x5b [ 76.497086] 0x242 [ 76.499123] 0x4d [ 76.501243] 0xd1 [ 76.503271] 0x10 [ 76.505299] 0x28 [ 76.510935] last_cmd_act = [ 76.510937] 0x0 [ 76.513885] 0x1 [ 76.515821] 0x0 [ 76.517757] 0xff [ 76.519704] 0x1 [ 76.521732] 0x1 [ 76.523668] 0x1 [ 76.525604] 0x0 [ 76.527540] 0x1 [ 76.529486] 0x213 [ 76.535109] last_cmd_resp_index = 2 [ 76.538799] last_cmd_resp_id = [ 76.538802] 0x827c [ 76.542117] 0x827c [ 76.544329] 0x8243 [ 76.546540] 0x805b [ 76.548761] 0x805b [ 76.550973] 0x8242 [ 76.553185] 0x804d [ 76.555396] 0x80d1 [ 76.557608] 0x8010 [ 76.559828] 0x8028 [ 76.565819] last_event_index = 1 [ 76.569233] last_event = [ 76.569236] 0x0 [ 76.571999] 0x81 [ 76.573936] 0x0 [ 76.575963] 0x0 [ 76.577907] 0x0 [ 76.579844] 0x0 [ 76.581780] 0x0 [ 76.583716] 0x0 [ 76.585652] 0x0 [ 76.587587] 0x0 [ 76.593035] num_data_h2c_failure = 0 [ 76.596809] num_cmd_h2c_failure = 1 [ 76.600500] num_data_c2h_failure = 0 [ 76.604275] num_cmdevt_c2h_failure = 0 [ 76.608241] num_int_read_failure = 0 [ 76.612015] last_int_status = 64 [ 76.615422] num_alloc_buffer_failure = 0 [ 76.619572] num_pkt_dropped = 0 [ 76.622888] num_noo_cmd_node = 0 [ 76.626202] num_event_deauth = 0 [ 76.629617] num_event_disassoc = 0 [ 76.633208] num_event_link_lost = 0 [ 76.636890] num_cmd_deauth = 0 [ 76.640121] num_cmd_assoc_success = 0 [ 76.643987] num_cmd_assoc_failure = 0 [ 76.647860] num_cons_assoc_failure = 0 [ 76.651818] cmd_resp_received=0 [ 76.655133] event_received=0 [ 76.658180] max_tx_buf_size=4096 [ 76.661587] tx_buf_size=3072 [ 76.664626] curr_tx_buf_size=3072 [ 76.668134] data_sent=0 cmd_sent=0 [ 76.671725] ps_mode=1 ps_state=0 [ 76.675133] wakeup_dev_req=0 wakeup_tries=0 wakeup_timeout=0 [ 76.681121] hs_configured=0 hs_activated=0 [ 76.685448] pps_uapsd_mode=0 sleep_pd=0 [ 76.689506] tx_lock_flag = 0 [ 76.692545] scan_processing = 0 [ 76.695859] scan_state = 0x0 [ 76.698907] bypass_pkt_count=0 [ 76.702132] mp_rd_bitmap=0x0 curr_rd_port=0x0 [ 76.706734] mp_wr_bitmap=0xffffff curr_wr_port=0x0 [ 76.711987] mp_data_port_mask = 0xffffff [ 76.716314] last_recv_rd_bitmap=0x0 mp_invalid_update=0 [ 76.721843] last_recv_wr_bitmap=0xffffffff last_mp_index=0 [ 76.727641] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 76.734364] 0x00 [ 76.734367] 0x00 [ 76.736395] 0x00 [ 76.738432] 0x00 [ 76.740460] 0x00 [ 76.742488] 0x00 [ 76.744516] 0x00 [ 76.746543] 0x00 [ 76.748580] 0x00 [ 76.750609] 0x00 [ 76.752637] 0x00 [ 76.754665] 0x00 [ 76.756692] 0x00 [ 76.758729] 0x00 [ 76.760757] 0x00 [ 76.762785] 0x00 [ 76.768417] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 76.775131] 0x00 [ 76.775133] 0x00 [ 76.777162] 0x00 [ 76.779199] 0x00 [ 76.781227] 0x00 [ 76.783255] 0x00 [ 76.785283] 0x00 [ 76.787311] 0x00 [ 76.789348] 0x00 [ 76.791376] 0x00 [ 76.793404] 0x00 [ 76.795437] 0x00 [ 76.797465] 0x00 [ 76.799502] 0x00 [ 76.801531] 0x00 [ 76.803559] 0x00 [ 76.809192] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 76.815906] 0x00 [ 76.815908] 0x00 [ 76.817944] 0x00 [ 76.819973] 0x00 [ 76.822001] 0x00 [ 76.824029] 0x00 [ 76.826057] 0x00 [ 76.828093] 0x00 [ 76.830121] 0x00 [ 76.832149] 0x00 [ 76.834177] 0x00 [ 76.836205] 0x00 [ 76.838241] 0x00 [ 76.840269] 0x00 [ 76.842297] 0x00 [ 76.844325] 0x00 [ 76.849957] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 76.856671] 0x00 [ 76.856673] 0x00 [ 76.858711] 0x00 [ 76.860739] 0x00 [ 76.862774] 0x00 [ 76.864803] 0x00 [ 76.866831] 0x00 [ 76.868868] 0x00 [ 76.870897] 0x00 [ 76.872925] 0x00 [ 76.874953] 0x00 [ 76.876981] 0x00 [ 76.879018] 0x00 [ 76.881046] 0x00 [ 76.883074] 0x00 [ 76.885102] 0x00 [ 76.890734] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 76.897448] 0x00 [ 76.897451] 0x00 [ 76.899488] 0x00 [ 76.901516] 0x00 [ 76.903544] 0x00 [ 76.905572] 0x00 [ 76.907599] 0x00 [ 76.909636] 0x00 [ 76.911665] 0x00 [ 76.913693] 0x00 [ 76.915721] 0x00 [ 76.917749] 0x00 [ 76.919785] 0x00 [ 76.921813] 0x00 [ 76.923841] 0x00 [ 76.925869] 0x00 [ 76.931501] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 76.938223] 0x00 [ 76.938226] 0x00 [ 76.940254] 0x00 [ 76.942282] 0x00 [ 76.944310] 0x00 [ 76.946337] 0x00 [ 76.948374] 0x00 [ 76.950402] 0x00 [ 76.952430] 0x00 [ 76.954457] 0x00 [ 76.956485] 0x00 [ 76.958521] 0x00 [ 76.960550] 0x00 [ 76.962578] 0x00 [ 76.964605] 0x00 [ 76.966633] 0x00 [ 76.972265] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 76.978987] 0x00 [ 76.978990] 0x00 [ 76.981018] 0x00 [ 76.983046] 0x00 [ 76.985074] 0x00 [ 76.987102] 0x00 [ 76.989138] 0x00 [ 76.991167] 0x00 [ 76.993195] 0x00 [ 76.995222] 0x00 [ 76.997250] 0x00 [ 76.999286] 0x00 [ 77.001315] 0x00 [ 77.003343] 0x00 [ 77.005371] 0x00 [ 77.007399] 0x00 [ 77.013031] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 77.019753] 0x00 [ 77.019756] 0x00 [ 77.021784] 0x00 [ 77.023812] 0x00 [ 77.025840] 0x00 [ 77.027876] 0x00 [ 77.029905] 0x00 [ 77.031940] 0x00 [ 77.033969] 0x00 [ 77.035997] 0x00 [ 77.038033] 0x00 [ 77.040062] 0x00 [ 77.042090] 0x00 [ 77.044118] 0x00 [ 77.046145] 0x00 [ 77.048182] 0x00 [ 77.053806] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 77.060529] 0x00 [ 77.060531] 0x00 [ 77.062560] 0x00 [ 77.064587] 0x00 [ 77.066615] 0x00 [ 77.068652] 0x00 [ 77.0x00 [ 77.072708] 0x00 [ 77.074736] 0x00 [ 77.076764] 0x00 [ 77.078801] 0x00 [ 77.080829] 0x00 [ 77.082857] 0x00 [ 77.084884] 0x00 [ 77.086912] 0x00 [ 77.088949] 0x00 [ 77.094572] mp_wr_bitmap：0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 77.101295] 0x00 [ 77.101297] 0x00 [ 77.103326] 0x00 [ 77.105354] 0x00 [ 77.107381] 0x00 [ 77.109418] 0x00 [ 77.111446] 0x00 [ 77.113474] 0x00 [ 77.115502] 0x00 [ 77.117529] 0x00 [ 77.119566] 0x00 [ 77.121595] 0x00 [ 77.123623] 0x00 [ 77.125650] 0x00 [ 77.127678] 0x00 [ 77.129715] 0x00 [ 77.135341] bss_index = 0, tx_pkts_queued = 0 tx_pause [ 77.140796] Host:chillair-r1234yf-00050 Timestamp:9c6953b9 [ 77.146691] Driver version = SDIW612---18.99.2.p19.10-MM6X18540.p33-GPL-(FP92) [ 77.154431] main_state = 3 [ 77.157287] ioctl_pending = 1 [ 77.160428] tx_pending = 0 [ 77.163285] wmm_tx_pending[0] = 0 [ 77.166783] wmm_tx_pending[1] = 0 [ 77.170291] wmm_tx_pending[2] = 0 [ 77.173790] wmm_tx_pending[3] = 0 [ 77.177288] rx_pending = 0 [ 77.180152] lock_count = 44 [ 77.183100] malloc_count = 49 [ 77.186231] mbufalloc_count = 0 [ 77.189554] hs_skip_count = 0 [ 77.192685] hs_force_count = 0 [ 77.195909] Media state ="Disconnected" [ 77.200059] carrier off [ 77.202641] tx queue 0: stopped [ 77.205956] tx queue 1: stopped [ 77.209279] tx queue 2: stopped [ 77.212595] tx 队列 3: stopped [ 77.215911] mlan0: num_tx_timeout = 0 [ 77.219799] -------- Dump info End--------- [ 77.237865] IPv6: ADDRCONF(NETDEV_UP): mlan0: link is not ready [ 77.270404] SDIO Func0 (0x0-0x9)：ERR [ 77.274349] SDIO Func1 (0x10-0x17)：ERR [ 77.278454] SDIO Func1: (0x8) ERR [ 77.282147] SDIO Func1 (0xe8-0xff)：ERR [ 77.387444] SDIO Func1 (0xe8-0xff)：ERR [ 77.391567] set pending clean [ 77.471612] SDIO Write ERR [ 77.474573] SDIO Write ERR [ 77.477436] ==== DEBUG MODE OUTPUT START: 77.469673 ==== [ 77.483111] SDIO Write ERR [ 77.485995] SDIO Write ERR [ 77.488871] ==== DEBUG MODE END ==== [ 77.492866] IOCTL 失败： a69aa9f8 id=0x20000, sub_id=0x20007 action=1, status_code=0x80000007 [CMD_CANCEL] (CMD_CANCEL) Re: IW611: Unable to setup Linux driver 你好@mlytvyn 您能试试 50MHz 的频率吗？ 顺祝商祺！ 肖恩 Re: IW611: Unable to setup Linux driver 我有 TI Sitara AM4376。 image.png image.png MMC 总线配置如下：   &mmc3 { status = "okay"; dmas = <&edma_xbar 30 0 1>, <&edma_xbar 31 0 2>; dma-names = "tx", "rx"; pinctrl-names = "default", "sleep"; pinctrl-0 = <&mmc3_pins_default>; pinctrl-1 = <&mmc3_pins_sleep>; vmmc-supply = <&dcdc4>; bus-width = <4>; cap-sdio-irq; ti,non-removable; max-frequency = <25000000>; /* slow down to 25MHz for bring-up */ }; MMC 总线控制器设法检测到 Wi-Fi 芯片，内核加载了正确的驱动程序，驱动程序使用提供的固件 blob 闪存了芯片，并从芯片中获得了固件版本。对我来说，这不像是 SDIO 配置问题，而像是与驱动程序（或 FW）有关的问题。 第一个错误发生在这里 [ 10.529596] IOCTL 失败： 1b0efb8f id=0x200000, sub_id=0x200046 action=1, status_code=0x3 [FW_CMDRESP] 司机在这个阶段要做什么？ 顺祝商祺！ 米哈伊洛 Re: IW611: Unable to setup Linux driver 你好@mlytvyn 您使用的是哪台主机？ 驱动程序加载和固件下载没有问题。 sdio 通信报告错误。 顺祝商祺！ 肖恩 Re: IW611: Unable to setup Linux driver 您好， 变化不大 mlytvyn_0-1780995812806.png 在这里，我启动了 mlan0，然后得到 mlytvyn_2-1780995954838.png mlytvyn_1-1780995851394.png 我遇到了同样的错误 IOCTL failed: 61e24fe7 id=0x200000, sub_id=0x200046 action=1, status_code=0x3 [FW_CMDRESP] 失败 Re: IW611: Unable to setup Linux driver 你好@mlytvyn 能否告诉我们您使用的是哪种 iw612 模块？还是您正在使用 iw612evk？我注意到你的 sd 接口是 3.3V，你匹配了 sdio 功率级吗？ 顺祝商祺！ 肖恩 Re: IW611: Unable to setup Linux driver 我使用的是 Silex SX-SDMAX 表面贴装版（https://www.silextechnology.com/connectivity-solutions/embedded-wireless/sx-sdmax）。据我所知，VIO 和 VIO_SD 上的电压决定了信号电平。 

S32K344（PMSMモーター）の例に関する質問 おはよう、 私は御社のFRDM評価ボードをGD3000パワードライバーとSunriseモーターと組み合わせて使用しています。私は、こちらのリンクからあなたの同僚の一人が示した手順に従ってみました。 https://github.com/nxp-appcodehub/an-mc-pmsm-foc-2sh-s32k344 まず、基板は2枚あります。1枚はGD3000モータ・ドライバ、もう1枚はFRDM-S32K344評価ボードです。システムに電源を供給するには、GD3000ドライバを介して12V電源を接続する必要がありますが、FRDMボード上のスイッチはオフにしておく必要があります。システムの電源を入れた後、Freemasterインターフェースに接続するには、スイッチを「オン」にする必要がありますか？それとも、システムに損傷を与えることなくインターフェースと通信する方法はありますか？ よろしくお願いいたします Re: Question about a example of S32K344 (Motor PMSM) こんにちは、 @JonAnder_Amante さん。 ドキュメントの「ハードウェアの接続」セクションによると、2枚のボードを使ったセットアップは以下のようになります。 12V電源はGD3000基板を介して接続する必要があります。 デバッグと通信を有効にするには、USB Type-CケーブルをFRDMボードに接続する必要があります。 注意すべき点は、K344MINIは3.3Vで動作するのに対し、モーターコントローラーボードは5Vで動作するということです。コード内には、5Vと3.3Vの動作電圧を切り替えることができるソフトウェアスイッチ（SWトリガー）があります。 BR、VaneB

S32 Design Studio ARMライセンスの更新／延長 こんにちは、NXP チームの皆様、 S32 Design StudioのARMライセンスを延長したいです。 有効期限： 2026年5月26日 アクティベーションコード： 75C4-1E5C-1D9D-F005 ありがとうございます サティシュ Re: S32 Design Studio ARM License Renewal / Extention こんにちは、 お客様のS32DSライセンスが延長されました。 Re: S32 Design Studio ARM License Renewal / Extention 延長していただきありがとうございます。ご支援ありがとうございます。