How to setup and use the libcamera on the imx8mplus We need to perform the libcamera software ISP on the imx8mplus board to understand how efficiently it can work. According to official libcamera documents it have the support for the IMX8MP for both hardware ISP and also with ISI. I think from the ISI it is with software ISI. But the documentation/guide to perform this is unclear and very confusing. I am new to libcamera and a lot of confusions on how it works exactly and how it is going to help us in this software ISP part. we have tested the gstreamer bayer2rgb element also, not satisfied with results.  Our som is imx8mplus & kernel version  6.6.52-compulab-4.1-g94ac18e782b4-dirty. Thanks and regards  Vishnu S i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: How to setup and use the libcamera on the imx8mplus Hello,   For the implementation of libcamera in our BSP you can refer to chapter 7.3.9 Libcamera in the i.MX Linux User's Guide    Also as reference there is an open source on GitLab  https://gitlab.com/ideasonboard/nxp/libcamera 

s32k144 は通信できます例程报错 编译出现以下情况 説明 リソース パス 場所 タイプ make: *** [Sources/subdir.mk:37:ソース/遅延.o]エラー 1 s32k144_Demo_CANFD C/C++ 問題 make: *** [Sources/subdir.mk:37:Sources/font.o]エラー 1 s32k144_Demo_CANFD C/C++ 問題 make: *** [Sources/subdir.mk:38:Sources/key.o]エラー 1 s32k144_Demo_CANFD C/C++ 問題 make: *** [Sources/subdir.mk:38:Sources/main.o]エラー 1 s32k144_Demo_CANFD C/C++ 問題 make: *** [Sources/subdir.mk:38:Sources/oled.o]エラー 1 s32k144_Demo_CANFD C/C++ 問題 make: *** [Sources/subdir.mk:38:Sources/sys_cfg.o]エラー 1 s32k144_Demo_CANFD C/C++ 問題 make: *** 未完了のジョブを待機中.... s32k144_Demo_CANFD C/C++ 問題 Re: s32k144 can通信例程报错 こんにちは 私はS32 Design Studio for ARMバージョン2.2を使用しており、S32 Design Studio for ARM 2.2 - Update 1がインストールされています。Processor Expertコードを生成し、正常にコンパイルできます。 よろしくお願いします、 ロビン ------------------------------------------------------------------------------- 注記： この投稿があなたの質問への回答になっている場合は、「解決策として承認」ボタンをクリックしてください。ありがとう！ - 最後の投稿から7週間はスレッドをフォローしますが、それ以降の返信は無視されます。 後日、関連する質問がある場合は、新しいスレッドを作成し、閉じられたスレッドを参照してください。 -------------------------------------------------------------------------------

S32K566 IMCR 競合エラー MCU: S32K566 MCALパッケージ：RTD 0.8.0（S32K5_RTD_0_8_0_D2512_ASR_REL_4_9_REV_0000_20251205） ポートプラグイン: Port_TS_T40D85M8I0R0 ツール: EB Tresos / NXP MCAL ジェネレーター (McalGenerator_Nxp_S32K5-0.8.0) 説明： Port MCALプラグインを使用して、S32K566の複数のADC0アナログ入力ピンを設定しようとしています。複数のADC0入力チャネルを設定すると、コードジェネレーターがIMCR競合エラーを報告します。 構成： PCR 209 → モード: ADC0_ADC0_CH2_P2_IN (SIUL2_3のPORT209にマッピングされています) PCR 226 → モード: ADC0_ADC0_CH4_P4_IN （SIUL2_3のPORT226にマッピングされています） 問題： ADCピンが1つだけ設定されている場合、コード生成は成功しますが、IMCRインデックスは0と報告されます。2つ目のADCピンを追加すると、両方のピンがSIUL2_3上の同じIMCRインデックス0にマッピングされるため、IMCR競合エラーが発生します。 Port_S32K5_Resource.m ファイルを調べたところ、すべての ADC0 アナログ入力チャネルが IMCR マッピング 0 で定義されていることがわかりました。 この問題を解決するには、どのような設定変更が必要ですか？ これが既知のバグである場合、何か回避策はありますか？ Re: S32K566 IMCR Confilct Error こんにちは、 @JaeHeonJeong さん。 S32K5はまだNPI（新製品導入）段階にあるため、専用のサポートチャネルをご利用いただくことをお勧めします。直接FAEサポートにお問い合わせいただくか、こちらのページ（ https://support.nxp.com/s/?language=en_US ）からチケットを送信して、地域のFAEチームに割り当ててください。あるいは、御社専用のプライベートなコミュニティスペースがあるのかもしれませんが、私にはアクセス権限がないので分かりません。 S32K5は、このコミュニティではまだサポートされていません。ご理解いただきありがとうございます。 よろしくお願いいたします。 ルーカス Re: S32K566 IMCR Confilct Error ADC0チャンネルは、異なるIMCRを持つ異なるIOピンに基づいている可能性があります。各IOピンは1つのIMCRに専用されているが、 K556の設定については、比較的新しいデバイスなのでよく分かりません。スクリーンショットを投稿してもらえますか？

IMX95-NAND Support Is there any recommended NAND Flash (2GB or at least 1GB) part which can be used with IMX95 in case we need to use NAND for booting, OS etc. and eMMC for data storage? Also is there any document application note or Board schematic in which IMX95 is interfaced with Serial NAND   Flash Re: IMX95-NAND Support Hi, Thank you for your interest in NXP Semiconductor products, There are not recommended parts since NXP portfolio does not include memories, however this module has been tested for NAND Boot with different processors, give it a try. It contains a W25N02KWZEIR. Regards

在 RW612 上使用 EAP-TLS 您好 我正试图在一个企业接入点上设置 WiFi 连接（我的情况是 WPA2-enterprise，但也可能是其他任何接入点）。 由于需要动态加载证书，我定义了 eap_ca_cert 和 eap_client_key 将数据存储在 RAM 中，并执行以下操作： struct wifi_enterprise_creds_params creds{ .ca_cert = eap_ca_cert, .ca_cert_len = strlen(reinterpret_cast (eap_ca_cert)), .client_cert = eap_client_cert, .client_cert_len = strlen(reinterpret_cast (eap_client_cert)), .client_key = eap_client_key, .client_key_len = strlen(reinterpret_cast (eap_client_key)) }; net_mgmt(NET_REQUEST_WIFI_ENTERPRISE_CREDS, m_netIface, &creds, sizeof(creds)); struct wifi_connect_req_params params{}; params.ssid = reinterpret_cast (m_wiFiStationConfig.ssid.data()); params.ssid_length = m_wiFiStationConfig.ssid.size(); params.security = WIFI_SECURITY_TYPE_EAP_TLS; static const char* identity = "user@example.org"; params.eap_identity = reinterpret_cast (identity); params.eap_id_length = strlen(identity); net_mgmt(NET_REQUEST_WIFI_CONNECT, m_netIface, &params, sizeof(params)); 对 net_mgmt 的调用没有错误返回，但我没有看到发生任何事情。下面是 wpa_supplicant 日志： 00017717: [networkThread] net_wifi_mgmt: wifi_connect: ssid 45 6d 62 53 57 5f 41 73 75 73 41 50 |EmbSW_As usAP 00017719: [networkThread] net_wifi_mgmt: wifi_connect: psk 00017720: [networkThread] net_wifi_mgmt: wifi_connect: (networkThread): ch 6 sec 7 00017721: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: remove_network, argc: 2 00017723: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: remove_network 00017724: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: all 00017725: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'REMOVE_NETWORK all' 00017727: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: REMOVE_NETWORK all 00017728: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'ADD_NETWORK' 00017730: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: ADD_NETWORK 00017731: [networkThread] wpa_supp: wpa_printf_impl: NET added: 0 00017732: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017733: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017734: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017735: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: ssid 00017736: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: "EmbSW_AsusAP" 00017737: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017739: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='ssid' 00017740: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=14): [REMOVED] 00017742: [hostap_handler] wpa_supp: wpa_printf_impl: ssid - hexdump_ascii(len=12): 00017743: [hostap_handler] wpa_supp: _wpa_hexdump_ascii: 45 6d 62 53 57 5f 41 73 75 73 41 50 |EmbSW_As usAP 00017745: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017746: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017747: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017748: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: scan_ssid 00017749: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: 1 00017751: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017752: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='scan_ssid' 00017753: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=1): [REMOVED] 00017755: [hostap_handler] wpa_supp: wpa_printf_impl: scan_ssid=1 (0x1) 00017756: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017757: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017758: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017759: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: key_mgmt 00017760: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: NONE 00017761: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017763: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='key_mgmt' 00017764: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=4): [REMOVED] 00017766: [hostap_handler] wpa_supp: wpa_printf_impl: key_mgmt: 0x4 00017767: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017768: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017769: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017770: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: ieee80211w 00017771: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: 0 00017772: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017774: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='ieee80211w' 00017775: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=1): [REMOVED] 00017777: [hostap_handler] wpa_supp: wpa_printf_impl: ieee80211w=0 (0x0) 00017778: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017779: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017780: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017781: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: proto 00017782: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: RSN 00017783: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017785: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='proto' 00017786: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=3): [REMOVED] 00017787: [hostap_handler] wpa_supp: wpa_printf_impl: proto: 0x2 00017789: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017790: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017791: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017792: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: key_mgmt 00017793: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: WPA-EAP 00017794: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017796: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='key_mgmt' 00017797: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=7): [REMOVED] 00017798: [hostap_handler] wpa_supp: wpa_printf_impl: key_mgmt: 0x1 00017799: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set, argc: 3 00017801: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set 00017802: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: openssl_ciphers 00017803: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: "DEFAULT:!EXP:!LOW" 00017804: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET openssl_ciphers "DEFAULT:!EXP:!LOW"' 00017806: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE SET 'openssl_ciphers'='"DEFAULT:!EXP:!LOW"' 00017807: [hostap_handler] wpa_supp: wpa_printf_impl: openssl_ciphers='"DEFAULT:!EXP:!LOW"' 00017809: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017810: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017811: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017812: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: group 00017813: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: CCMP 00017814: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017816: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='group' 00017817: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=4): [REMOVED] 00017818: [hostap_handler] wpa_supp: wpa_printf_impl: group: 0x10 00017819: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017821: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017822: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017823: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: pairwise 00017824: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: CCMP 00017825: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017826: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='pairwise' 00017828: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=4): [REMOVED] 00017829: [hostap_handler] wpa_supp: wpa_printf_impl: pairwise: 0x10 00017830: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017831: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017832: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017833: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: group_mgmt 00017834: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: AES-128-CMAC 00017836: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017837: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='group_mgmt' 00017839: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=12): [REMOVED] 00017840: [hostap_handler] wpa_supp: wpa_printf_impl: group_mgmt: 0x20 00017841: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017842: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017843: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017844: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: proto 00017845: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: RSN 00017847: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017848: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='proto' 00017849: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=3): [REMOVED] 00017851: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017852: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017853: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017854: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: eap 00017855: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: TLS 00017856: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017858: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='eap' 00017859: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=3): [REMOVED] 00017860: [hostap_handler] wpa_supp: wpa_printf_impl: eap methods - hexdump(len=16): 00 00 00 00 0d 00 00 00 00 00 00 00 00 00 00 00 00017862: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017864: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017865: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017866: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: identity 00017867: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: "user@example.org" 00017868: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017869: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='identity' 00017871: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=18): [REMOVED] 00017872: [hostap_handler] wpa_supp: wpa_printf_impl: identity - hexdump_ascii(len=16): 00017873: [hostap_handler] wpa_supp: _wpa_hexdump_ascii: 75 73 65 72 40 65 78 61 6d 70 6c 65 2e 6f 72 67 |user@exa mple.org 00017876: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017877: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017878: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017879: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: anonymous_identity 00017880: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: "(null)" 00017881: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017883: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='anonymous_identity' 00017884: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=8): [REMOVED] 00017886: [hostap_handler] wpa_supp: wpa_printf_impl: anonymous_identity - hexdump_ascii(len=6): 00017887: [hostap_handler] wpa_supp: _wpa_hexdump_ascii: 28 6e 75 6c 6c 29 |(null) 00017889: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017891: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017892: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017892: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: ca_cert 00017893: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: "blob://ca_cert" 00017895: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017896: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='ca_cert' 00017898: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=16): [REMOVED] 00017899: [hostap_handler] wpa_supp: wpa_printf_impl: ca_cert - hexdump_ascii(len=14): 00017900: [hostap_handler] wpa_supp: _wpa_hexdump_ascii: 62 6c 6f 62 3a 2f 2f 63 61 5f 63 65 72 74 |blob://c a_cert 00017903: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017904: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017905: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017906: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: client_cert 00017907: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: "blob://client_cert" 00017908: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017910: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='client_cert' 00017911: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=20): [REMOVED] 00017912: [hostap_handler] wpa_supp: wpa_printf_impl: client_cert - hexdump_ascii(len=18): 00017914: [hostap_handler] wpa_supp: _wpa_hexdump_ascii: 62 6c 6f 62 3a 2f 2f 63 6c 69 65 6e 74 5f 63 65 |blob://c lient_ce 72 74 |rt 00017917: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017918: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017920: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017920: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: private_key 00017921: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: "blob://private_key" 00017923: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017924: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='private_key' 00017926: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=20): [REMOVED] 00017927: [hostap_handler] wpa_supp: wpa_printf_impl: private_key - hexdump_ascii(len=18): 00017928: [hostap_handler] wpa_supp: _wpa_hexdump_ascii: 62 6c 6f 62 3a 2f 2f 70 72 69 76 61 74 65 5f 6b |blob://p rivate_k 65 79 |ey 00017932: [networkThread] wpa_supp: wpa_printf_impl: Calling wpa_cli: set_network, argc: 4 00017933: [networkThread] wpa_supp: wpa_printf_impl: argv[0]: set_network 00017934: [networkThread] wpa_supp: wpa_printf_impl: argv[1]: 0 00017935: [networkThread] wpa_supp: wpa_printf_impl: argv[2]: private_key_passwd 00017936: [networkThread] wpa_supp: wpa_printf_impl: argv[3]: "(null)" 00017937: [hostap_handler] wpa_supp: wpa_printf_impl: ml: Control interface command 'SET_NETWORK [REMOVED]' 00017939: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: SET_NETWORK id=0 name='private_key_passwd' 00017940: [hostap_handler] wpa_supp: wpa_printf_impl: CTRL_IFACE: value - hexdump_ascii(len=8): [REMOVED] 00017942: [hostap_handler] wpa_supp: wpa_printf_impl: private_key_passwd - hexdump_ascii(len=6): [REMOVED]   我是不是漏掉了什么？这样做可行吗？ RW612 @zephyr Re: Using EAP-TLS on RW612 看起来存在一个已知错误(https://github.com/zephyrproject-rtos/zephyr/issues/94326)。如果在wifi_enterprise_creds_params中定义 ca_cert2、client_cert2 和 client_key2，就能正常工作！

S32DS License Extension Request Hello. My license has expired, so I would like to request an extension. Re: S32DS License Extension Request Hi,  your S32DS license has been extended. Please activate S3DS again with your old code.  Re: S32DS License Extension Request Thank you. It works well.

SafeRTOS_GCC_S32K344_WEB_v9.6.2 I am using SafeRTOS package: SafeRTOS_GCC_S32K344_WEB_v9.6.2 My setup: IDE: S32 Design Studio v3.5 Installed RTD: 3.x Issue: Getting compilation errors (missing headers / driver mismatch) Observation: This SafeRTOS project seems to be based on RTD 6.x Questions: Which exact RTD version is required for this SafeRTOS package? Is RTD 6.0.0 compatible with S32DS v3.5? Do I need any additional plugins or updates in S32DS? Any specific environment variable or path configuration needed? Re: SafeRTOS_GCC_S32K344_WEB_v9.6.2 Thanks for the clarification. Also is their document like RTD_3_0_0_download_latest_July_2024__only_P07 document for 3.6 software installtion. Based on your response, I understand that: RTD 6.0.0 requires S32 Design Studio v3.6.1 My current setup (S32DS v3.5 + RTD 3.x) is not compatible I will migrate to the recommended environment. However, I need some guidance regarding correct setup for S32DS v3.6.x: Could you please confirm the exact installation sequence for: S32 Design Studio v3.6.1 RTD 6.0.0 (S32K3) Should RTD be installed via: S32DS Update Site (Extensions & Updates), or Manual package installation (offline ZIP method)? Is there any specific S32DS v3.6.x update (patch version) required to ensure compatibility with RTD 6.0.0? After installation, are there any additional steps required such as: SDK path configuration Environment variables Toolchain selection Can you confirm if importing the SafeRTOS project directly will automatically detect RTD 6.0.0, or manual configuration is needed? Re: SafeRTOS_GCC_S32K344_WEB_v9.6.2 Hi, Q: Which exact RTD version is required for this SafeRTOS package? A: SafeRTOS is a 3rd‑party product, so NXP cannot strictly define which RTD version is required. This is primarily a question for the SafeRTOS package developer. If the developer states that the package is based on RTD 6.0.0, then that RTD version should be used. Q: Is RTD 6.0.0 compatible with S32 Design Studio v3.5? A: No. RTD 6.0.0 is intended to be used with S32 Design Studio v3.6.1, not v3.5. Q: Do I need any additional plugins, updates, or special configuration? A: No. If the SafeRTOS package is based on RTD 6.0.0, then using S32DS v3.6.1 with RTD 6.0.0 installed is sufficient. No additional plugins, environment variables, or special configuration are required. BR, Petr Re: SafeRTOS_GCC_S32K344_WEB_v9.6.2 Hi, you can follow bellow video guides on https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/How-To-Download-Install-Activate-and-Use-the-S32-Design-Studio/ta-p/2015086 https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/How-To-Download-Install-and-Configure-the-RTD-5-0-0-with-S32/ta-p/2015104 Different RTD version is used in this video, but steps are the same.  When you import a project into S32DS, the RTD version is not automatically checked. BR, Petr

NVT4858HK - Output to Output and Part to Part Skew for VCCA=1.8V and VCCB=1.8V. Also use for QSPI Hi,  As shown in below image from below linked NVT4848 datasheet, the output to output skew for the NVT4858HK is specified at 200ps max with VCCA=1.2V and VCCB = 3.3V OR 1.8V.  I would like to confirm:  The output to output skew for all outputs on a single NVT4858HK IC with both VCCA and VCCB operating at the same 1.8V supply voltage The part to part skew for two separate NVT4858HK IC's both operating with VCCA and VCCB operating at the same 1.8V supply voltage (can assume both parts are within same temperature, say within 5C or so) Can NXP please provide this info? I have application where want to use these parts for redriving long traces for eMMC which is 8 bit wide data bus so requires two NVT4858HK parts.  Also considering using as a QSPI redriver for long traces, but want to confirm the skew. Does NXP see any issue using this part for QSPI? https://www.nxp.com/docs/en/data-sheet/NVT4858.pdf Thanks! Level Shifters Re: NVT4858HK - Output to Output and Part to Part Skew for VCCA=1.8V and VCCB=1.8V. Also use for QSP Sorry but I'm not following.  Table 13 from datasheet that I posted in original question provides the output to output skew of the NVT4858HK right? It's 200ps max for clk/cmd to data and 200ps max for data to data? So you do have output to output skew or am I misunderstanding that table? Then I am asking for the skew for case where VCCA=1.8V and VCCB=1.8V.  For part to part skew, in below linked forum post when asked if there would be any timing issue with splitting signals for an SD card interface across two separate NVT4858 parts, you had stated that should not be an issue. This means there must be some known timing relationship between the two parts, right? How can the answer to that post be no issue if there is no info about timing between two NVT4858 parts? https://community.nxp.com/t5/Digital-Signal-Controllers/two-NVT4858-use-question/m-p/1484273  And in this forum post, user shows schematic with an eMMC interface split across multiple NVT4858 parts. How can it be known this would work to meet eMMC timing requirements without knowing skew between the parts? https://community.nxp.com/t5/High-Performance-Analog-Front/CLK-CMD-and-DATA-pins-unconnected-when-they-are-unused-right/m-p/2096977  Re: NVT4858HK - Output to Output and Part to Part Skew for VCCA=1.8V and VCCB=1.8V. Also use for QSP HI Steve Unfortunately we don't have others about the output to output and part to part skew for NVT4848 except datasheet's parameters. But it can be used in QSPI communication and without any issue. Thanks! Re: NVT4858HK - Output to Output and Part to Part Skew for VCCA=1.8V and VCCB=1.8V. Also use for QSP Alright then.  One additional question, can you confirm the NVT4858HK is suitable for 8 bit eMMC level translation?

Sensorless PMSM Field-Oriented Control V2 I am currently implementing sensorless control for PMSM using field-oriented control in combination with the AMCLIB_PMSMBemfObsrvDQ and the AMCLIB_TrackObsrv for the ARM Cortex M7F. I have a several kW motor with a mechanical speed sensor mounted to the shaft. I am using as a reference the DRM148 Rev.1, 02/2016. I would like to achieve a situation where I have sensored closed-loop FOC with an observer running in parallel in the background fed with the right feedback information such that in a steady-state condition the measured (sensor) speed and the estimated observer speed converge. Referring back to Fig. 23, from the DRM148, the estimated observer speed is converging near the open-loop speed during start-up. In the AMCLIB_PMSMBemfObsrvDQ I use the sensor speed output (converted to angular electrical rotor speed) as an input to the BEMF observer from standstill (so no open-loop startup). From 0 - 100 RPM the observer is initialized, whereas for speed >100 RPM it uses feedback and the init function is not used anymore. Furthermore, the requested voltages (Udq*) and currents (Idq*) are used for the BEMF observer input(s). I convert the AMCLIB_TrackObsrv output electrical rotor speed to mechanical speed in RPM and visually compare this to the actual rotor/sensor mechanical shaft speed. This all happens in closed-loop manner (sensored). However, the AMCLIB_TrackObsrv output speed still does not converge on a long time frame (e.g. >10 seconds) while keeping the rotor speed constant (e.g. 500 RPM). This is in no-load condition. When applying load to the motor shaft the estimated mechanical speed from the observer decreases rapidly. What are possible causes for this difference in RPM between the true sensor mechanical speed and the estimated observer mechanical speed when using sensored closed-loop control? Re: Sensorless PMSM Field-Oriented Control V2 Hello @General_motor_control , Thanks for your post. Could you let me know which specific NXP product you are using? Is it i.MX RT or another else? BR Celeste Re: Sensorless PMSM Field-Oriented Control V2 Hello @General_motor_control , It may be several factors can explain why the observer speed does not converge to the sensor speed. The most common is wrong observer inputs. The BEMF observer in DRM148 expects actual applied voltage and measured currents, not references (Udq*, Idq*). The model explicitly relies on the motor voltage equation (incl. Rs·I + dψ/dt), so any mismatch between commanded and real voltage (dead-time, DC-bus ripple, saturation) introduces steady error. And sometimes parameter mismatch (Rs, Ld/Lq, Ke) may occur. The observer is model-based, it uses an RL current observer + BEMF estimation. Even small Rs or inductance errors cause bias in estimated BEMF resulting in wrong speed. Also pay attention to scaling / unit inconsistency. DRM148 uses fixed-point fractional scaling for all quantities. Any mismatch (voltage, current, speed normalization) leads to slow drift or offset. Double-check scaling and pole-pair conversion is necessary. Hope it help you. BR Celeste

Wrynose - relase date? Hi, new yocto release is coming - when can we expect meta-qoriq bsp with wrynose support? I need to plan whether we will be able to switch to a new release before we freeze our code base.  Re: Wrynose - relase date? Hello, NXP currently documents/supports releases such as Kirkstone , Mickledore , and Scarthgap for Layerscape/QorIQ workflows, including meta-qoriq usage in the yocto-sdk manifests. For some component upgrades, NXP does occasionally communicate forward release targets when they are committed. For example, an ATF update in meta-qoriq was stated as planned for 6.12.20-2.0.0-25Q2 .So the planning answer is: there is no verified public schedule for Wrynose support in meta-qoriq BSP . If your code-freeze decision depends on that support landing, the available documentation does not support assuming it will be available in time regards   regards

Success status of flash.bin flashing Flashing of flash.bin of flash_spl binary is successfully completing 100% but later flashiong of wic image is not proceding. Help me in understanding why flash.bin is not rturning done status. Re: Success status of flash.bin flashing Hello, How are you flashing it? Maybe is not able to move to fastboot, you can confirm it in debug console. Best regards. Re: Success status of flash.bin flashing When i checked for SPL in generated flash.bin below is the content. Help me where could i been wrong build-wayland/tmp/deploy/images/imx8qxpc0mek$ strings flash.bin | grep -i spl spl: ERROR: unsupported device SPL: Unsupported Boot Device! SPL: failed to boot from all boot devices U-Boot SPL 2024.04-lf_v2024.04+g6c4545203d1+p0 (Nov 15 2024 - 04:02:13 +0000) SPL: Image overlaps SPL SPL: Image too large spl: unsupported mmc boot device. spl: could not initialize mmc. error: %d spl: could not find mmc device %d. error: %d spl: mmc init failed with error: %d spl: mmc partition switch failed spl: mmc: wrong boot mode display_init Display the FIPS mode of the SoC by reading fuse 0xA, bit 3 Successfully finished the power up sequence of display. SPL Phase TI Keystone SPL Image TI OMAP SPL With GP CH sfspl StarFive SPL Image display MMC info u-boot,dm-spl splashimage=0x9e000000 display-timings display-subsystem fsl,imx-display-subsystem //ldb@562210e0/lvds-channel@0/display-timings/timing0 display0 display1 split_vm_region Re: Success status of flash.bin flashing Hello, The log shows that is not able to find a bootable device. Are you using a custom image? If yes, what changes did you do? Are you using the MEK board? Best regards.

IMX8M Plus NPU — Batched TFLite inference shows no per-image speedup Hi NXP, We're running a quantized (uint8) TFLite segmentation model on the IMX8M Plus NPU using the libvx_delegate.so external delegate. The model is a MobileNet-based UNet with input shape [batch, 256, 256, 3]. To test whether larger batch sizes improve throughput, we've created a separate .tflite file for each batch size (1, 2, 4, 8, 16, 32, 64), each with the batch dimension fixed at conversion time. We then measured both total inference time and per-image time across 10 trials. Expected behaviour: Per-image time should decrease as batch size increases, since the NPU should be able to amortize overhead and better pipeline execution. Observed behaviour: Total inference time scales roughly linearly with batch size, giving a flat per-image time across all batch sizes. Batching provides no throughput benefit. Our questions: Does the VX delegate / NPU on the IMX8M Plus actually support batched execution, or does it process images sequentially regardless of batch size? Is there a recommended way to maximise throughput — e.g. multiple interpreter instances in separate threads, or a different batching API? Are there any eIQ / TIM-VX settings that need to be enabled for true batch parallelism? Any insight appreciated. Thanks. Re: IMX8M Plus NPU — Batched TFLite inference shows no per-image speedup Hi @gabriel_gosden, Thank you for contacting NXP Support! 1) The i.MX8M Plus NPU does not support true batched execution. Even if a TFLite model is converted with a fixed batch dimension, the VX/TIM‑VX stack processes each image in the batch sequentially. This is why total inference time scales linearly with batch size and per‑image latency remains flat. 2) The recommended approach is to use a batch size of one and focus on pipelining and parallelism on the host side. Typical strategies include running preprocessing, NPU inference, and post processing in separate threads, and in some cases using multiple TFLite interpreter instances to overlap CPU work and reduce idle time. Any throughput gains come from better pipeline utilization, not from NPU batch parallelism. 3) There are no eIQ, VX, or TIM‑VX settings that enable true batch parallelism on the i.MX8M Plus. This limitation is architectural rather than configurable. Your measurement results indicate correct and efficient NPU usage, and batching simply does not provide throughput benefits on this hardware. Best Regards, Chavira

HSEファームウェアのロールバック保護が必要ですか？ HSE_Bファームウェアリファレンスマニュアルバージョン2.7には、（セクション11.7）「Secure-BAFを旧バージョンにアップデートすることは許可されていません」と記載されています。しかし、HSEファームウェア（FW-IMG）に関するそのような制限についてのドキュメントは見つかりません。 FW-IMGはロールバック保護されていない、という解釈は正しいでしょうか？ Re: Rollback protection for HSE firmware? こんにちは、 @FredrikMoller さん ドキュメントには、HSE FWのダウングレードが禁止されているとは明示的に記載されていません。しかし、ファームウェアのダウングレードは潜在的なセキュリティリスクを伴うため、現時点では推奨されていません。 開発目的のみで、HSEファームウェアの新しいバージョンでは、HSEファームウェアを消去できるサービスHSE_SRV_ID_ERASE_FWが提供されています。このサービスは、デバイスがCUST_DEL状態にある場合にのみ利用可能ですのでご注意ください。したがって、HSEファームウェアを消去し、その後、古いバージョンのファームウェアをインストールすることができます。 BR、VaneB

DBC file, s32k344: Do we need a DBC file for CAN communication between an S32K344 ECU and VeriStand I am working on a setup where 4 battery cell voltages are generated by a Comemso system, controlled through NI VeriStand, and applied as analog inputs to an NXP S32K344 MCU board. The S32K344 reads these voltages via ADC, runs undervoltage detection logic, and transmits the results (cell voltages and/or underrvoltage status flags) over CAN. The CAN bus is connected to an NI PXIe CAN interface, which uses a DB‑9 connector, and the outputs are visualized and tested in VeriStand / LabVIEW. I have a few questions where I am looking for clarification: For integrating the ECU CAN output with NI VeriStand, is a DBC file required? I have used dbc files for other connections to the PXiE chassis and assuming I have to for S32k344 as well, Could i receive the dbc file for this if there is any? From a hardware perspective, I am a bit unclear about the physical CAN connection: I do not know whether the S32K344 evaluation board provides a DB‑9 connector, or if CAN is only available via board headers or terminals. If the S32K344 board does not have a DB‑9, what is the correct way to connect its CAN interface (through CAN_H / CAN_L) to the PXIe module’s DB‑9 CAN connector? Are there any common mistakes or best practices related to CAN wiring, grounding, or termination that should be followed in such a PXIe‑based ECU test setup, since the voltages that comemso works with is very high. Re: DBC file, s32k344: Do we need a DBC file for CAN communication between an S32K344 ECU and VeriSt Hi @ishoboiM, 1. I believe this question is best to be redirected to NI: Support - NI. As of now, I am not aware of any option to generate a DBC file from within S32DS or RTD drivers. Mainly because a DBC describes application‑level behavior, not hardware. 2.1 No. Usually, S32K3 EVBs provide CAN output as pin headers, or through twisted pair connections, depending on the design and application. You have not mentioned which EVB specifically is being used, but for S32K3X4EVB-T172 (general purpose evaluation board), a normal pin connector is used: 2.2 CAN connector outputs CANH & CANL signals to be directly connected to the bus (termination resistors are still needed). This is then connected to the CAN transceiver TJA1443ATK/TJA1043: 3. Common mistakes include not installing both 120 Ω terminating resistors, not matching the same bitrate and sampling point between nodes, keeping low distances for testing purposes. Also, depending on the CAN transceiver, some initialization is required. On some devices, simply enabling CAN_STB and CAN_EN pins is enough, on others, a more complex initialization routine may be needed.   Best regards, Julián

flexbuilder lsdk2108 支持 SERDES1 协议 0x3333 您好， 我们在自定义主板中使用 LS1046A，图像是使用 flexbuild lsdk2108 编译的，我们的设计与 ARDB 开发套件类似。SERDES1 支持两个 10G 端口和两个 1G 端口，不使用 SERDES2。 我们已经根据我们的自定义主板编译了图像，一切正常，10G 端口 (xgmii) 和 1G 端口 (sgmii) 都运行正常。在我们的一个应用中，我们希望将两个 10G 端口都用作 1G 端口。为此，我们更改了 rcw、uboot 和 linux dts 文件。随函附上这些文件以供参考。 编译和主板启动后，我们可以看到 Linux 日志仍在寻找 10G 端口，而 ubuntu 文件系统没有显示 fm1-mac1 和 fm1-mac2 端口。附上启动日志以供参考。 从启动日志中可以明显看出，我们缺少了一些需要更改的内容。在这方面，要求支持需要修改哪些文件才能满足我们的要求。 谢谢& Regards-- 纳古尔瓦利-赛亚德 Re: flexbuilder lsdk2108 support for SERDES1 protocol 0x3333 您好， 感谢您的回复。按照建议，在 rcw、u-boot 和 linux dts 文件中进行更改。从所附的上一个日志文件中可以看到，初始信息显示如下。 "ETH0：FM1-MAC1，ETH1：FM1-MAC2，ETH2：FM1-MAC3，ETH3：FM1-MAC4，ETH4：FM1-MAC5，ETH5：FM1-MAC6 " 更改 u-boot dts 文件后，出现 fm1-mac1 和 fm1-mac2。请建议我们需要对 eth.c 文件做哪些修改。 此外，是否还需要修改任何其他文件。 谢谢& Regards-- 纳古尔瓦利-赛亚德 Re: flexbuilder lsdk2108 support for SERDES1 protocol 0x3333 你好 是的--对于 LS1046A，将两个 10G SerDes1 端口改为 1G 并不仅仅是 Linux DTS 变动。你需要对齐所有三层：RCW、U-Boot 主板以太网修复和 Linux DTS。如果 Linux 仍在探测 10G 端口，而 fm1-mac1 / fm1-mac2 没有出现，那么最有可能的问题是 U-Boot 在 Linux 启动之前仍在 DT 中禁用这些 MAC 节点 要使两个 LS1046A 10G 端口用作 1G 端口，必须将 RCW 更改为 SGMII 协议，例如 0x3333 ，更新 U-Boot eth.c 以使其不会禁用这些 MAC 节点，并更新 Linux DTS，以便使用正确的 PHY 或固定链路配置将这些端口描述为 sgmii。 此致问候 Re: flexbuilder lsdk2108 support for SERDES1 protocol 0x3333 您好， 我们按照建议修改了 rcw、eth.c、uboot dts 和 linux dts。现在我们可以枚举 Linux 启动后的 fm1-mac1 和 fm1-mac2 端口（附上以供参考）。 但我们无法通过这些端口进行数据通信。 还附上了日志文件以供参考。 请审查这些修改意见，并就需要做哪些修改提出进一步建议。 谢谢 -- 纳古尔瓦利-赛亚德

S32G-VNP-RDB3 GMAC こんにちは、S32G-VNP-RDB3 ボードで GMAC を使用したフレーム プリエンプションを実装していますが、1G bps で成功しました。10M bpsに変更したいのですが、変更できないので、制限は1G bpsでなければならないのでしょうか？ Re: S32G-VNP-RDB3 GMAC まず、ご回答いただきありがとうございます。私は2枚のS32G-VNP-RDB3ボードを用意し、GMAC同士を1対1のリンクで接続した後、フレームプリエンプションを実行しました。コアはMコアで処理された。私はループバックを使用せずに進めました。この時、時計や設定を写真のように設定しましたが、tx、rxと同様に、フレームプリエンプションのハンドシェイクがこの時点では発生しないという現象が見られました。解決策が必要です！ Re: S32G-VNP-RDB3 GMAC こんにちは、 @dongmin さん、 お問い合わせいただきありがとうございます。ご質問についてですが、プリエンプション設定は1Gbps専用ではありません。Gmac_Ip_InternalLoopbackを素早く変更して、プリエンプションと 10M bps を使用するようにしたところ、うまく動作しました。より的確なサポートを提供できるよう、以下の情報をお知らせください。 10Mbpsに設定できないというのはどういう意味ですか？ 両方の構成をどのようにテストしているか説明してください。 アプリケーションを実行しているコア数をお知らせください。 お使いのRTDおよび/またはBSPのバージョンをお知らせください。 ありがとうございます。 Re: S32G-VNP-RDB3 GMAC 私は今まさにこのように使っています！ Re: S32G-VNP-RDB3 GMAC こんにちは、 @dongmin さん、 詳細を教えていただきありがとうございます。こちら側で問題を再現してみて、解決策を見つけたいと思います。 可能であれば、前回の返信でお願いした情報を共有してください。 よろしくお願いします。 Re: S32G-VNP-RDB3 GMAC こんにちは、 @dongmin さん、 返信が遅くなり申し訳ありません。問題が再現できませんでした。プロジェクトを共有していただけますか？あるいは、問題が確認できるような簡略化されたバージョンを共有していただけますか？このコミュニティのプライベートメッセージ機能を利用するか、このThreadに言及したプライベートサポートチケットを作成してください。 よろしくお願いします。

rptr 停留在 AMDGPU [GFX 环测试超时] 中 你好 ，当 Amdgpu 调用 amdgpu_ih_process() 函数时，它会检查 rptr 是否等于 wptr，如果不等于，它就会调用 amdgpu_irq_dispatch() 函数，在这里我得到了以下错误信息 [ 26.272978] [drm:amdgpu_ih_process [amdgpu]] amdgpu_ih_process: rptr 0, wptr 16 [ 26.281052] [drm:amdgpu_irq_dispatch [amdgpu]]未注册中断 src_id：140 of client_id:0 [ 26.454946] amdgpu 0000:01:00.0：[drm:amdgpu_ring_test_helper[amdgpu]]*ERROR* ring gfx 测试失败 (-110) [ 26.465393] [drm:amdgpu_device_init [amdgpu]]]*ERROR* hw_init of IP block failed -110 [ 26.474932] amdgpu 0000:01:00.0：amdgpu: amdgpu_device_ip_init 失败 [ 26.481415] amdgpu 0000:01:00.0：amdgpu: GPU 启动过程中出现致命错误 [ 26.487791] amdgpu 0000:01:00.0：amdgpu：amdgpu：整理设备。 [ 26.494006] [drm:gfx_v8_0_set_eop_interrupt_state [amdgpu]] invalid me 2 [ 26.501433] [drm:gfx_v8_0_set_eop_interrupt_state [amdgpu]] invalid me 2 [ 26.508860] [drm:gfx_v8_0_set_eop_interrupt_state [amdgpu]] invalid me 2 [ 26.516252] [drm:gfx_v8_0_set_eop_interrupt_state [amdgpu]] invalid me 2 Re: rptr is stuck in AMDGPU [GFX ring test timeout] 你好 请分享更多信息，您正在使用什么MPU、自定义或恩智浦EVK、BSP版本以及您正在运行的完整测试。

S32G-VNP-RDB3 GMAC 你好，我正在用 GMAC 和 S32G-VNP-RDB3 主板进行帧抢占，但我成功实现了 1G bps。但我想把它改为 10M bps，但我做不到，那么限制必须是 1G bps 吗？ Re: S32G-VNP-RDB3 GMAC 首先，感谢您的回答。我有两个 S32G-VNP-RDB3 主板，通过 1:1 的链路将 GMAC 相互连接，然后继续进行帧抢占。使用 M 型磁芯。我没有使用环回，而是继续进行。此时，我如图所示设置了时钟和设置，但我看到了一个现象，此时没有发生帧抢占的握手，就像 tx、rx 一样。我需要一个解决方案！ Re: S32G-VNP-RDB3 GMAC 你好，@dongmin、 感谢您联系我们。关于您的问题，抢占配置并不只适用于 1G bps。 我迅速修改了Gmac_Ip_InternalLoopback，使用抢占和 10M bps，结果成功了。请提供以下信息，以便我为您提供更多帮助： 您说"不能" 配置为 10M bps 是什么意思？ 请说明您是如何测试这两种配置的。 请说明您是在哪个内核上运行应用程序的。 请分享您的 RTD 和/或 BSP 版本。 谢谢。 Re: S32G-VNP-RDB3 GMAC 我现在就是这么用的！ Re: S32G-VNP-RDB3 GMAC 你好@dongmin、 感谢您提供的详细信息。我会尝试在我这边重现这个问题，然后找到解决方案。 如果可能，请提供我在上次答复中要求的信息。 谢谢。 Re: S32G-VNP-RDB3 GMAC 你好，@dongmin、 对不起，我的回复晚了。我无法重现您的问题，能否与我分享您的项目？您可以使用本社区的私人信息功能或创建一个提及本主题的私人支持票据。 谢谢。

What is the cause of SMC_SC_LOCKED_NOP? Hello, when using imx8mp Android 15, the following message appears during startup. What could be causing this? thanks. 01-01 00:00:02.055 1 1 I init: Loaded kernel module /lib/modules/soc-imx8m.ko will appear when booting 01-01 00:00:02.062 1 1 E : trusty trusty: failed to get version: -1 01-01 00:00:02.062 1 1 I : trusty trusty: selected api version: 0 (requested 5) 01-01 00:00:02.067 83 83 E : trusty trusty: locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.067 84 84 E : trusty trusty: The message "locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.067 85 85 E : trusty trusty: locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.067 86 86 E : trusty trusty: locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.067 1 1 W : trusty trusty: trusty-share not supported on secure side, error=-1" could be causing this problem. Re: What is the cause of SMC_SC_LOCKED_NOP? Hi @GavinChen, Thank you for contacting NXP Support! Could you please provide more details about the error you are encountering? I have tested the i.MX8MP EVK using the pre compiled image, and it is working as expected on my side. Are you using an EVK board? Best regards, Chavira

Best IPTV service I've found after trying so many others I've been through so many different services trying to find something reliable and most of them had the same issues, buffering, content disappearing, streams dropping randomly. Been using SHOROC for a few months now and it's been different. Streams stay stable, the content library gets updated regularly, and I actually don't have to worry about my show disappearing the next day. The free trial was what got me to try it in the first place. No risk, just test it and see if it works. Been solid ever since. If you're tired of dealing with unreliable services, worth giving it a shot. the official website: https://shoroc.com