Skip to content

[META] LPC845-BRK on-hand burn-down: cover the open LPC8xx work end-to-end #586

Description

@zackees

Goal

We now have an LPC845-BRK physically on-hand and wired up. The remaining LPC8xx work is no longer hardware-blocked — this meta exists so we can burn it down end-to-end with a single rundown view across the fbuild side, the FastLED side, and the upstream framework / platform packages.

This is not a redesign. The existing per-issue plans stand. This meta only consolidates the remaining checklist so triage is one click.

For the FastLED-internal driver / RX / multi-strip / harness work, see the companion meta FastLED/FastLED#3040 — items unique to that scope live there.

Status of preceding metas

Open work — fbuild side

1. Deploy path on the LPC845-BRK board

Now unblocked by hardware-on-hand. The standalone monitor flow that #532 / #577 / #580 hardened end-to-end should now have a parallel deploy story for this board.

2. Build-flag propagation gap

3. CI canary for the 5 variants

Open work — FastLED side (fbuild-relevant)

These are the FastLED-side items that intersect with fbuild's deploy / build / CI pipeline. The pure-driver / RX / multi-strip items live under #3040.

Open work — upstream packages

  • zackees/ArduinoCore-LPC8xx#7fact-check linker scripts and core code against references. Hardware verification is exactly what catches the failures here.
  • zackees/platform-nxplpc-arduino#1make LPC8xx board manifests work in standalone PlatformIO projects. Affects fbuild interop only indirectly (since fbuild reads its own board manifests); document the divergence either way.

Dependency edges

Hardware-on-hand (this issue)
   ├──unblocks──► #551 ──blocks──► #565        (deploy + VCOM unwedge)
   ├──unblocks──► FastLED#3004                 (AutoResearch wiring)
   ├──unblocks──► FastLED#3014, FastLED#3015   (driver + loopback validation)
   └──unblocks──► ArduinoCore-LPC8xx#7         (linker / core fact-check)

FastLED#3002 (partial)  ──blocks──► FastLED#3015 (flash budget gate)
FastLED#3015            ──follows──► RxDevice / SCT-capture implementation in #3040
#551                    ──blocks──► #550 (canary needs deploy for the smoke-test step)
                                    FastLED#2990 (same)

Acceptance

This meta closes when:

  • All [ ] items above are either closed or explicitly punted with a follow-up linked here.
  • The LPC845-BRK builds + flashes + monitors + AutoResearch-round-trips on a real board through one full fbuild deploy + monitor cycle without intervention.
  • FastLED CI on the 5 LPC8xx variants is green on master for at least one full release cycle.

When (1) + (2) + (3) hold, declare LPC8xx end-to-end support shipped and close this meta + close any survivors that effectively duplicate it.

Decisions / framing

  • Scope = end-to-end LPC8xx burn-down on the fbuild side, cross-linked to FastLED. Not a redesign. Not a relitigation of the Stages 3/4 plan from the closed metas.
  • Priority: P2 (tracker). Each sub-issue carries its own priority; this meta is a triage view.
  • Pair with FastLED/FastLED#3040 rather than duplicate it. That meta owns the FastLED-internal driver/RX/multi-strip rundown; this one owns the fbuild deploy + CI-integration story plus the cross-repo connection.
  • The hardware-on-hand unblock is the trigger. Items that were only gated on "needs a maintainer with a board" can now move.

cc @zackees

Metadata

Metadata

Assignees

No one assigned

    Labels

    trackingUmbrella or tracking issue

    Type

    No type

    Projects

    Status
    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions