Board support packages
Bootloader, kernel configuration, device tree and root filesystem for your board.
Discuss thisFirmware & EmbeddedEmbedded Linux and RTOS
Embedded Linux and RTOS
built on a platform you can maintain.
Embedded Linux and RTOS work lives or dies on the board support layer. We bring up the bootloader, kernel, drivers and root filesystem against your actual board, so the system behaves predictably from first boot rather than only on reference hardware.
- BSP & kernel bring-up
- Device drivers
- Boot & root filesystem
Why Linux projects stallA distribution is not
A distribution is not
a working product.
Most embedded Linux difficulty sits in the layer nobody budgets for: a driver that misses a hardware quirk, a bootloader that assumes a partition layout the board does not have, or a filesystem that fills because nothing prunes logs. These appear only on real hardware, in the enclosure, at temperature.
We do the bring-up against your board and your constraints — storage, memory, update mechanism and power states — and document what was changed, so the system stays maintainable by someone who did not build it.
Reproducibility matters. The toolchain, kernel configuration and root filesystem are captured as buildable artefacts, so the image can be regenerated rather than patched on one machine.
- 01Brought up on your board
Bootloader, kernel and drivers verified on the actual hardware, not a reference platform.
- 02Drivers matched to hardware
Peripheral and bus drivers written against your schematic and pin assignment.
- 03Reproducible builds
Toolchain, kernel config and filesystem captured so images can be regenerated.
- 04Update path designed
Recovery and over-the-air update paths designed in, so a failed update is recoverable.
- Real hardwareBring-up completed on your board, so hardware quirks surface before the product ships.
- Documented BSPEvery board-specific change recorded, so the platform can be maintained later.
- Reproducible imageToolchain and configuration captured as buildable artefacts rather than one-off setup.
- Update & recoveryRecovery paths designed alongside the image, not bolted on afterwards.
What we deliver
Embedded Linux and RTOS services
Engagements cover a full platform bring-up, a specific layer such as drivers, or ongoing platform maintenance.
Kernel & driver development
Kernel configuration, out-of-tree drivers and hardware enablement.
Discuss thisDevice driver development
Drivers for the buses, sensors, storage, display and network devices you use.
Discuss thisBootloader development
U-Boot and equivalent bootloader work, including secure boot and recovery.
Discuss thisRoot filesystem & images
Minimal, reproducible filesystem images with the right services and update mechanism.
Discuss thisSystem integration
Display, network, storage, power management and application services integrated and tested.
Discuss thisWhat is included in scope
Scope is agreed in writing before work starts, so deliverables and responsibilities are clear.
- Platform & requirementsProcessor, kernel version, storage, memory, networking and update requirements agreed.
- Bootloader bring-upBootloader configured and verified against the board’s memory and storage layout.
- Kernel & driversKernel configuration, device tree and drivers developed and tested on hardware.
- Root filesystemMinimal filesystem built with required services, monitoring and update support.
- Integration & optimisationDisplay, network, power management and services integrated; boot time and memory tuned.
- Handover & reproducibilityBuild scripts, toolchain pinning and documentation delivered for ongoing maintenance.
Capabilities
Embedded Linux and RTOS capability
Platform work is judged by whether someone else can rebuild and extend it, so documentation and reproducibility are treated as deliverables.
Board support packages
Complete BSP including bootloader, device tree, kernel config and filesystem.
Kernel configuration
Kernel options, drivers and performance settings tuned for the target board.
Device drivers
Bus, storage, display, network and sensor drivers for the hardware you use.
Bootloaders & secure boot
Boot configuration, signature verification, anti-rollback and recovery.
Real-time & RTOS
FreeRTOS, Zephyr and equivalent kernels with task design and timing analysis.
Root filesystem
Minimal, reproducible images with only the services the product needs.
Power management
Suspend, sleep and wake behaviour implemented and current draw measured.
Build & maintenance
Reproducible build system, toolchain pinning and documented platform maintenance.
Microcontroller firmware is covered in firmware development, and user-space applications in Linux applications.
Our process
How a platform bring-up runs
Platform selection, bootloader, kernel and drivers, then a reproducible image and handover.
Platform selection
Processor, kernel, distribution approach, storage and update mechanism agreed.
Platform planBootloader & kernel
Bootloader configured, kernel built and the board brought to a first boot.
First bootDrivers & filesystem
Device drivers enabled and a minimal root filesystem with required services built.
Working platformOptimise & hand over
Boot time, memory and power tuned, then build scripts and documentation delivered.
Maintained platform
Technologies
Platforms and technologies
Kernel and distribution choices follow the product’s constraints and your team’s ability to maintain it.
- Linux kernelMainline and vendor kernel work, configuration and out-of-tree drivers
- BootloadersU-Boot and equivalent boot configuration, secure boot and recovery
- BSP toolingDevice tree, Yocto and Buildroot style build systems for reproducible images
- Device driversI2C, SPI, storage, display, network, input and sensor drivers
- RTOSFreeRTOS, Zephyr and equivalent kernels for real-time requirements
- Power & boot timeSuspend states, wake sources, boot time and memory footprint optimisation
A distribution that is powerful but unfamiliar to your team is an expensive choice. We factor ongoing maintenance capability into the recommendation, not just the feature list.
Industries
Firmware that fits your industry’s constraints.
Safety, connectivity and lifecycle expectations differ by sector, and they shape the architecture from the start.
Industrial
Control panels, motor drives, gateways and automation hardware for continuous operation.
IndustrialAutomotive
In-cabin electronics, LED drivers and control units designed around automotive electrical and thermal expectations.
AutomotiveEnergy & power
Monitoring, metering, conversion and control electronics for energy and power systems.
Energy & powerHealthcare
Diagnostic and monitoring devices designed with patient safety and compliance in mind.
HealthcareRailways
Onboard and signalling electronics built for vibration, temperature cycling and long maintenance cycles.
RailwaysDefence
Rugged, secure and mission-critical systems with controlled supply and documentation.
DefenceCapability examplesSee the engineering problem.
See the engineering problem.
Imagine the possibilities.
The scenarios below illustrate the kind of work we do — they are not published client case studies or measured results. Ask us about relevant experience for your product.
Illustrative · Industrial gateway
A new board brought up from scratch
Challenge: A processor board needed drivers, filesystem and services to reach a usable state.
Approach: Bootloader, kernel and drivers brought up on hardware, with a minimal reproducible image delivered.
Explore connectivityIllustrative · Secure device
A product needing secure boot and updates
Challenge: Field updates risked leaving units unbootable if interrupted.
Approach: Bootloader signature verification, dual images and rollback designed and tested through failed updates.
Explore embedded securityIllustrative · Battery device
A handheld with a tight power budget
Challenge: Active current and boot time were higher than the design allowed.
Approach: Suspend states, clock gating and boot time measured then tuned against the requirement.
Explore battery technologyFrequently asked questionsGood questions.
Good questions.
Clear starting points.
What buyers usually want to know before scoping this kind of work.
Ask about your requirements →What embedded Linux and RTOS services do you offer?
Board support packages, kernel configuration, device driver development, bootloader work, root filesystem and image creation, system integration, and platform maintenance.
Do you work with Yocto or Buildroot?
Both. The build system is selected to match your team’s capability and the reproducibility you need, rather than imposed as a default.
Can you bring up a board that has never run Linux?
Yes. Bootloader, kernel, device tree and drivers are developed against your schematic and verified on the actual hardware, which is where hardware-specific problems are actually found.
How do you ensure the image can be rebuilt?
Toolchain versions, kernel configuration and filesystem definition are captured as build scripts and pinned versions, so the image can be regenerated rather than only patched.
Do you help with power management?
Yes. Suspend and sleep states, wake sources, clock gating and current draw are implemented and measured against the product’s power budget.
Can you take over an existing platform?
Yes. We can review an existing BSP for driver quality, build reproducibility, boot time, update safety and maintainability, then prioritise the changes needed.
Related services
Firmware & Embedded
Explore the rest of the programme, or get in touch about this service directly.
Start your projectLet’s get your Linux platform
Let’s get your Linux platform
booting and maintainable.
Tell us about the processor, the board, what the product must do and how it will be updated. We will recommend a platform approach and a bring-up plan.
No complete specification needed. A short brief of your product and goals is enough to start.
What happens next?
- Share your product goal, application and current stage.
- Discuss the components, interfaces and constraints that matter.
- Agree a practical next step and the scope for a proposal.