Coarse-tier (USB) DU on a PTP node — the M4/M5 items split out of the PCIe tier

Aberta
#565 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
8/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
c, cpp, shell

Direção de pesquisa

This needs a USB DU on a PTP-locked rig, which a newcomer is unlikely to have, so start by reading src/AdapterCaps.h (sync_tier()), src/cell/TsfDiscipline.h (the ledger mode), and the refusal in examples/cell. The selftests tests/cell_m4_selftest.cpp and tests/cell_m5_selftest.cpp show what is simulated today. Done means a measured coarse-tier hold reported as distributions from tests/cell_ptp_multi.sh on real hardware, which is not achievable without the rig.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

enhancement

Part of the 5G-NR RAN EPIC #254. Split out of M4 #258 and M5 #259, which close on the PCIe tier. Everything here needs a USB DU on a PTP-locked node, and the rig doesn't have one.

What the rig has run

Only the tight tier: three RTL8852CE cells over PCIe, each beacon grid held to the PTP fabric by src/cell/TsfDiscipline.h in service mode (CELL_REF_PTP). They held 1.8–3.6 µs rms (testrig results/2026-11-04-m4-three-cell-beacon-sync.txt), with loss-of-sync auto-suspend verified (results/2026-11-05-m4-cell-sync.txt). The coarse tier exists in code and selftests only:

  • AdapterCaps::sync_tier() classifies a USB DU as coarse (src/AdapterCaps.h, ctest adapter_caps_derive).
  • TsfDiscipline.h has a ledger mode for the USB TBTT actuator, exercised only by a simulated selftest (tests/cell_m4_selftest.cpp).
  • examples/cell refuses service mode on a DU that isn't tight-sync, so a USB DU can't run as a disciplined cell today.
  • The coarse tier's ~0.5–1.5 ms comes from docs/time-distribution.md, not from a measurement (docs/cell-m4.md: "Not yet measured").
  • The M5 planner gives a coarse DU frequency separation only (tests/cell_m5_selftest.cpp). No coarse DU has run on the rig (docs/cell-m5.md).

Deliverables

  • A USB DU host on the PTP fabric: a host with a PTP-capable i226 link to the n300-1 hub (star, no switch in the timing path), qualified with testrig box_acceptance.sh, and a USB radio whose AdapterCaps passes the cell DU checks. Which USB radio and host is an open decision (#381 gate C asks the same question for ARM).
  • Service mode for the ledger variant in examples/cell, enabled for coarse-tier DUs (it is refused today).
  • tests/cell_ptp_multi.sh (from M4): one PCIe DU and one USB DU on one PTP timebase, with the hold reported per DU as distributions (rms, p95, p99). This measures the coarse tier.
  • The M5 coarse-tier rule on air: a coarse DU next to a tight one gets frequency separation, never a shared channel's time slots. The coordination run (m5_ran_coord.sh) with one USB DU.
  • Loss-of-sync on the coarse tier: the M4 auto-suspend test (stop ptp4l) with the USB DU.

Relationships

  • #381 (ARM cell-node spike), gate C: the same USB-tier discipline, on ARM.
  • M5 #259 keeps its PCIe item, applying channel separation to a running DU at runtime.
Linguagem predominante
C
Estrelas
56
Forks
29
Merge médio
3h 43min
PRs com merge (30d)
75

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de OpenIPC/devourer

Todas as issues de OpenIPC/devourer

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.