b84d637a5c
* Tweak the flashing script and XML file naming for the pre-signed case as is done when the script runs the signing itself. Note that external flash layouts are assumed not to require any tegrasign-type signing, which should always be the case for R36.x and later. * Make the script tolerant of not being able to fetch the target's serial number from the CVM EEPROM. There doesn't appear to be a way to fetch the CVM contents with pre-signed boot firmware. With these changes, when using pre-signed binaries, only one target can be flashed at a time from a given host. Signed-off-by: Matt Madison <matt@madison.systems>
OpenEmbedded/Yocto BSP layer for NVIDIA Jetson Modules
Jetson Linux release: R36.4.0 JetPack release: 6.1
Boards supported:
- Jetson AGX Orin development kit
- Jetson Orin NX 16GB (p3767-0000) in Xavier NX (p3509) carrier
- Jetson Orin NX 16GB (p3767-0000) in Orin Nano (p3768) carrier
- Jetson Orin Nano development kit
- Jetson AGX Orin Industrial 64GB (P3701-0008) in Orin AGX (P3737) carrier
This layer depends on: URI: git://git.openembedded.org/openembedded-core branch: master LAYERSERIES_COMPAT: styhead, walnascar
CUDA toolchain compatibility note
CUDA 12.6 supports up through gcc 13.2 only, so recipes are included
for adding the gcc 10 toolchain to the build for CUDA use, and cuda.bbclass
has been updated to pass the g++ 10 compiler to nvcc for CUDA code compilation.
Getting Help
For general build issues or questions about getting started with your build setup please use the Discussions tab of the meta-tegra repository:
- Use the Ideas category for anything you'd like to see included in meta-tegra, Wiki content, or the tegra-demo-distro.
- Use the Q&A category for questions about how to build or modify your Tegra target based on the content here.
- Use the "Show and Tell" category for any projects you'd like to share which are related to meta-tegra.
- Use the General channel for anything that doesn't fit well into the categories above, and which doesn't relate to a build or runtime issue with Tegra yocto builds.
Reporting Issues
Use the Issues tab in meta-tegra for reporting build or runtime issues with Tegra yocto build targets. When reporting build or runtime issues, please include as much information about your environment as you can. For example, the target hardware you are building for, branch/version information, etc. Please fill in the provided bug template when reporting issues.
We are required to provide an e-mail address, but please use GitHub as described above, instead of sending e-mail to oe4t-questions@madison.systems.
Contributing
Please see CONTRIBUTING.md for information on submitting patches to the maintainers.
Contributions are welcome!