Jump to content

What RidgeRun is Offering

From RidgeRun Developer Wiki


Follow us on: YouTube Twitter LinkedIn Email Share this page

Share This Page



What RidgeRun is Offering

RidgeRun provides a CIP-based Linux kernel support and maintenance path for Jetson AGX Xavier and Jetson Xavier NX. The work is based on a kernel baseline maintained by the Civil Infrastructure Platform (CIP).

The work covers more than getting the kernel to boot. It includes platform integration, subsystem validation, build procedures, and technical documentation so teams can evaluate the platform and understand its current state.

The sections below describe the main components of the work, the validation activities, the project artifacts, the scope boundaries, and possible additional engineering activities.

Solution Components

A kernel is only one part of a functional embedded platform.

For AGX Xavier and Xavier NX, evaluating a CIP-based kernel also requires checking platform-specific components and documenting which subsystems have been validated and which areas still require additional investigation.

For that reason, RidgeRun’s work combines several technical activities:

  • Xavier platform integration
  • BSP adaptation
  • Build and deployment procedures
  • Platform validation
  • Subsystem evaluation
  • Documentation of known limitations and observations

Together, these activities provide a documented view of the platform and its current status. They also give engineers a clear starting point for evaluating the baseline in their own environments.

Platform Evaluation and Validation

A significant part of the work is dedicated to understanding how the platform behaves on the selected kernel baseline. The evaluation is not limited to checking whether the system boots; it also covers core platform functionality, integration challenges, and subsystem status.

The validation process includes collecting evidence that engineering teams can review to understand the practical state and maturity of the different platform components.

Validation activities may include:

  • Boot verification
  • Runtime testing
  • Peripheral evaluation
  • Driver validation
  • Platform stability testing
  • Regression analysis

The resulting information helps engineering teams assess the platform, identify areas that require further work, and make decisions about future development or platform adoption.

Project Artifacts

The work may be accompanied by technical artifacts that help engineers understand and reproduce the integration.

Depending on the scope of the engagement, these artifacts may include:

  • Source repositories
  • Integration changes
  • Validation reports
  • Build procedures
  • Platform documentation
  • Subsystem status information

Together, these artifacts document how the platform was built, what was validated, and which limitations were identified. They can also serve as a reference for future platform maintenance, additional validation activities, and subsystem bring-up work.

Scope Boundary

This work focuses on maintaining Jetson AGX Xavier and Jetson Xavier NX platforms on a CIP-based kernel foundation.

It does not redesign existing products, replace all NVIDIA software components, or recreate the complete software environment from NVIDIA’s original platform releases.

Some platform capabilities still depend on NVIDIA firmware, userspace components, downstream drivers, or board-specific integrations. These dependencies remain part of the platform and are documented where they apply.

Defining these boundaries helps set realistic expectations about platform capabilities and the engineering work that may still be required.

Additional Engineering Activities

The maintained platform baseline can also serve as a starting point for additional engineering work when required by a project.

Depending on project requirements, this work may include:

  • Camera integration
  • Multimedia enablement
  • AI accelerator validation
  • Custom driver development
  • Board-specific adaptations
  • Product-specific testing

These activities are separate from the base platform evaluation. They can build on the same Xavier foundation and validation methodology, but their scope depends on the specific project requirements.




Cookies help us deliver our services. By using our services, you agree to our use of cookies.