Skip to content

blog: 179 features that change no bits - #877

Open
gHashTag wants to merge 1 commit into
mainfrom
blog/features-that-change-no-bits
Open

blog: 179 features that change no bits#877
gHashTag wants to merge 1 commit into
mainfrom
blog/features-that-change-no-bits

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Adds one blog post: features-that-change-no-bits, dated 2026-08-31.

What it reports

Material from the last 24 hours in openXC7/nextpnr-xilinx#165, plus the merged
changes it depends on:

  • The parity report (2026-08-27) named 179 missing BRAM configuration features
    as "the most concrete bitstream-parity item and the one I would fix first".
  • Its own author retracted that on 2026-08-28: the features are zero-codepoints,
    proven three independent ways (segbits, a bit2fasm round trip giving
    byte-identical 5 576 340 B frames in both arms, and a Vivado ML 2026.1 golden).
  • The real blocker was a clock route from a left-bank pad to a BUFG, which
    produced no feature-count delta and failed in two different-looking ways
    depending on the prjxray-db revision.
  • On 2026-08-30 three Sonata blinky bitstreams ran on a physical board, arm C
    being the one carrying openXC7/nextpnr#1.

Honesty notes

Build

npm run build:ci exits 0; the slug appears in dist/assets/Blog-D9NOt413.js
and gets its own chunk features-that-change-no-bits-DCKQ1Tl1.js.

Not merging — publication is the operator's decision.

🤖 Generated with Claude Code

A parity report between the himbaechel xilinx port and nextpnr-xilinx 0.9.3
ranked its own work items backwards: the 179 missing BRAM features are
zero-codepoints, and the blocker that kept a bitstream off a board produced no
feature-count delta at all. Adds the post with receipts for #165, its two
corrections, openXC7/nextpnr#1, prjxray-db#7, and the two open BUFIO items.

Every measurement is attributed upstream; none was reproduced here, and that is
stated in openQuestions.

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant