Measure & wire USB-Kestrel TSF-write / TBTT-follow so a USB 8852CU can run a cell node (M6 moving-UE)
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 12/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- cpp
- Bereich
- networking
Rechercherichtung
Start in src/kestrel/RtlKestrelDevice.cpp where tsf_write_ok and tbtt_follows_tsf are forced false for USB, and read the PCIe path that sets them from measurement. The USB analogue to build on is tests/kestrel_tbtt_probe.cpp (PCIe/8852C only) plus the cellcaps probe in examples/cellcaps, which produced the caps dump in the issue. Done means a measured TSF write and TBTT-follow on a USB 8852CU, the two caps gated on that measurement, and a cell UE landing its uplink in slot. This needs the physical radio on the bench, so it is not a code-only start.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Part of the scheduled-RAN epic #254; unblocks the portable moving-UE node in #563 (Option B) and the M6 follow-ups (#566).
What
A USB Kestrel (RTL8852CU/8832CU) cannot run a cell node today, because the cell caps gate (examples/cell caps_ok) requires tsf_write_ok ∧ tbtt_follows_tsf ∧ beacon_backoff_ctl ∧ hw_beacon_txtsf, and over USB the first two are false by policy, not by measurement:
// src/kestrel/RtlKestrelDevice.cpp
c.tsf_write_ok = !_device.is_usb(); // "USB is unmeasured, so it stays refused there"
c.tbtt_follows_tsf = !_device.is_usb();
This was confirmed on hardware (an RTL8852CU on z890p, read with the cellcaps probe):
{"radio":"usb 0bda:c85a","chip":"RTL8852C","variant":"C8852C","transport":"usb",
"tsf_write_ok":0,"tbtt_follows_tsf":0,"beacon_backoff_ctl":1,"hw_beacon_txtsf":1,
"ack_responder_ok":1,"hw_rx_timestamp":1,"hw_injected_mgmt_txtsf":1,"cell_node_ok":0}
So it is the same 8852C die as the fleet's 8852CE, correctly identified, with the ACK responder, HW beacon TX-TSF and RX timestamp all present — only the TSF-write / TBTT-follow pair is withheld because it has never been validated over the USB bus.
Why it matters
The M6 moving-UE bench (#563, Option B) needs a portable, battery-friendly UE node. A USB 8852CU is the obvious candidate — but a UE still needs caps_ok (its uplink is a TSF-steered HW beacon). Until the USB TSF path is measured and wired, no USB radio can be a cell UE, and the moving-UE walk has no portable node.
To do
- Measure, over USB, on the bench (8852CU/8832CU):
WriteTsfactually moves the TSF by the requested step — a read-add-write against the free-running counter, as the PCIe RTL8852CE bench did (the basis for the PCIetsf_write_ok).- TBTT follows the TSF: a
WriteTsfon an active HW beacon moves its TBTT with it — the USB analogue oftests/kestrel_tbtt_probe.cpp(currently PCIe + 8852C only), witnessed on a second radio.
- Wire it: set
tsf_write_ok/tbtt_follows_tsftrue for USB Kestrel gated on the measurement (by variant / measured flag), socaps_okpasses only where it has been shown to hold. - Rig check: run a cell UE on a USB 8852CU against a known-good DU (over-the-air sync, no PTP needed) and confirm its uplink lands in slot, as the PCIe UEs do.
Notes
beacon_backoff_ctl,hw_beacon_txtsf,ack_responder_ok,hw_rx_timestampare already true over USB, so only the TSF-write/TBTT pair is in question.- The
cellcapsprobe used above (examples/cellcaps, reads the cell-gate caps for any USB/PCIe radio) can be PR'd alongside if useful. - DU use over USB additionally needs PTP, which is a separate matter; this issue is scoped to the UE caps.
🤖 Generated with Claude Code
- Vorherrschende Sprache
- C
- Sterne
- 56
- Forks
- 29
- Ø Merge
- 3 Std. 43 Min.
- Gemergte PRs (30 T.)
- 75
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus OpenIPC/devourer
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 1 Tag
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)Evtl. vergeben @josephnef hat das heute übernommen. Offenenhancement
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 42/100
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 12/100
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 8/100
Maintainer antworten meist innerhalb von 1 Tag
-
M6 test realism — a moving-UE handover bench (conducted path-loss matrix, then an over-the-air walk)Offenenhancement
Schwierigkeit 5/5 Über eine Woche Anfängerfreundlichkeit 25/100
OpenIPC/devourer#563 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in OpenIPC/devourer
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
Maintainer antworten meist innerhalb von 1 Tag
-
Needs-Triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
Maintainer antworten meist innerhalb von 2 Tagen
-
issue: bug report
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
Maintainer antworten meist innerhalb von 2 Tagen
-
cross-platform fix-now
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
feature:index kind:crash status:confirmed triaged
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
clice-io/clice#1123 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag