Obeita

Custom embedded hardware and software development

Obeita develops embedded hardware, firmware and connected-device software for equipment manufacturers and integrators. Bring a new product requirement, an existing board or a device that needs a network connection. We define the engineering scope, implement the agreed design and test the hardware and software against your requirements.

Discuss your device and interfaces

Choose the work your product needs

Device connectivity and wireless integration

Connect serial and RS485 equipment, adapt protocols, or scope a BLE or Wi-Fi application. Device roles, data flow and recovery behavior guide the hardware and firmware work.

Explore connectivity

Embedded Linux, BSP and STM32 firmware

Bring up a board, adapt drivers or investigate boot and stability faults. Linux/BSP and MCU work have separate implementation and acceptance requirements.

Explore diagnostics

Custom IoT and Modbus gateways

Develop the interface and software path between field equipment and its host system. Compare gateway architectures, then validate the selected configuration on actual devices.

View gateway projects

From requirements to a tested delivery

  1. Define the scope. Review the product function, interfaces, current hardware and software, operating conditions and acceptance criteria. A diagnostic task or pilot can resolve uncertain parts first.
  2. Agree the implementation. Set the hardware, firmware and application boundaries in the contract, including any existing design or third-party dependencies.
  3. Design and verify. Complete the agreed hardware and software work, reproduce issues and test the selected configuration on physical equipment.
  4. Hand over the agreed deliverables. Specify boards, firmware or software builds, configuration notes and test records. Source code, design files, manufacturing support and ongoing maintenance are defined per project.

Representative delivered projects

Explore the engineering decisions behind a custom RK3566 terminal, an A133 touch terminal, a STM32 data-acquisition device, a multi-interface IoT gateway and a QCM6490 cellular edge platform. Each illustrates a different hardware and software boundary.

Our 16 anonymized case studies describe completed customer projects: requirements, contract agreement, hardware and software design, physical testing and delivery. The tested deliveries met the customers’ agreed requirements. Optional configurations and new-project performance need their own validation.

What to send for project scoping

Share the product goal, board or device model, interface documents, existing source availability, operating environment, expected quantity and target schedule. Include the behavior you need to verify. Certification, enclosure, production and support requirements should be identified before they become delivery commitments.

Tell us about your project