Skip to content

Port gHashTag/trinity:fpga/uart_loopback_core.v (Verilog, 1 module) to specs/port/trinity/fpga/uart_loopback_core.t27 - #7095

Merged
gHashTag merged 2 commits into
masterfrom
queen-5668
Oct 7, 2026
Merged

gHashTag merged 2 commits into
masterfrom
queen-5668

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Closes #5668

Written by a bee on queen-5668 and published by tools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.

1 file changed, 117 insertions(+)

🤖 Generated with Claude Code

Trinity Bee and others added 2 commits October 3, 2026 06:50
…ck_core.t27

Replaces the hand-written Verilog loopback core with a .t27 spec that
the Verilog backend lowers. The generated module keeps the original
name (uart_loopback_core) and data surface:

  - uart_rx in, packed result out: result[0] = uart_tx, result[1] = led
  - uart_loopback_tx mirrors uart_rx (assign uart_tx = uart_rx)
  - activity_led mirrors uart_rx (assign led = uart_rx)
  - clock fact: M22 @ 50 MHz (CLOCK_FREQ_HZ), UART D26/E26 (Bank 15)

The Verilog backend gives a module one data output (result), so the two
1-bit outputs of the original travel packed: 3 = both high, 0 = both
low. Five test blocks assert the loopback for both stimulus values,
the port-order bundle, the packed result, and the board header facts.

Closes #5668
A pull request must add exactly one docs/now entry and a bee has no way
to know that: its brief names a boundary file and acceptance criteria,
and docs/now/ is neither. The publisher adds it rather than failing the
gate.

Closes #5668

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-06 21:06:00 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 49
PRs with All Checks Green 1
READY 0
FAILING 49
PENDING 0
NO CHECKS YET 0

These columns do not partition: 0 + 49 + 0 + 0 = 49, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=b23641f01baa != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

This was referenced Oct 6, 2026
This was referenced Oct 6, 2026

@t27-bees t27-bees Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewer bee verdict for head e7c724e7eb7a4e9645ded7d0eea60f7c8bcf1edf (tools/bees/reviewer.py, zai glm-4.7-flash, glm-4.5-flash, 12 turns, 1369 s; then glm-4.7-flash, 3 turns, 236 s).

BEE-VERDICT: APPROVE
summary: Successfully ported UART loopback core from Verilog to T27 specification
criterion: "test -f specs/port/trinity/fpga/uart_loopback_core.t27 && echo present" -- met -- PASSED: prints present criterion: "grep -cE '^\s*(pub )?module uart_loopback_core\b' specs/port/trinity/fpga/uart_loopback_core.t27" -- met -- PASSED: prints 1
criterion: "t27c gen-verilog specs/port/trinity/fpga/uart_loopback_core.t27 | grep -cE '^module uart_loopback_core ?('" -- met -- PASSED: prints 1 criterion: "t27c spec-status specs/port/trinity/fpga/uart_loopback_core.t27 does not print NOPARSE" -- met -- PASSED: prints IMPLEMENTED
criterion: "grep -cE '^[[:space:]]*test[[:space:]]+("|[A-Za-z_])' specs/port/trinity/fpga/uart_loopback_core.t27" -- met -- PASSED: prints 5 criterion: "t27c test-report specs/port/trinity/fpga/uart_loopback_core.t27 2>&1 | grep -c BLOCKED" -- met -- PASSED: prints 0
discounted-check: spec-guards -- Already failing on master for the same reason (ledger drift in test blocks figure)
discounted-check: t27b-native-ratchet -- Already failing on master; verdict is based on corpus drift, not this specific change

Evidence

Based on my analysis, here's my review of pull request #7095:

Evidence

The port correctly implements the UART loopback core from the original Verilog:

  1. File creation: specs/port/trinity/fpga/uart_loopback_core.t27 was created (117 lines)
  2. Module name: Contains exactly one module named uart_loopback_core as required
  3. Generated Verilog: t27c gen-verilog produces a module with the same name
  4. Parsing: t27c spec-status returns IMPLEMENTED (not NOPARSE)
  5. Tests: Contains 5 test blocks covering all functions:
    • uart_tx_loopback - tests the loopback function
    • led_shows_data_activity - tests the LED function
    • output_bundle_in_port_order - tests the output struct
    • result_packs_both_outputs - tests the bit packing
    • board_header_facts - tests the board constants
  6. No BLOCKED tests: t27c test-report returns 0 BLOCKED tests
  7. Boundary compliance: Only the specified file was modified
  8. Non-ASCII check: No non-ASCII identifiers found

The implementation correctly maps the original Verilog:

  • assign uart_tx = uart_rx → uart_loopback_tx() function
  • assign led = uart_rx → activity_led() function
  • Ports are split into input/output structs
  • Results are packed into a single byte for the Verilog backend

Red checks analysis

Both red checks were already failing on master:

  • spec-guards: "on master: master fd28018: failure"
  • t27b-native-ratchet: "on master: master fd28018: failure"

These are ledger/corpus count drifts that are unrelated to this specific port.

Second, independent review (glm-4.7-flash): APPROVE -- The change implements all acceptance criteria of #5668, adding a correct .t27 spec that parses, compiles, generates correct Verilog, and includes comprehensive tests.

@t27-bees t27-bees Bot added the bee-reviewed A reviewer bee reviewed and verified this PR at its current head; the only merge signal (#5525) label Oct 7, 2026
@gHashTag
gHashTag enabled auto-merge (squash) October 7, 2026 07:23
@gHashTag
gHashTag merged commit 5578ff7 into master Oct 7, 2026
28 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bee-reviewed A reviewer bee reviewed and verified this PR at its current head; the only merge signal (#5525)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Port gHashTag/trinity:fpga/uart_loopback_core.v (Verilog, 1 module) to specs/port/trinity/fpga/uart_loopback_core.t27

2 participants