NAFE13388 水晶の仕様 RIOP RevB2では、NAFE13388 XTAL（X1、18.432 MHz）にどの水晶発振器仕様（ppm/負荷）を使用していますか？ Re: NAFE13388 crystal spec こんにちは、 部品番号: ECS-184-12-33Q-JES-TR PPM：20 PPM 負荷: 12 pF これがお役に立てば幸いです。

我能否使用任意一个 GPIO 引脚作为中断输入信号，并使其在边沿检测模式下工作？ 你好， 因为 6 个专用 IRQ(0~5) 引脚对我来说不够用，我需要其他 GPIO 引脚作为中断输入信号。所以，我有以下两个问题： 1. 是否可以将任意 GPIO 用作中断信号输入，并使其工作在边沿检测模式下？ 2. 如果上述第 1 题的答案是肯定的，那么专用 IRQ 和 GPIO 之间有什么区别？或许响应优先级更高？ 提前感谢！ 顺祝商祺！ 杰森

Wi-Fi 命令响应超时 我正在使用基于恩智浦 IW612 芯片组的 i.MXRT1062 跨界微控制器和村田 2EL M.2 无线卡开发一个项目。该项目使用了 MCUXpresso SDK 和 FreeRTOS。当前 SDK 版本为 25.12。 在固件运行过程中，调试控制台有时会显示以下输出： `[wifi] 警告：命令响应超时。命令 0x0，长度 1514，序列号 0x16` 或 `[wifi] 警告：命令响应超时。命令 0x0，长度 66，序列号 0x16` 或 `[wifi] 警告：命令响应超时。命令 0x0，长度 190，序列号 0x16` 或 `[wifi] 警告：命令响应超时。命令 0x0，长度 60，序列号 0x16` 我不知道这些行是什么意思，可能是无线模块出了问题。打印任务列表之后，会触发紧急情况并使固件停止运行。我认为这个问题通常发生在通过无线网络连接进行流量大小不一的传输约30分钟后。 SDK 文件中的相应位置位于 `wifi_wait_for_cmdresp` 函数中的 `中间件/wifi_nxp/wifidriver/wifi.c` 中。这一点还进一步得到证实：在之前的调试控制台输出与这一行之间，大约有20秒的间隔。 我该如何排查这个问题？我可以与您合作，提供进一步的调试信息或测试 SDK 的修复方案。 Re: Wi-Fi command response timeout 您好， 我知道您正在使用一个自定义应用程序，但您是以哪个 SDK 示例作为起点开发的？如果您能使用未经修改的 SDK 示例重现相同的问题，这将极大有助于定位问题。 看来驱动程序一直在等待命令响应，但在超时结束前并未收到响应。 请在 wifi_config.h 中启用以下调试宏： CONFIG_WIFI_CMD_RESP_DEBUG CONFIG_WIFI_EVENTS_DEBUG CONFIG_WIFI_IO_INFO_DUMP CONFIG_WIFI_EXTRA_DEBUG 启用宏后，请重新编译示例并再次进行测试。请分享输出结果。 最好用最新的 SDK 进行测试，看看问题是否依然存在。 Re: Wi-Fi command response timeout 这是固件卡住时的调试输出。如果您需要之前的日志行，请告诉我。 2026年6月23日 12:27:48.808 [RX] - [wifi] 警告：命令响应超时。命令 0x0，长度 890，序列号 0x16 SDIO多端口组寄存器值： **** 转储 @ 20218FC0 长度：196 **** 00 00 00 00 ff 00 00 00 c3 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 7f 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 03 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 00 00 00 00 00 87 0c 00 00 00 00 00 00 00 00 00 00 1c c2 06 c0 f4 德 09 c0 00 1e ff ff 00 0a 36 01 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff 00 00 00 00 00 00 00 00 ff ff ff ff 00 00 00 00 00 00 00 00 10 cc f0 ff ff ff ff ff 00 00 ff ff ff ff ff ff f4 74 04 c0 80 98 04 c0 00 00 00 00 ******** 结束转储 ******* 名称 状态 优先级 堆栈号 ================================================== 主任务 X 3 581 6 print_dhcp R 0 683 17 空闲 R 0 92 2 tcp/ip B 3 400 1 Tmr Svc B 4 196 3 supplicant_main_tas B 2 1456 14 nfc_cfg B 0 715 7 dhcpd_task B 3 406 15 HTTP 服务器 B 1 888 18 wifi_scan_task B 1 255 11 wlcmgr_task B 3 244 13 wifi_drv_task B 3 228 10 lwip_rx B 3 431 8 wifi_core_task B 3 276 12 [wifi] 开始处理挂起 [wifi] 正在发起 wifi 身份验证 [固件下载] S 2026年6月23日 12:27:48.824 [RX] - 开始从 0x602319fc 下载固件：1618224 2026年6月23日 12:27:54.807 [RX] - [wifi_io] 错误：SDIO - 固件就绪寄存器未设置 [wifi] 错误：sd_wifi_reinit 失败。状态码-1 断言：wlan_process_hang：550 断言失败：恐慌！ 断言错误“0”：文件“C:/tmp/mcuxsdk/mcuxsdk/中间件/wifi_nxp/wifidriver/incl/mlan_api.h”第65行函数名“panic” Re: Wi-Fi command response timeout @DanielRuvalcaba你好，请问这个问题有任何进展吗？SDK 26.03 版本也存在这个问题，您还需要我提供更多调试信息吗？

我正在寻找 AFT05MS004NT 在 30-45 MHz 频率范围内的阻抗。 我正在寻找阻抗 AFT05MS004NT1，30-45 MHz Z负载和Z源 请各位帮帮我 Re: I am looking for the impedance of AFT05MS004NT AT FREQ 30-45 MHZ 你好， 遗憾的是，我们没有 AFT05MS004NT 在 30–45 MHz 频率范围内的阻抗数据。 获取阻抗数据需要专用的特性分析过程，该过程必须针对每个感兴趣的频率分别进行。这个过程很耗时，通常侧重于设备最初被设计并预期运行的频率范围。评估其他频率通常需要设计和建造特定的测试夹具和匹配网络。 因此，对于标准特性范围之外的工作条件（例如不同的频率、功率级或电源电压），阻抗数据并不总是可用。 由此给您带来的不便，我们深表歉意，并感谢您的理解。

MPC574xP BCTRL Hi: My customer is using MPC5741P for Auto ESC application. Currently, they were asked by the end OEM about BCTRL pin characteristics, such as voltage region.  Could you help check and confirm it? Thanks. Below is the waveform, it's triangle, and  OEM asked to add decouple Cap. on base control output pin from MCU side.  Re: MPC574xP BCTRL Datasheets recommend different transistor as you can see below: Also it needs to be properly bypassed/decoupled. Pay attention mainly to VDD_LV_COR:

FTM CnV 更新问题 2 嗨，我又遇到了一个问题，我以前问过，也解决了，是 LDOK 寄存器出了问题。 但是即使解决了这个问题它仍然没有按照我的要求进行更新 cNV 并更改 脉冲 宽度请帮帮我这是我一直在研究的代码 #include "MKE02Z4.h" #define FTM_MOD 24 // 25 ticks → 1.25us @ 20MHz #define TICKS_0 7 #define TICKS_1 14 void FTM_Init(void) { SIM->SCGC |= SIM_SCGC_FTM2_MASK; FTM2->MODE = FTM_MODE_WPDIS_MASK | FTM_MODE_FTMEN_MASK; FTM2->CNTIN = 0; FTM2->CNT = 0; FTM2->MOD = FTM_MOD; FTM2->CONTROLS[0].CnSC = FTM_CnSC_MSB_MASK | FTM_CnSC_ELSB_MASK; FTM2->CONTROLS[0].CnV = TICKS_0; /* ENABLE CHANNEL OUTPUT (CRITICAL) */ FTM2->OUTMASK &= ~(1 << 0); /* Initial load */ *(volatile __UINT32_TYPE__ *)0x4003A098 = 0x0201; FTM2->SC = FTM_SC_CLKS(1) | FTM_SC_PS(0); *(volatile __UINT32_TYPE__ *)0x4003A064 = 0x00; } static inline void wait_ftm_period(void) { while(!(FTM2->SC & FTM_SC_TOF_MASK)); FTM2->SC &= ~FTM_SC_TOF_MASK; } uint32_t word = 0x5555; int main(void) { FTM_Init(); while (1) { for(int i = 0; i < 16; i++) { if (word & (1UL << i)) *(volatile __UINT32_TYPE__ *)0x4003A010 = TICKS_1; else *(volatile __UINT32_TYPE__ *)0x4003A010 = TICKS_0; /* ARM reload for next PWM cycle */ *(volatile __UINT32_TYPE__ *)0x4003A098 = 0x0201; /* WAIT ONE PWM PERIOD */ wait_ftm_period(); } } } Re: FTM CnV Update Problem 2 你好@Jana_muralidharan]。 对不起，我有点糊涂了。你是在问如何改变 PWM 的占空比，还是在问为什么你的占空比发生了变化？   谢谢！   BR 爱丽丝 Re: FTM CnV Update Problem 2 嘿我是这篇文章的作者我正在 WS2812B 工作所以我想用 PWM 来生成信号所以为什么要改变占空比所以我想知道用这个有可能做到吗 Re: FTM CnV Update Problem 2 你好@Jana_muralidharan 请使用 FTM_UpdatePwmDutycycle() API 更新 PWM 占空比。 有关更多详细信息，请参阅 ftm_simple_pwm 演示，其中 PWM 占空比定期更新。   /*! * 简要更新有源 PWM 信号的占空比。 * * 参数基 FTM 外围设备基地址 * 参数chnlNumber 通道/通道对编号。在组合模式下，它代表 * 通道对编号 * 参数currentPwmMode PWM 设置时设置的当前 PWM 模式 * 参数 dutyCyclePercent 新 PWM 脉冲宽度；该值应介于 0 到 100 之间 * 0 = 非活动信号（0% 占空比）... * 100=有源信号（100% 占空比） * 如果 PWM 更新成功，则返回 kStatus_Success * 失败时为 kStatus_Error */ status_t FTM_UpdatePwmDutycycle(FTM_Type*base.UpdatePwmDutycycle ftm_chnl_tchnlNumber、 ftm_pwm_mode_tcurrentPwmMode、 uint8_tdutyCyclePercent)   BR 爱丽丝 Re: FTM CnV Update Problem 2 你好 @Alice_Yang ，是的我正在尝试更改每个周期的 PWM 占空比，比如第一周期的 30% 占空比然后在第二周期 70% 的占空比就像这样。 有什么程序可以改变 PWM 占空比变化吗 它只是停留在最初的设定值上 Re: FTM CnV Update Problem 2 你好@Jana_muralidharan 这取决于您的应用。您可以参考您的需求设计。 关于这个 SDK 演示，它使用定时器溢出中断来更新 PWM 占空比。 BR 爱丽丝 Re: FTM CnV Update Problem 2 但能否请您告诉我，PWM 的更新周期是多少？ Re: FTM CnV Update Problem 2 哈哈 我遇到类似的问题 经过一番折腾 最终解决了。 我在S32K144上同时改变开关频率和占空比，发现频率可以任意改变，但与其同时改变的占空比却总是变不了。最终找到了问题， 问题出在这个位FTM_SC_CLKS上。 FTM一旦初始化完成并启动后，如果想要CnV的值，必须将FTM_SC_CLKS=0，即关掉时钟源，也就是使FTM停止工作。然后再修改CnV，修改完后再FTM_SC_CLKS=1，这样就可以改变占空比了。 我想MKE02Z4和S32K144有相似的FTM，它们的工作机制应该是相同的，你不妨试试。 祝你好运！

AFT05MS004NTのインピーダンス（周波数30～45MHz）を探しています。 私はインピーダンスを探しています AFT05MS004NT1、30～45MHz用ZロードおよびZソース 皆さん、助けてください Re: I am looking for the impedance of AFT05MS004NT AT FREQ 30-45 MHZ こんにちは、 残念ながら、AFT05MS004NTの30～45MHzの周波数範囲におけるインピーダンスデータは入手できていません。 インピーダンスデータを取得するには、専用の特性評価プロセスが必要であり、対象となる周波数ごとに個別に実行しなければならない。このプロセスは時間がかかり、通常はデバイスが当初特性評価され、動作するように意図されていた周波数範囲に焦点を当てます。追加の周波数を評価するには、特定の試験用器具やマッチングネットワークの設計・構築が求められることが多いです。 このため、インピーダンスデータは、異なる周波数、電力レベル、電源電圧など、標準的な特性評価範囲外の動作条件では必ずしも入手できるとは限りません。 ご迷惑をおかけして申し訳ございません。ご理解いただけますようお願い申し上げます。

エッジ検出モードで動作したGPIOピンを割り込み入力信号として使うことはできますか? こんにちは、 専用のIRQ（0～5）ピンが6本だけでは不十分なので、他のGPIOピンを割り込み入力信号として使用する必要があります。そこで、以下に2つの質問があります。 1. エッジ検出モードで動作する割り込み信号入力として、任意のGPIOを使用可能か? 2. 上記1が「はい」の場合、専用IRQとGPIOの違いは何ですか？応答を優先すべきでしょうか？ よろしくお願いいたします！ よろしくお願いいたします！ ジェイソン

S32K3 recovery issue when install HSE fw via MU We are currently developing secure boot functionality on the S32K344/S32K314 using HSE, based on the `S32K344_Advanced_SecureBoot` demo from the `S32K3_HSE_DemoExamples`. We have completed most of the feature development and can debug through successfully. In our configuration program, we calculate signatures for the BM, FBL, and APP using ED25519, write them to specified addresses in flash, and configure the SMR and CR for these three applications (BM as pre‑boot SMR, FBL and APP as post‑boot SMR). However, we have encountered some unclear issues and would appreciate your help. We are currently using the FULL_MEM form of HSE. Because we use the ED25519 algorithm to compute signatures for all application binaries, the configuration program takes a long time to execute. If a power failure occurs unexpectedly before the program finishes, we find that HSE enters an unrecoverable error state. Neither power‑cycling nor re‑flashing the firmware makes HSE respond to any host requests anymore. By checking the register at `0x4039C028` (HSE_CONFIG_GPR3), we see the value is `0xC0`; bit 0 has become `0`, which indicates that the HSE firmware may have been erased by SBAF. After power‑up, the MU0 FSR register is also `0`. We therefore tried to re‑install the HSE firmware. Since the normal IVT‑based installation method no longer works, we attempted installation via the MU interface. We simulated the steps described in the documentation, but found that after writing the SRAM address of the Pink Image into the MU Tx register (step 5), the value in HSE_CONFIG_GPR3 immediately changes from `0xC2` back to `0xC0` – i.e., bit 1 goes from `1` to `0` – and we never receive the expected success response `0xDACACADA`. We also referred to a similar issue on the forum:S32K3_The MU installation AB_SWAP process of HSE is incorrect. . We tried performing a functional reset immediately after step 5, but after the reset the new HSE firmware still cannot be installed. Could you please advise how to handle and recover from such a corrupted HSE state? Let me know if you need any adjustments. Re: S32K3 recovery issue when install HSE fw via MU Hi @chengjinwang  I’m unable to read the source files in the project you shared because they are encrypted. Please provide a version with plain (unencrypted) files. A few days ago, I created a Trace32 script to recover the HSE AB_SWAP firmware via the MU interface, so I quickly modified it for the FULL_MEM version. It works on my side - I receive the 0xDACACADA response. Do you wait approximately 1.5 seconds after writing the pink image location before performing any further actions? This delay is not explicitly mentioned in the FULL_MEM installation procedure, but it is required for the AB_SWAP version. This could be the issue. If you are using Trace32, let me know and I can share my script. Regards, Lukas Re: S32K3 recovery issue when install HSE fw via MU Here is the recovery program I'm using for HSE FW installation through MU; could you take a look and see what's wrong? Re: S32K3 recovery issue when install HSE fw via MU The attached file is the unencrypted version of the project I am currently using. For my tests, I am using the S32K344 chip, a PE debugger, and the S32DS project in the attachment. I tried waiting a few seconds after writing the Pink image to receive a successful response from SBAF, but that did not work either. Performing a functional reset directly also did not work. Could you please check if there are any issues with my MU installation routine in the attached project? Re: S32K3 recovery issue when install HSE fw via MU I tested the project on my board. First, I had to fix RAM initialization in startup files because I got hardfault when the pink file was copied to RAM. The RAM initialization is not the best one in these HSE demo examples, so I did quick fix like this: Pemicro debugger initializes the RAM automatically and RAM content is retained over functional resets, so you probably did not see this issue. But it would not work after power-on. I used Trace32 for debugging, so I saw it right at the beginning. Then I modified IVT – I removed pointer to the pink file, so it is not installed automatically after first reset and I can confirm installation via MU. And the result – I got 0xDACACADA and the firmware is installed via MU. So, the procedure is obviously correct. The question is why it does not work on your side. What is the SBAF version on your device? Please read double word at 0x4039_C020. Regards, Lukas Re: S32K3 recovery issue when install HSE fw via MU Additionally, we are currently using HSE FW version 0.2.55.0. Re: S32K3 recovery issue when install HSE fw via MU This is the result I read. Re: S32K3 recovery issue when install HSE fw via MU hello, @lukaszadrapa . I haven't resolved this issue yet. If you have any progress on your end, please let me know. Thank you. Re: S32K3 recovery issue when install HSE fw via MU Thank you! I successfully restored the HSE firmware by directly triggering a SWAP request. However, what puzzles me is that I had been using the FULL_MEM firmware all along—so why was the firmware restored via AB_SWAP in the end? Re: S32K3 recovery issue when install HSE fw via MU I’m sorry for delayed response. You have SBAF version 0.15.0 which is fully compatible with HSE firmware 0.2.55.0. There’s no problem with this. For my test, I erased the firmware completely using service HSE_SRV_ID_ERASE_FW, so there’s no valid backup in passive partition. In your case, it looks like the backup is available, so the flow may be different (not sure why this does not work). I can see in your code that swap only is not implemented. Could you try to add it to your code? This could solve the problem. Regards, Lukas Re: S32K3 recovery issue when install HSE fw via MU That’s interesting. Frankly speaking, I made a mistake – I’m jumping between a lot of customers and I was somehow under impression that you use AB_SWAP, not FULL_MEM. Otherwise I would not recommend it. I can see two possible explanations – if there’s still valid backup of the firmware, it is possible that the “swap” command works also for FULL_MEM version even if it is not described in the MU procedure for FULL_MEM. Second option is that functional resets triggered by your recovery application forced SBAF to erase the firmware completely and then the installation was successful. Not really sure, this is quite hard to reproduce and confirm...

FTM CnV更新問題2 こんにちは、別の問題があります。以前質問して解決しましたが、LDOKレジスタが間違っていました。 しかし、それを解決した後でも、私が求めていること、つまりCnVを更新してパルス幅を変更することはまだ実行されません。助けてください。これは私が取り組んでいたコードです。 #include "MKE02Z4.h" #define FTM_MOD 24 // 25 ticks → 1.25us @ 20MHz #define TICKS_0 7 #define TICKS_1 14 void FTM_Init(void) { SIM->SCGC |= SIM_SCGC_FTM2_MASK; FTM2->MODE = FTM_MODE_WPDIS_MASK | FTM_MODE_FTMEN_MASK; FTM2->CNTIN = 0; FTM2->CNT = 0; FTM2->MOD = FTM_MOD; FTM2->CONTROLS[0].CnSC = FTM_CnSC_MSB_MASK | FTM_CnSC_ELSB_MASK; FTM2->CONTROLS[0].CnV = TICKS_0; /* ENABLE CHANNEL OUTPUT (CRITICAL) */ FTM2->OUTMASK &= ~(1 << 0); /* Initial load */ *(volatile __UINT32_TYPE__ *)0x4003A098 = 0x0201; FTM2->SC = FTM_SC_CLKS(1) | FTM_SC_PS(0); *(volatile __UINT32_TYPE__ *)0x4003A064 = 0x00; } static inline void wait_ftm_period(void) { while(!(FTM2->SC & FTM_SC_TOF_MASK)); FTM2->SC &= ~FTM_SC_TOF_MASK; } uint32_t word = 0x5555; int main(void) { FTM_Init(); while (1) { for(int i = 0; i < 16; i++) { if (word & (1UL << i)) *(volatile __UINT32_TYPE__ *)0x4003A010 = TICKS_1; else *(volatile __UINT32_TYPE__ *)0x4003A010 = TICKS_0; /* ARM reload for next PWM cycle */ *(volatile __UINT32_TYPE__ *)0x4003A098 = 0x0201; /* WAIT ONE PWM PERIOD */ wait_ftm_period(); } } } Re: FTM CnV Update Problem 2 こんにちは@Jana_muralidharan ] すみません、ちょっと混乱してしまいました。PWM のデューティ サイクルを変更する方法を尋ねているのでしょうか、それともデューティ サイクルが変更された理由を尋ねているのでしょうか。   よろしくお願いします。   BR アリス Re: FTM CnV Update Problem 2 こんにちは、私はこの記事の筆者です。WS2812Bで作業しているので、PWMを使用して信号を生成することを考えました。SO、デューティサイクルを変更することについて考えていますが、これでそれが可能でしょうか？ Re: FTM CnV Update Problem 2 こんにちは@Jana_muralidharan PWM デューティ サイクルを更新するには、 FTM_UpdatePwmDutycycle() API を使用してください。 詳細については、PWM デューティ サイクルが定期的に更新される ftm_simple_pwm デモを参照してください。   /*! * brief アクティブな PWM 信号のデューティ サイクルを更新します。 * *パラメータベース FTM ペリフェラル ベース アドレス * param chnlNumber チャネル/チャネルペア番号。複合モードでは、これは * チャネルペア番号 *パラメータcurrentPwmMode PWMセットアップ中に設定された現在のPWMモード *パラメータdutyCyclePercent 新しいPWMパルス幅。値は0から100の間である必要があります。 * 0 = 非アクティブ信号 (デューティ サイクル 0%)... * 100=アクティブ信号（100%デューティサイクル） * PWM更新が成功した場合はkStatus_Successを返します * 失敗時のkStatus_Error */ status_t FTM_UpdatePwmDutycycle ( FTM_Type *base, ftm_chnl_t chnl番号、 ftm_pwm_mode_t現在のPwmモード、 uint8_tデューティサイクルパーセント)   BR アリス Re: FTM CnV Update Problem 2 こんにちは@Alice_Yang 、 はい、私はPWMデューティサイクルを毎サイクル変更しようとしています。例えば、第1周期は30%デューティサイクル、第2周期は70%デューティサイクルなどです。 PWMデューティを変更する手順はありますか？ ここでの問題は、最初に設定された値で止まってしまうことです Re: FTM CnV Update Problem 2 しかし、PWMがどのくらいの周期で更新されるのか教えていただけますか？ Re: FTM CnV Update Problem 2 こんにちは@Jana_muralidharan これはアプリケーションによって異なります。要件設計を参照できます。 この SDKs デモでは、タイマーオーバーフロー割り込みを使用して PWM デューティサイクルを更新します。 BR アリス Re: FTM CnV Update Problem 2 ハハ、私も似たような問題に遭遇して、試行錯誤の末にようやく解決しました。 S32K144では、スイッチング周波数とデューティサイクルを同時に変更してみたところ、周波数は任意に変更できるものの、同時に変更したデューティサイクルは変更できないことがわかりました。最終的に問題の原因を突き止めました。それはFTM_SC_CLKSというビットにありました。 FTMが初期化され起動したら、CnVの値を変更するには、まずFTM_SC_CLKS=0に設定する必要があります。これによりクロックソースがオフになり、FTMの動作が停止します。次にCnVを変更し、最後にFTM_SC_CLKSを再び1に設定してデューティサイクルを変更します。 MKE02Z4とS32K144は似たようなFTMを搭載していると思うので、動作原理も同じはずです。試してみてもいいかもしれません。 幸運を！

Wi-Fiコマンド応答タイムアウト 私はi.MXRT1062クロスオーバーMCUと、NXP IW612チップセットを搭載した村田製作所製2EL M.2ワイヤレスカードを使用したプロジェクトに取り組んでいます。このプロジェクトはMCUXpresso SDKとFreeRTOSを使用しています。現在のSDKバージョンは25.12です。 ファームウェアの動作中に、デバッグコンソールに次のような出力が表示されることがあります。 `[wifi] 警告: コマンド応答がタイムアウトしました。コマンド 0x0、長さ 1514、シーケンス番号 0x16 または `[wifi] 警告: コマンド応答がタイムアウトしました。コマンド 0x0、長さ 66、シーケンス番号 0x16 または `[wifi] 警告: コマンド応答がタイムアウトしました。コマンド 0x0、長さ 190、シーケンス番号 0x16 または `[wifi] 警告: コマンド応答がタイムアウトしました。コマンド 0x0、長さ 60、シーケンス番号 0x16 これらの線が何を意味するのか分かりません。おそらく無線モジュールに何らかの問題があるのでしょう。その後、タスクリストが印刷され、パニックが発生し、ファームウェアが停止します。無線接続のトラフィックが多かれ少なかれ多い状態が約30分経過した後に問題が発生するようです。 SDKファイル内の対応する箇所は、`middleware/wifi_nxp/wifidriver/wifi.c`にある`wifi_wait_for_cmdresp`関数内にあります。これは、前回のデバッグコンソール出力とこの行の間に約20秒の間隔があることをさらに裏付けています。 どうすればこの問題を解決できますか？デバッグに関する追加情報を提供したり、SDKの修正をテストしたりするために、協力させていただきます。 Re: Wi-Fi command response timeout こんにちは、 カスタムアプリケーションを使用していることは理解していますが、どのSDKサンプルを起点として使用しましたか？変更を加えていないSDKのサンプルを使用して同じ動作を再現できれば、問題の特定に大いに役立ちます。 ドライバーはコマンド応答を待っていたようですが、タイムアウトになる前に応答を受信できなかったようです。 wifi_config.h ファイルで、以下のデバッグマクロを有効にしてください。 CONFIG_WIFI_CMD_RESP_DEBUG CONFIG_WIFI_EVENTS_DEBUG CONFIG_WIFI_IO_INFO_DUMP CONFIG_WIFI_EXTRA_DEBUG マクロを有効にしたら、サンプルを再構築して再度テストしてください。出力結果を共有してください。 最新のSDKを使ってテストしてみて、問題がまだ発生するかどうかを確認するのが良いでしょう。 Re: Wi-Fi command response timeout これはファームウェアがハングアップした際のデバッグ出力です。過去のログラインが必要な場合はお知らせください。 2026年6月23日 12:27:48.808 [RX] - [wifi] 警告:コマンド応答タイムアウト。指揮0x0、レン890、セクノ0x16 SDIOの複数ポートグループレジスタの値: ダンプ @ 20218FC0 レン:196 **** 00 00 00 00 FF 00 00 00 c3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0 7f 00 01 00 01 00 01 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 03 00 01 00 01 00 01 00 01 00 01 00 01 00 01 00 00 00 00 00 00 87 0c 00 00 00 00 00 00 00 00 00 00 00 1c c2 06 c0 F4 DE 09 C0 00 1E FF FF 00 0A 36 01 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF 00 00 00 00 00 00 00 00 FF FF FF 00 00 00 00 00 00 00 00 00 10 cc F0 FF FF 00 00 FF FF FF FF FF F4 74 04 c0 80 98 04 c0 00 00 00 00 ダンプ*******終了 名前 状態 優先度 スタック Num ================================================== main_task 3 581 6 print_dhcp R 0 683 17 アイドル R 0 92 2 TCP/IP B 3 400 1 Tmr Svc B 4 196 3 supplicant_main_tas B 2 1456 14 nfc_cfg B 0 715 7 dhcpd_task B 3 406 15 HTTPサーバーB 1 888 18 wifi_scan_task B 1 255 11 wlcmgr_task B 3 244 13 wifi_drv_task B 3 228 10 lwip_rx B 3 431 8 wifi_core_task B 3 276 12 [wifi] 処理開始 [wifi] wifi認証解除を開始 [FWダウンロード] S 2026/06/23 12:27:48.824 [RX] - 0x602319fc からファームウェアのダウンロードを開始: 1618224 2026/06/23 12:27:54.807 [RX] - [wifi_io] エラー: SDIO - FW Ready レジスタが設定されていません [wifi] エラー: sd_wifi_reinit が失敗しました。ステータスコード -1 ASSERT: wlan_process_hang: 550 アサート失敗: パニック! ASSERT エラー " 0 ": ファイル "C:/tmp/mcuxsdk/mcuxsdk/middleware/wifi_nxp/wifidriver/incl/mlan_api.h" 行 "65" 関数名 "panic" Re: Wi-Fi command response timeout こんにちは、@DanielRuvalcaba さん、この件について何か進展はありますか？SDK 26.03でも同じことが起きますが、もっとデバッグ情報が必要ですか?

NAFE13388 crystal spec Which crystal spec (ppm/load) does RIOP RevB2 use for the NAFE13388 XTAL (X1, 18.432 MHz)? Re: NAFE13388 crystal spec Hello, Part number: ECS-184-12-33Q-JES-TR PPM: 20 PPM Load: 12 pF Hope this helps.

Neutron Converted YOLOv8n model is not giving proper output in i.MX95 Hi there, I have exported full quantized int8 YOLOv8n Object Detection model from ultralytics. I have converted it to run on NPU using neutron converter from latest eIQ Toolkit version 1.17 and I have tried to execute it on i.MX95 hardware.  I have tried both converted and non-converted model with NPU delegate but seems like only the Neutron Graph which is present on converted model is going to execute on NPU. When I compare the raw outputs from both model, converted model is giving multiple false positives with more than 95% score. The same script I am using for both converted and non-converted model but having issue with converted model only. I have validated with multiple approaches, getting same everytime. When I have inspect both the models with netron app, I have found major architectural changes in converted model. Here, some points I want to ask is, 1. Is the lastest object detection architectures like YOLOv8 and YOLOv11 is supported on Neutron Converter with eIQ Toolkit version 1.17? If yes then what are steps you are following please let me know. 2. Do you have tested the YOLOv8 and YOLOv11 with NPU on i.MX95? If yes then can you please send the model for verification and Post-Processing steps as well. 3. If we want to execute the operations apart from Neutron Graph on Neutron NPU in i.MX95 then what is the process? 4. If we want to execute the models mentioed above on GPU in i.MX95 then what is the process? I have gone through the Machine Learning User Guide as well but haven't found related details. If you want any details from my side to debug this then feel free to ask. Thanks, Vatsal Re: Neutron Converted YOLOv8n model is not giving proper output in i.MX95 Hello, The issue you're experiencing with false positives from the Neutron-converted YOLOv8n model is a known challenge. Current support for YOLOv8 models on the i.MX95 NPU is still being optimized, and architectural changes during conversion can affect performance. Regarding your specific questions: 1. YOLOv8 architecture support in eIQ Toolkit 1.17 is still being improved. The recommended conversion workflow is: - Ensure proper int8 quantization when exporting your model - Use the latest eIQ Toolkit (v1.17) for conversion with neutron-converter - Command: `./neutron-converter --input [your-model].tflite --target imx95 --use-python-prototype` 2. While YOLOv8 is supported, it may not be fully optimized yet. YOLOv5 has shown better compatibility with current NPU implementations. The NXP team is actively working on improving YOLOv8/YOLOv11 support. 3. To execute operations beyond Neutron Graph on the NPU, you need to analyze your model with the eIQ or netron tool to identify which operators are successfully converted to run on the NPU (shown as neutronop content). Operators not converted will run on CPU. 4. For GPU execution on i.MX95, you would use the TensorFlow Lite GPU delegate instead of the NPU delegate. This requires modifying your inference code to use the GPU delegate. You can verify model operation distribution by examining the converted model in netron - any operators with "neutronop" content are executed on NPU, while others remain on CPU. Regards Re: Neutron Converted YOLOv8n model is not giving proper output in i.MX95 We have performed the training again with YOLOv5s with our custom dataset and try to do inference as you were claiming that YOLOv5 is giving good results with neutron converter in previous chat. The issue is still there with YOLOv5 as well. I am attaching the results as well for the reference. Where we tried with converted and non-converted int8 tflite YOLOv5s model.  Now, If you are claiming that YOLOv5 is giving good results then why don't you share the validated model with us. Please share all steps you are following from export, quantization to convert and what are the steps you are following for post-processing as well. So that we can validate your model and replicate the steps you have followed at our end. Please share you benchmarking and profiling data with i.MX95 as well if you can share.  Re: Neutron Converted YOLOv8n model is not giving proper output in i.MX95 Hello @Bio_TICFSL! I've noticed NXP team suggest to use the --use-python-prototype flag, however my neutron converter does not recognize it. Is it supported on Windows, or it is only compatible with the Linux eIQ release? Re: Neutron Converted YOLOv8n model is not giving proper output in i.MX95 That is also a question for me. I have done with Linux eIQ and it's not working me as well. So I have skipped it and try to convert the model with passing the target arg only. Re: Neutron Converted YOLOv8n model is not giving proper output in i.MX95 Hi @Bio_TICFSL ,  Since it's long time, I am still waiting for the reply from your side. We are stuck here, and we have some urgency as well. Kindly request you to please reply as soon as possible. Regards, Vatsal [i.MX95 NPU] YOLOv5n/v8n/v11n Neutron-converted Models Run but Return No Detections (Zero Output) Issue Description I am evaluating YOLO object detection models on the i.MX95 NPU using the Neutron converter. While the INT8 quantized TFLite models run successfully and detect objects on the Cortex-A55 CPU, the compiled neutron.tflite versions yield zero detections (empty/no output) when offloaded to the NPU, despite executing inference without crashing. Environment & Hardware Setup   Hardware: i.MX95 19x19 LPDDR5 EVK (A1 Revision) OS/Kernel: Linux 6.12.34-lts-next-gbe78e49cb433 #1 SMP PREEMPT (aarch64) NXP Toolchain: MCU-SDK v25.09.00 + Linux 6.12.34_2.1.0 Models Tested: YOLOv5nu, YOLOv8n, YOLOv11n (Ultralytics) Workflow Steps & Commands Used 1. Quantization (Ultralytics Export) Models were exported to INT8 full integer quantization with a 320x320 resolution: yolo export model=yolov8n.pt format=tflite int8=True imgsz=320# (Repeated identically for yolov11n.pt and yolov5nu.pt)   Status: Works perfectly on CPU. yolovXn_full_integer_quant.tflite detects objects correctly on the A55 cores. 2. Neutron Compilation The TFLite models were compiled for the i.MX95 NPU using the Neutron converter from MCU_SDK_25.09.00+Linux_6.12.34_2.1.0: ./neutron-converter --input yolov8n_full_integer_quant.tflite --target imx95 --output yolov8n_full_integer_quant_neutron.tflite   Status: Fails to detect objects on NPU. The compiled model loads and runs inference without throwing syntax or execution errors, but output tensors return zero detections for the exact same test images. Observed Symptoms & Suspected Root Causes   Operator Fallbacks: Did the converter fall back to CPU for specific YOLO layers (like custom Anchors, SiLU/Swin activations, or Non-Max Suppression)? Quantization Scaling/Asymmetry: YOLO models exported via Ultralytics often use asymmetric quantization or have specific output tensor scaling that the Neutron NPU driver might misinterpret. Output Tensor Formatting: The inference runs, which suggests the input pipeline is fine, but the output bounding boxes/scores are either blank or completely garbage values. Questions for NXP Experts   Are there known limitations or mandatory optimization flags needed in the neutron-converter specifically for Ultralytics YOLO architectures? Should the NMS (Non-Max Suppression) layer be stripped out before passing the TFLite model to the Neutron converter? Does the i.MX95 Neutron SDK require symmetric quantization (per_channel=True or False) to parse the output layers properly? Any guidance, reference scripts, or working YOLO deployment notes for the i.MX95 NPU would be highly appreciated.        

NFC PN7160 Hello, I have custom board with NXP PN7160 nfc device. The goal is to have MIFARE plus sl3 working on linux. Currently we are using libnfc-nci and we are able to detect badges (tag arrival and departure). Is there a library to manage MIFARE plus provided by NXP ? If yes does this library also provide functions to write AES keys to the badges ? thanks Re: NFC PN7160 Hello @angelobticino Hope you are doing well. PN7160 Software supporting MIFARE devices is secured under NDA (Non-Disclosure Agreement), the information is not public and it is located under the PN7160 Secure Files. However, I must mention that available software only offers support for MIFARE DESFire devices. Functionality related to MIFARE Plus must be implemented by you based on MIFARE Plus EV2 documentation (relevant documentation is also secured under NDA and must be requested through MIFAE Plus EV2 Secure Files). If you are interested in those resources, you can try requesting an NDA directly from the NDA online form; after your request is processed, you should be contacted by the NXP NDA team. If you have any questions, please consult the Non-Disclosure Agreement FAQs. Once you have a valid NDA with NXP, or if you already have a valid one, you will need to request access this document through Secure Access Rights by following the instructions from this page: Secure Access Rights | NXP Semiconductors. Also, I would recommend checking the Secure Access Rights FAQs | NXP Semiconductors. Regards, Eduardo.

S32K388 电源 您好 S32K388， 我正在我的一个应用程序中使用 S32K388。V11原本应该由V15的末端稳压器NMOS供电。但我希望使用外部DC/DC变流器来提供这1.5V电压。这可行吗？ 顺祝商祺！ 朱尔斯 Re: S32K388 power supplies 你好@JulesW ， 根据 S32K388 电源架构，V11 必须使用来自 V15 电源轨的外部 NMOS 末端稳压器生成，如硬件设计指南中所述。 但是，如果你的问题是 1.5V V15 电源轨本身是否可以由外部 DC/DC 变流器供电，那么这是可行的。S32K388 EVB 也采用了这种方法，其中一个跳线选项是 1.5 V 电源轨由 PMIC 在外部生成。 顺祝商祺！ 帕维尔

NFC PN7160 你好， 我有一块定制电路板，上面搭载了NXP PN7160 NFC设备。 目标是让 MIFARE 和 sl3 在 Linux 上运行。 目前我们正在使用 libnfc-nci，并且能够检测到徽章（标签到达和离开）。 NXP 是否提供了用于管理 MIFARE Plus 的库？ 如果答案是肯定的，那么这个库是否也提供了将AES密钥写入徽章的功能？ 谢谢 Re: NFC PN7160 你好@angelobticino 希望你一切都好。 支持 MIFARE 设备的 PN7160 软件受 NDA（保密协议）保护，该信息不公开，并且位于PN7160安全文件下。 但是，我必须指出，现有软件仅支持 MIFARE DESFire 设备。与 MIFARE Plus 相关的功能必须由您根据MIFARE Plus EV2文档实施（相关文档也受保密协议保护，必须通过 MIFARE Plus EV2 安全文件提出申请）。 如果您对这些资源感兴趣，您可以尝试直接通过NDA 在线表格申请 NDA；您的申请处理完毕后，NXP NDA 团队应该会与您联系。如有任何疑问，请参阅保密协议常见问题解答。 一旦您与 NXP 签订了有效的 NDA，或者如果您已经拥有有效的 NDA，您需要按照此页面上的说明，通过安全访问权限请求访问此文档：安全访问权限 | NXP 半导体。另外，我建议您查看NXP 半导体的“安全访问权限常见问题解答” 。 问候， 爱德华多。

Regarding the download link for S32K3_RTD_7_0_0 I'm looking to download an RTD executable from the NXP website that meets the following criteria, but I can't find it. Could you please provide the download link? I'm in a hurry, so I would appreciate a quick response. S32K3_RTD_7_0_0_D2510_ASR_REL_4_9_REV_0000_20251031 I found the following downloadable product, which is similar, but it requires an RTD (Ready-to-Download) that meets the above conditions. SW32K3_S32M27x_RTD_R21-11_6.0.0_QLP04_HF01_D2510.exe SW32K3_S32M27x_RTD_R23-11_7.0.0_D2511.exe SW32K3_S32M27x_RTD_R23-11_7.0.0_QLP03_D2512.exe Re: S32K3_RTD_7_0_0のダウンロードリンクについて Hi Do you need to use EBTresos or S32DS? If you need to use EBTresos, please download and install S32K3_S32M27x Real-Time Drivers ASR R23-11 Version 7.0.0 (SW32K3_S32M27x_RTD_R23-11_7.0.0_D2511.exe). If you need to use S32DS, please download S32K3_S32M27x Real-Time Drivers ASR R23-11 Version 7.0.0 (SW32K3_S32M27x_RTD_R23-11_7.0.0_D2511_DesignStudio_updatesite.zip). Best Regards, Robin

S32K388 power supplies Hello S32K388, I am using the S32K388 for one of my applications. The V11 is meant to be supplied by a last mile regulator NMOS from V15. However I would like to supply this 1.5V from a external DC/DC converter. Is that feasible? Best regards, Jules Re: S32K388 power supplies Hello @JulesW , Based on the S32K388 power architecture, V11 must be generated using the external NMOS last-mile regulator from the V15 rail, as described in the Hardware Design Guidelines. However, if your question is whether the 1.5 V V15 rail itself can be supplied from an external DC/DC converter, then this is feasible. This is also the approach used on the S32K388 EVB, where one jumper option is that the 1.5 V rail is generated externally by the PMIC. Best regards, Pavel

OV5640 Interfacing with i.MX RT1170 (Without Display) Image Capture and Streaming to Desktop Hello, I am using the i.MX RT1170-EVKB board, and my goal is to capture images from the OV5640 camera and view either the captured image or a live video stream on my desktop PC without using an LCD display. I have tried the MIPI CSI SDK examples and was able to capture image data in RAW format. However, I am facing several issues. The captured output is in RAW format, and I could not find any documentation explaining how to properly convert or view these images. The captured images appear to have incorrect colors or filter-like artifacts, making it difficult to verify whether the camera output is correct. I could not find any official documentation, application notes, or video tutorials describing the complete workflow for capturing images from the OV5640 and viewing them on a desktop PC. There is no clear reference explaining how to stream the camera output over Ethernet or USB without using the onboard display. I also tried the sd_jpeg example, but I encountered multiple problems. During integration, the project reported missing JPEG library configuration files such as jconfig.h. After resolving some build issues, I continued to encounter compilation and integration errors while combining the JPEG encoder with the MIPI CSI camera example. I was unable to generate a valid JPEG image from the captured camera frame. My objective is to: Interface the OV5640 camera with the i.MX RT1170-EVKB board without using an LCD display. Capture images and transfer them to my desktop PC for viewing. Stream live video from the camera to my desktop PC over Ethernet, if supported. I would appreciate your guidance on the following questions: Is there an official SDK example or reference project for this use case? Is there any documentation explaining the complete image capture pipeline from the OV5640 through MIPI CSI, memory, JPEG or RAW processing, and Ethernet or USB transfer to a desktop PC? Is live streaming over Ethernet supported on the RT1170-EVKB? If yes, could you recommend the appropriate SDK example or middleware? Are there any known issues with the sd jpeg example or any additional configuration steps required to integrate it with the MIPI CSI camera examples? Any guidance, documentation, or reference projects would be greatly appreciated. Thank you for your support. Re: OV5640 Interfacing with i.MX RT1170 (Without Display) Image Capture and Streaming to Desktop HI @Sureshk123, We don't have an official example project or reference design for your application. That said, from my understanding, I would recommend you tackle the complete application as follows: Camera capture path (OV5640 > MIPI CSI > cameraBuffer) This part we do have an example application, which are the aforementioned MIPI CSI SDK examples. Keep in mind that, as per ERR051248: "Video Mux Controller (VIDEO_MUX), raw data and YUV422 (10 bit) formats to the MIPI_CSI2 block are not supported." Using the parallel CSI is an optional workaround, either that or a video decoder. Once you have the adequate data on your cameraBuffer, you can integrate example projects from our SDK based on USB or lwIP to transport this data to your PC. I would recommend looking into JPEG encoding only after the buffer is known to work. BR, Edwin.

SE050E2HQ1/Z01Z3Zに必要な熱データ こんにちは、チームの皆さん、 部品番号の熱抵抗データと動作接合部温度情報を探しています。 SE050E2HQ1/Z01Z3Z ありがとうございます。 ひどい スマート・カード Re: Thermal Data required for SE050E2HQ1/Z01Z3Z こんにちは、 @Harsh_Bhavsar さん。 詳細については、 https://www.nxp.com/docs/en/data-sheet/SE051.pdfをご参照ください。それらはほとんど同じです。 心から、 カン