Generated banner for Jetson Download Bsp
Generated logo for Jetson Download Bsp

Jetson Download Bsp

NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA

  • Skill
  • Tool integration
  • Cloud and DevOps
  • Apache-2.0
  • Medium risk

From the author

Download NVIDIA Jetson Linux BSP artifacts (BSP tarball, sample rootfs, public_sources, x-tools, guides) for the active target. Use for Auto Setup; not for extraction or profile edits.
— the description by Jetson Team

AutoGineer summary

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

The jetson-download-bsp skill manages the network-based acquisition of essential NVIDIA Jetson Linux BSP components. It is designed as a foundational step for the Auto Setup process, ensuring that required tarballs, source packages, toolchains, and documentation are correctly staged in the workspace. The skill strictly handles downloading and verification, leaving extraction and configuration to subsequent setup skills. It enforces strict version matching against official NVIDIA release archives and performs disk space validation before initiating transfers.

What it does

  • Resolves and validates the target Jetson Linux release against official NVIDIA archives.
  • Downloads BSP tarballs, sample rootfs, public sources, and cross-compilation toolchains.
  • Stages developer and user guides into the designated workspace documentation directory.
  • Performs disk space verification to ensure sufficient capacity before downloading.
  • Validates downloaded file integrity and naming conventions against expected release tokens.
  • Provides a comprehensive fetch plan for user review before modifying the workspace.

When to use it

  • When preparing a workspace for Jetson Linux development using the Auto Setup path.
  • When you need to ensure all required BSP artifacts are present before running initialization skills.
  • When you need to verify that your current workspace has the correct artifacts for a specific L4T release.

Advantages

  • Ensures consistent workspace structure by placing files in expected locations for downstream tools.
  • Prevents accidental overwrites by checking for existing files and requiring confirmation.
  • Reduces manual effort by automating the discovery of artifacts from official NVIDIA pages.
  • Maintains safety by using temporary files and atomic renaming during the download process.

Usage examples

“Run the auto setup download for the latest Jetson Linux release.”
The agent identifies the latest supported release, presents a download plan, verifies disk space, and stages all required BSP artifacts in the workspace.
“Download BSP artifacts for R36.4.4.”
The agent validates that R36.4.4 is supported for the active platform, fetches the specific artifacts, and confirms their presence in the local directory.

Install

  1. Download the skill as a ZIP:

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

    mkdir -p .agents/skills && unzip jetson-download-bsp.zip -d .agents/skills

Documentation by Jetson Team

Download BSP Artifacts

jetson-download-bsp owns network fetches for the Auto Setup path. It does not extract archives, initialize source trees, register documents, or edit the active target profile. Those remain owned by jetson-init-image, jetson-init-source, and jetson-link-docs.

When to invoke

  • /jetson-quick-start selected Auto Setup.

  • The user wants NVIDIA BSP artifacts downloaded into the current workspace before running setup skills.

Inputs and outputs

Resolve the active profile per ../../context/target-platform-contract.md. Refuse if no active profile exists.

Follow the shared quick_start_prefill contract. When invoked by /jetson-quick-start, this skill consumes quick_start_prefill.mode and quick_start_prefill.download.bsp_release as the requested release when present. Missing or invalid prefilled values are not fatal, but a concrete release is required before any download starts.

Use the workspace root as the parent of target-platform/. Place files where downstream setup skills already search:

ArtifactDestination
Jetson Linux BSP tarball<bsp_image.root_path or workspace/Image>/Jetson_Linux_R<ver>_aarch64.tbz2
Sample rootfs tarball<bsp_image.root_path or workspace/Image>/Tegra_Linux_Sample-Root-Filesystem_R<ver>_aarch64.tbz2
public_sources.tbz2<workspace>/Downloads/public_sources.tbz2
x-tools.tbz2<workspace>/Downloads/x-tools.tbz2
Developer Guide<documents.root_path or workspace/Documents>/
User Guide<documents.root_path or workspace/Documents>/

Do not write bsp_image:, source:, or documents: blocks. The next setup skills will register derived metadata after extraction or user confirmation.

Procedure

Resolve target release

Fetch the release list from: https://developer.nvidia.com/embedded/jetson-linux-archive

From the archive and linked release pages, list concrete releases that explicitly support the active platform. Let the user choose a concrete Jetson Linux / L4T release token (R36.4.4, 36.4.4, 38.2, 38.2.1, 38.4, etc.); do not proceed with a family placeholder such as R38.x. A concrete release token is an optional leading R followed by two or three numeric dotted components. Preserve the token exactly as the official page presents it; do not add .0, remove a patch component, or otherwise normalize it. Sort release choices by dotted numeric order descending (newest first), comparing the components that are present; keep source-provided recommendations in descriptions.

Resolve quick_start_prefill.download.bsp_release as follows:

  • Concrete and supported: continue with that release.

  • Missing, skip, blank, or a family placeholder (R38.x, 38.x): show supported concrete releases and ask the user to choose one.

  • Concrete but unsupported or ambiguous: stop before artifact discovery and show the active platform, requested BSP release, supported concrete releases, and source archive or release page.

Never auto-substitute the requested release with a supported release, even when there is only one supported option.

For unsupported or ambiguous prefill, ask with the shared User input prompt style, to choose exactly one click-to-select action:

  • pick_supported_release — user selects one supported concrete release.

  • confirm_override — user confirms the incompatible release and enters an override reason.

  • cancel — stop with no downloads.

Do not continue to "Locate release artifacts" until the selected release is concrete and supported, or the user explicitly confirms override. Record any override reason in the final summary. If the user cancels, stop with no downloads. Do not claim support unless the archive or linked release page explicitly lists the active platform.

Discovery retries

For every artifact WebFetch in "Resolve target release" and "Locate release artifacts" (BSP, rootfs, public_sources.tbz2, x-tools.tbz2, Developer Guide, User Guide), try 3 attempts before marking it missing:

  1. Focused prompt — artifact name + file type.

  2. Verbatim link dump on the same URL — "list every hyperlink, text and href, no filtering". Accept product-specific names and .html indexes.

  3. Verbatim dump on a sibling page — Jetson Linux archive, JetPack downloads, or https://docs.nvidia.com/jetson/archives/r<ver>/.

Only after all 3 fail, route to user-paste / skip. Never fabricate URLs.

Locate release artifacts

Follow links from the selected release page. Never construct NVIDIA download URLs by string concatenation.

Required artifacts:

  • Jetson Linux BSP image tarball.

  • Tegra Linux sample root filesystem tarball.

  • public_sources.tbz2.

  • x-tools.tbz2 / Crosstool-NG Toolchain gcc matching the selected BSP release.

  • Developer Guide.

  • User Guide.

If a guide is not available as a direct file link, accept the release documentation URL as the artifact and record it in the final summary. If the toolchain is listed on a JetPack downloads page instead of the release page, follow the official page link and match the selected BSP release; do not synthesize the URL from a release number. Do not proceed until each required artifact is downloaded, already present at its destination, represented by a URL, or explicitly skipped by the user.

Show the fetch plan

Before changing the workspace, print a plan with:

  • selected release and release page URL;

  • active platform summary (reference_devkit.name, optional custom_carrier.name, and flash_config);

  • source URL and destination path, or documentation URL, for every artifact;

  • any existing destination file that will be reused;

  • any artifact that requires browser/EULA handling instead of curl.

Default to Download all. Do not ask an extra confirmation when every required artifact is downloadable, already present for reuse, or a documentation URL to record. Print the plan and continue to disk-space verification.

Still stop and ask before side effects in any of these cases:

  • the release required an incompatibility override;

  • a required artifact is missing and needs user-paste / skip;

  • a destination file would be overwritten rather than reused;

  • the artifact requires browser/EULA handling;

  • disk-space verification fails or cannot be computed safely.

Verify disk space

Sum Content-Length across artifacts to download (curl -sI <url>); refuse if df -B1 --output=avail <workspace> headroom < sum × 1.2. Skip URL-only artifacts.

Download safely

Create destination directories as needed. For direct file links, use a temporary .part path and rename only after success:

mkdir -p "<destination-dir>"
curl -fL --retry 3 --retry-all-errors --retry-delay 5 -o "<destination>.part" "<artifact-url>"
mv "<destination>.part" "<destination>"

If a destination file already exists and is non-empty, reuse it by default after showing its path. Ask before overwriting. If an artifact download fails due to 404, 401/403, EULA/browser authentication, or a network error, stop and show the artifact URL plus expected destination path. Ask the user to download the file manually, skip that artifact, or cancel. Do not synthesize alternate NVIDIA URLs.

Validate filenames

Before finishing, verify the BSP and rootfs tarball filenames contain the exact R<ver> token from the official artifact URL or filename discovered in Step 2. <ver> may have two or three numeric components (R38.2, R38.2.1, R38.4, etc.). Do not infer R38.2.0 from R38.2, and do not assume that a selected two-component release maps to a three-component tarball name:

  • Jetson_Linux_R<ver>_aarch64.tbz2

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

Verify public_sources.tbz2 is a bzip2 tarball when it exists locally:

file -b "<workspace>/Downloads/public_sources.tbz2" | grep -q "bzip2 compressed"

Verify x-tools.tbz2 the same way when it exists locally:

file -b "<workspace>/Downloads/x-tools.tbz2" | grep -q "bzip2 compressed"

Warn, but do not fail, if document filenames differ from the release version; NVIDIA documentation naming is less consistent than tarballs.

Finish

Report the selected release, downloaded/reused/skipped artifacts, and exact local paths. Then hand back to the caller with:

  1. /jetson-init-image

  2. /jetson-init-source

  3. /jetson-link-docs

Gotchas

  • Keep this skill download-only; extraction belongs to jetson-init-image and jetson-init-source.

  • Put image tarballs in the image root, not Downloads/, because jetson-init-image searches the image root, workspace root, and current directory.

  • Put public_sources.tbz2 in Downloads/ because jetson-init-source auto-discovers that path for Branch A.

  • Put x-tools.tbz2 in Downloads/ because jetson-init-source auto-extracts that path and writes the resulting source.toolchain prefix.

  • The User Guide maps to documents.bsp_user_guide in the profile schema (alongside bsp_developer_guide). jetson-link-docs writes it when the user confirms; this skill only stages the file or URL.

Purpose

Stage the four NVIDIA-shipped artifacts (BSP, sample rootfs, public_sources, x-tools) plus the Developer / User Guides at the exact paths the Setup skills look in, so /jetson-init-image, /jetson-init-source, and /jetson-link-docs can run offline once this skill is done.

Prerequisites

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

  • Network access to developer.nvidia.com and the Jetson Linux archive page.

  • Workspace layout with the expected Image/, Source/, Downloads/, and Documents/ roots (default workspace shape).

Limitations

  • Download-only; never extracts, runs apply_binaries.sh, mounts sources, registers documents, or mutates the active profile.

  • Release selection is bounded to entries published on the official Jetson Linux archive; pre-release or internal builds are out of scope.

  • No retry / mirror logic — failures are surfaced to the user, not silently retried.

Troubleshooting

  • Release page not reachable — check VPN / proxy; do not invent fallback URLs. Stop and report.

  • Archive name mismatch with active platform — verify the release declares the active reference devkit; if not, ask the user to pick a supported release or switch target via /jetson-set-target.

  • public_sources.tbz2 missing on archive — some releases ship it as a separate page; follow the release-page link rather than guessing the URL.

  • Existing files in the destination — refuse to overwrite without confirmation; downloads must be idempotent at the user's discretion.

References

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

Written for: Claude Code

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.

Needs: Names Claude Code tools

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-download-bsp · 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-download-bsp.zip