Capsule payload for orin nano 8G

Hi,

Our customer would like to know which file is the capsule payload for orin nano 8G + devkit.

TEGRA_BL_3701_000.Cap
TEGRA_BL_3701_agx_super.Cap
TEGRA_BL_3767_nanoe8gb_super.Cap
TEGRA_BL_3701_agx.Cap
TEGRA_BL_3767.Cap
TEGRA_BL_3767_super.Cap
TEGRA_BL_3701_agx_ind.Cap
TEGRA_BL_3767_nanoe8gb.Cap

Thx
Yen

hello yenchao,

you may see-also developer guide for Jetson Modules and Configurations, it’s P3767-0005 for Orin Nano 8GB.
please see-also readme file for reference, $OUT/Linux_for_Tegra/tools/ota_tools/version_upgrade/Image_based_OTA_Examples.txt

@yenchao
To add to Jerry’s note, TEGRA_BL_3767_nanoe8gb.Cap is your exact target file from that list for the Orin Nano 8GB variant.

Hi Jerry,

Sorry, I mean p3767-0003 orin nano 8g module, not p3767-0005 orin nano 8G on devkit module.

Which one is for p3767-0003 orin nano 8g module?
TEGRA_BL_3767_nanoe8gb_super.Cap
TEGRA_BL_3701_agx.Cap
TEGRA_BL_3767.Cap
TEGRA_BL_3767_super.Cap
TEGRA_BL_3701_agx_ind.Cap
TEGRA_BL_3767_nanoe8gb.Cap

What is 3767_nanoe8gb?
It seems like it didn’t show up in R36.5.

Thx
Yen

Hi Andrey,

But nanoe8gb didn’ t show up in R36.5.
So I don’t think TEGRA_BL_3767_nanoe8gb.Cap is for p3767-0003 Orin Nano 8GB.

Thx
Yen

Hi Yen,
If the nanoe8gb variant isn’t exposed in that specific release, the generalized TEGRA_BL_3767.Cap (or TEGRA_BL_3767_super.Cap) serves as the base capsule covering the p3767 board family for the Orin Nano production module (-0003).

Jerry can also confirm the exact intended mapping for -0003 in R36.5, but the base 3767 binary handles that hardware group.
Alternatively, if there’s ongoing ambiguity with the pre-built binaries in R36.5, you can always generate a clean, exact capsule payload directly from the Linux_for_Tegra/ root:

sudo ./build_l4t_bup.sh jetson-orin-nano-devkit mmcblk0p1
./generate_capsule/l4t_generate_soc_capsule.sh \
    -i bootloader/payloads_t23x/bl_only_payload \
    -o ./TEGRA_BL.Cap t234

hello yenchao,

you may refer to jetson-orin-nano-devkit.conf,
there’s SKU handling for loading board specific binaries.
for instance,

         elif [ "${board_sku}" = "0003" ]; then
                 BPFDTB_FILE="tegra234-bpmp-3767-0003-3509-a02.dtb";
                 DTB_FILE=tegra234-p3768-0000+p3767-0003-nv.dtb;

Hi Jerry,

Which one is for p3767-0003 orin nano 8g module?

TEGRA_BL_3767_nanoe8gb_super.Cap
TEGRA_BL_3701_agx.Cap
TEGRA_BL_3767.Cap
TEGRA_BL_3767_super.Cap
TEGRA_BL_3701_agx_ind.Cap
TEGRA_BL_3767_nanoe8gb.Cap

What is 3767_nanoe8gb?

Could you give me a definite answer?

Thx
Yen

hello yenchao,

may I also know what’s your commands for creating payload.

Hi Jerry,

These files are in rootfs/opt/ota_package/t23x by default, not I created.

TEGRA_BL_3767_nanoe8gb_super.Cap
TEGRA_BL_3701_agx.Cap
TEGRA_BL_3767.Cap
TEGRA_BL_3767_super.Cap
TEGRA_BL_3701_agx_ind.Cap
TEGRA_BL_3767_nanoe8gb.Cap

Thx
Yen

hello yenchao,

TEGRA_BL_3767_nanoe8gb.Cap it’s used for an Orin NX 8GB module
you should using below capsule payload for P3767-0003 Orin Nano 8GB.
for instance,
jetson-orin-nano-devkit ==> TEGRA_BL_3767.Cap
jetson-orin-nano-devkit-super ==> TEGRA_BL_3767_super.Cap

Hi Jerry,

How about Orin NX 16GB module?
Which one is for p3767-0000 Orin NX 16GB?

Thx
Yen

hello yenchao,

as you may know..
both Orin Nano and Orin NX modules on the reference carrier board can be flashed using jetson-orin-nano-devkit for the standard configuration, or jetson-orin-nano-devkit-super for the super configuration.

Orin Nano 8GB and Orin NX 16GB share the same capsule file for each configuration, as shown below.

Module Standard configuration Super configuration
Orin Nano 8GB (P3767-0003 / P3767-0005) TEGRA_BL_3767.Cap TEGRA_BL_3767_super.Cap
Orin NX 16GB (P3767-0000) TEGRA_BL_3767.Cap TEGRA_BL_3767_super.Cap

each capsule contains multiple board-specific bootloader payloads.
during the update, the payload matching the module’s board information. therefore, sharing the same capsule file does not mean both modules receive identical firmware.