OE4T Meeting Notes 2023 03 09

Video

https://youtu.be/ye5Z4dzWyE0

Attendees

6

Topics

• Container changes
  • See thread here regarding getting deepstream samples working on the container
  • Fix in https://github.com/OE4T/meta-tegra/pull/1194
  • Workaround/solution is to drop in nvidia prebuilt versions of gstreamer plugins, libv4l2 plugins in tegra-container-passthrough
• Will still see some errors from things like rivermax SDK and triton. May need to build your own container with necessary runtimes if this is something you need.
• Used sato plus one additional package to bring up deepstream samples in container. Shouldn’t need many additional packages above base for a dedicated docker build. Main things you’d need is display support (if you need display) and camera support.
• You can also figure out the minimal set of kernel modules, minimize the kernel modules used. Docker has a script which can help identify these.
• Capsule partition updates
  • Discussed https://docs.nvidia.com/jetson/archives/r35.2.1/DeveloperGuide/text/SD/Bootloader/UpdateAndRedundancy.html#generating-the-capsule-update-payload
  • We need to ensure we tie rootfs, bootloader and kernel all together, keep version locked. Don’t see a reason for the “Manually Sync” part there
  • Dan has verified capsule update works with stock L4T, doesn’t work with OE4T yet.
  • extlinux is built into l4t launcher EFI application. Suffers from similar issues that cboot faced, doesn’t really fully accept full range of syntax. Need to be careful about how it’s formatted. Needs to be signed if secure boot enabled. That means you need to pad out ot byte boundaries. If the signing tool does this for you it pads with non-pritable characters. Want to experiment with doing away with L4TLauncher as EFI app, look at Grub or SDBoot. Tricky part is that we are still using devicetrees, not sure how the alternatives work with devicetrees. Have used systemd-boot previously, worked well. Would be nice to have something similar.
  • Other issue with A/B is there’s a single usb partition, no redundancy. No slot B for the boot ESP partition. Still weary about A/B updates which include everything as there’s a window here where the ESP partition update could be a problem.
  • Not using kernel partition and either using extlinux.conf approach or some other way to bundle kernel into the filesystem is probably the correct approach. Ideally NVIDIA would just focus on one approach and get rid of the dedicated kernel partitions.
  • L4TLauncher seems like an approach which tries to preserve cboot look and feel. It might be better to switch to something that is more common to other ARM UEFI platforms. Haven’t looked at everything L4TLauncher does to see if there are things that are necessary for the boot flow. Might be difficult to move to another platform.
• How to integrate software update for Jetson AGX Orin Devkit, ultimately Orin Nano, ideally swupdate
  • Is there a path to update the rootfs only. Is it something I should expect to work quite easily or are there a lot of blockers.
  • Related discussion in https://github.com/OE4T/meta-tegra/discussions/1191
  • It could be relatively straightforward to update only the rootfs by modifying extlinux.conf
• CFP submitted for EOSS
  • Slides are due ~ 1 week before the conference in June or late May
  • Will know about acceptance around April 10th
• Debian based distro built on OE4T
  • Wouldn’t suggest meta-debian
  • https://github.com/siemens/isar - project which can build a rootfs. Would need a meta-tegra-isar
  • Would be a question of how many recipes you’d need to fork.