Custom system integration
Embedded Redesign
Board Support Package for System Houses
Embedded expertise backed by experience
Every industry has its own unique requirements: In medical technology, the focus is on transparent, stable system behavior; in measurement and testing technology, on reproducible data acquisition; and in transportation and environmental technology, above all on robustness in field operations. Through our experience with many successfully completed projects, we understand these differences—and know what matters most when it comes to integration, stabilization, and maintainability in day-to-day operations.
Embedded systems must operate reliably over the long term and provide clearly defined system states and predictable behavior. From a technical standpoint, this involves robust peripheral integration, deterministic data acquisition, and safe state transitions, including recovery strategies. Maintenance and updates must remain predictable—especially for mature platforms.
- Cancer Research and Tumor Therapy
- Incubators for newborns
- Infrastructure for reading pacemakers
- ECG machine (study)
- Med-Panel for emergency responders
- Panel for in-vehicle emergency medicine
- Breathalyzer
- Electronic magnifier for the visually impaired
- Dialysis technology
- Scaling/rotation of image content on high-resolution patient monitors
Imaging systems feature high data rates and are timing-sensitive: Success depends on a stable data path from the sensor to processing (buffering, format handling, synchronization). Common bottlenecks include drop-frame prevention, reproducible initialization (start/stop/recovery), and consistent image quality. The system must remain stable even under load and deliver defined image data for analysis.
- Optical measurement analysis
- Camera system for drones
- Camera system for satellites
- Numerous camera drivers for various image sensors
Since access and maintenance may be limited during operation, embedded systems must be particularly robust in the event of failures and easy to diagnose. From a technical standpoint, this requires stable data paths, predictable timing behavior, and defined recovery strategies. Resources are often strictly allocated, so efficient processing and seamless system integration are essential.
- Camera Systems for military vehicles for Environmental Monitoring
- Fogging System for Emergency Vehicles (ROSY)
- Drones
- Med-Panel for Emergency Personnel
- Camera System for Satellites
Embedded systems often form the core of measurement data acquisition, control, and data transmission in continuous operation. Robust sensor and I/O paths, stable communication, and well-defined state machines for operation and recovery are critical. Because devices remain in the field for many years, maintainability, updatability, and predictable behavior under environmental conditions are particularly important.
- Data loggers for heat meters (residential sector)
- Monitoring of wind turbines
- Water quality measurement technology
- Wireless transmission/collection of data for optimization in combined heat and power plants
Here, embedded software serves as the foundation for reproducible data acquisition and precise time references. Typical requirements include deterministic timing (triggering/sampling), stable driver paths, and performance under load. Diagnostic capabilities (logging, measurement points, error states) are crucial for reliably validating measurement chains in the field.
- Optical measurement analysis
- Magnetic field meter
- Gas leak detector
- Gap measurement device
- Spectrum analyzer
- Breathalyzer
- High-voltage tester
- Distance measurement/positioning
- Data concentrator for RFID applications
- Specialized/precision scales
- Tire tread depth gauge
- Electrical safety testing equipment
Systems are often subjected to extreme cycles (power cycles, temperature, vibration). Robust boot, resume, and reconnect paths, stable communication, and reliable HMI/display chains are essential. Updates and enhancements must be possible without causing any adverse effects, ensuring long-term operational stability.
- Smart vehicle displays (e.g., trucks, construction vehicles)
- Rearview camera with display in the mirror
- Access control system
- Onboard computer for local public transit
- Distance measurement/positioning
Harsh environments meet sensor and actuator technology and mobile power supply. Embedded integration requires robust I/O paths, reliable restart behavior, and stable state logic. Deterministic timing for actuators and robust communication/localization can be critical, depending on the device.
Equipment often runs continuously and must remain stable despite load changes and malfunctions. Robust HMI/control interfaces, reliable sensors, and deterministic control logic are essential. A well-defined state model with error and recovery behavior reduces maintenance costs and downtime.
What matters here is smooth usability, stable connectivity, and reliable media/sensor paths. From a technical standpoint, UI latency, robust wireless connections, and clean state management (start/stop/resume) are often critical. The interaction must function consistently even in changing environments.
- Multimedia system for yachts
- Tracking system for ski routes
- Component of a gaming computer
- Software for slot machines
Here, embedded software is key to ensuring responsive event processing and reliable peripheral connectivity (readers, sensors, actuators). Stable interfaces (e.g., I2C/SPI/USB), deterministic event handling, and robust error handling (reconnect, timeout, power interruption) are critical. Safety requirements are implemented in accordance with current standards.
- Building Automation Control Panels and Accessories
- Door/Access Control Systems
- 3D Fingerprint Scanners
Embedded components are closely integrated with machine operations and user interfaces. Key requirements include robust HMI/touch integration, reliable communication with controllers, and defined responses to failures and reconnections. Long service life and maintainable integration are essential, as systems are used for many years.
Cross-industry embedded projects must operate reliably, integrate diverse hardware seamlessly, and be scalable within established platforms. From a technical standpoint, this often involves stable interfaces, seamless driver integration, predictable updates, and a software foundation that can be flexibly adapted to various devices and use cases.
The Quick Check for Your Initial Consultation
Integration risks vary significantly depending on the industry: real-time performance, the variety of interfaces, image processing, wireless stability, lifecycle considerations, or robust user interfaces. With the Quick Check, you can let us know the key technical priorities for your project. This allows us to communicate more precisely with you during our initial consultation and find solutions efficiently.
Selected Projects in Detail
The following examples illustrate typical approaches from our embedded system integration work: stable platforms as a foundation, low-level driver and interface development, and robust data paths all the way to the application. Through all our embedded projects, we have gained in-depth expertise, allowing you to benefit from our practical experience. If your specific field of application isn’t listed here, please contact us anyway—many core technical components are cross-industry, and feasibility as well as integration risks can be clearly addressed during an initial consultation.
INFICON – Complete Linux BSP for Leak Detector Platform on i.MX8MP
Initial Situation
An embedded Linux platform was to be developed as a stable foundation for a new generation of leak detection devices—tailored to a SMARC module on a custom carrier board.
Task
Development of a complete Linux BSP as the platform foundation for use in the new leak detector (successor model).
Implementation
SIGMA developed the complete Linux BSP for i.MX8MP (SMARC) on the customer-specific baseboard, thereby creating the technical foundation for further system integration and application development in the target device.
Result
The customer describes the collaboration as high-quality, efficient, and reliable in terms of deadlines, and envisions further joint projects in the future.
Operating system: Linux
Processor/SoC: NXP i.MX8MP
Form factor: SMARC module on a custom carrier board
SIGMA contribution: Complete Linux BSP
TQ-Systems – MIPI connection of Vision-Components camera modules to the i.MX8M
Background
For standard and custom products, camera modules from Vision Components needed to be reliably connected to the MIPI interface of an i.MX8M hardware platform.
Task
Integration of the camera modules (OV9281 and IMX327 sensors) into the i.MX8M platform, including development of the necessary drivers for the MIPI connection.
Implementation
SIGMA developed the required MIPI driver for the TQ i.MX8M hardware and integrated the camera modules so that they can be used reliably in the intended products.
Result
The customer highlights the professional and prompt execution of the project.
- Operating system: Linux
- Processor/SoC: i.MX8M
- Interface: MIPI (camera modules)
- Sensors: OV9281 (OmniVision), IMX327 (Sony)
- SIGMA's contribution: MIPI drivers and integration for the target platform
Berlin Space Technologies – High-Performance Embedded Software for Nanosatellites
Background
The goal was to develop a system for use in space that would enable image capture, data processing, and transmission within a small satellite in low Earth orbit.
Task
Development of key software components for a high-performance embedded system to serve as the foundation for processing and transmitting image data captured in orbit.
Implementation
On behalf of BST, SIGMA developed key software components for an embedded system featuring a quad-core processor and an attached SSD, designed for image capture and data processing during satellite operations.
Result
According to the client, a reliable solution was created for transmitting and processing images captured in space.
- System Type: High-performance embedded system
- Compute: Quad-core processor
- Storage: Connected SSD
- Use Case: Image acquisition + data processing in a small satellite
- SIGMA's Contribution: Key components of the embedded software
Cross-sectoral elements
Many embedded projects vary across industries, but they share similar technical components. In system integration, the focus is less on “individual features” and more on stable data paths, clean interfaces, and reproducible behavior in the target device—even under load, after updates, or when peripherals change. These project components are particularly common across industries:
HMI / Control & Display UnitsDisplay / Touch
Camera & Sensorsvisible / IR
Communication & InterfacesFieldbus / Serial / Ethernet
Data Converters & Data CollectorsGateway / Controller
No. The industries listed reflect selected project experience and typical areas of application. In embedded projects, the industry itself is usually less important than the technical requirements, such as sensor integration, HMI development, driver integration, communication interfaces, platform migration, or redesign. For this reason, much of our experience can also be applied to related or new areas of application. No. The industries listed represent selected project experiences and typical application areas. In embedded projects, the industry itself is usually less important than the technical task at hand, such as sensor integration, HMI development, driver integration, communication interfaces, platform migration, or redesign. For this reason, much of our experience can also be applied to related or new application areas.
Yes. We also familiarize ourselves with new industry contexts if the technical foundation aligns with our areas of expertise. This includes, in particular, embedded Linux, BSPs, drivers, HMIs, interface integration, system migration, and the further development of existing embedded systems. What matters most to us is the functionality, constraints, and integration requirements of your device.
No. In practice, technical transferability is more important than an exact match in industry. For example, if a project has similar requirements regarding image processing, display connectivity, field interfaces, updateability, or system stability, existing project experience is often highly applicable—even if the target product comes from a different market sector.
Yes. A large portion of our projects don’t start from scratch, but rather within established systems. We provide support in analyzing existing hardware and software, troubleshooting field issues, resolving integration problems, managing platform migrations, and further developing existing devices. We step in exactly where your project currently stands.
Both. We provide support for clearly defined tasks such as driver development, BSP adaptation, HMI integration, and debugging, as well as for more comprehensive projects involving architecture, implementation, stabilization, and handover. The scope of the project is tailored to your needs, your team setup, and the current state of the system.
Yes. We don’t necessarily start from scratch; instead, we continue to work with existing BSPs, Linux environments, hardware platforms, and already integrated components. If an existing foundation is technically sound, we build upon it. If it poses a structural obstacle, we assist with targeted revisions or a sensible migration path.
Yes. This applies, for example, to component end-of-life announcements, outdated operating systems, lack of maintainability, new hardware platforms, or changes in performance and interface requirements. The goal here is not necessarily a complete overhaul, but rather a technically sound solution that carefully balances cost, risk, and future-proofing.
Yes. In many projects, it is not entirely clear at the outset whether the root cause lies in the hardware, drivers, timing, interfaces, configuration, or system architecture. This is precisely why a structured technical analysis is so important. We help narrow down potential causes, identify dependencies, and determine the next logical steps with confidence.
Yes. We provide support for both early development phases and existing production devices. Depending on the specific situation, this may involve bring-up, integration, and architectural considerations, or stability, maintainability, updateability, and further development during the ongoing product lifecycle.
It is helpful to have information about the target platform, the current software version, the components used, interfaces, existing issues or requirements, as well as timelines and the project context. Even if not everything has been fully documented yet, this information usually provides a good basis for assessing where to start and what kind of technical support is appropriate.
We will be happy to present solutions for your industry and your processes. Talk to the specialists for SMEs.
request now
