Firmware / software engineering · process deck

Firmware / software process deck

From business analysis and requirements to design documents, implementation, virtual target testing, and real MCU/SoC integration.

Slide 1 of 7 14%

Slide 01 · Route

Firmware / software workflow

Business analysis → requirements → design description → protocols → implementation → virtual target tests → real target integration.

C/C++PythonMATLABSimulinkQEMURenodeDocker

Slide 02 · Analysis

Business analysis and requirements

We can start before the client has a complete specification. We clarify the goal, constraints, interfaces, risks, and expected behavior.

Business contextUse case, operating scenario, user/system value.

RequirementsFunctions, limits, timing, target constraints, acceptance criteria.

VariantsArchitecture options, toolchain options, implementation path.

Gate AScope is clear

The work starts from measurable requirements, not assumptions.

Slide 03 · Documentation

Design description

Documentation is the engineering contract for implementation, review, testing, and future porting.

ArchitectureComponents, states, data flow, error handling.

InterfacesSignals, messages, units, ranges, timing.

Testing basisAcceptance criteria, test cases, expected results.

ArtifactDesign description that can be reviewed by engineers and used for implementation.

Slide 04 · Documentation

Communication protocol and cooperation rules

We describe how modules communicate before code is written or generated.

ProtocolFrame format, fields, IDs, CRC, byte order, update rate.

CooperationProducer/consumer, acknowledgements, retries, faults.

TraceabilityRequirement → design item → code → test.

Gate BDocument → code

The reviewed document is the source for manual or AI-assisted implementation.

Slide 05 · Implementation

Implementation path

We select the fastest controlled route: write code manually, generate parts from documents, or use MATLAB/Simulink for portability and scaling.

C/C++ for embedded logic, drivers, protocol handling, and target integration.
Python for prototypes, tools, test scripts, data checks, and automation.
AI-assisted generation for scaffolds, parsers, serializers, tests, and adapters from reviewed documents.
MATLAB/Simulink for models, control logic, generated code, and easier adaptation across variants.

Document → Code / Model → Review

Slide 06 · Test

Virtual target integration

Before real hardware, we run integration and tests in reproducible environments.

DockerRepeatable toolchain, build, scripts, and demos.

QEMUBoard-level checks and early software integration.

RenodeMCU/SoC simulation, peripherals, and multi-node scenarios.

GoalFind interface and logic defects before real hardware becomes the bottleneck.

Slide 07 · Target

Real MCU / SoC integration and handover

After virtual fixes, we move to the real target and close the hardware-firmware loop.

Bring-upBuild, flash, debug, logging, diagnostics.

HW/FW testsProtocol, timing, stability, fault handling, regression.

HandoverCode, models, Docker setup, design docs, test evidence.

Gate CReady for client review

Result is runnable, documented, and testable.

Contact

Send a short firmware / software context

Useful inputs: business goal, target hardware, existing requirements, protocols, signal/interface tables, timing limits, models/code, logs, and expected behavior.

solution@contimech.org