to pass to initrd-flash for Orin NX (and possibly other
future targets) that have no internal storage.
Signed-off-by: Matt Madison <matt@madison.systems>
Make the image dependencies and inclusion of the initrd-flash
image conditional on whether TEGRAFLASH_INITRD_FLASH_IMAGE is
non-null. This allows users to exclude initrd-flash support
from their builds, if desired.
Signed-off-by: Matt Madison <matt@madison.systems>
The NVIDIA signing tools added a pyfdt package, so we need to
clean up the __pycache__ created for that as well as the
top-level one.
Signed-off-by: Matt Madison <matt@madison.systems>
* Support separate internal and external flash layouts
* Unify the post-signing function, which is the same
across the two Soc types, and populate a '.presigning-vars'
file there to be used by the initrd flashing script
* Populate a '.env.initrd-flash' file to set environment
variables needed by the initrd flashing script
Signed-off-by: Matt Madison <matt@madison.systems>
and use a variable to make it easier to customize (or to update it
if NVIDIA changes the default again).
Signed-off-by: Matt Madison <matt@madison.systems>
This adds an L4T_DEB_FEED_SKIP_POOL_APPEND option
that can be enabled to skip appending the
'/pool/group/pkg/etc' suffix to the deb feed for
additional components that are hosted outside of
the L4T deb repos.
Signed-off-by: Ian Stewart <istewart@nvidia.com>
The recent changes to the helper scripts added a check on
'fuselevel' being set for fetching the chip ID from the device,
so we need to make sure that variable is set when creating
an SDcard image.
Signed-off-by: Matt Madison <matt@madison.systems>
The doflash.sh script generated for t234 devices was erroneously
including environment variable settings for BOARDID, FAB, etc.,
bypassing the fuse/EEPROM read logic in the helper script, probably
because the script was broken. Now that the script has been fixed, remove
those settings so the actual values are queried from the device
during flashing.
Signed-off-by: Matt Madison <matt@madison.systems>
Allow the user to replace the standard TEGRA_ESP_IMAGE image by not
depending on the respective do_image_complete task.
The preferred image can be set via IMAGE_TEGRAFLASH_ESPIMG, after
setting TEGRA_ESP_IMAGE to empty.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
This change adds support (adapted from kernel-fitimage handling) for
out-of-tree device tree binary generation. It looks for a provider
of virtual/dtb, and if this exists, enables the copying of device
tree binaries generated by this recipe.
Signed-off-by: Kurt Kiefer <kurt.kiefer@arthrex.com>
to simplify JetPack revision updates that change *some* of the
nvidia-l4t-* packages to use an updated time/date stamp, but leave
some with the older time/date stamp.
Signed-off-by: Matt Madison <matt@madison.systems>
The 'esp' name was a bit too generic, so renaming should avoid possible
conflicts with other layers.
Also fix a minor typo in the log output in the mkespfs function.
Signed-off-by: Matt Madison <matt@madison.systems>
To enable use of the stock L4T _rootfs_AB.xml layouts, we have to
add replacements for LNXFILE_b, APP_b, and APPUUID_b in the layout
configuration.
Signed-off-by: Matt Madison <matt@madison.systems>
This variable is used everywhere the TNSPEC is calculated, instead
of MACHINE. It can be used to set a different machine name for
compatibility with BUP packaging or NVIDIA's bootload tools.
One example of this is NVIDIA's nvbootctrl tool part of the initial
Jetpack 5 release that matches the devkit machine name against the
COMPATIBLE_SPEC string. A custom TNSPEC_MACHINE name can be used
here to satisfy this match (e.g. 'mymachine-jetson-agx-xavier-devkit')
but the actual MACHINE variable can remain as simply 'mymachine'.
Signed-off-by: Kurt Kiefer <kurt.kiefer@arthrex.com>
The L4T flash.sh script makes a copy of the mb1 firmware and
modifies the flash layout to use that for the second MB1FILE
entry for t194 devices. Comments in the script indicate that
this is necessary, so do the same here.
Signed-off-by: Matt Madison <matt@madison.systems>
* use EMMC_BCT/EMMC_BCT_OVERRIDE variables for the sdram config
file(s) instead of ${MACHINE}.cfg/${MACHINE}-override.cfg
* add missing mb2 firmware for Orin
Signed-off-by: Matt Madison <matt@madison.systems>
- Removing dynamically generated container csv files for nvidia
container passthrough mechanism, as NVIDIA has moved to base l4t.csv
which includes all the container passthrough references
Signed-off-by: Atharva Nandanwar <anandanwar@sighthound.com>
* Now using tegra-flashtools-native
* T234 systems use same naming for the EMMC_BCT file as T194
* Start fixing up BUP payload generation for T234 (not done yet)
Signed-off-by: Matt Madison <matt@madison.systems>
This was added earlier in the kernel recipe, for handling
bundled initrds; make the corresponding change here for
the non-bundled case.
Signed-off-by: Matt Madison <matt@madison.systems>
With UEFI, the kernel args are extracted from the boot image,
rather than being processed from the device tree, so remove
all the device tree mangling we were doing and instead add
the args to the boot image creation step in the kernel
recipe.
Signed-off-by: Matt Madison <matt@madison.systems>
The DTB overlayss are now provided by the kernel and UEFI recipes and
put in ${IMAGE_DEPLOY_DIR}, so copy them from there.
Also fix the flashvars handling for tegra234 platforms during BUP
generation.
Signed-off-by: Matt Madison <matt@madison.systems>
Not that the conversion type name is still 'cboot' for now,
even though we're not using cboot any more.
Signed-off-by: Matt Madison <matt@madison.systems>
* Drop t210, t186 support
* Replace cboot with UEFI
* Replace trusty with OPTEE
* Other miscellaneous updates
Signed-off-by: Matt Madison <matt@madison.systems>
Fix a typo which I missed when reviewing the INITRAMFS_LINK_NAME
change, and add an explicit inherit of kernel-artifact-names rather
than relying on the indirect inherit of that class through some
of the other image classes, so that variable is always defined.
Signed-off-by: Matt Madison <matt@madison.systems>
This change leverages the INITRAMFS_LINK_NAME to 'dynamically' build
the image name returned from tegra_kernel_image method during tegra_flash
building.
This helps avoid build failures if a custom INITRAMFS_LINK_NAME is used
to generate a bundled kernel and ramdisk image.
By default, INITRAMFS_LINK_NAME expands to
INITRAMFS_LINK_NAME ?= "initramfs-${KERNEL_ARTIFACT_LINK_NAME}"
which would yield:
KERNEL_ARTIFACT_LINK_NAME ?= "${MACHINE}"
resulting in no change to default behavior.
Signed-off-by: Kevin Vanden Berge <kvandenberge@gmail.com>
for use in bbappends where we need to add a check on
opengl in DISTRO_FEATURES for just tegra platforms.
Signed-off-by: Matt Madison <matt@madison.systems>
* Use CXX_FOR_CUDA to determine the compiler to pass to nvcc
* Add support for setting CMAKE_CUDA_ARCHITECTURES based on
the CUDA_ARCHITECTURES variable
Signed-off-by: Matt Madison <matt@madison.systems>
for redirecting the gcc toolchain used by nvcc (and,
if necessary, directly compiled CC/C++ code) for
compatibility with CUDA. This class can be inherited
by recipes that need to compile CUDA-compatible code
but do not need the CUDA toolkit dependencies.
The class sets variables CC_FOR_CUDA and CXX_FOR_CUDA.
Recipes needing to use this version of the compiler
must set CC and/or CXX to point to these variables.
Signed-off-by: Matt Madison <matt@madison.systems>
