Yocto TEGRA_BUPGEN_SPECS for Jetson AGX Xavier

Hello Nvidia team,

I am using Yocto development for generating kernel, dtb and rootfs using :
Nvidia meta
path = repos/meta-tegra
url = GitHub - OE4T/meta-tegra: BSP layer for NVIDIA Jetson platforms, based on L4T
branch = dunfell-l4t-r32.4.3
And
path = repos/meta-tegra-community
url = GitHub - OE4T/meta-tegra-community: Repository for community-maintained recipes for additional packages for NVIDIA Jetson platforms

And also swupdate meta :
path = repos/meta-swupdate
url = GitHub - sbabic/meta-swupdate: Yocto receipes to generate a swupdate rootfilesystem as initrd

I have define a custom configuration machine.

All works fine but with some batch of Nvidia Xavier AGX production, the swupdate do not work.
This issue is due to the parameters TEGRA_BUPGEN_SPECS who not contains all listing board.

In my conf I have something like that :

# Extracted from l4t_generate_soc_bup.sh for BOARDID=2888 and board=jetson-agx-xavier-devkit
TEGRA_BUPGEN_SPECS ?= "fab=400;boardsku=0001;boardrev=H.0 \
                       fab=400;boardsku=0001;boardrev=J.0 \
                       fab=400;boardsku=0001;boardrev=L.0 \
                       fab=400;boardsku=0004;boardrev=M.0 \
                       fab=400;boardsku=0004;boardrev=P.0 \
                       fab=401;boardsku=0004;boardrev=B.0 \
                       fab=402;boardsku=0005;boardrev=C.0 \
                       fab=402;boardsku=0005;boardrev=G.0 "

If the Xavier used for a swupdate have not the associative fab / sku / rev info in my conf, that will not work.
Someone knows how can I get all the listing ?
I don’t understand where the comment comes from, so I cannot generate the full listing.

Hello,

Welcome to the NVIDIA Developer forums! Your topic will be better served in the Jetson category.

I will move this over for visibility.

Cheers,
Tom

1 Like

We don’t support Yocto currently, however our partner does, please visit Yocto Support for NVIDIA Jetson Platforms - Yocto Support for NVIDIA Jetson Platforms - Setting up Yocto - RidgeRun Developer Connection

Hello, thanks for the answer.

If we forget Yocto, I just need the full listing of Nvidia Xavier AGX, which associate ‘FAB’, ‘SKU’ and ‘REV’.
Did you know how to have that for your board ?

"fab=400;boardsku=0001;boardrev=H.0 \
                       fab=400;boardsku=0001;boardrev=J.0 \
                       fab=400;boardsku=0001;boardrev=L.0 \
                       fab=400;boardsku=0004;boardrev=M.0 \
                       fab=400;boardsku=0004;boardrev=P.0 \
                       fab=401;boardsku=0004;boardrev=B.0 \
                       fab=402;boardsku=0005;boardrev=C.0 \
                       fab=402;boardsku=0005;boardrev=G.0 "

Someone :( ?

I don’t quite understand what is your question here.

If you want to check the module info of your board, read the module eeprom content through i2c and it will tell.

cat /etc/nv_boot_control.conf would also give some info.

I don’t have /etc/nv_boot_control.conf in my Yocto build, I will search how I can add it.

To try to be more understandable:

I have a lot off Xavier AGX board, and I want to create a yocto compatible with all them, and to be compatible I need the complete “TEGRA_BUPGEN_SPECS”.
I search a way to have it for all my Xavier always in the box.

For now, I must flash each board, check the associated values ‘FAB’, ‘SKU’ and ‘REV’, and add them if it’s new, to my config machine. It’s little boring so I search a way to have the full list in advance.