Skip to content

DEV-1047 Know the nRF52840 Span by Nordic's VID and its product string - #302

Closed
marknolan wants to merge 1 commit into
masterfrom
DEV-1047_nordic_span_discovery
Closed

marknolan wants to merge 1 commit into
masterfrom
DEV-1047_nordic_span_discovery

Conversation

@marknolan

@marknolan marknolan commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

Part of DEV-1047, scope item 2. ShimmerResearch/Shimmer-Advance-API#474 uses it, so this one merges first.

Why

The nRF52840 Span (verisense-firmware SR9_SPAN_NRF52840) is one CDC port under Nordic's VID, with no FTDI bridge and no MSP430 BSL. Nothing in SH_SEARCH describes it, and the only supported SPAN_VERSION assumes a BSL.

What

  • SH_SEARCH.SPAN_NRF52840 ("NeuroLynQ Span") and SERIAL_PORT.NORDIC_VEND_ID ("1915"), with isSpanNrf52840(vendorId, productString) as the one rule each platform's detection calls.
  • No PID in the rule, on purpose. 0x5210 is provisional and unallocated under Nordic's VID. Matching on the product string means an allocated PID needs no desktop release. Web Serial cannot see product strings, so neurolynq-web-sdk still has to follow the PID.
  • SPAN_VERSION.SPAN_NRF52840: supported, with the new isMspBslSupported() false. Appended, so the existing ordinals are unchanged.

Tests

API_00012_SpanNrf52840IdentityTest (8 tests) pins the rule to the strings Windows reported for the bench devices on 2026-09-24. That includes the NeuroLynQ-mode Verisense on the same VID, which is a node and must not match. The full ConsensysApi build is green locally.

Other stacks

None need this. Shimmer-C-API, pyshimmer and SwiftAPI do not discover Spans. neurolynq-web-sdk PR #1 carries the same dongle as NEUROLYNQ_SPAN_NRF52840, by VID/PID.

🤖 Generated with Claude Code

The nRF52840 Span (verisense-firmware SR9_SPAN_NRF52840) is one CDC port
under Nordic's VID, with no FTDI bridge and no MSP430 BSL. Nothing in
SH_SEARCH describes it, and the only supported SPAN_VERSION assumes a BSL.

- SH_SEARCH.SPAN_NRF52840 ("NeuroLynQ Span") and
  SERIAL_PORT.NORDIC_VEND_ID ("1915"), with isSpanNrf52840() as the one
  rule every platform's detection applies. It takes no PID on purpose:
  0x5210 is provisional and unallocated under Nordic's VID, and a PID
  match would need a host release whenever it changes.
- SPAN_VERSION.SPAN_NRF52840, supported, and isMspBslSupported() so a
  caller can tell a Span reset and programmed through a BSL from one
  that is not. Appended, so the existing ordinals stand.

API_00012 pins the rule to the product strings Windows reported for the
bench devices on 2026-09-24, including the NeuroLynQ-mode Verisense on
the same VID, which is a node and must not match.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@marknolan

Copy link
Copy Markdown
Member Author

Superseded by #308, which carries this PR's commit unchanged, together with the rest of DEV-1047's Java driver changes, as one PR for review. Closed without merging; the branch is kept.

@marknolan marknolan closed this Sep 28, 2026
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