How neuromorphic hardware learns to live with lost spikes
Analog neuromorphic hardware has the same scaling problem as living neural tissue: the compute elements cannot be multiplexed, time-shared, or paused, so a bigger system means more units and an interconnect between them. Heinemann and Schemmel's answer for BrainScaleS-2 is a routing chiplet whose central design bet is that spikes and configuration data obey opposite contracts: spike traffic may be dropped, because synapses in biology are unreliable anyway, while control traffic must be bit-perfect, and both can share one physical link.
Source: A Unified Interconnection Network for Chiplet-Based Scaling of the BrainScaleS Neuromorphic System, arXiv:2609.13563 [cs.AR], submitted 11 September 2026. Primary source. Read: the full 8-page arXiv PDF, including the chiplet architecture, the error-control and flow-control design, the simulation evaluation and the comparison table against SpiNNaker, spiNNlink, DYNAP-SE2 and earlier BrainScaleS interconnects.
What the work claims
This is a systems design paper with simulation validation, from the Heidelberg group that builds BrainScaleS-2. The claim is that a single unified interconnection network can carry both classes of traffic a scaled neuromorphic machine generates, event messages whose payload is pure timing and which tolerate small losses, and non-event messages such as configuration data and processor traffic which demand reliability, over one shared physical link, without either class destroying the other. In cycle-accurate simulation the design sustains 95% link bandwidth utilization for the surrogate-gradient training workload across a wide range of spike-to-secured traffic ratios at a bit error rate of 1 in 10^10, with little added spike timing jitter.1
The numbers attached: 22 Gbit per second per direction and port over chip-to-chip links tested to a bit error rate at or below 1 in 10^10; a round-trip event latency of 32 nanoseconds between two routing chiplets at a 4-nanosecond physical delay, 16 nanoseconds single hop; an estimated post-synthesis area of about 0.17 square millimeters in 65 nanometer technology, of which 0.13 square millimeters is buffers; and a 19-bit event payload that can label up to 524,288 neurons, enough for at least 1,024 BrainScaleS-2 chips before label reuse becomes necessary.
How it works
BrainScaleS-2 is a 65-nanometer SoC that emulates up to 512 neurons and 131,072 synapses in continuous-time analog circuitry, running 1,000 times faster than biological real time, with on-chip ADCs and an embedded processor for flexible plasticity rules. The analog core is a fixed physical resource: an emulated neuron exists once, cannot be time-multiplexed, and the silicon runs whether or not you are watching. Monolithic scaling of analog silicon is unattractive, so the proposed architecture tiles routing chiplets in a 2D mesh, each attachable to a BrainScaleS-2 die or an FPGA, mixing process nodes so the analog core stays where it is cheap and the digital fabric advances.
The design's core insight is a refusal to give both traffic classes the same protection. A spike carries no payload; its information is its arrival time. Biological synaptic transmission is unreliable, as the authors note, citing measurements of transmitter release probability, and a neuromorphic system is expected to function despite a small loss of spikes. So event messages are transmitted unsecured and synchronously, and congestion simply drops them, with the receiving side treating arrival time as the presynaptic time. Everything else, configuration writes, processor messages, ADC samples heading to a host for surrogate-gradient training, is error-intolerant and gets the full machinery: Hamming(7,4) forward error correction on the phit type and framing bits, 90-bit flits with a 7-bit CRC giving Hamming distance 3, a link-level automatic-repeat-request protocol with negative acknowledgements and timeout retransmission, and credit-based flow control, all routed wormhole-style by dimension-ordered X-Y routing so packet ordering is preserved. A weighted arbiter gives event phits priority while guaranteeing the secured traffic a configurable minimum throughput, and the two classes are interleaved at the phit level over the same 22-bit-per-nanosecond parallel bus rather than partitioned statically.
Where a skeptic should push
The load-bearing assumption is that dropped spikes are benign, and it deserves real pressure. The biological analogy cuts both ways: synaptic unreliability in real tissue is not random packet loss but a structured, adaptive process with short-term plasticity shaping it, and a scaled mesh that silently discards spikes under congestion is making a computational intervention, not merely tolerating physics. The paper validates loss tolerance only indirectly; there is no experiment here showing that a trained network on the interconnected system retains accuracy under realistic congestion-induced loss patterns. The authors' own earlier multi-chip work is cited for communication, but the end-to-end effect on learning is asserted, not measured in this paper.
Second, this is simulation-only validation, and the simulation stack is worth reading carefully. Correctness of the RTL components was verified formally, which is strong, but the performance claims come from a cycle-accurate model of the chiplets coupled to simplified fixed-latency lossy link models. The headline 32-nanosecond round trip excludes the routing-chiplet-to-BrainScaleS die latency; the event router evaluated is a placeholder broadcast design, with a real multicast router acknowledged as the primary remaining challenge and an expected overhead. The reliability arithmetic contains the paper's most candid number: the single-link mean-time-between-failure bound is on the order of a day, but a 16 by 16 mesh has 960 chip-to-chip links, so the system-level figure degrades to order minutes in the worst case, accepted on the argument that failing to sustain a bandwidth target is usually non-fatal because a few lost ADC samples can be tolerated. That is a defensible engineering trade, but it is a trade, and it sits in tension with the reliability story the secured channel tells.
Third, generality. The design is tuned to BrainScaleS-2's traffic shape and to one specific chip-to-chip link family; the authors note that longer multi-phit event messages or a third error-detected-but-not-corrected traffic class would be needed to make it portable.
Scaling organoids means interconnects, not bigger tissue
For organoid intelligence the uncomfortable parallel is exact. A BrainScaleS-2 analog core cannot be multiplexed, paused, or shared; neither can a living neural culture. A dish of cortical tissue computes what it computes, when it computes it, and the route to a bigger biological computer is not a bigger organoid, which hits diffusion limits, but many organoids joined by an interconnect. That is precisely the architecture this paper engineers for silicon, and the field has no equivalent design discipline: no accepted way to label units, route events between cultures, or define what may be lost in transit. The 19-bit label space, the 524,288-neuron addressability, the credit flow control: these are the unglamorous decisions someone will have to make for multi-organoid systems, and this paper is a working template for making them.
The opportunity is the two-contract insight, which transfers to biological rigs almost without modification. An organoid data chain carries exactly the same two classes: spike streams, where a lost event is tolerable and timing is the message, and everything else, stimulation commands, calibration tables, metadata, where a corrupted value is catastrophic because it misdrives the tissue. Most current MEA pipelines protect both classes equally or neither systematically. A rig that prioritizes spike traffic, drops it under congestion rather than delaying it, and wraps its control path in acknowledgements and flow control would gain determinism where it matters and stop paying reliability costs where it does not. The early-confidence and timing-jitter analyses in this paper also supply the right acceptance criteria: what matters for a spike link is the distribution of arrival-time error, not the delivery rate.
The threat is what chiplet scaling does to the speed argument for tissue. A mesh of BrainScaleS-2 dies runs at 1,000 times biological speed with bounded inter-chip latency, and this paper removes the last structural objection, the interconnect, from scaling it further. The remaining advantages of living tissue, adaptivity, plasticity, the richness of biochemical dynamics, are real but they are also slow, and a silicon analog-emulation fabric that is fast, reproducible, and now architecturally extensible narrows the envelope in which biological computing is the right answer to anything. The honest reading is that reliability engineering, the dullest part of this paper, is the part biological computing is furthest from matching: silicon can now state, per link, its error rate, its worst-case latency and its failure-time bound. No organoid system can state any of the three.
The bottom line
Established: a unified chiplet interconnect can multiplex timing-critical, loss-tolerant spike traffic with fully protected control traffic over a single link, with formally verified components and simulation evidence of 95% bandwidth utilization for the surrogate-gradient training workload, 32-nanosecond chiplet-to-chiplet round-trip event latency at 4-nanosecond physical delay, and order-day single-link failure bounds at a bit error rate of 1 in 10^10. Hypothesis, not established: that congestion-induced spike loss leaves learned computation intact on the full system, since no end-to-end accuracy-under-loss experiment is shown; that the placeholder broadcast router's replacement will preserve the latency figures; and that the order-minutes worst-case mesh-level failure bound is acceptable for real training campaigns. What would confirm the design is silicon: a multi-chiplet prototype with measured jitter and a learning workload run across it. What would break it is evidence that realistic spike-loss patterns degrade analog-network training on BrainScaleS-2 non-trivially, which the current evaluation is not built to detect.
Frequently asked questions
Why can't BrainScaleS-2 just be made as one big chip?
Because its compute elements are analog. Each BrainScaleS-2 die physically emulates up to 512 neurons and 131,072 synapses in continuous-time circuitry that cannot be time-multiplexed or paused, and analog circuitry does not benefit from newer process nodes the way digital logic does. Chiplets let the analog cores stay on a cheap mature process while a digital routing fabric in a 2D mesh connects many dies.
Why are spikes sent without error correction?
Because a spike carries no payload; its information is its arrival time. The design assumes a neuromorphic system should tolerate a small loss of spikes, as biological synapses are unreliable, so under congestion spikes are simply dropped and the arrival time on the receiving side is taken as the presynaptic time. Error correction, retransmission, and flow control are reserved for traffic that must be bit-perfect, like configuration data and processor messages.
What are the headline performance figures?
In simulation, the design sustains 95% link bandwidth utilization for a surrogate-gradient training workload across a wide range of traffic mixes at a bit error rate of 1 in 10^10. Round-trip event latency between two routing chiplets is 32 nanoseconds at a 4-nanosecond physical delay. The link runs 22 Gbit per second per direction, and the router plus protocol logic is estimated at about 0.17 square millimeters in 65 nanometer technology.
What are the known weaknesses?
Everything is validated in simulation with simplified link models, and the event router used is a placeholder broadcast design, with a real multicast router still to be built. The layer-wise reliability math is candid about scale: while a single link's failure bound is on the order of a day, a 16 by 16 mesh contains 960 links, pushing the worst-case system figure to order of minutes, accepted because losing some bandwidth is usually non-fatal.
How does this compare to other neuromorphic interconnects?
The paper's comparison table covers SpiNNaker-1's chip-to-chip link and spiNNlink, DYNAP-SE2, and two earlier BrainScaleS-2 interconnects. This design transmits only 22 bits per event, has a sub-100-nanosecond single-hop latency, and is the only one of the set to carry unsecured real-time event traffic and fully protected control traffic multiplexed over the same physical link.
What does a neuromorphic interconnect teach organoid computing?
That scaling living computation will mean interconnects, not bigger cultures, and that the field will need the same unglamorous decisions made here: unit labels, routing, and a split between spike traffic, which may be dropped because timing is its meaning, and control traffic, which must be protected. It also sets a competitive bar: silicon analog emulation now pairs 1,000-fold speed with a formally specified reliability contract that no tissue-based system can yet match.
References
- Heinemann and Schemmel. A Unified Interconnection Network for Chiplet-Based Scaling of the BrainScaleS Neuromorphic System. arXiv:2609.13563 [cs.AR]. 2026. https://arxiv.org/abs/2609.13563. Accessed 2026-10-15.