search

Expected Outcome

hashtag
Files

  • Tarball

  • Pre-built BSP

hashtag
Tarball

The tarball involves all the necessary files for the flashing, compile, and duplicate the porting environment, e.g.,

hashtag
Build

  • build_pack.sh _ the script to create the tarball

  • build_device_tree.sh _ compile the device tree

  • build_kernel.sh _ compile the kernel

  • build_clean.sh _ the script to create the tegra default configuration for kernel and device tree compilation

hashtag
Kernel and Device Tree

  • sources/kernel/kernel-jammy-src/arch/arm64/configs/defconfig _ the modified kernel config

  • build/.config _ the modified kernel config

  • kernel/Image rootfs/boot/Image _ compiled kernel image

  • sources/hardware/nvidia/t23x/nv-public/nv-platform/Makefile sources/hardware/nvidia/t23x/nv-public/nv-platform/*.dts sources/hardware/nvidia/t23x/nv-public/nv-platform/*.dtsi _ migrated device tree for our product from Jetson dev kits examples

  • boardName_SKU.dtb _ a compiled device tree for each SKU

  • boardName_decompiled.dts _ a decompiled device tree source from dtb for developing

hashtag
Flashing

  • flash_pinmux.sh _ flashing the Jetson without pre-built BSP, only pinmux, device tree, and kernel.

    • It would be perfect if we can adapt the right conf for different Jetson SKU in one command

  • flash_sysmtem_image_reuse.sh _ flashing the Jetson with pre-built BSP, only pinmux, device tree, and kernel.

    • It would be perfect if we can adapt the right conf for different Jetson SKU in one command

  • SKU.conf _ config file for each Jetson SKU for the flashing command

  • SKU.conf.common _ include file for SKU.conf to declare common settings

  • bootloader/$boardName-gpio-default.dtsi bootloader/$boardName-padvoltage-default.dtsi bootloader/$boardName-pinmux.dtsi bootloader/generic/BCT/$boardName-padvoltage-default.dtsi bootloader/generic/BCT/$boardName-pinmux.dtsi _ pinmux related (right path needs to be clarifed)

  • bootloader/tegra234-mb2-bct-common.dtsi _ a config for MB2

hashtag
Pre-built BSP

We expected the customer could use the BSP to verify our hardware, which implies that the BSP will involve

  • JetPack 6.0 Production Release

  • NVIDIA SDK installed, e.g., TensorRT, CUDA, DeepStream, etc ...

  • Updated kernel to support all hardware IO, e.g., YUV format, PPS, and other necessary patch on Jetson's developer forum

  • device tree

  • startup script

  • GMSL2 camera driver for selected cameras

  • acpid with proper settings for ignition power control, e.g., link

hashtag
Startup Script

  • It would be wonderful if we add a little mechanism to swap the deafult dtb for different Jetson SKU. Or maybe we should removed the FDT ... dtb inside the bootloader, to force it to read the dtb inside specfici partition

PreviousCreate a Pure JetPack 6.0 Production Release EnvironmentNext[WIP] Jetson Background Information

Last updated