Skip to content
Talk to us

Healthcare

Makers of connected medical devices that run embedded Linux. They need software support that runs from a first diagnosis through to a versioned release.

Hardware
NXP i.MX8M · Boundary Devices module
The work
Long-term platform support

The work

Diagnosis and a versioned release

Audio and GPIO faults found, and Release 1.2.0 shipped

Case data

Industry
Healthcare, medical devices
Product line
A medical device on a Boundary Devices module
Scope
Error logging, library integration, audio debugging, GPIO configuration, versioned release
  1. Error logging

    We investigated how Linux captures and logs a fault, so the team can diagnose what the field reports.

  2. Application libraries

    We added the Linux libraries the application layer needed.

  3. Audio regression

    We isolated the cause of strange audio behaviour that a recent image had introduced.

  4. GPIO

    We configured the pins on the module, which enabled the hardware those lines carry.

  5. Release 1.2.0

    We built and shipped a stable, versioned update to the platform.

Connectivity, interface and application support

The same platform, grown over time

Case data

Industry
Healthcare, medical devices
Scope
Real-time clock and serial ports, Wi-Fi and USB OTG, image builds and testing, Qt interface packaging and releases, multimedia, Windows SDK
  1. Clock and serial ports

    We added RTC support and two more UART ports, for the peripherals the product had to reach.

  2. Wi-Fi and USB OTG

    We added both, which widened the network and peripheral options open to the device.

  3. Image builds

    We build and validate a series of images. After each one we test the Qt graphical effects and the audio.

  4. The on-device interface

    We package and release the HMI application. We integrated a C++ ORM library into a custom Yocto layer, for structured data on the device.

  5. Multimedia

    We added font, GIF and PNG rendering to the Qt interface, and we fixed GStreamer audio playback. The device has a startup tone.

  6. Windows SDK

    We prepared and documented one, so the customer's own engineers build against the platform themselves.

A camera platform, built from nothing

A second customer, a second hardware revision, and vulnerability tracking from the start

Case data

Industry
Healthcare, connected medical devices
Product line
A medical device with a camera, two hardware revisions
Silicon
NXP i.MX8M
Scope
Custom Yocto layer, graphics and camera integration, SDK, over-the-air updates, disk layout, vulnerability tracking, continuous integration
  1. The Yocto layer

    We reworked the custom layer the whole product builds from. It was the largest single piece of this engagement.

  2. Camera and interface

    We integrated Qt 6, and we found and fixed the crash in the camera path underneath it.

  3. Over-the-air updates

    We integrated UpdateHub and we tested it against the device.

  4. Vulnerability tracking

    We integrated CVE tracking into the build. On a medical device this is not something to add later.

  5. Continuous integration

    We set it up and we documented it, so the customer's own engineers run and understand the build. It was the second largest piece of work here.

  6. Production imaging

    We created the disk layout, and we debugged a failure in the vendor manufacturing tool that writes it.

  7. A second hardware revision

    We added support for it, on the same platform and the same build.

  8. SDK

    We integrated one, so the customer builds applications against the platform themselves.

Tell us what your product must do

Write one paragraph about the product, the silicon and the deadline. An engineer who does this work will read it and answer you.