FPGA Scrubber Architecture: Radiation Protection for Space Systems
Space radiation poses a serious threat to electronics, especially programmable logic devices like FPGAs. Single-event upsets (SEU) or functional interrupts (SEFI) can alter configurations or cause malfunctions, making scrubbers an essential part of spacecraft architecture—not just an optional add-on.
Physical Effects of Radiation in Semiconductors
Ionizing radiation in space triggers four main types of damage in microelectronics, each demanding tailored protection strategies.
Key radiation effects:
- SEU (Single Event Upset) — bit flip in memory from a charged particle
- SEFI (Single Event Functional Interrupt) — temporary glitch in control logic or state machines
- SEL (Single Event Latchup) — parasitic thyristor activation leading to overheating
- TID (Total Ionizing Dose) — cumulative oxide damage degrading device parameters
For SRAM- or Flash-based FPGA configuration memory, a single flipped bit can reroute signals or break logic. In low Earth orbit, heavy ion flux hits 1-10 particles/cm²/s, giving unprotected million-bit devices an SEU rate of about 10⁻⁵–10⁻⁶ per second.
How Configuration Scrubbers Work
A scrubber is a hardware or software module that continuously monitors and corrects FPGA configuration memory. Its core job: detect and fix errors before they pile up past the tipping point.
Typical readback scrubber cycle:
- Read the current configuration frame from the FPGA
- Compare it bit-by-bit against a golden reference in protected memory
- On mismatch, log the error address and rewrite the frame with reference data
- Move to the next frame and repeat
The key metric is scrub period, which must be shorter than the average time between SEUs. For a 50 Mbit config at 20 MHz, a full scrub cycle takes about 150 ms.
Scrubber Architecture Types
Implementation choices hinge on mission needs like radiation tolerance, size/weight limits, and budget.
By system placement:
- Internal scrubbers — IP cores inside the FPGA. Pros: fast response, easy integration. Cons: vulnerable to the same radiation as main logic, eats chip resources.
- External scrubbers — dedicated ICs. Pros: FPGA-independent, radiation-hardened. Cons: extra board components, slower operation.
- Hybrid setups — internal + external scrubbing. Maximizes fault tolerance with quick fixes and deep recovery.
By method:
- Blind scrubbing — rewrites all frames sequentially, no checks
- Readback scrubbing — reads, compares to reference, spot-corrects
- CRC-based checking — verifies config integrity via checksums
For space missions needing 99.9%+ uptime, external readback scrubbers shine: independent recovery without halting payloads.
External Scrubber Architecture: BSV7CBRH Example
The BSV7CBRH specialized IC acts as a smart bridge between config memory and FPGA, packing full radiation protection features.
Key features:
- Bitstream loading at system startup (cold boot)
- Continuous config monitoring in readback or blind modes
- SEU/SEFI detection and correction with status register logging
- Remote reconfiguration via UART/SPI
- Hardware write-protect against unauthorized overwrites
BSV7CBRH specs:
- Core voltage: 1.8 V ±5%
- Clock speed: up to 20 MHz
- Power draw: ~1 W (typical at 20 MHz, 125°C)
- Temp range: -55...+125 °C
- TID: 100 krad (Si) — about 5 years in LEO
- SEL threshold: ≥75 MeV·cm²/mg
- SEU threshold: ≥37 MeV·cm²/mg for scrubber config logic
Supported FPGAs:
- Native: BMTI series (BQVR, BQR2V, BQR5V, BQR7V, BQR7K)
- Compatible: Xilinx Virtex, Kintex-7, Virtex-7 (bitstream tweaks needed)
- Works with other FPGAs via parallel slave config interface
Key Design Considerations for Scrubbing Systems
Board layout:
- Keep traces between scrubber and FPGA under 5 cm
- Dedicated ground plane under CBGA for heat dissipation
Clocking:
- Dedicated 20 MHz source with <50 ps jitter
- Backup oscillator or external clock switchover
Memory redundancy:
- Golden bitstream in dual independent Flash cells
- CRC-check reference before use
Telemetry and diagnostics:
- SEU correction counters by address range to shared telemetry bus
- Scrubber status monitoring (IDLE/READ/COMPARE/WRITE)
- Error flags (CRC mismatch, timeout, write fail)
Comparison with Alternatives
Xilinx built-in SEM IP:
- Pros: minimal hardware
- Cons: SEFI vulnerability, poor legacy support
External controller IC:
- Pros: FPGA-independent, remote reconfig
- Cons: extra board parts
RAD5500 microcontroller:
- Pros: total independence, upgradable
- Cons: complex and pricey
For high-radiation environments (LEO/MEO), external scrubbers strike the best balance of reliability, performance, and cost.
Validation and Radiation Testing
Scrubber validation mimics space conditions through rigorous tests.
Core test types:
- TID testing — Co-60 gamma irradiation to 100 krad (Si) with real-time param checks
- SEL/SEU tests — heavy ions at particle accelerators
- Thermal cycling — 1000 cycles -55...+125 °C per MIL-STD-883
Analysis tools:
- SPENVIS (Space Environment Information System)
- OMERE (External Radiation Environment Modeling)
- CREME96 (Cosmic Ray Effects on Micro-Electronics)
Key Takeaways
- Configuration scrubbing is a must-have for space FPGA designs, not optional
- Scrubber choice fits mission needs: internal for moderate risks, external for critical ops
- Scrub period must beat average SEU intervals to avoid multi-error buildup
- Error telemetry yields vital data for radiation analysis and future hardware
- Full testing (TID, SEL, thermal) validates real-world radiation hardness
— Editorial Team
No comments yet.