Debian Compilation issue for imx8MP During the debian compilation for imx8mp i am facing this issue  sed: couldn't open temporary file /home/iwave/SUMAN/LZ/flexbuild/build_lsdk2506/rfs/rootfs_lsdk2506_debian_desktop_arm64/etc/pam.d/sedZCczOs: Permission denied I changed the ownership and kept for compilation but still i am facing this issue. Re: Debian Compilation issue for imx8MP Hi @Neha_V, Some build systems expect to run inside a controlled environment like chroot to simulate root privileges. This is especially important when building root filesystems or modifying system level directories, as it helps avoid permission-related issues and ensures the build process behaves as expected. Try the next command: sudo LANG=C.UTF-8 chroot /path/to/rootfs qemu-aarch64-static /bin/bash Best regards, Chavira

CLEV6630B CLEV6630B アンテナ (30×50 mm) のインピーダンス整合回路図をお願いします。私の製品には、65×65 mm アンテナの回路図のみが付属していました。 ご返答と回路図をありがとうございます。しかし、キットに付属のボード上の抵抗器が回路図と異なることに気付きました。確認のため抵抗器を 1 つ取り外しました。回路図では 1.6 kΩ と表示されていますが、私のボードでは 2.2 kΩ の抵抗器が 2 つ並列に接続されています。私の回路図とキットに同梱されていたボードのどちらが間違っているのでしょうか? アンテナの写真を添付します。 私の問い合わせに迅速に対応していただき、ありがとうございます。 Re: CLEV6630B こんにちは@mrmorais あなたの調子が良いといいのですが。 このキットに含まれるアンテナは、すでに CLEV6630B ボードで動作するように調整されています。カスタム アンテナを使用する場合は、 AN11019 CLRC663 アンテナデザインに従って適切なマッチングとチューニングを実行する必要があります。また、別のリーダーにアンテナを実装する場合は、対応するアンテナデザインおよびマッチング ガイドを参照してください。 よろしくお願いいたします。 エドゥアルド。

S32N55：不支持 NETC 交换机的配置"EthSwtEnableSharedLearning" 。 你好，团队、 RTD 版本：SW32N_RTD_R21-11_1.8.0_CD05 1.在 EB Tresos 中，配置选项 EthSwtEnableSharedLearning 目前为灰色，不支持。 希望可以在 EB Tresos 中配置该选项，以支持 FID 功能。 2.一旦 EthSwtEnableSharedLearning 设置为false 后，FDB 表中的 FID 就可以配置为独立的 vlan MAC 学习。目前，FDB 表中的 FID 在驱动程序中硬编码为0。 顺祝商祺！ 唐生。 优先级：中等 RTD 资料来源直接客户 Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte 你好@Nhi_Nguyen 感谢你的支持 顺祝商祺！ 唐生。 Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte 你好@Tangsheng_Zhou、 SW 团队回应说，他们没有支持这一功能的计划。如果客户需要，请提出申请。 顺祝商祺！ Nhi Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte 你好@Nhi_Nguyen 感谢您的反馈， 是否有计划开发这一功能？ 如果是，能否提供预计的时间表？ 谢谢您！ 顺祝商祺！ 唐生。 Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte 你好@Tangsheng_Zhou、 此版本中的所有驱动程序均以早期质量交付。你看到的灰色功能，他们还不支持。 顺祝商祺！ Nhi

S32N55: NETC スイッチの構成「EthSwtEnableSharedLearning」はサポートされていません。 こんにちは、チームの皆さん RTDバージョン: SW32N_RTD_R21-11_1.8.0_CD05 1.EB Tresos では、構成オプション EthSwtEnableSharedLearning は現在グレー表示されており、サポートされていません。デフォルト値はtrueに設定されているようです。 EB Tresos でこのオプションを設定して、FID 機能をサポートできるようになることを期待します。 2. EthSwtEnableSharedLearning が構成可能になり、 falseに設定されると、FDB テーブル内の FID を独立した VLAN MAC 学習用に構成できるようになります。現在、FDB テーブル内の FID は0としてハードコードされています。 よろしくお願いいたします。 唐生。 優先度: 中 RTD 出典: 直接お客様 Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte こんにちは@Nhi_Nguyen ご対応ありがとうございます。 よろしくお願いいたします。 唐生。 Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte こんにちは@Tangsheng_Zhouさん SW チームは、この機能をサポートする予定はないと回答しました。お客様がご希望の場合は、お申し付けください。 よろしくお願いいたします。 ニ Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte こんにちは@Nhi_Nguyen ご返信ありがとうございます。 この機能を開発する予定があるかどうか教えていただけますか? もしSOなら、予想されるタイムラインも教えていただけますか? よろしくお願いします！ よろしくお願いいたします。 唐生。 Re: S32N55: The configuration "EthSwtEnableSharedLearning" for NETC switch is not supporte こんにちは@Tangsheng_Zhouさん このリリースのすべてのドライバは、Pre-early 品質で提供されます。灰色で表示される機能はまだサポートされていません。 よろしくお願いいたします。 ニ

New location for Restricted Data Package (SPSDK) Restricted Data Package is moved to a new location.  For details, read here id:SPSDK [start:Sept 27 2025] [end:Sept 27 2026] announcement

88W9098 超时 cmd id (27.589481)区域设置 成功加载驱动程序后（同时使用 6.12.34_2.1.0 和 6.12.34_2.1.0 测试和 lf-6.12.20_2.0.0）： [10.246097] wlan：正在加载 MWLAN 驱动程序[10.255576] wlan：注册到总线驱动程序...[10.260485] usbcore：注册了新的接口驱动程序 usbxxx[10.260525] wlan_pcie 0000:05:00.0：启用设备 (0000-> 0002) [10.260760] PCI 内存映射 Virt0：00000000a3674d6f PCI 内存映射 Virt2： 0000000053f18fe1 [10.269043] Attach moal handle ops，card 接口类型：0x206 [10.274941] rps 从模块参数设置为 f[10.291492] igc 0000:04:00.0 lan0：从 eth3 重命名 [10.298609] PCIE9098：来自用户的初始模块参数 cfg [10.303656] card_type：PCIE9098，配置块：0 [10.3083 28] calg80211_wext=0xf [10.311851] max_vir_bss=1 [10.316042] cals=1 _data_cfg=无 [10.319638] drv _mode = 1[10.322765] ps_mode = 2 [10.325755] auto_ds = 2[10.328735] host_mlme=enable [10.332161] fw_serial 关闭 [10.335728] fw_name= nxp/pcie9098_wl an_v1. bin [ 10.340656] rx_work=1 cpu_num=4 [ 10.344301] 启用 moal_recv_amsdu_packet。 [ 10.344442] Attach mlan adapter operations.card_type is 0x206。 [ 10.355619] intel_rapl_msr：检测到 PL4 支持。 [10.358439] intel_rapl_common：找到了 RAPL 域名包[10.358444] intel_rapl_common：找到了 RAPL 域核心 [10.358447] intel_rapl_common：找到 RAPL 域名 psys [10.360956] 请求固件：nxp/pcie9098_wlan_v1.bin [10.634941] F W 下载完毕，大小 509624 字节[10.771109] u32 分类器 [10.771113][10.771114] 输入设备上的性能计数器在 [10.771115] 配置的操作 [10.920898] 无线局域网固件处于活动状态 [10.924357] on _time 是 10923577575 [10.94330 4] VDLL 图片：len=15 3752[10.943380] fw_cap_info=0xc8fcefa3，dev_cap_mask=0xfffffff [10.943387] max_p2p_conn = 8，max_sta_conn = 48 [10.943389] 设置 int_sel_mask=0x2020001 [10.958210] 注册恩智浦 802.11 适配器 mlan0[10.963100] 无线局域网：版本 = pcie9098--17.92.1.p149.76-mm6x17540.p7 -(FP 92) [10.970892] wlan_pcie 0000:05:00.1：启用设备 (0000-> 0002) [10.971118] PCI 内存映射 Virt0：00000000682d701f PCI 内存映射 Virt2 ：00000000da5fa8d7 [10.979878] Attach moal handle ops，卡接口类型：0x206 [10.986225] rps 设置为 f 模块参数 [10.990900] PCIE9098：从 usr cf g 初始化模块参数[10.996392] 卡片类型：PCIE9098，配置块：1 [11.001511] cfg80211_wext=0xf [11.004956] max_vir_bss=1[11.008080] cal_data_cfg=none [11.011599] drv_mode = 2 [11.0 14643] ps_mode = 2 [11.017536] _ds = 2 [11.020407] host_ml me= 启用[11.023722] fw_serial 关闭 [11.026850] fw_name=nxp/pcie9098_wlan_v 1.bin [ 11.031606] rx_work=1 cpu_num=4 [ 11.035223] 启用 moal_recv_amsdu_packet。 [ 11.035349] Attach mlan adapter operations.card_type is 0x206。 [ 11.036909] 请求固件：nxp/pcie9098_wlan_v1.bin [ 11.043235] WLAN FW 已在运行！跳过固件下载 [ 11.043240] WLAN FW 处于活动状态 [ 11.046675] 开启时间为 11045896137 [ 11.051094] VDLL 映像：len=153752 [ 11.051106] fw_cap_info=0x48fcefa3, dev_cap_mask=0xffffffff [ 11.051112] max_p2p_conn = 8, max_sta_conn = 48 [ 11.051114] set int_sel_mask=0x2020001 [ 11.051846] wlan: muap%d set max_mtu 2000 [ 11.061600] 注册恩智浦 802.11 适配器 muap0 [ 11.066435] wlan: version = PCIE9098--17.92.1.p149.76-MM6X17540.p7-(FP92) [11.074306] wlan：注册到总线驱动程序完成[11.0 79144] wlan：驱动程序已 成功加载 执行 `iw reg set` 的结果是 [26.642084] 固件触发固件转储 [26.645207] =====FW 触发器转储 ==== [26.648952] ==== 开始接收固件转储事件 ====[26.653824] === [26.653886] FW 处于调试模式 (0xea) [26.85 3243] Drv 信息总字节数 = 248900 (0x3243) cc44)[26. 853247] === 驱动程序信息 转储结束= ==[26.853248] === 启动驱动程序信息转储===[26.853394] FW 处于调试模式 (0xea) [27.052742] Drv 信息总字节数 = 248907 (0x3cc4b)[27.052745] === [27.819598] 超时 cmd id (27.589481) CHAN_REGION_CFG [0x24 2]，act = 0x1 [27.819617] Dump Rx CMD 响应错误：[27.819621] cmDresp Buf：[27.819629] 63 00 01 00 5b 00 5f 00 00 19 10 00 00 01 00 01 00 07 00 [27.819635] 45 00 43 41 20 24 0 1 17 28 01 17 2c 01 17 30 01 [27.819641] 17 3c 01 17 64 01 17 70 01[27.819646] 68 01 17 6c 01 17 70 01 70 01 17 74 01 17 84 01 17 88 [27.819649] BSS 类型 = 1 BSS 角色= 1[27.819653]----------------转储信息----------- ... [ 27.820163] -------- Dump info End--------- [ 27.820175] Host:igw-605000031 Timestamp:2025-10-23 13:31:20 [ 27.820182] 驱动程序版本 = PCIE9098--17.92.1.p149.76-MM6X17540.p7-(FP92) [27.820185] main_state = 4 [27.820187] ioctl_pending = 1 [27.820190] tx_pending = 0 [27.820192] wmm_tx_pending [0] = 0 [27.820194] wmm_tx_pending [1] = 0 [27.820199]] wmm_tx_pending [3] = 0 [27.8 20201] rx_pending = 0 [27.820203] lock_count = 44 [27.820206] malloc_count = 48 [27.820208] mbufalloc_count = 136 [27.820211] malloc_count = 4 [27.820213] hs_skip_count = 0 [27.820218] 媒体状态 = " 已断开连接 " [27.820221] 运营商关闭 [27.820224] tx 队列 0：已停止 [27.820227] tx 队列 1：已停止 [27.820230] tx 队列 2：已停止 [27.820233] tx 队列 3：已停止 [27.820235] hotspot0：num_t x_timeout = 0 [27.820244] 配置空间寄存器： [27.823829] reg: 0x00 value=0x2b441b4b [27.823835] reg: 0x04 value=0x00100406 [27.823840] reg: 0x10 value=0x 0000000c [27.823844] reg: 0x18 value=0x81000004 [27.823848] reg: 0x2c value=0x2b441b4b [27.823852] reg: 0x3c value=0x000002ff [27.823856] reg: 0x44 value=0x00000008 [27.823860] reg: 0x80 value=0x10120140 [27.823864] reg: 0x98 value=0x00000000 [27.823869] reg: 0x170 value=0x0001001e [27.82387 4] F W 在调试中 模式 (0xea) [27.823876] FW Scrach 寄存器：[27.827147] reg: 0x1c90 value=0xfedcba00 [27.827151] reg: 0x1c98 value=0x1c98 value=0x1c98 value=0x1000030 [27.926368] reg: 0x126ea69 [27.827155] reg: 0x1c9c value=0x1000030 [27.926368] reg: 0x1c9c value=0x1000030 [27.926368] reg: 0xx1c98 value=0x126ea69 [27.926373] reg: 0x1c9c value=0x10000 30 [28. 023800] ==== 固件转储结束 : 2360256 字节 ==== 其他信息 操作系统：Debian GNU/Linux 12 (bookworm) 内核版本： 6.12.22-igw-amd64 中央处理器英特尔（R）凌动（TM）x7433RE Wifi 卡：NXP 88W9098 Wi-Fi 6 (ax) MAC (rev 03) Re: 88W9098 Timeout cmd id (27.589481) CHAN_REGION_CFG 你好@johnj_dejero 我在我们的平台上尝试了您的问题，没有任何问题。我想您可能需要检查主机端的设置。 顺祝商祺！ 肖恩 Re: 88W9098 Timeout cmd id (27.589481) CHAN_REGION_CFG 此外，相关的 `iw dev` 显示接口的 txpower 为 0 dBm： Interface hotspot0 ifindex 22 wdev 0x700000001 addr 60:09:c3:84:f1:76 ssid 605000031 type AP channel 44 (5220 MHz)，width: 40 MHz, center1: 5230 MHz txpower 0.00 dBm 尽管内核中的区域最终被配置为 CA，但固件似乎并没有得到正确配置。 iw reg get global country CA: DFS-ETSI (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 23), (W) (5250 - 5330 @ 80), (N/A, 20), (W), DFS ... Re: 88W9098 Timeout cmd id (27.589481) CHAN_REGION_CFG 上述下载失败的原因是： Your userId does not have sufficient privilege to proceed with download. 我们的操作系统是内核版本为 6.12 的 debian，监管数据库位于 /lib/firmware/regulatory.db 目录下。 请注意，我们可以通过 /etc/modprobe.d/cfg80211.conf 配置国家代码 options cfg80211 ieee80211_regdom=CA 但由于上述固件问题，我们无法通过 iw reg 设置进行更改。 Re: 88W9098 Timeout cmd id (27.589481) CHAN_REGION_CFG 你好@johnj_dejero 我们提供了配置 tx 功率限制的方法，您可以参考以下方法更新功率限制表。由于我不熟悉您使用的主机，也许他们的系统中没有提供国家代码功率表。 https://www.nxp.com/webapp/Download?colCode=AN13463&appType=license 顺祝商祺！ 肖恩 Re: 88W9098 Timeout cmd id (27.589481) CHAN_REGION_CFG iw reg set CA 但任何地区（美国、日本、中国等）都会出现这种情况。 Re: 88W9098 Timeout cmd id (27.589481) CHAN_REGION_CFG 你好@johnj_dejero 能否共享您发出的" iwreg set"的完整 cmd？您使用的是哪个地区代码？ 顺祝商祺！ 肖恩 Re: 88W9098 Timeout cmd id (27.589481) CHAN_REGION_CFG 我们在使用 imx6q + 内核 6.6.118 时也遇到了这个问题（稳定的主线）+ jody-w377（通过 sdio 提供 sd9098）使用驱动程序/固件版本 6.6.52_2.2.0。 [ 52.162008] IOCTL failed: 6efc4a66 id=0x200000, sub_id=0x200046 action=1, status_code=0x3 [ 57.196820] Timeout cmd id (57.190255) CHAN_REGION_CFG [0x242], act = 0x1 [ 57.197092] 42 [ 57.197129] 02 [ 57.197161] 0b [ 57.197193] 00 [ 57.197259] 20 [ 57.197292] 10 [ 57.197324] 00 [ 57.197354] 00 [ 57.197384] 01 [ 57.197413] 00 [ 57.197470] 00 [ 57.197501] 00 [ 57.197532] 00 [ 57.197561] 00 [ 57.197592] 00 [ 57.197623] 00 [ 57.197712] BSS type = 1 BSS role= 1 [ 57.197746] ------------Dump info----------- [ 57.197776] Commmand Timeout [ 57.197928] mlan_processing =0 [ 57.197968] main_lock_flag =0 [ 57.198000] main_process_cnt =113 [ 57.198032] delay_task_flag =0 [ 57.198062] mlan_rx_processing =0 [ 57.198117] rx_pkts_queued=0 [ 57.198150] more_task_flag = 0 [ 57.198182] num_cmd_timeout = 1 [ 57.198213] last_cmd_index = 2 [ 57.198245] last_cmd_id = [ 57.198271] 0x5b [ 57.198301] 0x5b [ 57.198332] 0x242 [ 57.198361] 0x10c [ 57.198392] 0x10c [ 57.198421] 0x10c [ 57.198451] 0x10c [ 57.198480] 0x10c [ 57.198511] 0x10c [ 57.198541] 0x16 [ 57.198601] last_cmd_act = [ 57.198627] 0x1 [ 57.198657] 0x1 [ 57.198686] 0x1 [ 57.198716] 0x1 [ 57.198746] 0x1 [ 57.198775] 0x1 [ 57.198805] 0x1 [ 57.198835] 0x1 [ 57.198867] 0x1 [ 57.198897] 0x1 [ 57.198959] last_cmd_resp_index = 1 [ 57.198991] last_cmd_resp_id = [ 57.199017] 0x805b [ 57.199047] 0x805b [ 57.199077] 0x810c [ 57.199162] 0x810c [ 57.199196] 0x810c [ 57.199226] 0x810c [ 57.199257] 0x810c [ 57.199288] 0x810c [ 57.199319] 0x810c [ 57.199349] 0x8016 [ 57.199412] last_event_index = 6 [ 57.199443] last_event = [ 57.199470] 0x81 [ 57.199500] 0x81 [ 57.199531] 0x81 [ 57.199561] 0x81 [ 57.199591] 0x81 [ 57.199621] 0x81 [ 57.199651] 0x81 [ 57.199681] 0x81 [ 57.199713] 0x81 [ 57.199744] 0x81 [ 57.199804] num_data_h2c_failure = 0 [ 57.199835] num_cmd_h2c_failure = 0 [ 57.199866] num_data_c2h_failure = 0 [ 57.199898] num_cmdevt_c2h_failure = 0 [ 57.199929] num_int_read_failure = 0 [ 57.199960] last_int_status = 128 [ 57.199991] num_alloc_buffer_failure = 0 [ 57.200022] num_pkt_dropped = 0 [ 57.200052] num_no_cmd_node = 0 [ 57.200083] num_event_deauth = 0 [ 57.200113] num_event_disassoc = 0 [ 57.200144] num_event_link_lost = 0 [ 57.200174] num_cmd_deauth = 0 [ 57.200204] num_cmd_assoc_success = 0 [ 57.200235] num_cmd_assoc_failure = 0 [ 57.200265] num_cons_assoc_failure = 0 [ 57.200295] cmd_resp_received=0 [ 57.200326] event_received=0 [ 57.200356] max_tx_buf_size=4096 [ 57.200387] tx_buf_size=3328 [ 57.200418] curr_tx_buf_size=3328 [ 57.200449] data_sent=0 cmd_sent=0 [ 57.200480] ps_mode=1 ps_state=0 [ 57.200513] wakeup_dev_req=0 wakeup_tries=0 wakeup_timeout=0 [ 57.200544] hs_configured=0 hs_activated=0 [ 57.200575] pps_uapsd_mode=0 sleep_pd=0 [ 57.200608] tx_lock_flag = 0 [ 57.200638] scan_processing = 0 [ 57.200667] scan_state = 0x0 [ 57.200701] bypass_pkt_count=0 [ 57.200731] mp_rd_bitmap=0x0 curr_rd_port=0x0 [ 57.200762] mp_wr_bitmap=0xffffffff curr_wr_port=0x0 [ 57.200794] mp_data_port_mask = 0xffffffff [ 57.200825] last_recv_rd_bitmap=0x0 mp_invalid_update=0 [ 57.200858] last_recv_wr_bitmap=0xffffffff last_mp_index=0 [ 57.200892] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.200925] 0x00 [ 57.200953] 0x00 [ 57.200984] 0x00 [ 57.201014] 0x00 [ 57.201043] 0x00 [ 57.201073] 0x00 [ 57.201103] 0x00 [ 57.201133] 0x00 [ 57.201162] 0x00 [ 57.201191] 0x00 [ 57.201221] 0x00 [ 57.201250] 0x00 [ 57.201279] 0x00 [ 57.201309] 0x00 [ 57.201339] 0x00 [ 57.201368] 0x00 [ 57.201429] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.201461] 0x00 [ 57.201489] 0x00 [ 57.201521] 0x00 [ 57.201551] 0x00 [ 57.201581] 0x00 [ 57.201611] 0x00 [ 57.201640] 0x00 [ 57.201670] 0x00 [ 57.201700] 0x00 [ 57.201729] 0x00 [ 57.201758] 0x00 [ 57.201788] 0x00 [ 57.201818] 0x00 [ 57.201847] 0x00 [ 57.201877] 0x00 [ 57.201906] 0x00 [ 57.201967] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.202000] 0x00 [ 57.202027] 0x00 [ 57.202058] 0x00 [ 57.202087] 0x00 [ 57.202116] 0x00 [ 57.202146] 0x00 [ 57.202175] 0x00 [ 57.202205] 0x00 [ 57.202234] 0x00 [ 57.202265] 0x00 [ 57.202294] 0x00 [ 57.202323] 0x00 [ 57.202354] 0x00 [ 57.202383] 0x00 [ 57.202413] 0x00 [ 57.202443] 0x00 [ 57.202503] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.202537] 0x00 [ 57.202563] 0x00 [ 57.202593] 0x00 [ 57.202622] 0x00 [ 57.202651] 0x00 [ 57.202680] 0x00 [ 57.202710] 0x00 [ 57.202739] 0x00 [ 57.202769] 0x00 [ 57.202798] 0x00 [ 57.202828] 0x00 [ 57.202857] 0x00 [ 57.202887] 0x00 [ 57.202916] 0x00 [ 57.202946] 0x00 [ 57.202975] 0x00 [ 57.203036] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.203070] 0x00 [ 57.203097] 0x00 [ 57.203126] 0x00 [ 57.203156] 0x00 [ 57.203186] 0x00 [ 57.203215] 0x00 [ 57.203245] 0x00 [ 57.203275] 0x00 [ 57.203304] 0x00 [ 57.203334] 0x00 [ 57.203363] 0x00 [ 57.203392] 0x00 [ 57.203421] 0x00 [ 57.203452] 0x00 [ 57.203481] 0x00 [ 57.203511] 0x00 [ 57.203571] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.203605] 0x00 [ 57.203633] 0x00 [ 57.203663] 0x00 [ 57.203693] 0x00 [ 57.203723] 0x00 [ 57.203753] 0x00 [ 57.203783] 0x00 [ 57.203812] 0x00 [ 57.203842] 0x00 [ 57.203870] 0x00 [ 57.203902] 0x00 [ 57.203932] 0x00 [ 57.203962] 0x00 [ 57.203992] 0x00 [ 57.204023] 0x00 [ 57.204053] 0x00 [ 57.204113] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.204149] 0x00 [ 57.204176] 0x00 [ 57.204206] 0x00 [ 57.204236] 0x00 [ 57.204266] 0x00 [ 57.204345] 0x00 [ 57.204385] 0x00 [ 57.204417] 0x00 [ 57.204448] 0x00 [ 57.204477] 0x00 [ 57.204508] 0x00 [ 57.204538] 0x00 [ 57.204568] 0x00 [ 57.204597] 0x00 [ 57.204627] 0x00 [ 57.204656] 0x00 [ 57.204716] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.204750] 0x00 [ 57.204777] 0x00 [ 57.204806] 0x00 [ 57.204837] 0x00 [ 57.204867] 0x00 [ 57.204896] 0x00 [ 57.204925] 0x00 [ 57.204955] 0x00 [ 57.204984] 0x00 [ 57.205014] 0x00 [ 57.205045] 0x00 [ 57.205074] 0x00 [ 57.205104] 0x00 [ 57.205133] 0x00 [ 57.205163] 0x00 [ 57.205192] 0x00 [ 57.205253] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.205286] 0x00 [ 57.205313] 0x00 [ 57.205343] 0x00 [ 57.205372] 0x00 [ 57.205401] 0x00 [ 57.205432] 0x00 [ 57.205462] 0x00 [ 57.205492] 0x00 [ 57.205522] 0x00 [ 57.205552] 0x00 [ 57.205581] 0x00 [ 57.205610] 0x00 [ 57.205640] 0x00 [ 57.205669] 0x00 [ 57.205699] 0x00 [ 57.205729] 0x00 [ 57.205788] mp_wr_bitmap: 0x0 mp_wr_ports=0x0 len=0 curr_wr_port=0x0 [ 57.205821] 0x00 [ 57.205848] 0x00 [ 57.205877] 0x00 [ 57.205906] 0x00 [ 57.205935] 0x00 [ 57.205966] 0x00 [ 57.205996] 0x00 [ 57.206026] 0x00 [ 57.206056] 0x00 [ 57.206085] 0x00 [ 57.206114] 0x00 [ 57.206143] 0x00 [ 57.206174] 0x00 [ 57.206204] 0x00 [ 57.206234] 0x00 [ 57.206264] 0x00 [ 57.206326] bss_index = 0, tx_pkts_queued = 0 tx_pause [ 57.206359] -------- Dump info End--------- [ 57.206418] Host:connect Timestamp:2026-02-09 16:04:32 [ 57.206462] Driver version = SD9098----17.92.1.p149.53-MM6X17505.p7.1-(FP92) [ 57.206494] main_state = 4 [ 57.206524] ioctl_pending = 1 [ 57.206556] tx_pending = 0 [ 57.206588] wmm_tx_pending[0] = 0 [ 57.206619] wmm_tx_pending[1] = 0 [ 57.206651] wmm_tx_pending[2] = 0 [ 57.206682] wmm_tx_pending[3] = 0 [ 57.206713] rx_pending = 0 [ 57.206744] lock_count = 42 [ 57.206775] malloc_count = 48 [ 57.206807] mbufalloc_count = 0 [ 57.206838] hs_skip_count = 0 [ 57.206870] hs_force_count = 0 [ 57.206901] Media state = "Disconnected" [ 57.206931] carrier off [ 57.206963] tx queue 0: stopped [ 57.206997] tx queue 1: stopped [ 57.207030] tx queue 2: stopped [ 57.207061] tx queue 3: stopped [ 57.207093] wlp5s0: num_tx_timeout = 0 [ 57.210175] FW in debug mode (0xea) [ 57.217470] SDIO Func0 (0x0-0x9): 43 03 06 06 07 00 00 02 03 00 [ 57.218109] SDIO Func1 (0x10-0x17): 00 00 00 00 ff ff ff ff [ 57.219125] SDIO Func1: (0x8) c3 (0x58) 00 (0x5c) 88 (0x5d) 00 (0x60) 87 (0x61) 0c (0x62) 00 (0x64) 10 (0x65) 00 (0x66) 00 (0x68) 00 (0x69) 00 (0x6a) 00 [ 57.220958] SDIO Func1 (0xe8-0xff): dc fe 92 ea 43 01 00 00 24 01 70 c8 e0 47 80 00 00 00 00 00 00 00 00 00 [ 57.323171] SDIO Func1 (0xe8-0xff): dc fe 92 ea 43 01 00 00 24 01 70 c8 e0 47 80 00 00 00 00 00 00 00 00 00 [ 57.323218] Cancel all pending cmd and txrx queue [ 57.323246] IOCTL failed: 6efc4a66 id=0x200000, sub_id=0x200046 action=1, status_code=0x80000007 [ 57.323499] ==== DEBUG MODE OUTPUT START: 57.316948 ==== [ 57.324283] DUMP_SIZE=0xf0000 [ 57.333688] Start DUMP output 57.327133, please wait... [ 57.361764] Block woal_cfg80211_scan in abnormal driver state [ 57.376296] INFO: trying to register non-static key. [ 57.381305] The code is fine but needs lockdep annotation, or maybe [ 57.387587] you didn't initialize this object before use? [ 57.392998] turning off the locking correctness validator. 这是在配置接入点时发生的。我们的国家代码由 hostapd 的 "country_code=xx "设置，其中 FR 或 JP 会导致问题（尚未测试其他国家代码）。 请注意，回到 6.6.36_2.1.0就能解决这个问题。

XGATE Warning A22011 Operand out of range MC9S12XEP100, CW Special edition, relocatable assembler, dual processor, XGATE in RAM. I'm having some success in my project getting XGATE to handle some of the interrupts, but I've run into an interesting problem. Things worked well until I started adding more shared variables. At one point I got the warning "A22011 Operand out of range". My project is getting fairly big and complex so I just made a short test program to re-create the problem. The program is just the Fibo one that the wizard puts together with some more shared variables added. Up to 16 word variables is fine, after that it I get the warning and when I run the program the variables beyond 16 don't update. I have no idea how to fix this. Any suggestions would be greatly appreciated. Regards, Robert Re: XGATE Warning A22011 Operand out of range Hi Ladisalv, Excellent! That was what I needed. I studied your code and it made sense to me . I incorporated it into a basic test code and it worked as expected. I experimented with it a bit and that also worked as expected. Thanks so much for giving me that clue to the puzzle. Now, I have one more related related question about XGATE semaphores, but I think it would be better protocol to start and new thread, which I will do.  Thanks again for your help, I don't know if I could have figured it out on my own or not. Regards, Robert.  Re: XGATE Warning A22011 Operand out of range Hi, I have forgotten….. The instruction you use in given form has offset of 5 bits long, represents number of bytes and you use words. M[RB, #OFFS5] ⇒RD So max offset is 32 bytes or 16 words. Look at this simple example of writing the Array of 256 words addressed by variable index. Note that R0 is always 0. XGATE_DATA: SECTION ; put your variables here ALIGN 2 Arr DS.W 256 Index DS.W 1 XGATE_CODE: SECTION ; interrupt handler for the software trigger 0 ALIGN 2 SoftwareTrigger0_Handler: ; load index with value LDW R2, Index ; Addr to Index LDL R3, #17 ; STW R3, (R2,R0) ; Save Index value ;-------------------------- Write Arr[5] = 0x1234 LDW R3, Index ; Get address of Index ; R3 = get address of index LDW R2, (R3, R0) ; R2 = Index LSL R2, #$1 ; Calculate Index in bytes; R2 = Index*2 data set is size of word ; Get position of Arr[Index] LDW R3, Arr ; Base address of Addr ADD R4, R2,R3 ; Calculate Arr[Index] position = Arr + Index*2 LDW R3, #$1234 STW R3, (R4, R0) ; Write Arr[Index] = $1234 Note, in the memory window you will see Arr[0..512] (even we defined Arr DS.W 256) so writing word to arr index 17 will in reality write word to Arr[34] and arr[35] in memory window. Note that similar is read from the array. If you want to use instruction with #OFF5 then you can make something like addressing 2dimensional array of words which has elements [x,16]. But I see this as little bit complicated. Best regards, L. Re: XGATE Warning A22011 Operand out of range Hi Ladislav, Thanks very much for having a look at my code. In this test code I just want to load the contents of XGATE_CounterXX, increment it and store it back into XGATE_CounterXX. The code works fine until I get to XGATE_Counter_17, then I get the out of range error. It would be preferable if I could get the value from XGATE_Counter_17 (and on for more variables) by using the offset from the beginning of .data. I assumed that the command line LDW R2,(R1,#(XGATE_CounterXX - MyData)) did just that, but it seems to limit me to a maximum of 32 bytes or 16 words from the start of .data. Just what is it that the command LDW R2,(R1,#(XGATE_CounterXX - MyData)) does? I can't find any description of it in any of the information that I have. If my interpretation of the manuals is correct, it is faster (more efficient?) to run XGATE out of RAM rather than Flash, and isn't that the  whole point of using XGATE to handle the interrupts?  Using "C" language for anything for me is not an option because I do not speak the language.   Re: XGATE Warning A22011 Operand out of range Hi, having read last update I started to be more confused. Would not be easier to prepare c code example as a development platform. Moreover, think about xgate in flash and ram, or process basic functions on xgate and then call (continue) with the interrupt on CPU (it is also possible).  BR Ladislav Re: XGATE Warning A22011 Operand out of range Hi, The question I have is > What do you want to do.... LDW R2,(R1,#(XGATE_CounterXX - MyData)) ; load counter INC R2 STW R2,(R1,#(XGATE_CounterXX - MyData)) ; store counter Is that right you want to get a value from XGATE_CounterXX, increment it and then put it back? Or do you want to get an offset of the XGATE_CounterXX from MyData, incremnt it and put the value to the XGATE_CounterXX? Or....? Best regards, Ladislav Re: XGATE Warning A22011 Operand out of range Oops. Error on last post. Should be 32 variables (16 words), not 16 variables. Re: XGATE Warning A22011 Operand out of range I've been doing some more troubleshooting on this, reading the manuals, studying the PRM and .map files and using the debugger. I am using non-paged RAM and non-banked Flash. The manual tells me that XGATE register R1 is preloaded with the initial pointer of the channel's service request vector. XGATE register R7 is preloaded with either the contents of XG1SP74 or XG1SP31. Using the de-bugger I can see that the the linker has placed the shared variables  starting at address XGATE $E100. Addresses XGATE $E100 to $FFFF correspond to logical addresses $2100 to $3FFF. With R1 containing $E100 I can only access 16 variables before I get and "out of range " error. In my project I eventually want XGATE to handle 27 different interrupt routines. One of which has to use a 256 byte lookup table. Any suggestions on how I can handle this issue would be greatly appreciated. Regards, Robert

i.MX6ULL 板卡在恢复模式 — 无法启动或对闪存进行编程 我第一次使用基于 i.MX6ULL 的板。该板通过 USB 到以太网接口连接到我的 Linux 电脑。 当我连接 USB 电缆时，设备显示为： 总线 001 设备 005：ID 15a2:0080 飞思卡尔半导体有限公司 i.MX 6ULL SystemOnChip 系统处于恢复模式 处理器似乎被卡在 USB 恢复模式中，我不知道如何让它摆脱这种状态。板无法正常开机或启动，我无法对闪存进行编程。 我的目标是使用 MFG 工具将 U-Boot 和其他映像编程到闪存中，但我似乎无法让主板启动或退出恢复模式。 谁能建议我如何解决这个问题或指导我完成启动或刷新板的正确步骤？ 预先感谢您的帮助！ 致以最诚挚的问候， ERR Re: i.MX6ULL Board Stuck in Recovery Mode – Unable to Boot or Program Flash 你可以将启动模式转到串行下载模式，然后使用 uuu 将映像下载到板上的 SD 或 emmc，然后将启动模式设置为从你身边的闪存启动。 如果还是不行，请告诉我们。

rw612 ble gatt Server paring how to fixed passkey rw612 -> gatt server   NoInputNoOutput phone ->gatt client ble paring，how to fixed rw612 passkey （for example 123456，Not a random value），phone input 123456 to pair rw612 Re: rw612 ble gatt Server paring how to fixed passkey Hi @Christine_Li, Thank you so much for the quick response! The patch you shared worked perfectly, and I’m now able to set the fixed PassKey successfully. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Siddhesh_Nayak  Thanks for reaching me out. I will share the patch with you through working email. And for your information, I already report this issue to our internal SAE team, I think they are evaluating to include the patch in our future release. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi @Christine_Li, I am upgrading the SDK v25.09.00 from v2.15.00 in our MW. I have noticed the same where in even If I set the CONFIG_BT_FIXED_PASSKEY and I call bt_passkey_set(FIXED_PASSKEY_VALUE). the bt_conn_auth_cb.passkey_display callback gives me a random PassKey instead of the Fixed.  This was working perfectly with the SDK version v2.15.00. Environment Details : Board used: FRDM-RW612 SDK : v25.09.00 application : Custom Application. Can you please help me out solve the issue? Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Thanks for your trying and let me know your result!   Can you please create a new case to track the new issue and mark my answer as a solution for this case? We always recommend to track one issue with one case, so that we can provide a better reference for future cases.   And for your info, we always deal with the case with different priority level. If you have a company email, please do not hesitate to create case with your company's email. It might increase the priority of your case.   If you don't have, please ignore my hints. And we will still continue to support you with current priority.   Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li Thanks for the reply, I have tried it and it works，follow the steps you provided,passkey is fiexd to 123456, but a new problem arises: when finish bonding,I try to get Battery Service,it is not work and rw612 shell seems not work. Please take a look at my log to see if there are any problems, thanks for any help. @bt> bt.init @bt> Bluetooth initialized Settings Loaded 29224: DEBUG bt_pal_smp.c:9449:LE SC enabled @bt> bt.advertise on Advertising started @bt> bt.auth display @bt> bt.fixed-passkey 123456 ----func: cmd_fixed_passkey, line: 4347------- @bt> ----func: cmd_fixed_passkey, line: 4368--passkey 123456----- @bt> BLE Connected: 44:BD:E2:B9:92:FD (random) 58269: DEBUG bt_pal_smp.c:7164:conn 200273BC handle 128 58269: DEBUG bt_pal_smp.c:5436:chan 2002948C cid 0x0006 44:BD:E2:B9:92:FD (random)@bt> LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE conn param req: int (0x0006, 0x0006) lat 0 to 500 LE PHY updated: TX PHY LE 1M, RX PHY LE 1M LE conn param updated: int 0x0006 lat 0 to 500 LE conn param req: int (0x0018, 0x0018) lat 0 to 500 LE conn param updated: int 0x0018 lat 0 to 500 LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE PHY updated: TX PHY LE 2M, RX PHY LE 2M LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 2120) LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 2120) Confirm pairing for 44:BD:E2:B9:92:FD (random) 75262: DEBUG bt_pal_smp.c:9303:event 2 75262: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 75262: DEBUG bt_pal_smp.c:8515:SMP event = SMP_AUTHENTICATION_REQUEST, status 0 75262: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 75262: DEBUG bt_pal_smp.c:8812:Recvd SMP_AUTHENTICATION_REQUEST 75262: DEBUG bt_pal_smp.c:8824:Bonding type : Bonding 44:BD:E2:B9:92:FD (random)@bt> bt.auth-pairing-confirm 44:BD:E2:B9:92:FD (random)@bt> Passkey for 44:BD:E2:B9:92:FD (random): 123456 81122: DEBUG bt_pal_smp.c:9303:event 4 81122: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 81122: DEBUG bt_pal_smp.c:8515:SMP event = SMP_PASSKEY_DISPLAY_REQUEST, status 0 81122: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 81122: DEBUG bt_pal_smp.c:8946:Event : SMP_PASSKEY_DISPLAY_REQUEST 81122: DEBUG bt_pal_smp.c:8947:BD Address : FD 92 B9 E2 BD 44 88372: DEBUG bt_pal_smp.c:9303:event 6 88372: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 88373: DEBUG bt_pal_smp.c:8515:SMP event = SMP_KEY_EXCHANGE_INFO_REQUEST, status 0 88373: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 88373: DEBUG bt_pal_smp.c:8965:Event : SMP_KEY_EXCHANGE_INFO_REQUEST 88373: DEBUG bt_pal_smp.c:8966:BD Address : FD 92 B9 E2 BD 44 Re: rw612 ble gatt Server paring how to fixed passkey Hi， @flybir  Yes， I send it again just now. Please check your email and let me know whether you received the patch, and whether this patch works on your side. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li     Thanks for the reply, I did not receive the patch you shared to me by email.     Did you send to the  yuxi_klrs@163.com ? Re: rw612 ble gatt Server paring how to fixed passkey Hi @flybir  Have you already added the patch I shared to you by email? If no, please firstly add the patch, then have a try.  Thanks! From your shared log, I see below: The passkey doesn't fixed to 123456, it is showing: 047307 is your passkey. I guess you didn't add my patch shared to you by email. 88617: DEBUG bt_pal_smp.c:8824:Bonding type : Bonding bt.auth-pairing-confirm 49:7B:58:F5:35:CA (random)@bt> Passkey for 49:7B:58:F5:35:CA (random): 047307 Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li     Thanks for the reply, I have tried it and it still didn't work，follow the steps you provided，passkey is still not fiexd to 123456；     The FW image I have used provided by the directory:  /components/conn_fwloader/fw_bin/rw61x_sb_ble_a2.bin     Please take a look at my log to see if there are any problems, thanks for any help. /************************************************ENABLE DEBUG LOG *************************************/ @bt> bt.init @bt> Bluetooth initialized Settings Loaded 6065: DEBUG bt_pal_smp.c:9449:LE SC enabled @bt> bt.advertise on Advertising started @bt> bt.auth display @bt> bt.fixed-passkey 123456 ----func: cmd_fixed_passkey, line: 4347------- @bt> ----func: cmd_fixed_passkey, line: 4368--passkey 123456----- BLE Connected: 49:7B:58:F5:35:CA (random) 81457: DEBUG bt_pal_smp.c:7164:conn 200273BC handle 128 81457: DEBUG bt_pal_smp.c:5436:chan 2002948C cid 0x0006 49:7B:58:F5:35:CA (random)@bt> LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE conn param req: int (0x0006, 0x0006) lat 0 to 500 LE PHY updated: TX PHY LE 1M, RX PHY LE 1M LE data len updated: TX (len: 251 time: 2120) RX (len: 27 time: 328) LE conn param updated: int 0x0006 lat 0 to 500 LE conn param req: int (0x0018, 0x0018) lat 0 to 500 LE conn param updated: int 0x0018 lat 0 to 500 Confirm pairing for 49:7B:58:F5:35:CA (random) 88617: DEBUG bt_pal_smp.c:9303:event 2 88617: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 88617: DEBUG bt_pal_smp.c:8515:SMP event = SMP_AUTHENTICATION_REQUEST, status 0 88617: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 88617: DEBUG bt_pal_smp.c:8812:Recvd SMP_AUTHENTICATION_REQUEST 88617: DEBUG bt_pal_smp.c:8824:Bonding type : Bonding bt.auth-pairing-confirm 49:7B:58:F5:35:CA (random)@bt> Passkey for 49:7B:58:F5:35:CA (random): 047307 94322: DEBUG bt_pal_smp.c:9303:event 4 94322: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 94322: DEBUG bt_pal_smp.c:8515:SMP event = SMP_PASSKEY_DISPLAY_REQUEST, status 0 94322: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC 94322: DEBUG bt_pal_smp.c:8946:Event : SMP_PASSKEY_DISPLAY_REQUEST 94322: DEBUG bt_pal_smp.c:8947:BD Address : CA 35 F5 58 7B 49 Pairing failed with 49:7B:58:F5:35:CA (random) reason: Authentication requirements (4) Security failed: 49:7B:58:F5:35:CA (random) level 1 reason: Authentication failure (1) 106742: DEBUG bt_pal_smp.c:9303:event 1 106742: DEBUG bt_pal_smp.c:9321:RX queue put buf 20029708 106742: DEBUG bt_pal_smp.c:8515:SMP event = SMP_AUTHENTICATION_COMPLETE, status 1028 106742: DEBUG bt_pal_smp.c:8535:conn = 0x200273BC Bond deleted for 49:7B:58:F5:35:CA (random), id 0 Disconnected: 49:7B:58:F5:35:CA (random) (reason 0x13) 109800: DEBUG bt_pal_smp.c:5452:chan 2002948C cid 0x0006 @bt> Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  I already tested it locally, and it can work on my side. Please see attachment for my test logs. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Firstly add the patch I shared to you by email, then test with below steps. Please let me know whether it works for you. If it does work, please do not hesitate to mark my answer as a solution for this case. Thanks!   Please have a try with below steps: Test process (RW61x as slave，phone with nrf app as master): 1/ bt.init 2/ bt.advertise on 3/ bt.auth display 4/ bt.fixed-passkey 123456 5/ nrf app connect redfinch 6/ nrf app bond 7/ bt.auth-pairing-confirm 8/ nrf app input passkey 123456 Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li   Thanks for the reply, I have tried it and it didn't work, When my phone is paired with the RW612, I don't need to enter any passkey.     Please take a look at my log to see if there are any problems, thanks for any help. SHELL build: Oct 24 2025 Copynight 2020 NXP @bt> bt.init @bt> Bluetooth initialized Settings Loaded @bt> bt.fixed-passkey 123456 @bt> bt.advertise on Advertising started @bt> BLE Connected: 78:7B:E1:EC:D5:AC（random） Re: rw612 ble gatt Server paring how to fixed passkey Hi， @flybir  Yes， you are right.  I checked  and found that this API isn't called by anywhere. You might need to call it by referring this example: edgefast_bluetooth_shell. In this example, it calls this API bt_passkey_set(); And please remember enable this Macro: #define CONFIG_BT_FIXED_PASSKEY 1 is also needed. Please see below for my test logs, hope it can help you. @bt> bt.fixed-passkey 123456 Christine:enter cmd_fixed_passkey! @bt> Christine:fixed_passkey is: (passkey 123456) Setting fixed passkey failed (err 0) Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Thanks for your quick reply. Let me check it further, then share with you. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @Christine_Li   Thanks for the reply, I have tried it and it didn't work. Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Can you please have a try with below Macro in edgefast_bluetooth_config.h #define CONFIG_BT_FIXED_PASSKEY 1 Please let me know whether it works for you. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Are you using FRDM-RW612? YES What's your MCUXpresso IDE version? v25.6 SDK version? FRDM-RW612 25.06.00 which example you are using?  frdmrw612_wireless_uart I want the Bluetooth pairing code of the RW612 to be fixed to 123456, and the phone can be paired with the RW612 with a fixed pairing code. I have tryed bt_passkey_set(123456)  not work. Thanks for any help！ Re: rw612 ble gatt Server paring how to fixed passkey Hi, @flybir  Are you using FRDM-RW612? What's your MCUXpresso IDE version? SDK version? and which example you are using? Please let me know more backgrounds of your question, so that I can check further for you. Best regards, Christine. Re: rw612 ble gatt Server paring how to fixed passkey Thanks for any help Re: rw612 ble gatt Server paring how to fixed passkey Hi @Christine_Li , I'm facing the same issue mentioned above. Could you please share the patch with me. My email is: said.alghabra@subzero.com. Please also CC: marcus.dufrane@subzero.com Re: rw612 ble gatt Server paring how to fixed passkey Hi, @saidalghabra  Sorry for my late reply. For this request, can you please help to create a new case to us? We are not allowed to share the patch  to anyone except have case tracking and company's system reviewing/verifying. And also, please let me know which chipset you are using and your SDK version. Thanks for your corporations! Best regards, Christine.

SJA1105P PHYモードMAC間接続の問題 こんにちは、NXP 現在、SJA1105 で接続の問題が発生しています。S32K3 + SJA1105 + TJA1103を使用しています。 現在、PHY から SJA1105 に送信されたデータは他のポートに転送でき、S32K3 も SJA1105 からデータを受信でき、データは正確です。 ただし、S32K3 が SJA1105 にデータを送信した後、SJA1105 はそのデータを他のポートに転送しません。ポート 0 の RXD ピンで正しい波形が受信されていることがわかりますが、他のポートからは波形が放射されていません。 どのような問題が考えられますか?何か提案はありますか? 以下は私のハードウェアトポロジとスクリプト構成です。スクリプトはsimplePQRS.pyを使用して変更されています。 よろしくお願いします、 シアンロン Re: SJA1105P PHY MODE MAC to MAC connection issue サポートありがとうございます。SJA1105のRX_ERがグランドにコネクテッドされていない Re: SJA1105P PHY MODE MAC to MAC connection issue こんにちは、 提供された情報に基づいて提案するのは難しい。トポロジとスクリプトの変更は正しいようです。 簡単なヒント: スイッチ ポート 0 で使用されていない場合は、RX_ER が接地されていることを確認してください。 さらにコメントするには、さらに情報を提供してください。 完全な回路図、または少なくとも S32K3 + SJA1105 + TJA1103 接続の部品を共有していただけますか? sja1105_simple.pyを共有していただけますか? どのようなトラフィックがありますか? BR、ペトル

SJA1105P PHY MODE MAC to MAC connection issue Hi,NXP I'm currently encountering a connection issue with the SJA1105. I'm using S32K3 + SJA1105 + TJA1103. At present, the data sent from the PHY to the SJA1105 can be forwarded to other ports, and the S32K3 can also receive the data from the SJA1105, and the data is correct. However, after the S32K3 sends data to the SJA1105, the SJA1105 does not forward the data to other ports. I can see that there is a correct waveform received on the RXD pin of Port 0, but no waveforms are emitted from other ports. What could be the possible problems? Do you have any suggestions? Below are my hardware topology and script configurations.My script is modified using simplePQRS.py Best Regards, xianlong Re: SJA1105P PHY MODE MAC to MAC connection issue Thanks for your support. The RX_ER of my SJA1105 is not connected to ground Re: SJA1105P PHY MODE MAC to MAC connection issue Hi, hard to suggest based on info provided. A topology and script modification looks correct. Quick tip, be sure you have RX_ER grounded if not used on switch port 0. To comment more please provide more info. Could you share your full schematic, or part for S32K3 + SJA1105 + TJA1103 connection at least? Could you share your sja1105_simple.py? What kind of traffic do you have? BR, Petr

SJA1105P PHY MODE MAC 至 MAC 连接问题 你好，恩智浦 我目前遇到了 SJA1105 的连接问题。我使用的是 S32K3 + SJA1105 + TJA1103。 目前，从 PHY 发送到 SJA1105 的数据可以转发到其他端口，S32K3 也能接收到来自 SJA1105 的数据，且数据正确无误。 但是，S32K3 向 SJA1105 发送数据后，SJA1105 不会将数据转发到其他端口。我可以看到端口 0 的 RXD 引脚接收到了正确的波形，但其他端口没有发出任何波形。 可能存在哪些问题？您有什么建议吗？ 以下是我的硬件拓扑和脚本配置。我的脚本使用 simplePQRS.py 进行了修改 敬上， xianlong Re: SJA1105P PHY MODE MAC to MAC connection issue 感谢您的支持。SJA1105 的 RX_ER 没有接地 Re: SJA1105P PHY MODE MAC to MAC connection issue 您好， 根据所提供的信息，很难提出建议。拓扑和脚本修改看起来是正确的。 要发表更多评论，请提供更多信息。 能否分享您的完整电路图，或至少是 S32K3 + SJA1105 + TJA1103 连接的部分？ 能否分享您的 sja1105_simple.py？ 您的流量是多少？ BR, Petr

L4Re 虚拟机监控器 Uart 输出 我在 s32z.cc 中看到了 S32Z 平台引导程序中 DCC UART 的初始化代码。那么如何在 S32Z280-594EVB 中使用 DCC UART 输出？ 如何使用 J-Link 连接和配置，然后查看 DCC 日志输出？ 如果 J-Link 无法在 S32Z280-594EVB 上使用，我应该如何通过（虚拟机监控器）引导程序中的串行端口输出 printf 日志？ Re: L4Re Hypervisor Uart output 那么在 L4Re 中是否无法通过 DCC 输出 printf 日志？或者，能否通过 S32 调试探针或劳特巴赫调试器输出 printf 日志？ Re: L4Re Hypervisor Uart output hi，steven52777 感谢您与我们联系。 调试 S32Z280-594EVB 开发板通常涉及使用 S32 调试探针和劳特巴赫调试器。 有关详细信息，请参阅 S32ZE_GreenVIP_1.3.0 的分步步骤。 BR 乔伊

imx8mp vpu encoder: vc8000e: driver segmentation fault 0x0000ffffd83ba748 in VCEncStrmEncodeExt () from /lib/libhantro_vc8000e.so.1 (gdb) bt #0 0x0000ffffd83ba748 in VCEncStrmEncodeExt () from /lib/libhantro_vc8000e.so.1 warning: could not convert 'main' from the host encoding (ANSI_X3.4-1968) to UTF-32. This normally should not happen, please file a bug report. #1 0x0000ffffd83bdc00 in VCEncStrmEncode () from /lib/libhantro_vc8000e.so.1 #2 0x0000ffffd84e771c in VCEnc_encoder_encode () from /lib/libfslvpuwrap.so.3 #3 0x0000ffffd84e8124 in VPU_EncEncodeFrame () from /lib/libfslvpuwrap.so.3 #4 0x0000ffffd85a2af4 in ?? () from /lib/gstreamer-1.0/libgstvpu.so #5 0x0000fffff65bf9b8 in ?? () from /lib/libgstvideo-1.0.so.0 #6 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #7 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #8 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #9 0x0000fffff7aba87c in ?? () from /lib/libgstbase-1.0.so.0 #10 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #11 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #12 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #13 0x0000fffff7aba87c in ?? () from /lib/libgstbase-1.0.so.0 #14 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #15 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #16 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #17 0x0000ffffd86a6cac in ?? () from /lib/gstreamer-1.0/libgstvideorate.so #18 0x0000fffff7abaeb0 in ?? () from /lib/libgstbase-1.0.so.0 #19 0x0000fffff7aba7fc in ?? () from /lib/libgstbase-1.0.so.0 #20 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #21 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #22 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #23 0x0000fffff4218118 in ?? () from /lib/gstreamer-1.0/libgstcoreelements.so #24 0x0000fffff7923390 in ?? () from /lib/libgstreamer-1.0.so.0 #25 0x0000fffff749e954 in ?? () from /lib/libglib-2.0.so.0 #26 0x0000fffff749dc68 in ?? () from /lib/libglib-2.0.so.0 #27 0x0000fffff72b0d14 in ?? () from /lib/libc.so.6#28 0x0000fffff731364c in ?? () from /lib/libc.so.6 Certain combinations of bitrates, gop size and complexity seem to exarcerbate this. I would like to fix the segfault at source so I need the source code for the following library: libhantro_vc8000e.so.1 Is this available anywhere? Graphics & Display i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Linux Suspected Software Defect Re: imx8mp vpu encoder: vc8000e: driver segmentation fault Hello, The source code is proprietary you need to check with professional services if you can obtain the source code. https://www.nxp.com/support/support/nxp-engineering-services/professional-support-for-processors-and-microcontrollers:PREMIUM-SUPPORT Regards

EIQ 模型动物园 recipe.sh 您好， ，我是一名用户，试图在恩智浦芯片上运行一个物体检测模型。我注意到，与 EIQ Model Zoo GitHub 对象检测部分中的其他模型不同，没有配方.sh 脚本可以将 FastestDet 从 ONNX 转换为 TFLite。我是否有可能获得访问权限？当我尝试使用 EIQ 门户网站时，输入形状并没有从 NCHW 变为 NHWC。 谢谢！ #i.MX RT1050     i.MX RT105x i.MX RT106x Re: EIQ model zoo recipe.sh 你好@SungWonJung 动物园模型不提供培训脚本。如果客户自己训练模型，则应使用开源的FastestDet项目。 Re: EIQ model zoo recipe.sh 感谢您的回复 我在 i.MX RT1050 上成功运行了来自(https://github.com/NXP/eiq-model-zoo/blob/main/tasks/vision/object-detection/fastestDet/dperson_shufflenetv2.tflite)的 FastestDet TFLite 模型。 现在，我想用自己的自定义数据集对模型进行微调。 然而，与(https://github.com/NXP/eiq-model-zoo/blob/main/tasks/vision/object-detection)中提供的其他模型不同— 例如 Centernet 或 NanoDet-M，其中包含转换脚本 (配方.sh、例如https://github.com/NXP/eiq-model-zoo/blob/main/tasks/vision/object-detection/nanodet-m/recipe.sh)- 看来 FastestDet 没有这样的脚本。 我想知道是否有可能获得类似的 FastestDet 转换配方。 (当我尝试使用 eIQ 门户时，转换失败了，因为 NCHW 没有更改）。 谢谢！ Re: EIQ model zoo recipe.sh 您好， 请澄清有关此问题的更多细节，例如参考链接、哪个示例、SDK 版本、如何重现。

S32K312 SAFなしのフォールトインジェクション こんにちはチーム アプリケーションで SAF と SPD が使用されていない場合、これらの種類の障害に対する反応をテストするために FCCU に障害を注入することは可能ですか? リファレンス マニュアルで、Non-critical Fault Fake (NCFF) レジスタを見つけました。このレジスタに値を書き込むと障害が注入されますか? ありがとう。＆よろしく。 西アンチ Re: S32K312 Fault Injection without SAF こんにちは@linxianti さん CMU は FCCU にコネクテッドされておらず、いくつかの VLD ソースのみがリンクされています。 参考までに、RTD MCAL MCU ドライバを使用する簡単な CMU の例を次に示します。 https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K344-MCAL-MCU-ClockMonitor-v1-0-S32DS36-RTD600/ta-p/2179976 LVD 機能をテストするには、電源電圧を操作CAN。 ちなみに、SPD/SAF も NCFF インジェクションを使用します。 よろしくお願いいたします。 ダニエル Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applications or product design. Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction. Re: S32K312 Fault Injection without SAF こんにちは、ダニエル ご返信ありがとうございます。 EIM に関しては、EIM はメモリに関連する障害を注入するためにのみ使用されますか。リファレンスマニュアルにこの説明を見つけたからです。これは他のフォールトインジェクションには適用されません。例えばクロック障害か電圧障害ですよね？ もしそうなら、NCFF を書く以外にどのようにしてこの種の障害を注入 CAN ますか。NCFF を記述すると、障害の処理を検証することしかCANず、障害の検出はカバーされないためです。 ありがとう。& よろしく。 西アンチ Re: S32K312 Fault Injection without SAF こんにちは@linxianti さん SAF と SPD は、EIM (エラー インジェクション モジュール) を介してペリフェラル ハードウェアに障害を注入します。 対照的に、NCFF レジスタはペリフェラルに影響を与えずに、FCCU に直接障害を注入します。 FCCU 障害処理をペリフェラル障害源から独立してテストすることが目的の場合は、NCFF の使用が適切です。 よろしくお願いいたします。 ダニエル   

SO/QSレジスタの読み取り中に問題が発生し、MC17XS6500EEK（MPC5775B SPI）の出力がちらつく 私はSPI経由でMPC5775B MCUからMC17XS6500EEK HSDを制御しています。 基本的な出力制御は正常に動作しますが、ステータス レジスタを定期的に読み取ろうとすると問題が発生します。 現在やっていること 起動時にHSDを初期化します。 出力を構成する 初期化中にSOAモードを設定する ウォッチドッグトグルを定期的に有効にする 出力はアプリケーションロジックに基づいて正常に動作します 1秒ごとにステータスを読み取ります: SO/QSレジスタアドレスをINIレジスタに書き込む SO/QSの応答を読み返す 障害が検出された場合は、特定のチャネルアドレスをINIレジスタに書き込み、その応答を読み取ります。 完了したら、ステップ1の元のINIレジスタ値を復元します。 ウォッチドッグは毎回切り替えられる 問題 これを実行すると、出力がちらつき、デバイスが再初期化されたように見えます。 実行時に INI レジスタを変更すると、構成された出力に副作用が生じるようです。 私の質問 SO/QS レジスタを読み取るためだけに、初期化後にINI レジスタを変更することは許可されていますか/安全ですか? そうでない場合、構成された出力を妨げたり、ちらつきやリセットを引き起こしたりせずにステータス (SO/QS およびチャネル障害) を読み取るための推奨 SPI シーケンスは何ですか? アプリケーションノートへのガイダンスや参照があれば役立ちます。 Re: Issue while reading SO/QS registers causes outputs to flicker on MC17XS6500EEK (MPC5775B SPI) こんにちは、 @davidtosenovjan 、 MC17XS6500EEK HSD では、障害情報をどのようにポーリングできますか?これに関するサンプルコードはありますか? 現在、SOA モード ビットを I/O ステータスに設定して HSD を初期化し、I/O ステータス SO 応答アドレスを SO レジスタ アドレスとして使用しています。私のアプローチは、クイック ステータス レジスタ (QSR) を定期的にポーリングし、障害が検出された場合は、個々のチャネルをポーリングして詳細な障害情報を取得し、それに応じて処理することです。 ただし、チャネル固有の障害をポーリングすると、HSD は障害を自動的にリセットするようです。障害ステータスをリセットせずに障害情報を適切に取得する方法に関するサンプル コードまたはガイダンスを共有していただけますか? Re: Issue while reading SO/QS registers causes outputs to flicker on MC17XS6500EEK (MPC5775B SPI) 出力のちらつきは、SO/QS レジスタへのアクセス方法による意図しない再初期化によって発生する可能性があります。 これを回避するには、各 SPI トランザクションに、次の内容を含む適切にフォーマットされた 16 ビットの入力ワードが含まれていることを確認してください。 - ウォッチドッグビット（D15）を修正 - 有効パリティ（D14） - 適切なレジスタ アドレスとバンクの選択。 SPI フレーム外での INI レジスタの変更は避けてください。代わりに、NXP の AN5106 アプリケーション ノートに記載されている標準 SPI プロトコルを使用します。これにより、出力リセットをトリガーすることなく安定した動作が保証されます。 https://www.nxp.com/docs/en/application-note/AN5106.pdf

imx8mp vpu 编码器：VC8000e：驱动程序分段故障 0x0000ffffd83ba748 in VCEncStrmEncodeExt () from /lib/libhantro_vc8000e.so.1 (gdb) bt #0 0x0000ffffd83ba748 in VCEncStrmEncodeExt () from /lib/libhantro_vc8000e.so.1 warning: could not convert 'main' from the host encoding (ANSI_X3.4-1968) to UTF-32。这通常不会发生，请提交错误报告。 #1 0x0000ffffd83bdc00 在 VCEncStrmEncode () 中，来自 /lib/libhantro_vc8000e.so.1 #2 0x0000ffffd84e771c 在 VCEnc_encoder_encode () 中，来自 /lib/libfslvpuwrap.so.3 #3 0x0000ffffd84e8124 在 VPU_EncEncodeFrame () 中，来自 /lib/libfslvpuwrap.so.3 #4 0x0000ffffd85a2af4 in ?? () from /lib/gstreamer-1.0/libgstvpu.so #5 0x0000fffff65bf9b8 in ?? () from /lib/libgstvideo-1.0.so.0 #6 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #7 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #8 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #9 0x0000fffff7aba87c in ?? () from /lib/libgstbase-1.0.so.0 #10 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #11 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #12 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #13 0x0000fffff7aba87c in ?? () from /lib/libgstbase-1.0.so.0 #14 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #15 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #16 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #17 0x0000ffffd86a6cac in ?? () from /lib/gstreamer-1.0/libgstvideorate.so #18 0x0000fffff7abaeb0 in ?? () from /lib/libgstbase-1.0.so.0 #19 0x0000fffff7aba7fc in ?? () from /lib/libgstbase-1.0.so.0 #20 0x0000fffff78e43a8 in ?? () from /lib/libgstreamer-1.0.so.0 #21 0x0000fffff78e65bc in ?? () from /lib/libgstreamer-1.0.so.0 #22 0x0000fffff78ee6f4 in gst_pad_push () from /lib/libgstreamer-1.0.so.0 #23 0x0000fffff4218118 in ?? () from /lib/gstreamer-1.0/libgstcoreelements.so #24 0x0000fffff7923390 in ?? () from /lib/libgstreamer-1.0.so.0 #25 0x0000fffff749e954 in ?? () from /lib/libglib-2.0.so.0 #26 0x0000fffff749dc68 in ?? () from /lib/libglib-2.0.so.0 #27 0x0000fffff72b0d14 in ?? () from /lib/libc.so.6 #28 0x0000fffff731364c in ?? () from /lib/libc.so.6 某些比特率、gop 大小和复杂性的组合似乎会使这种情况变得更加严重。 我想从源代码上修复 segfault，因此我需要以下库的源代码： libhantro_vc8000e.so.1 这个在哪里可以买到？ 图形与显示 i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Linux 疑似软件缺陷 Re: imx8mp vpu encoder: vc8000e: driver segmentation fault 你好 源代码是专有的，您需要向专业服务机构咨询是否可以获得源代码。 https://www.nxp.com/support/support/nxp-engineering-services/professional-support-for-processors-and-microcontrollers:PREMIUM-SUPPORT 此致

ERR050686 S32G ATF BL2 的 I2C 恢复支持 嗨，团队、 Linux 电路板支持包、启动 和内核支持 I2C 恢复，但 客户报告了一个问题，即 I2C SDA 线路在 BL2 中与 VR5510 PMIC 进行的 I2C 通信期间卡住了 。 为了恢复 I2C SDA，他们将 ERR050686 中描述的变通方法应用于 BL2 I2C 设备驱动程序。 目前，BL2 I2C 驱动程序默认不支持ERR050686 的解决方法，因此客户需要自行实施。 是否有可能在 BL2 I2C 设备驱动程序中正式支持这种解决方法？ 原票：https://community.nxp.com/t5/S32G-Internal-Community/S32G2-I2C-workaround-support-for-ATF-BL2/td-p/2192284# BRs， 天祥 Linux BSP Re: ERR050686 I2C recover support for S32G ATF BL2 @Tianxiang_Huang 你好、 团队将尽快提供答复。

imx93 寄存器 SDIO 通用驱动程序 HI NXP 1。我想将 SDIO 控制器注册为 /dev/my_dev 设备，这样应用层就可以通过这个节点控制 SDIO。 Linux Re: imx93 register SDIO generic driver 你好@yrj 如需驱动程序代码，请咨询我们的工程服务部门： https://www.nxp.com/support/support/nxp-engineering-services:SW-SUPPORT B.R Re: imx93 register SDIO generic driver 你好@pengyong_zhang 1.它只需要一个支持 CMD52 和 CMD53 的标准 SDIO 接口。 Re: imx93 register SDIO generic driver 你好@yrj 您提出这一请求的目的是什么？你想控制 SDIO 设备或更改相关的寄存器是什么？ B.R