Tinverse Linux Yocto

A controlled Yocto Linux platform for robotics.

Tinverse Linux Yocto packages board support, kernel policy, drivers, firmware, services, applications, and image configuration as reviewable layers and recipes. Teams keep a familiar BitBake integration surface while the shipped image and its evidence remain tied together.

Controlled customization

Adapt the image without losing configuration control.

Tinverse can tailor the machine support, vendor runtime, standard or real-time kernel, packages, services, security policy, and application integration for the product. The automated request interface exposes a bounded set of supported profiles; broader recipe, layer, and application changes are controlled engineering inputs. Tinverse validates every accepted combination before dispatching BitBake. The exact customization request is saved, hashed, and named in the signed release bundle alongside the image it produced.

Board and kernel

Choose a supported machine, device support, vendor stack, and standard or real-time kernel policy.

Recipes and services

Shape the installed packages, applications, services, users, networking, and production access policy.

Evidence profile

Make software inventory, licensing, vulnerability review, and release-signing expectations part of the build request.

Embedded Linux composition

Make the board and image choices explicit.

Machine

Select one board profile.

The machine configuration binds device tree, boot files, kernel fragments, drivers, firmware, and board identity to the intended target.

Image

Compose the required runtime.

Recipes and image features select packages, services, security policy, application payloads, and standard or real-time behavior.

Evidence

Retain the BitBake release outputs.

Package and license manifests, software inventories, vulnerability reports, build history, image hashes, and verification records follow the image.

Build entry point

A controlled wrapper invokes the selected kas configuration. The filename keeps the board and real-time choice visible before the build begins.

tools/env/build_yocto_image.sh \
  --kas yocto/kas/tinverse-agx-orin-devkit-rt.yml \
  --build-name agx-rt

Board-specific images

Machine configurations keep hardware support and image composition tied to the selected board.

Standard and real-time variants

Image configurations select the applicable kernel policy without hiding the target or release-specific validation.

Yocto evidence workflow

BitBake outputs support package, license, software-inventory, vulnerability, build-history, and release reviews.

FDA submission support

Evidence for the Linux platform in your device.

For a production release, Tinverse supplies the platform records an integrating medical-device team needs to identify, assess, and verify the Yocto image used in its product. Production release assembly fails if the required software inventory, licensing, vulnerability output, reviewed disposition, build history, target results, or known-anomalies review is missing.

Identity

Show exactly what was delivered.

Retained customization request, source revision, pinned layers and KAS configuration, machine profile, vendor version, image hash, and signed release manifest.

Software

Account for the image contents.

Exact image package manifest, SPDX SBOM output, license manifest, build history, and the applicable vendor and SOUP records.

Assurance

Support risk and verification review.

CVE output, reviewed vulnerability disposition, lifecycle and traceability records, known platform anomalies, build records, and release-specific boot, driver, service, security, recovery, and timing results.

These records support the Linux platform portion of a submission. The finished-device manufacturer remains responsible for device classification, hazards, system validation, clinical claims, and the final FDA submission.

Target programs

Board profiles for embedded and accelerated robotics.

Current configurations cover BeagleBone Black, Jetson AGX Orin, and Jetson AGX Thor program paths. Production release still depends on the exact board, image, driver, boot, and timing evidence required by the product.

Contact engineering@tinverse.com.