Attendees

10

Video

https://youtu.be/RPq1jCL_mKw

Discussion

Branch Updates

• Master and Scarthgap both at 36.4.3
• Master also working with GCC 15 upgrade, latest merge in https://github.com/OE4T/meta-tegra/pull/1896
• 35.6.1 pending at https://github.com/OE4T/meta-tegra/pull/1891
  • Currently at kirkstone, will work to port to scarthgap
• Walnascar released
  • Pulled branch for this a while back, will update in demo distro
  • Will start deprecating styhead, will focus on just walnascar, scarthgap and kirkstone going forward.
  • Next LTS release will be in 2026
• Compiler changes in upstream is mostly done
• Discussion about future support for OOT kernel from NVIDIA, LTS upstream but not linux-yocto

JTAG Probe usage in recent generations, especially Xavier or Orin

• Post from Ilies in 2020, never got it working.
• Attempting to use ARM developer studio
• Attempting to troubleshoot lockup on CPU0

Devicetree issues

• See discussion in https://github.com/OE4T/meta-tegra/issues/1895
• Runtime application through UEFI
• Since devicetrees are no longer in the kernel this doesn’t work anymore
• Needs a different approach
• Recent related change in master/scarthgap in https://github.com/OE4T/meta-tegra/pull/1882
  • All you need to do is depend on upstream devictree after this change
  • This likely broke the example in https://github.com/OE4T/tegra-demo-distro/tree/master/layers/meta-tegrademo/recipes-bsp/tegrademo-devicetree
  • Gets a depends on kernel out of tree, kernel include has changed, should be similar to this.

Swupdate status update

• https://github.com/OE4T/tegra-demo-distro/issues/333 - out of space in 4GB
• https://github.com/OE4T/tegra-demo-distro/issues/332 - I believe needs something like https://groups.google.com/g/swupdate/c/ZrDn9hVCet8/m/4lZhxoFfAgAJ - wondering how I’m the only one seeing this on master/styhead

Labgrid

• August talk in Amsterdam, ELC Europe
• Second stage using Yocto
  • Image with RPIos, run ansible to do labgrid setup.
  • Is proven, not pushed anywhere yet.
  • Implementation is known good, just not public yet.
  • Need to power cycle the unit, need UART for early boot messages
  • Next have one RPI be a runner, once builder is done those could be sent off to coordinator, this will push to devices.
  • Test cases all in pytest.
  • Using robot framework report format binformat-misc and qemu-static
  • Considering a change SDK for host tools on signing server, may be able to do something similar for tegraflash.

OSS Denver

• June 23-25 https://events.linuxfoundation.org/open-source-summit-north-america/
• Reach out to Dan if you will be there and would like to meet up.