Measure & wire USB-Kestrel TSF-write / TBTT-follow so a USB 8852CU can run a cell node (M6 moving-UE)

Aperta
#579 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

  1. Measure, over USB, on the bench (8852CU/8832CU):
    • WriteTsf actually 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 PCIe tsf_write_ok).
    • TBTT follows the TSF: a WriteTsf on an active HW beacon moves its TBTT with it — the USB analogue of tests/kestrel_tbtt_probe.cpp (currently PCIe + 8852C only), witnessed on a second radio.
  2. Wire it: set tsf_write_ok / tbtt_follows_tsf true for USB Kestrel gated on the measurement (by variant / measured flag), so caps_ok passes only where it has been shown to hold.
  3. 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_timestamp are already true over USB, so only the TSF-write/TBTT pair is in question.
  • The cellcaps probe 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

Lingua principale
C
Stelle
56
Fork
29
Merge medio
3h 43m
PR unite (30g)
75

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenIPC/devourer

Tutte le issue di OpenIPC/devourer

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.