Which image should I bitbake?

[fei4xu]

Hi,

After source poky-dunfell/oe-init-build-env build I got this:

You can now run 'bitbake '
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support

and I found another image: tegra-minimal-initramfs which inherit core-image.

I'd like to check which image should I bitbake to reproduce an image which is close to Nviida's pre-build flash image?

Thanks.

[madisongh]

None of the images you build using OE/Yocto Project tools will be very close to the Ubuntu 18.04 image that NVIDIA provides with L4T/JetPack, as the underlying design principles are fundamentally different. Here, you start small and build in exactly what you need, rather than having a fully-featured set of binaries for a wide variety of use cases that run generically across broad swathes of hardware.

That said, you might want to consider using the demo distro we have here, rather than poky, as a starting point, which has several images that combine core features with L4T/JetPack contents.

[sgserg]

The only thing missing from our JetPack 4.4 support is a a recipe for VPI.

Is there any place documenting which JetPack components are [not] supported by meta-tegra?

[ichergui]

Hey @sgserg

Please check our wiki page

By using this wiki page, you can align with L4T to check Jetpack components

[sgserg]

Thanks @ichergui, I've seen that page, it lists the versions, but it is only in this issue I see that VPI is missing.
Maybe other versions miss something else?

[ichergui]

@sgserg

First release version of VPI is 1.0.12 that Nvidia provides in Jetpack 4.5 / L4T-R32.5.0
Do you need it for Jetpack 4.4 ? if so, I will discuss with @madisongh and I will add it to dunfell-l4t-r32.4.3

[sgserg]

@ichergui, turns out we don't use VPI, so no need to add it anywhere on my account, thanks! I was just worried there might be other JetPack components not supported by meta-tegra.

[notthetup]

Semi-related question:

I was trying to build various images core-image-sato-dev, core-image-minimal-dev, core-image-full-cmdline but I only managed to connect to the Jetson over SSH on core-image-sato-dev.

Is there a list that explains what each of these images contains? Based on the yocto documentation it's really hard to guess/dechiper why certain images are inaccessible over SSH.

[lfdmn]

Try this out

bitbake -g <image name> && cat pn-buildlist | grep -ve "native" | sort | uniq

[madisongh]

Also, if you've already built an image, you'll fine a .manifest file for it in the same directory (under $BUILDDIR/tmp/deploy/images) where the image is placed.

You can also look at the image recipes themselves, as a starting point.