Follow-ups left open by the 8852C ACK responder review (#489)

未關閉
#490 5 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
6/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
c

研究方向

Start with the #489 review thread, since most measurements are excluded there. Item 3 is the most contained entry point: HalKestrel::coex_mac_init sets ENBT only for the 8852B, so the 8852C path needs a fix. Item 1 depends on hardware bench work with a firmware RAM dump and a vendor A/B, and AdapterCaps.h holds the matrix to update. Done means a root cause or a reproducible fix for the dead-ACK sessions, not a guess.

由索引模型根據 Issue 內容生成。

描述

enhancement

Left open by the review and bisect of #489 (8852C hardware ACK responder). Bench: TX50UH (RTL8832CU) x2, 8812CU soliciting with CCX tx.report, near field.

1. 8852C bring-ups that never answer an ACK: cause unknown

The responder arms, the entry reads back, injection works, and the chip answers no ACK for the whole session. Measured rate on this bench: ~1/3 of soft re-runs in the morning, ~85% by the afternoon, on ch161 and ch6, on both units; one 8852B-side report of ~1 in 55 from the author.

Excluded by measurement (details in the #489 review thread):

  • temperature (meter flat; dead at the coldest reading after 120 s VBUS-offs) and retained chip state (120 s VBUS cuts);
  • the TX chain (99% of host-injected frames witnessed in a dead session) and the soliciting side (an independent witness sees the ACKs vanish);
  • every host-readable register and SRAM read at the correct 0x20 stride: ADDR_CAM, BSSID CAM, DMAC/CMAC tables (uninitialised in RX-only sessions, no separating bit), MAC 0x8000/0xC000/0xD800 blocks, BB 0x10000-0x17FFF, RF path 0/1, GNT;
  • levers: host-written minimal and vendor-default CMAC entries, the CMAC H2C, forced WiFi-only GNT with and without the vendor coex init, a host-written BSSID CAM entry, the CAM slot.

The one lead: R_AX_WMAC_TX_INFO0_DEBUG (0xCAE8) reads 0x10914012 in every dead session and 0x10915012 in good ones (bit 12), so the TMAC does issue the response, and the RF path-0 TX registers show it never reaches the RF. Next experiments: a firmware RAM dump dead vs good, and a vendor rtl8852cu A/B on the same unit with a real station answering, to learn whether the vendor bring-up ever shows the state at all.

2. Kestrel host injection on ch161 nearly silent

Both TX50UH units, txdemo TX-only at 6M, 20 ms gap, ch161: 6-10 of ~290 frames witnessed, by either an 8852C or the 8812CU, in good and dead ACK sessions alike. Same setup on ch6: 97-99%. Earlier 8852C -> 8812CU injection A/Bs (~97%) were on ch6. Needs a 5 GHz injection A/B against the vendor driver on this unit before any 5 GHz Kestrel TX number is trusted.

3. 8852C coex init on the C die is a no-op

HalKestrel::coex_mac_init sets ENBT for the 8852B only, so on the 8852C both write_lte calls time out ("Kestrel coex: LTE interface not ready" twice per session) and the GNT stance is skipped. The vendor's 8852C path (coex_8852c.c) does not use the LTE window (mac_write_lte_8852c returns MACNOTSUP); it writes R_AX_GNT_SW_CTRL and R_AX_BTC_CFG / R_AX_BT_CNT_CFG / R_AX_CCA_CFG_0 directly. Cold state read on this unit: GNT_SW_CTRL 0x175775, GNT_VAL 0x118 (BT granted, WL not), BTC_CFG bit 31 clear. Forcing the WiFi-only grant did not change item 1, so this is a correctness cleanup, not a fix.

4. Bench note

The dead rate in item 1 rose through a day of back-to-back sessions on both units and no power cycle reset it. Anyone measuring the 8852C responder late in a session day will see a different rate from the morning; the matrix in AdapterCaps.h should say when in the day its rows were taken.

主要語言
C
星號
56
分支
29
平均合併
3 小時 43 分鐘
30 天內合併 PR
75

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

OpenIPC/devourer 的其他 Issue

查看 OpenIPC/devourer 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。