Generated banner for Jetson Init Image
Generated logo for Jetson Init Image

Jetson Init Image

NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • Medium risk

From the author

Extract Jetson Linux + sample-rootfs tarballs and run apply_binaries.sh for the active target, then record bsp_image in the profile. Use after jetson-init-target; not for source-tree setup.
— the description by Jetson Team

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill automates the setup of the Jetson Board Support Package (BSP) environment. It extracts the Jetson Linux and sample-rootfs tarballs, executes the necessary binary application scripts, and updates the active target profile with the BSP image metadata. It intelligently detects the required GPU stack (nvgpu or OpenRM) based on the target hardware and ensures the environment is correctly configured for subsequent development steps.

What it does

  • Locates and validates Jetson Linux and sample-rootfs tarballs on the local filesystem.
  • Extracts BSP components into the designated workspace directory.
  • Applies binaries using the appropriate GPU stack flag based on the target SoC generation.
  • Records the BSP version and root path in the active target profile.
  • Verifies existing installations to prevent accidental overwrites.
  • Ensures the environment is ready for source tree initialization.

When to use it

  • When setting up a new Jetson development workspace after defining the target platform.
  • When a downstream process reports a missing Linux_for_Tegra directory.
  • When the active profile lacks the required bsp_image configuration block.
  • When you need to ensure the correct GPU driver stack is applied for your specific Jetson module.

Advantages

  • Automates complex manual extraction and configuration steps.
  • Prevents configuration errors by automatically selecting the correct GPU stack.
  • Maintains consistency by updating the project profile with verified metadata.
  • Safeguards existing installations by requiring explicit confirmation for overwrites.

Usage examples

“Initialize the BSP image for my current target.”
The agent identifies the target, locates the required tarballs, extracts them, applies the correct GPU binaries, and updates the profile with the BSP version.
“Set up the Jetson Linux environment in /opt/jetson/bsp.”
The agent validates the path, performs the extraction and binary application, and records the custom root path in the active profile.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/nvidia/jetson-init-image/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip jetson-init-image.zip -d .agents/skills

Documentation by Jetson Team

Initialize BSP Image

Output is only bsp_image: in the active profile: derived version plus root_path only when overriding <workspace>/Image.

When to invoke

  • The user asks to extract, prepare, or initialize the BSP image.

  • A downstream skill reports missing <bsp_image.root_path>/Linux_for_Tegra/.

  • The active profile has no bsp_image: block yet.

Procedure

Resolve target and image path

Resolve the active profile per ../../context/target-platform-contract.md. Refuse if there is no active profile or reference_devkit: is missing.

<workspace> is the parent of the active profile's target-platform/ directory. <bsp_image.root_path> defaults to <workspace>/Image.

Profile stateAction
bsp_image.root_path existsUse it without prompting.
bsp_image: exists without root_pathUse <workspace>/Image.
No bsp_image: blockAsk once: Enter for default, or absolute override path.

For an override, validate that the closest existing parent is writable. Omit root_path when the default is used.

Determine GPU stack

Use the shared GPU-driver invariant from ../../context/target-platform-contract.md. Derive the expected stack from reference_devkit.module.id and the catalogue:

Chip familyModule IDsStackapply_binaries.sh flag
T234 / Orinp3701, p3767nvgpunone
T264 and later / Thor+p3834OpenRM--openrm

Refuse unknown module IDs. The --openrm flag is only valid on BSP releases that ship the OpenRM stack; if the active BSP doesn't expose the flag, omit it regardless of what the target wants.

Reuse or extract

If <bsp_image.root_path>/Linux_for_Tegra/ already exists:

  1. Do not extract over it unless the user explicitly requested re-extraction and accepted the overwrite risk.

  2. Derive the on-disk version from Linux_for_Tegra/nv_tegra_release. Ask before replacing a different recorded bsp_image.version.

  3. Verify the installed GPU stack against the platform-derived expectation when possible. Detection precedence (first probe that yields a definitive answer wins):

    1. Linux_for_Tegra/rootfs/etc/nv_tegra_release carries an INSTALL_TYPE= token on BSP releases that expose it (newer lines). Read and compare directly.

    2. Otherwise, find Linux_for_Tegra -name nvgpu.ko: present → nvgpu, absent → OpenRM.

    3. If the chip family has only ever shipped one stack (e.g. T234 / Orin is always nvgpu in current BSPs), fall back to the catalogue-derived expectation without disk probing.

If the installed stack conflicts with the active target, refuse and ask the user to re-extract with the correct stack or fix the target profile. Otherwise skip extraction and update the profile.

Locate tarballs

When extraction is needed, search:

  1. <bsp_image.root_path>/

  2. <workspace>/

  3. current working directory

Prompt for absolute paths for anything missing. Required filenames:

  • Jetson_Linux_R<ver>_aarch64.tbz2

  • Tegra_Linux_Sample-Root-Filesystem_R<ver>_aarch64.tbz2

Both filenames must contain the same R<ver> token. Refuse mismatches and record <ver> as bsp_image.version. Do not download tarballs.

Extract and apply binaries

Use absolute tarball paths; they may live outside <bsp_image.root_path>.

ROOT="<bsp_image.root_path>"
BSP_TARBALL="<absolute path to Jetson_Linux_R<ver>_aarch64.tbz2>"
ROOTFS_TARBALL="<absolute path to Tegra_Linux_Sample-Root-Filesystem_R<ver>_aarch64.tbz2>"

mkdir -p "$ROOT"
tar xjf "$BSP_TARBALL" -C "$ROOT"
sudo tar xpjf "$ROOTFS_TARBALL" -C "$ROOT/Linux_for_Tegra/rootfs"

cd "$ROOT/Linux_for_Tegra"
if [ "$GPU_STACK" = "openrm" ]; then
  sudo ./apply_binaries.sh --openrm
else
  sudo ./apply_binaries.sh
fi

Set GPU_STACK from the "Determine GPU stack" step above. Abort on the first failing command and surface the failed command.

Update the active profile

Persist the resolved BSP image metadata in the active target profile so later skills can find the BSP without re-prompting. Preserve existing blocks, comments, and quoted SKU values; use a round-tripping YAML writer such as ruamel.yaml.

bsp_image:
  root_path: <absolute override path>  # omit for <workspace>/Image
  version: "<derived version>"

Rules:

  • Same version and same root path: no rewrite.

  • Different version: ask before updating.

  • Different recorded root_path: refuse automatic rewrite.

  • Always quote version.

Finish

Report the image path, extracted vs reused state, GPU stack, derived version, and profile update status. Then suggest /jetson-init-source.

Purpose

Materialize Linux_for_Tegra/ on disk by extracting the right Jetson Linux + sample-rootfs tarballs and running apply_binaries.sh with the GPU-stack flag derived from the active target (nvgpu for T234, OpenRM for T264+). Then commit the derived BSP version into the profile's bsp_image: block.

Prerequisites

  • Active target profile resolved per ../../context/target-platform-contract.md.

  • Jetson Linux BSP tarball and matching sample-rootfs tarball staged on disk (e.g. by /jetson-download-bsp or hand-placed).

  • Write access to the workspace Image/ root (or the override bsp_image.root_path).

  • sudo available for apply_binaries.sh.

Limitations

  • Writes only the bsp_image: block; source tree, documents, and carrier profile are owned by sibling skills.

  • Refuses to overwrite an existing Linux_for_Tegra/ without explicit user direction.

  • Does not download tarballs; rely on /jetson-download-bsp or hand-stage the inputs.

Troubleshooting

  • apply_binaries.sh exits non-zero — re-read its console output; most failures are missing sudo, missing rootfs tarball, or wrong GPU stack flag for the SoC generation.

  • nv_tegra_release absent after extract — extraction stopped early; verify tarball integrity and rerun.

  • Recorded version disagrees with the tarball filename — the tarball was renamed; trust the value parsed from Linux_for_Tegra/nv_tegra_release over filenames.

  • Different recorded root_path already in profile — refuse and ask the user to confirm before overwriting.

References

  • ../../context/target-platform-contract.md

  • ../../references/bsp-platforms-catalogue.md

  • ../../references/platform_template.yaml

  • ../jetson-init-target/SKILL.md

  • ../jetson-init-source/SKILL.md

  • ../jetson-flash-image/SKILL.md

Files

LICENSE

Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Medium risk

  • Large base64-encoded blobs

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Jetson Team
Publisher
NVIDIA (Official)
Distributed by
NVIDIA
Source
NVIDIA/skills · skills/jetson-init-image · commit fce3cca
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE-APACHE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Jetson Team or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download jetson-init-image.zip