PlatformsFaststream SiliconFaststream RadioFaststream VisionConnected EdgeFaststream SecureMobility & Rail
ProductsSemiconductor IPIP CoresWireless & RANEdge & GatewaysTracking & IdentificationSoftware & FrameworksConnected Systems
Technology5G protocol stackWireless and RF architectureBaseband and low PHYForward error correctionControl and data planeHigh-speed interfacesFirmware and bootSilicon root of trustSoftware-defined vehicleAutomotive OTAFunctional safety
AIAI Engineering ServicesEdge AI & Embedded MLComputer Vision EngineeringSensor Fusion & PerceptionAI Silicon & AccelerationMLOps for DevicesAI Visual InspectionPredictive MaintenanceDriver MonitoringVideo Analytics & Safety
SolutionsSemiconductorIndustrial AIConnected ProductsAsset TrackingMHE Tracking & UtilizationBluetooth AoA RTLSWearable TrackingAutomotive & MobilitySmart InfrastructureSecure IdentityWireless & SatelliteNTN Asset TrackingPrivate 5GSmart WashroomsFuel ManagementSmart BuildingsWorker SafetyEnergy MonitoringSmart AgricultureSmart CityAutonomous PlatformsAssembly AutomationLiDAR Rail SafetyHardware Wallet
IndustriesSemiconductorTelecommunicationsIndustrial & ManufacturingAutomotive & MobilityTransportation & RailAerospace & DefenceHealthcare & MedicalEnergy & UtilitiesOil & GasRetailConsumer ElectronicsMedia & EntertainmentSmart Infrastructure & IoT
ServicesSystem Integration overviewASIC & SoC DesignRTL to GDSIIVerification methodologyDFT and silicon testLow-power designMixed-signal integrationDesign enablementFPGA DesignFPGA-to-ASIC ConversionAnalog, Mixed-Signal & RFHardware & High-Speed PCBEmbedded SoftwareCloud, OTA & Device ManagementManufacturing TransitionHow we engage
CompanyAbout FaststreamEngineering ExcellenceLeadership & OrganisationHow We EngageQuality & ComplianceStandards & EcosystemPartners & EcosystemTrust CentreLocations & DeliveryNewsroom & MediaCareersCase StudiesKnowledge CenterWhite PapersGlossaryNewsletterResources & Support
ContactStart a projectHow we engage
Talk to us
HOW WE WORK

Engineering Process & Toolchain

A result you cannot reproduce is not a result — and an engineering team is only as trustworthy as the trail it leaves. Faststream runs silicon, firmware and systems work on one disciplined toolchain: everything in version control, every change reviewed, continuous integration that runs the regressions, and a trace from requirement to test that is a byproduct of how the work is run, not a document assembled at the end.

EDA & PCB toolsGit version controlCI/CDAutomated regressionTraceabilityHardware-in-the-loop
ShareLinkedIn
One loop, run on every change: commit to version control, reviewed, built and regressed by continuous integration, validated against real hardware, and released as a reproducible, traceable artifact — with failing regressions routed straight back to the author.
regression fails → back to authorCOMMITREVIEWmerge requestINTEGRATEbuild + regressionVALIDATEhardware-in-the-loopv1.0RELEASEtraceable artifact
PROCESS

How the work is actually run.

01

Requirements and traceability

Every work item is linked to the requirement it satisfies and the test that will prove it, in the issue tracker. Traceability from specification to signed-off test is continuous — a property of how the work is tracked, not a spreadsheet reconstructed before an audit.

02

Version control for everything

RTL, firmware, scripts, constraints, test benches and documentation live in Git. Nothing reaches a build outside the repository, and history is the single source of truth for what changed, when and why.

03

Peer review as a gate

No change merges without a reviewed merge request — read by an engineer who did not write it. Review is the cheapest place to remove a defect, and the gate is not optional because that is the point of a gate.

04

Continuous integration

Every push triggers an automated build. Nightly regressions run the suite against the coverage and test plan, so a break is found in hours against a specific change, not discovered at a milestone when the cause is buried.

05

Automated test and regression

Unit, integration and system tests run without anyone remembering to launch them. Results are tracked over time so a slow regression in coverage or performance is visible as a trend, not a surprise.

06

Hardware-in-the-loop

Firmware and system software are exercised against real target hardware or an emulated model, with instruments and stimulus automated. The bug that only appears on the real device is the one worth catching before release.

07

Release and handover

A tagged, reproducible build shipped with its test evidence and traceability. Handover is a deliverable with a trail behind it — not a drop of files and a hope that the environment can be recreated later.

TOOLCHAIN

The tools the work runs on.

Three stacks, one discipline. The hardware design flow is vendor-current and multi-foundry. The development stack spans the languages, operating systems and frameworks the product needs. The software-and-process toolchain wraps all of it in version control, automation, test and traceability. We work in your house stack where you have one; where we bring our own, these are the standards we run.

Hardware design & EDA tools

Hardware design and EDA tools
StageTools we work in
Synthesis & place-and-routeCadence Genus & Innovus · Synopsys Fusion Compiler
Timing & equivalence signoffSynopsys PrimeTime & Formality
Custom, analog & AMSCadence Virtuoso, Spectre & Spectre AMS · Synopsys CustomSim (FastSPICE)
Functional & AMS simulationSynopsys VCS / VCS-AMS · Siemens Questa
Physical verificationSiemens Calibre — DRC / LVS / PEX
Power, EM-IR & RF/EMAnsys RedHawk-SC & Totem · Cadence Voltus · Ansys HFSS
DFT & testSiemens Tessent — scan, ATPG, MBIST
PCB, lab & benchHigh-speed PCB layout with SI/PI · automated bench: oscilloscopes, logic & protocol analysers, VNA, SMU, ATE

Development stack

Development stack
AreaWhat we work in
LanguagesC / C++ · Python · SystemVerilog / VHDL · Rust · Tcl · MATLAB & Simulink
Embedded OS & RTOSEmbedded Linux (Yocto / Buildroot) · FreeRTOS · Zephyr · QNX · bare-metal
Frameworks & middlewareAUTOSAR · ROS 2 · BSP / HAL · gRPC / Protobuf · MQTT · device SDKs
Edge AI / MLPyTorch · TensorFlow Lite · ONNX · TVM — quantised for on-device inference
Hardware–software co-designPartitioning, HW/SW interface contracts, co-simulation and co-verification
Compilers & toolchainsGCC / LLVM, cross-toolchains, custom backends and intrinsics, SDK / BSP toolchains
Kernel & driversLinux kernel, device drivers, board bring-up, mainline upstreaming

Software & process toolchain — yours or ours

Software and process toolchain
LayerWhat it doesHow we work
Version controlGit repositories, protected branches, reviewed merge requests, full historyGitHub, GitLab, Bitbucket or Azure Repos — yours or ours
CI / CDAutomated builds on every change; nightly HDL & software regressions; artifactsJenkins, GitLab CI, GitHub Actions or Azure DevOps
Issue tracking & AgileBacklog, sprints or phase-gates, requirement-to-task-to-test linksJira, Azure Boards or GitLab — your cadence
Test & verificationUnit, integration and system tests; coverage measurement; HDL verificationpytest, GoogleTest, Unity / Ceedling, Robot Framework, cocotb, UVM
Static analysis & qualityDefect, security and coding-standard analysis in the pipelineCoverity, clang-tidy, MISRA C/C++, SAST
Containers & reproducibilityVersioned, signed artifacts in reproducible build environmentsDocker & Kubernetes; environments recreated, not guessed
Standards & traceabilityRequirement-to-test traceability for safety and regulated programmesAligned to ISO 26262, DO-178C or IEC 62304 as the programme needs
THE UNCOMFORTABLE PART

Process is only real if it survives a deadline.

A toolchain abandoned the week before tape-out or release was never a process, only a slide. The discipline that counts is the one that holds when the schedule is tight: the change still reviewed, the regression still run, the traceability link still made.

Which is why Faststream automates the discipline wherever possible, so it does not depend on anyone remembering it under pressure. A gate a human can quietly skip at 2am is not a control. A pipeline that refuses to merge an unreviewed, un-regressed change is.

WHERE THIS APPLIES

Industries this serves.

COMMON QUESTIONS

What engineers ask about this.

01

Do you work in our toolchain or yours?

Either. Most customers want the work delivered into their own Git repositories, CI and issue tracker so it is theirs from day one. Where there is no existing stack, we stand up a Git-based pipeline, issue tracking and regression automation and hand it over documented.

02

How is requirements traceability maintained?

Every work item is linked to the requirement it satisfies and the test that proves it, inside the issue tracker, so a trace from specification to signed-off test exists continuously rather than being reconstructed for an audit or a safety case.

03

What does hardware-in-the-loop cover?

Firmware and system software exercised against real target hardware or an emulated model, with instruments and stimulus automated, so behaviour that only appears on the real device is caught before release rather than in the field.

KEEP READING

Related work.

BUILD WITH FASTSTREAM

Bring us the difficult part.

Tell us the specification, the constraint and the deadline. Programmes that cross silicon, radio, embedded and AI are where Faststream is strongest.