Repository navigation
Conversation
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]>
This was referenced Sep 24, 2026
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 inSH_SEARCHdescribes it, and the only supportedSPAN_VERSIONassumes a BSL.What
SH_SEARCH.SPAN_NRF52840("NeuroLynQ Span") andSERIAL_PORT.NORDIC_VEND_ID("1915"), withisSpanNrf52840(vendorId, productString)as the one rule each platform's detection calls.0x5210is 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, soneurolynq-web-sdkstill has to follow the PID.SPAN_VERSION.SPAN_NRF52840: supported, with the newisMspBslSupported()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 fullConsensysApibuild is green locally.Other stacks
None need this. Shimmer-C-API, pyshimmer and SwiftAPI do not discover Spans.
neurolynq-web-sdkPR #1 carries the same dongle asNEUROLYNQ_SPAN_NRF52840, by VID/PID.🤖 Generated with Claude Code