EB tresos Studio 27.1 Activation Error Hello buddy： I tried to activate EB tresos Studio 27.1 using the EB Client Licese Administrator_1_5_1 software and reported an error as follows： Status: 4, Creating request Status: 5, Request created Status: 6, Context created Status: 7, Connected to remote server Status: 8, Request Sent Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 10, Waiting for response Status: 9, Polling for response Status: 11, Done ERROR: flxActAppActivationSend (50040,41147,10248) The quantity specified exceeds maximum quantity allowed (0). Connection to FlexNet Operations Server failed. You know why？ Re: EB tresos Studio 27.1 Activation Error You said "I found out that the activation code has been updated" , updated by what? By email, your nxp comunity msg ? They sent you an email? I did not receive any msgs on this.  Re: EB tresos Studio 27.1 Activation Error Hi buddy： Update on the latest situation. Today, I found out that the activation code has been updated. But it did not arrive at the update time it had announced. I used the new activation code to activate EB. It worked. I think there might be a BUG. If you have a similar problem, you can watch over the next few days to see if the activation code changes. Re: EB tresos Studio 27.1 Activation Error It should be server side issue. I got same error with u: Hi, I have exact same issue: system issue me with a code below: 7D06-3C29-B753-21AB yesterday. But after I use above sn code active it, eb studio always says error: flxActAppActivationSend(50040,41247,10248) That activation request yields no right to a license. Connection to FlexNet Operations server failed. Need your help. Thanks, Thomson

FS26 FCCU1 single PWM monitoring Hi, can please someone tell me what should be the configuration for FS2633D FCCU1 PWM monitoring?  I have configured FCCU_CFG to 110 to use FCCU1 PWM monitoring and input level monitoring on FCCU2. I can't get the reset to working even if I don't apply any PWM wave to FCCU1 pin. My watchdog reset is working fine so no hardware issue in the reset connection.  Also, it would be great if someone can give me an example of a valid PWM wave on FCCU1 or just explain in terms of duty cycle and frequency because the datasheet makes it a bit confusing. It would be a great help if this can be done.  Thanks a lot. Functional Safety Power solution Re: FS26 FCCU1 single PWM monitoring HI : For example, tPULSE_FCCU_HF =8us, that means both high and low duration time is 8us, T=16us, corresponding PWM frequency is 62.5KHZ(50% duty cycle). “tPULSE_FCCU_HF”  means FCCU will report a failure if High or low pulse duration is smaller than 8us(typ), 6us(min), 10us(max). “tPULSE_FCCU_LF” means FCCU will report a failure if  High or low pulse duration is larger than 64us(typ), 51us(min), 80us(max). As a result: FCCU is 100% good when high or low duration time is within 10us~51us(frequency is within 9.8K~50K), there is some buffer considered, so  FCCU12_GF = 10KHZ~45KHZ. FCCU is 100% bad when high or low duration time is below 6us or above 80us(frequency is >83K or <6.25K), there is some buffer considered, so FFCCU12_BLF =5KHZ max and FFCCU12_BHF =90KHZ min. Re: FS26 FCCU1 single PWM monitoring So, when the wave is low it should b/w 51-80us and when its high it should be b/w 6-10? Am I correct or is it something different? And why the "good" PWM range of 10-45 KHz is different than the bad low and bad high frequency, shouldn't the bad frequency be less than 10KHz and greater than 45KHz according to that range? What am I missing? Re: FS26 FCCU1 single PWM monitoring 1:You can get the detection time here for the high or low level on PWN monitoring : 2:bad frequency are below showed: <5KHZ or >90KHZ Re: FS26 FCCU1 single PWM monitoring My main confusion is regarding the PULSE_FCCU_HF and PULSE_FCCU_LF time. Are they related to the duty cycle of the wave? And if good frequency range is between 10-45KHz then how is bad frequency is greater than 90KHz?  Will there be no fault if I just give a PWM of 30KHz (good frequency) of any duty cycle? Or is it something different? Re: FS26 FCCU1 single PWM monitoring Hi aad1tya We list all of the configuration information about FCCU PWM/lever monitoring in datasheet page188-190--->20.7.3 FCCU single PWM monitoring activated For example FCCU configure PWM frequency /level threshold : You can read them. Hope this could help you!

Layerscape Hardware Security Module(HSM) storage questions Hello, In the LSDK User Guide mentions that the SoCs can internally store keys using an HSM. "NXP SoCs such as LS1046A can store keys securely using built-in SoC capabilities - virtual HSM. With such devices, sensitive private keys never leave the device and cryptographic operations are performed on this virtual HSM"(LSDKUG-Rev21.08, CH 6.5.1). I could not find a reference to whether it is stored using secure non-volatile storage (SNVS), or if it is stored in volatile memory requiring a battery connected such as the with the "Battery Backed Security Monitor supply". Does the SoC need to keep some voltage after powering off to keep the keys stored securely? And just to confirm, this feature applies to all arm trusted firmware(TFA) enabled CPUs? QorIQ LS1 Devices Re: Layerscape Hardware Security Module(HSM) storage questions Hello @jvfausto  Hope this post finds you well, They are stored in a non-volatile memory. BR, Hector V Re: Layerscape Hardware Security Module(HSM) storage questions Hello @jvfausto  Hope this email finds you, This email is to inform that I keep working on the solution on this case. I’ll keep you informed on the process, Have a great day.   BR, Hector Villarruel

FS26 FCCU1シングルPWMモニタリング こんにちは、誰かが私にFS2633D FCCU1 PWM監視の構成を教えてください。 FCCU_CFG to 110 を FCCU1 PWM 監視と FCCU2 の入力レベル 監視を使用するように構成しました。 FCCU1ピンにPWM波を適用しないと、リセットが機能しません。ウォッチドッグのリセットは正常に機能しているため、リセット接続にハードウェアの問題はありません。 また、FCCU1の有効なPWM波の例をどなたか教えていただけると幸いです。または、データシートが少し混乱させるため、デューティサイクルと周波数の観点から説明してください。これができれば、とても助かります。 どうもありがとうございます。 機能安全 電源ソリューション 日時:FS26 FCCU1シングルPWMモニタリング では、波が低いときは白黒51-80us、高いときは白黒6-10になるべきなのでしょうか? 私は正しいですか、それとも何か違うのですか? また、10〜45 KHzの「良い」PWM範囲が悪い低周波数や悪い高周波と異なるのはなぜですか、その範囲に応じて、悪い周波数は10KHz未満で45KHzを超えるべきではありませんか? 何が足りないのか? 日時:FS26 FCCU1シングルPWMモニタリング 私の主な混乱は、PULSE_FCCU_HFとPULSE_FCCU_LF時間に関するものです。それらは波のデューティサイクルに関連していますか? また、良好な周波数範囲が10〜45KHzの場合、不良周波数はどのようにして90KHzを超えますか? 任意のデューティサイクルで30KHz(良好な周波数)のPWMを与えるだけで問題はありませんか?それとも何か違うのでしょうか?

是否可以使用 i.MX8MPlus 上为单 SPI 线和 QSPI 线设计的芯片？ 回复：是否可以在 i.MX8MPlus 上使用设计用于单 SPI 线和 QSPI 线的芯片？ 我们的设计中需要 SRAM，但是处理器上没有任何剩余的 SPI 线，因为处理器仅支持 3 个 SPI 接口并且它们已经被占用。因此，我们想知道是否可以通过处理器的 QSPI 端口（其中引脚与 NAND 引脚复用）连接单个 SPI SRAM。 回复：是否可以在 i.MX8MPlus 上使用设计用于单 SPI 线和 QSPI 线的芯片？ 您的主板上有哪些启动闪存？

Is it possible to use a chip designed for single SPI line with QSPI lines on the i.MX8MPlus? Re: Is it possible to use a chip designed for single SPI line with QSPI lines on the i.MX8MPlus? We need SRAM in our design but we don't have any single SPI lines left from the processor due to the processor only supports 3 SPI interfaces and they are already occupied. Therefore we wonder if it's possible to connect a single SPI SRAM on the QSPI-port (where the pins are multiplexed with NAND-pins) from the processor.  Re: Is it possible to use a chip designed for single SPI line with QSPI lines on the i.MX8MPlus? Which boot flash have on your board?

BSDLファイルSPC5743RMLU5 こんにちはNXPの専門家、 SPC5743RMLU5用のbsdlファイルが必要です、どなたか助けていただけますか? ありがとうございます。 Re: SPC5743RMLU5 BSDLファイル 得た！迅速な対応ありがとうございました! Re: SPC5743RMLU5 BSDLファイル 要求されたファイルを添付しています。

RT1020 EVK , SDK wi-fi direct support is possible? Hello ,  It is simple question,  I reviewd all  example about wifi.   but I Can not find  the example of wi-fi direct funtionality   in  SDK 2.13.0 RT1020. So. Is there  any doc. or someting  about Entering wi-fi direct mode from Station mode? Do I have to  implement wi-fi direct using  Soft AP  of   wifi_cli example i.MXRT 102x Re: RT1020 EVK , SDK wi-fi direct support is possible? Hi @Seongyon_Jeong  It seems difficult to implement wifi direct feature base on RT1020 EVK board, the root causes are SW resouce limitation and adapation of some modules of M.2 interface, so we can find the SDK/example in RT1050/1060/11xx, but we can not support them in RT1020 EVK.  Sorry for inconvenient. B.R, Sam

RT1020 EVK、SDK Wi-Fiの直接サポートは可能? こんにちは それは簡単な質問です、 Wi-Fiに関するすべての例をレビューしました。だがしかし SDK 2.13.0 RT1020でWi-Fiダイレクト機能の例は見つかりません。 だから。何かドキュメントはありますか。または、ステーションモードからWi-Fiダイレクトモードに入ることについて何かありますか? wifi_cli例のソフトAPを使用してWi-Fiダイレクトを実装する必要がありますか i.MXRT 102倍

Change Gui Guider font size What is the proper #include for standard fonts in Gui Guider-1.8.1-GA? This works in custom code.     lv_obj_set_style_text_font(ui_Label_Timer, &lv_font_montserrat_12, LV_PART_MAIN | LV_STATE_DEFAULT); But, changing font size results in a compilation failed.  This font has no issue in the UI editor.     lv_obj_set_style_text_font(ui_Label_Timer, &lv_font_montserrat_24, LV_PART_MAIN | LV_STATE_DEFAULT); Re: Change Gui Guider font size Hi @Johnny5  If you want to add lv_font_montserratMedium_12,  Please declare in file gui_guider.h BR Harry

i.MX8MPlusで、シングルSPIライン用に設計されたチップをQSPIラインで使用することは可能ですか? Re:i.MX8MPlusのQSPIラインで単一のSPIライン用に設計されたチップを使用することは可能ですか? デザインには SRAM が必要ですが、プロセッサが 3 つの SPI インターフェイスしかサポートしておらず、すでに使用されているため、プロセッサから SPI ラインが 1 つも残っていません。したがって、プロセッサからQSPIポート(ピンがNANDピンと多重化されている)に単一のSPI SRAMを接続することが可能かどうか疑問に思います。 Re:i.MX8MPlusのQSPIラインで単一のSPIライン用に設計されたチップを使用することは可能ですか? ボードにはどのブートフラッシュがありますか?

请让我知道当连接的设备发出“解除关联”时如何通知。 尊敬的恩智浦支持团队， 我目前正在使用 88W8887 并需要接入点模式的帮助。 当连接到接入点的 STA 设备断开连接时，STA 设备会发出“解除关联”。 有没有办法在发出“解除关联”时发出通知？ 此外，当 AP 和 STA 之间的连接通过发出此“解除关联”时，是否有办法发出断开连接通知？ 我正在使用“SD-WLAN-UART-BT-8887-U16-MMC-W15.87.19.p64-15.100.19.p64-C4X15704_A2-MGPL”。 ・Linux 内核版本 v3.18.24 ・hostapd 版本：2.10 ・wpa_supplicant 版本：2.10 我将非常感激您对以下几点的指导： TCC8971（Telechips）是否需要特定的配置或设置才能与 Marvell 88W8887 WiFi 设备一起在 AP 模式下有效运行？ 是否有任何固件更新或特定版本可以更可靠地支持 AP 模式？ 我可以使用任何其他故障排除步骤或工具来诊断和解决连接问题吗？ 感谢您的时间和帮助， 此致， 高地宏之 协议：Wi-Fi 回复：请告诉我当连接的设备发出“解除关联”时如何通知。 非常感谢您的解决方案。 回复：请告诉我当连接的设备发出“解除关联”时如何通知。 你好， @Pioneer 感谢您的反馈，我们随时欢迎您。 如果对此案没有其他担忧，您介意将我之前的回复标记为解决方案吗？这样我们就可以结案了。 如果您将来有任何其他问题，请随时向我们创建新案例。 祝你有美好的一天~ 顺祝商祺！ 克里斯汀。 回复：请告诉我当连接的设备发出“解除关联”时如何通知。 亲爱的克里斯汀， 非常感谢您的详细回复和指导。非常感谢您对当前系统限制的解释，以及对应用层日志分析和实现的建议。 针对 Linux 和 Android 平台的建议以及有关最新固件版本的信息非常有用。我将继续更新固件并查看推荐的故障排除文档。 也感谢您提供有关日志捕获和诊断连接问题的说明。我一定会参考它们。 再次对各位的鼎力支持表示感谢。如果将来我需要进一步的帮助，我期待您能继续提供帮助。 此致， 高地宏之 回复：请告诉我当连接的设备发出“解除关联”时如何通知。 你好， @Pioneer 感谢您为我们创建案例。 请参阅我的内联回复： 1. 发出“解除关联”命令时，有什么方法可以发出通知吗？当 AP 和 STA 之间的连接因发出“解除关联”命令而断开时，有什么方法可以发出断开连接通知吗？ ==>很抱歉造成不便。目前，从控制器方面来看，我们还没有这样的策略，当连接的 STA 与以 AP 模式工作的 88W8887 断开连接时，可以自动向最终用户报告/通知。您可以查看相关的 dmesg 日志、journal 日志，或者 Wi-Fi OTA 日志，并根据日志内容自行实现应用层的需求。 TCC8971（Telechips）是否需要特定的配置或设置才能与 Marvell 88W8887 Wi-Fi 设备一起在 AP 模式下有效运行？ ==>对于 Linux 平台，您可以参考《在运行 Linux 操作系统的 i.MX 8M Quad EVK 上开始使用基于 NXP 的无线模块 - 用户手册》 对于Android平台，您可以参考： 在运行Android 14操作系统的i.MX 8M Quad EVK上使用基于NXP的无线模块入门指南 是否有任何固件更新或特定版本可以更可靠地支持 AP 模式？ ==>我们的最新版本是： SD-WLAN-UART-BT-8887-U16-MMC-W15.87.19.p69-15.100.19.p69-CS4X15711_A2-MGPL 您可以通过上面的链接下载并更新您的 FW。我们始终建议客户使用最新版本，因为它包含一些已知的修复并具有更好的兼容性。 我可以使用任何其他故障排除步骤或工具来诊断和解决连接问题吗？ ==>您可以参考i.MX 8M Quad EVK 上基于 NXP 的无线模块的功能配置指南 - 用户手册。 第 3 节 Wi-Fi 驱动程序调试包含一些 Wi-Fi 调试的指导步骤。 特别是对于连接问题，我们通常会捕获 dmesg、wpa_supplicant 日志和 Wi-Fi OTA 日志来查看发生了什么。 如何捕获 dmesg 日志： 在Linux终端上，直接执行：dmesg > log.log 它会将 dmesg 日志保存到 log.log 文件中并保存在您的主机平台上。 如何捕获 wpa_supplicant 日志： 您可以使用以下步骤启用请求者日志： 1. 启动开发板 2. 终止 wpa_supplicant 3.打开“vi /lib/systemd/system/wpa_supplicant.service” 4. 在末尾添加 -ddd “ExecStart=/usr/sbin/wpa_supplicant -u -ddd” 5.重启开发板 6. 使用 nmcli 运行场景 7. 运行 journalctl -a -b 来捕获请求者日志 如何捕获 Wi-Fi OTA 日志使用 wireshark 或 Ominipeek 和支持监控模式的 Wi-Fi 卡来捕获 Wi-Fi OTA 日志。 为了解决连接问题，我们需要确定根本原因是来自我们这边还是来自远程那边。从驾驶员侧或 FW 侧。我们的Wi-Fi芯片端或者您的应用程序端。无论如何，一旦我们发现任何证据表明问题出在我们的 Wi-Fi 方面，我们就会尝试解决它。除了验证之外您不需要做任何事情。 如果需要我们的 Wi-Fi 芯片支持，请随时创建案例。 顺祝商祺！ 克里斯汀。

It can't work about FlexCAN in S32K312. Hi NXP: I'd like to try FlexCAN function in example code(FreeRTOS_Toggle_Led_Example_S32K312), but it can't work. I have using logic analyzer for quering issue, and CAN TX/RX pin are not expected, please help me, many thanks. 1.MCU pin29(CAN-RX):it always appears some strange signal. 2.MCU pin54(CAN-TX):always high. environment: 1.SW32K3 FreeRTOS 10.6.0 version 4.0.0 is based on S32K3 RTD 4.0.0 2.set speed 500KBps of FlexCAN 3.we're using CAN transceiver(TI TCAN1044) attachment: 20241223-FreeRTOS_Toggle_Led_Example_S32K312.7z 20241223-LA_CAN_screenshot.png Re: It can't work about FlexCAN in S32K312. Hi Senlent: Sorry,it's my fault.I found an issue about Logic analyzer. I used scope and LA at the same time, and scope is normal no strange wave, so I changed another channels of LA and wave is perfect,thanks again. have a good day. Re: It can't work about FlexCAN in S32K312. Hi@f-nelson Maybe this may be a hardware problem, such as the transceiver and its peripheral circuits, but this transceiver is not made by NXP, so I can't help you evaluate it. Re: It can't work about FlexCAN in S32K312. Hi NXP: many thanks for your modified. In this mornring, I tried to modify flexCAN protocol clock to 24Mhz as FIRC clock source and adjusted bit rate to 500kbps, and then it can works about CAN bus function by LA or PCAN-viewer, but it still has some strange data wave of CAN-RX. just now I used your modified workshop for testing and the result is the same. Do you have any ideas of CAN-RX pin? thanks. PS.I captured wave pictures by LA from your modify workshop as attachment. Re: It can't work about FlexCAN in S32K312. Hi@f-nelson Lot of error in your project and i made some modification in the attachments. Re: It can't work about FlexCAN in S32K312. Hi NXP: just now I changed porting code from Example_S32K358_FlexCAN_Ip_TXRX_ISR_rtd400 which your recommanded, and maked sure GPIO is normal, but the result is the same failed, please help me as soon as possible, thanks. attachment: 20241223-test_CAN2.7z 20241223-20231223-CAN_transceiver_schematic.png Re: It can't work about FlexCAN in S32K312. Hi NXP: thansk for your suggestion. I created new project of S32K312 and porting example code from "S32KXX AUTOSAR R21-11 RTD 4.0.0 D2311 Example Projects\FlexCAN_Ip_Example_S32K344",but the result is the same. in fact,I curious about CAN-RX signal is always outputing strange wave. Is it possible about pin setting issue or something else? Re: It can't work about FlexCAN in S32K312. Hi@f-nelson Please do not add FreeRTOS first, and then test whether the CAN function is normal. When the CAN function is normal, add FreeRTOS for testing. This is a demo base on RTD 4.0.0 and you can refer to first. Example S32K358 FlexCAN TXRX ISR S32DS35 RTD400 https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K358-FlexCAN-TXRX-ISR-S32DS35-RTD400/ta-p/1981987

ISP_FLASH_TRIG_0 and ISP_SHUTTER_TRIG_0 meaning Hi everyone, I'm working with the NXP i.MX 8M Plus SoC and trying to understand the functionality of two ISP (Image Signal Processor) trigger signals: ISP_SHUTTER_TRIG_0 ISP_FLASH_TRIG_0 Re: ISP_FLASH_TRIG_0 and ISP_SHUTTER_TRIG_0 meaning @joanxie thank you for the info Re: ISP_FLASH_TRIG_0 and ISP_SHUTTER_TRIG_0 meaning they are defined by the ISP IP owner, why do you need to know this? SHUTTER  TRIG clock is for ISP shutter module, and flash trigger is for flash light control, this is all I can share with you in the public community

Please let me know how to notify when 'Disassociate' is issued from the connected device. Dear NXP Support Team, I am currently working with 88W8887 and require assistance with Access Point mode. When a STA device connected to the access point is disconnected, the STA device issues a 'Disassociate'. Is there a way to notify when this 'Disassociate' is issued? Additionally, is there a way to issue a disconnection notification when the connection between AP and STA is severed by issuing this "Disassociate"? I am using "SD-WLAN-UART-BT-8887-U16-MMC-W15.87.19.p64-15.100.19.p64-C4X15704_A2-MGPL". ・Linux Kernel Version v3.18.24 ・hostapd Version：2.10 ・wpa_supplicant Version：2.10 I would greatly appreciate your guidance on the following points: Are there specific configurations or settings required for the TCC8971（Telechips） to operate in AP mode effectively with the Marvell 88W8887 WiFi device? Are there any firmware updates or specific versions that support AP mode more reliably? Any additional troubleshooting steps or tools that I can use to diagnose and resolve the connection issues? Thank you for your time and assistance, Best regards, Hiroyuki Kohchi Protocol: Wi-Fi Re: Please let me know how to notify when 'Disassociate' is issued from the connected device. Thank you very much for the solution. Re: Please let me know how to notify when 'Disassociate' is issued from the connected device. Hi, @Pioneer  Thanks for your feedback and you are always welcome. If no other concerns on this case, would you mind mark my previous reply as a solution? So that we can close this case. Please feel free to create new case to us if you have any other questions in the future. Have a nice day~ Best regards, Christine. Re: Please let me know how to notify when 'Disassociate' is issued from the connected device. Dear Christine, Thank you very much for your detailed response and guidance. I greatly appreciate your explanation of the current system limitations, as well as your suggestions regarding log analysis and implementation at the application layer. The recommendations for both Linux and Android platforms, along with the information about the latest firmware release, have been very helpful. I will proceed with updating the firmware and reviewing the recommended troubleshooting documents. Thank you also for the instructions on log capturing and diagnosing connection issues. I will definitely refer to them. Once again, I would like to express my gratitude for your thorough support. I look forward to your continued assistance should I need further help in the future. Best regards, Hiroyuki Kohchi Re: Please let me know how to notify when 'Disassociate' is issued from the connected device. Hi, @Pioneer  Thanks for creating case to us. Please see my inline reply: 1. Is there a way to notify when this 'Disassociate' is issued? Is there a way to issue a disconnection notification when the connection between AP and STA is severed by issuing this "Disassociate"? ==>Sorry for the inconvenience. Currently, from controller side, we do not have such kind of policy which can automatically report/notify to end users when the connected STA disconnected with our 88W8887 working in AP mode. You can check related dmesg logs, journal log, or Wi-Fi OTA logs. According to the logs implement the requirement in application layer by yourself.  Are there specific configurations or settings required for the TCC8971（Telechips） to operate in AP mode effectively with the Marvell 88W8887 Wi-Fi device? ==>For Linux platform, you can refer to  Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Linux OS - User manual For Android platform, you can refer to: Getting Started with NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android 14 OS Are there any firmware updates or specific versions that support AP mode more reliably? ==>Our latest release is: SD-WLAN-UART-BT-8887-U16-MMC-W15.87.19.p69-15.100.19.p69-CS4X15711_A2-MGPL You can download it through above link and update your FW. We always suggest customer to use latest release because it includes some known fixes and has better compatibility. Any additional troubleshooting steps or tools that I can use to diagnose and resolve the connection issues? ==>You can refer to Feature Configuration Guide for NXP-based Wireless Modules on i.MX 8M Quad EVK - User manual. In section 3 Wi-Fi driver debugging, it includes some guide steps for Wi-Fi debug. And specially for connection issues, we usually capture dmesg, wpa_supplicant journal logs and Wi-Fi OTA logs to see what happened.  How to capture dmesg logs: On Linux terminal, directly execute: dmesg > log.log  It will save the dmesg logs into log.log file and saved on your host platform. How to capture wpa_supplicant journal logs: You can use below steps to enable the supplicant logs: 1. boot up the board 2. killall wpa_supplicant 3. open "vi /lib/systemd/system/wpa_supplicant.service"  4. add -ddd at end "ExecStart=/usr/sbin/wpa_supplicant -u -ddd" 5. reboot the board 6. Run the scenario using nmcli 7. run journalctl -a -b to capture the supplicant logs How to capture Wi-Fi OTA logsWith wireshark or Ominipeek and Wi-Fi card which supported monitor mode to capture Wi-Fi OTA logs. To resolve connection issue, we need to identify what's the root cause, is from our side or from remote side. From driver side or FW side. Our Wi-Fi chip side or your application side. Anyway, once we find any evidence shows that the issue is from our Wi-Fi side, we will try to fix it. And you do not need to do anything except validation. Please feel free to create case if need our support on our Wi-Fi chips. Best regards, Christine.

TX_CLK Signal Configuration in 100BASE-T1 Test Mode on SJA1110 Hi  We are currently testing the 100BASE-T1 test mode on the SJA1110 switch. During the tests, we found that the Jitter (SLAVE) requires an additional TX_CLK signal. The Software User Manual for the SJA1110 indicates that additional configuration is necessary to switch LOC_WAKE_IN to TX_CLK. We switching the PHY into different testmodes, and some of the test modes have passed. However, we still do not observe any signal on TX_CLK. We also reviewed the switch_config_sja1110evm example in S32 Design Studio, where only the test mode is configured. Could you please advise if any additional configuration is required to enable the TX_CLK signal? Thank you for your support. Re: TX_CLK Signal Configuration in 100BASE-T1 Test Mode on SJA1110 Hello, @steven-Yeh  Thanks for the post. Since this is SJA1110EVM related questions, which is not directly related with S32G, I suggest posting it in the following forum: https://community.nxp.com/t5/Other-NXP-Products/bd-p/other For them to provide more proper support. Sorry for your inconvenience. Best Regards Chenyin

S32K344 Hardware CRC issue Hi, there I used the crc of the S32K344 with hardware calculation type to calculate the CRC of the pflash, but I couldn't get the result. I don't know why. Please help me. the attached is my test code. RTD:3.0 S32DS:3.5   Re: S32K344 Hardware CRC issue Hi @ZDDL  Which is the expected result? I ask you to please test your code with just a value to verify the behavior. Also, have you already try the Crc_Ip_Example? My recommendation is to take a look at this example, which you might find useful. BR, VaneB

Dma transfer on S32K310  while i am testing the Dma function on S32K310, i find that the destination buffer is not updated. then tried to read the Dma status, this is the value of error register. this is how the variables initialized Re: Dma transfer on S32K310 thank you, good solution! Re: Dma transfer on S32K310 Hi @LeoYang-, As per the debug session that I checked with you, we can conclude that the cause is: somehow, the CH0_ES[ERR] bit was set before calling the Dma_Ip_Init() function, and after, the destination address and source address can't be written into the DADDR and SADDR registers by Dma_Ip_SetLogicChannelTransferList() function. This is the solution: write 1 to clear the CH0_ES[ERR] bit before calling the Dma_Ip_Init() function. Best regards, Dan

How to fix Yocto QA error [already-stripped] Following UG10164 v.LF6.6.52_2.2.0 I tried to build sdk, but recived a QA error [already-stripped].  Does anybody have an idea how to fix it? PC: ubuntu20.04 x86_64 1. Init build env:  $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.52-2.2.0.xml $ repo sync $ DISTRO=fsl-wayland MACHINE=imx8dxl-b0-lpddr4-evk source imx-setup-release.sh -b build-imx8dxl-b0 2. build: $ bitbake core-image-minimal -c populate_sdk QA error: ERROR: ptest-runner-2.4.5+git-r0 do_package: QA Issue: File '/usr/bin/ptest-runner' from ptest-runner was already stripped, this will prevent future debugging! [already-stripped] ERROR: ptest-runner-2.4.5+git-r0 do_package: Fatal QA errors were found, failing task. ERROR: Logfile of failure stored in: /work/QNX/imx-yocto-bsp/build-imx8dxl-b0/tmp/work/cortexa35-fsl-linux/ptest-runner/2.4.5+git/temp/log.do_package.2700152 ERROR: Task (/work/QNX/imx-yocto-bsp/sources/poky/meta/recipes-support/ptest-runner/ptest-runner_2.4.5.bb:do_package) failed with exit code '1' Linux Yocto Project Re: How to fix Yocto QA error [already-stripped] Thanks for your reply. This QA occured on Ubuntu 20.04, but it did not happen on Ubuntu 22.04. Although I don't know the reason, it seems to be caused by the OS version. Adding INSANE_SKIP can skip it with ptest-runner, but there are many packages with this problem. So, the best way may be updating the os version. Re: How to fix Yocto QA error [already-stripped] Hello, The QA error happens because the binary is stripped too early, blocking debugging. You can fix it by skipping the already-stripped check in the recipe or stopping the stripping during the build. Just add INSANE_SKIP_${PN} = "already-stripped" to the recipe and rebuild. Re: How to fix Yocto QA error [already-stripped] Hi, I try to build again with the same steps that you've taken, that is success. NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/4.6/x86_64-nativesdk-libc-4.6.tar.xz;sha256sum=6bf00154c5a7bc48adbf63fd17684bb87eb07f4814fbb482a3fbd817c1ccf4c5 (will check PREMIRRORS first) Sstate summary: Wanted 2888 Local 0 Mirrors 0 Missed 2888 Current 0 (0% match, 0% complete)############################### | ETA: 0:00:00 Initialising tasks: 100% |############################################################################################################| Time: 0:00:03 NOTE: Executing Tasks WARNING: gnu-config-native-20240101+git-r0 do_fetch: Failed to fetch URL git://git.savannah.gnu.org/git/config.git;protocol=https;branch=master, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 6495 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 10 seconds Summary: There were 3 WARNING messages. Please try to clean the recipe "ptest-runner" and then rebuild it. bitbake -c cleanall ptest-runner My host: 22.04.1-Ubuntu Regards Harvey

example application from sdk i.e. ethosu_apps is not running as expected I'm trying to following instructions (from section 6.2.7 ) on building Cortex-M33 firmware from the SDK downloaded. using GNU arm toolchain 13.x , I'm able to compile the demo application ethosu_apps But from uboot when I ran it, I'm seeing error logs in COM/serial port of Cortex M33 ================== Initialize Arm Ethos-U E: NPU error(s) occured during inference. (ethosu_driver.c:542) E: NPU status=0x00000804, qread=0, cmd_end_reached=0 (ethosu_device_u55_u65.c:182) Node ethos-u (number 0) failed to invoke with status 1 E: Invoke failed for inference: job=job (inference_process.cpp:281) Inference status: failed ================== I expected it to work as is, can someone help me here ? NPU|ML Re: example application from sdk i.e. ethosu_apps is not running as expected Thanks @Chavira . with the supplied patch I can see label_image working as expected. Re: example application from sdk i.e. ethosu_apps is not running as expected Hi @phanichinimilli! Please try attached patch. Re: example application from sdk i.e. ethosu_apps is not running as expected Thanks @Chavira , With the suggested change I can see ethosu_apps.bin seems to be working as expected when launched from uboot. Have you got a chance to look into the issue I've mentioned in post ? Re: example application from sdk i.e. ethosu_apps is not running as expected HI @phanichinimilli! Please try below change. --- a/boards/mcimx93evk/demo_apps/ethosu_apps/source/ethosu_apps.cpp +++ b/boards/mcimx93evk/demo_apps/ethosu_apps/source/ethosu_apps.cpp @@ -36,7 +36,7 @@ #endif #define DDR_MEMORY_ADDRESS 0x8C000000 -#define OCRAM_MEMORY_ADDRESS 0x204E0000 +#define OCRAM_MEMORY_ADDRESS 0x204D0000 #define BYTES_TOPRINT 0x30000 Re: example application from sdk i.e. ethosu_apps is not running as expected Its pleasing to see quick responses. In your step #3 I'm afraid , you need to pass external_delegate argument to label_image for the inference to run on ETHOSU, else the inference runs on A55, that is why the inference results are in A55 lines. (Please forgive me for confusing you with label_image_release vs label_image, it is actually label_image ) If you provide external delegate argument to label_image, logs on M33 console would be seen, ref to section-2.7.2  (you might have to provide vela model if the command doesnt work -- for me it works only with vela model) > cd /usr/bin/tensorflow-lite-2.16.2/examples > vela mobilenet_v1_1.0_224_quant.tflite > ./label_image -m output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l labels.txt --external_delegate_path=/usr/lib/libethosu_delegate.so The above procedure works okay(below) for me with default/original ethosu_firmware, /usr/bin/tensorflow-lite-2.16.2/examples# ./label_image -m output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l labels.txt -external_delegate_path=/usr/lib/libethosu_delegate.so INFO: Loaded model output/mobilenet_v1_1.0_224_quant_vela.tflite INFO: resolved reporter INFO: before CreateAllDelegates INFO: Ethosu delegate: device_name set to /dev/ethosu0. INFO: Ethosu delegate: cache_file_path set to . INFO: Ethosu delegate: timeout set to 60000000000. INFO: Ethosu delegate: enable_cycle_counter set to 0. INFO: Ethosu delegate: enable_profiling set to 0. INFO: Ethosu delegate: profiling_buffer_size set to 2048. INFO: Ethosu delegate: pmu_event0 set to 0. INFO: Ethosu delegate: pmu_event1 set to 0. INFO: Ethosu delegate: pmu_event2 set to 0. INFO: Ethosu delegate: pmu_event3 set to 0. INFO: EXTERNAL delegate created. INFO: EthosuDelegate: 1 nodes delegated out of 1 nodes with 1 partitions. INFO: Applied EXTERNAL delegate. INFO: settings->number_of_warmup_runs 2 INFO: invoked INFO: average time: 3.762 ms INFO: Predicted label = 907 But If I replace default one with compiled one I see error(below) and can see logs in M33 console, My expectation is that with compiled ethosu_firmware inference should be successful /lib/firmware/# reboot /lib/firmware/# cp ethosu_apps_rpmsg.elf ethosu_firmware /usr/bin/tensorflow-lite-2.16.2/examples# ./label_image -m output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l labels.txt -external_delegate_path=/usr/lib/libethosu_delegate.so INFO: Loaded model output/mobilenet_v1_1.0_224_quant_vela.tflite INFO: resolved reporter INFO: before CreateAllDelegates INFO: Ethosu delegate: device_name set to /dev/ethosu0. INFO: Ethosu delegate: cache_file_path set to . INFO: Ethosu delegate: timeout set to 60000000000. INFO: Ethosu delegate: enable_cycle_counter set to 0. INFO: Ethosu delegate: enable_profiling set to 0. INFO: Ethosu delegate: profiling_buffer_size set to 2048. INFO: Ethosu delegate: pmu_event0 set to 0. INFO: Ethosu delegate: pmu_event1 set to 0. INFO: Ethosu delegate: pmu_event2 set to 0. INFO: Ethosu delegate: pmu_event3 set to 0. INFO: EXTERNAL delegate created. INFO: EthosuDelegate: 1 nodes delegated out of 1 nodes with 1 partitions. INFO: Applied EXTERNAL delegate. INFO: settings->number_of_warmup_runs 2 ERROR: Ethos_u inference failed ERROR: Node number 1 (EthosuDelegate) failed to invoke. ERROR: Failed to invoke tflite *** In both the cases Im seeing expected logs on M33 COM port 2. My observations of running M33 executables from linux i.e. by using "remoteproc0" are exactly same as yours. 3. Inference runner is different example that runs inference on ethosu. This example seems to work with both firmwares in step#1 #cd /usr/bin/ethosu/examples #./inference_runner -d /dev/ethosu0 -n output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l labels.txt -o output_data_detection -t 1080000000 Re: example application from sdk i.e. ethosu_apps is not running as expected Hi @phanichinimilli! I got the next response from the apps team: I can reproduce identical ethosu_apps_rpmsg.bin startup success from U-Boot (I assume because the rpmsg app doesn't attempt any inferences) and the same ethosu_apps.bin failure on SDK 2.16.000, gcc-arm-eabi-none-10-2020-q4-major (as noted in UG10166) and BSP LF6.6.52-2.2.0. I launched it from U-Boot as follows (the bootaux 0x201e0000 0 address in UG10166 is suspect): u-boot=> fatload mmc 1:1 ${loadaddr} ethosu_apps.bin 49800 bytes read in 3 ms (15.8 MiB/s) u-boot=> cp.b ${loadaddr} 0x201e0000 ${filesize} u-boot=> bootaux 0x1ffe0000 0 ## Starting auxiliary core addr = 0x1FFE0000... u-boot=> █ Just as you observed on the Cortex-M33 console: Initialize Arm Ethos-U E: NPU error(s) occured during inference. (ethosu_driver.c:542) E: NPU status=0x00000804, qread=0, cmd_end_reached=0 (ethosu_device_u55_u65.c:182) Node ethos-u (number 0) failed to invoke with status 1 E: Invoke failed for inference: job=job (inference_process.cpp:281) Inference status: failed However, I find some of the steps in UG10166 a bit confusing. Lack of familiarity isn't helping matters. E.g., there is no middleware/ethos-u-core-software/examples directory. E.g., .out vs. .bin . Repeating your steps: using 2.16 sdk build ethosu_apps_rpmsg application boot linux, replace ethosu_firmware with elf of #1 Yikes…parameters would make this software less fiddly. Before replacing anything in the imx-image-full YP build it behaved as demonstratred in §2.7. Then I replaced ethosu_firmware as in steps 1-2: $ cd /lib/firmware $ mv ethosu_firmware ethosu_firmware.orig $ ln -s ethosu_apps_rpmsg.elf ethosu_firmware Note: Booting Linux with the rpmsg device tree: setenv fdtfile imx93-11x11-evk-rpmsg.dtb; boot . run default inference test on ethosu from linux ./label_image_release -m output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l lab I was stymied for a bit finding label_image_release in UG10166. (Replacing the obnoxiously long default shell prompt with $␣ in my examples for readability.) Then returning to run label_image again…success. Just to be certain, I rebooted and power cycled and tried again. $ cd /usr/bin/tensorflow-lite-2.16.2/examples/ $ ./label_image -m mobilenet_v1_1.0_224_quant.tflite -i grace_hopper.bmp -l labels.txt INFO: Loaded model mobilenet_v1_1.0_224_quant.tflite INFO: resolved reporter INFO: Created TensorFlow Lite XNNPACK delegate for CPU. INFO: invoked INFO: average time: 153.342 ms INFO: 0.768627: 653 military uniform INFO: 0.105882: 907 Windsor tie INFO: 0.0196078: 458 bow tie INFO: 0.0117647: 466 bulletproof vest INFO: 0.00784314: 835 suit observe logs in M33 com-port No output. Was the Linux label_image program supposed to do something with ethosu_firmware? I don't see it or the sysfs paths referenced in a dump of the program's string table. E.g., $ strings label_image | grep remoteproc $ strings label_image | grep ethosu $ █ So I'm not sure what steps 1 & 2 have to do with label_image. The CM33 isn't running. I saw nothing in the CM33 serial console. Remoteproc reports offline. So I tried running my symlinked ethosu_firmware from step 2 above: $ cd /sys/devices/platform/remoteproc-cm33/remoteproc/remoteproc0 $ cat state offline $ cat firmware rproc-imx-rproc-fw $ echo /lib/firmware/ethosu_firmware > firmware $ cat firmware /lib/firmware/ethosu_firmware $ echo start > state I observed the expected Initialize Arm Ethos-U on the CM33 serial console. Re-running step 3 gave the same results as above with nothing more printer on the CM33 serial console — it's not interacting with ethosu_firmware. Where am I out of sync with you? I've tried to be copy-paste exact in my procedure. P.S: while inference_runner command works fine with my ethosu_firmware ./inference_runner -d /dev/ethosu0 -n output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l labels.txt -o output_data_detection -t 1080000000 Did your postscript get cut off while you were composing this message? FWIW, my attempt to run ethosu_apps.elf from remoteproc failed: $ echo /lib/firmware/ethosu_apps.elf >firmware $ cat state offline $ echo start >state -bash: echo: write error: Invalid argument $ cat state offline $ dmesg | tail [ 61.593023] audit: type=1327 audit(1709089028.676:26): proctitle="(systemd)" [ 61.593650] audit: type=1334 audit(1709089028.676:27): prog-id=22 op=LOAD [ 252.292643] remoteproc remoteproc0: powering up imx-rproc [ 252.292727] remoteproc remoteproc0: Direct firmware load for /lib/firmware/ethosu_apps.elf failed with error -2 [ 252.292737] remoteproc remoteproc0: Falling back to sysfs fallback for: /lib/firmware/ethosu_apps.elf [ 252.295520] remoteproc remoteproc0: Booting fw image /lib/firmware/ethosu_apps.elf, size 227536 [ 252.308739] imx-rproc remoteproc-cm33: Translation failed: da = 0xffec288 len = 0x60000 [ 252.308761] remoteproc remoteproc0: bad phdr da 0xffec288 mem 0x60000 [ 252.308766] remoteproc remoteproc0: Failed to load program segments: -22 [ 252.309016] remoteproc remoteproc0: Boot failed: -22 Re: example application from sdk i.e. ethosu_apps is not running as expected Chavira, Thanks for confirmation. on ethosu_apps A small clarification is needed on ethosu_apps_rpmsg, can you please confirm at your side? What I have done ? 1. using 2.16 sdk build ethosu_apps_rpmsg application 2. boot linux, replace ethosu_firmware with elf of #1 3. run default inference test on ethosu from linux ./label_image_release -m output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l lab INFO: Loaded model output/mobilenet_v1_1.0_224_quant_vela.tflite INFO: resolved reporter INFO: before CreateAllDelegates INFO: Ethosu delegate: device_name set to /dev/ethosu0. INFO: Ethosu delegate: cache_file_path set to . INFO: Ethosu delegate: timeout set to 60000000000. INFO: Ethosu delegate: enable_cycle_counter set to 0. INFO: Ethosu delegate: enable_profiling set to 0. INFO: Ethosu delegate: profiling_buffer_size set to 2048. INFO: Ethosu delegate: pmu_event0 set to 0. INFO: Ethosu delegate: pmu_event1 set to 0. INFO: Ethosu delegate: pmu_event2 set to 0. INFO: Ethosu delegate: pmu_event3 set to 0. INFO: EXTERNAL delegate created. INFO: EthosuDelegate: 1 nodes delegated out of 1 nodes with 1 partitions. INFO: Applied EXTERNAL delegate. INFO: settings->number_of_warmup_runs 2 ERROR: Ethos_u inference failed ERROR: Node number 1 (EthosuDelegate) failed to invoke. ERROR: Failed to invoke tflite! 4. observe logs in M33 com-port I can see logs are same , when compared to default ethosu_firmware executable P.S: while inference_runner command works fine with my ethosu_firmware ./inference_runner -d /dev/ethosu0 -n output/mobilenet_v1_1.0_224_quant_vela.tflite -i grace_hopper.bmp -l labels.txt -o output_data_detection -t 1080000000 Re: example application from sdk i.e. ethosu_apps is not running as expected HI @phanichinimilli! I was thinking that you have the problem on iMX93-QSB board. I tried with the iMX93-EVK and the ethosu_apps_rpmsg is working as expected but the ethosu_apps have an issue in iMX93-EVK. I will report this issue to our internal team and I will update this community post as soon as possible with the solution of the apps  team. Best Regards! Chavira Re: example application from sdk i.e. ethosu_apps is not running as expected Thanks for the response. I'm using sdk of imx93_evk (not imx93_qsb), Im not sure if it makes any difference. >tftp 0x80000000 ethosu_apps.bin >cp.b 0x80000000 0x201e0000 0x20000 >bootaux 0x1ffe0000 0 Do I have set any env variables in uboot ? Please let me know if I'm missing any step. P.S:  The ethosu_apps_rpmsg application from sdk is not behaving, similar to ethosu_firmware Re: example application from sdk i.e. ethosu_apps is not running as expected HI @phanichinimilli! Thank you for contacting NXP Support! I tried with the iMX93-QSB and I didn't see errors. I compiled the example using MCUXPRESSO for VS CODE the version of the SDK that I am using is 2.16. Best Regards! Chavira