** Description changed:

  [ Impact ]
  
  * This SRU updates /lib/firmware for NVIDIA Tegra Jetson Orin (NX, Nano, and 
AGX) devices using Jetson Linux v36.5 binaries.
  * Changes include:
    - Updated: display-t234-dce.bin, rtl8822cu_fw, nvhost_tsec_desc.fw, and 
nvhost_tsec_riscv.fw.
    - Added: rtl8852cu_config and rtl8852cu_fw.
  
  * Firmware updates are necessary to guarantee full compatibility with the 
linux-nvidia-tegra-jetson kernel.
  * The target release for this change is Ubuntu 22.04 LTS (Jammy Jellyfish).
  * The package has been successfully built and available for testing at the 
following PPA: https://launchpad.net/~esteban-vazquez/+archive/ubuntu/lp2146610
  
  [ Test Plan ]
  
  1. Connect the Jetson AGX Orin device to a monitor.
  
  2. Flash and boot the device using the current Ubuntu for Jetson
  candidate image: https://cdimage.ubuntu.com/nvidia-tegra/ubuntu-
  server/jammy/daily-preinstalled/manual/jammy-preinstalled-server-
  arm64+tegra-jetson.img.xz
  
  3. After booting, update the system to the latest available packages.
  
-    ```
-    sudo apt update
-    sudo apt upgrade
-    ```
+    ```
+    sudo apt update
+    sudo apt upgrade
+    ```
  
  4. Install the updated `linux-firmware-nvidia-tegra` package from the
  proposed repository and reboot the system.
  
  5. Confirm that the Tegra Security Controller (tsec) firmware files were
  loaded correctly and review the `fw_logs`.
  
-    ```
-    $ sudo dmesg | grep -iE "tsec|tsec.*firmware|tsec.*fw"
-    [    5.166370] tsec 15500000.tsec: Adding to iommu group 32
-    [    5.273095] tsec 15500000.tsec: tsec fw req success in 100 ms
-    [    5.276272] tsec 15500000.tsec: RISC-V boot using kernel allocated Mem
-    [    5.283013] tsec 15500000.tsec: RISC-V boot success
-    
-    $ sudo cat /sys/kernel/debug/tegra_tsec/fw_logs
-    Tsec Logs Start: read_offset=0 write_offset=79 buffer_size=4080 
magic=0xf007ba11
-    Initializing GSP application...
-    Configuring systick for FMODEL/EMU to 1562... 
-    Tsec Logs End
-    ```
+    ```
+    $ sudo dmesg | grep -iE "tsec|tsec.*firmware|tsec.*fw"
+    [    5.166370] tsec 15500000.tsec: Adding to iommu group 32
+    [    5.273095] tsec 15500000.tsec: tsec fw req success in 100 ms
+    [    5.276272] tsec 15500000.tsec: RISC-V boot using kernel allocated Mem
+    [    5.283013] tsec 15500000.tsec: RISC-V boot success
+ 
+    $ sudo cat /sys/kernel/debug/tegra_tsec/fw_logs
+    Tsec Logs Start: read_offset=0 write_offset=79 buffer_size=4080 
magic=0xf007ba11
+    Initializing GSP application...
+    Configuring systick for FMODEL/EMU to 1562...
+    Tsec Logs End
+    ```
  
  6. Ensure that the Realtek Bluetooth firmware was loaded and the
  interface is active with assigned addresses and data activity.
  
-    ```
-    $ sudo dmesg | grep -iE "rtk_btusb.*firmware|rtk_btusb.*fw"
-    [    7.896651] rtk_btusb: load_firmware start
-    [    7.897160] rtk_btusb: fw name is  rtl8822cu_fw
-    [    7.898656] rtk_btusb: load_firmware: New gEVersion 3
-    [    7.898658] rtk_btusb: rtk_get_fw_project_id: opcode 0, len 1, data 13
-    [    7.898663] rtk_btusb: fw_version = 0xefd6d8d7
-    [    7.898692] rtk_btusb: fw: exists, config file: exists
-    [    7.898694] rtk_btusb: load_firmware done
-    $ sudo apt install -y bluez
-    $ sudo hciconfig
-    hci0:      Type: Primary  Bus: USB
-       BD Address: 90:E8:68:BC:88:A8  ACL MTU: 1021:6  SCO MTU: 255:12
-       UP RUNNING 
-       RX bytes:1429 acl:0 sco:0 events:96 errors:0
-       TX bytes:3117 acl:0 sco:0 commands:96 errors:0
-    ```
+    ```
+    $ sudo dmesg | grep -iE "rtk_btusb.*firmware|rtk_btusb.*fw"
+    [    7.896651] rtk_btusb: load_firmware start
+    [    7.897160] rtk_btusb: fw name is  rtl8822cu_fw
+    [    7.898656] rtk_btusb: load_firmware: New gEVersion 3
+    [    7.898658] rtk_btusb: rtk_get_fw_project_id: opcode 0, len 1, data 13
+    [    7.898663] rtk_btusb: fw_version = 0xefd6d8d7
+    [    7.898692] rtk_btusb: fw: exists, config file: exists
+    [    7.898694] rtk_btusb: load_firmware done
+    $ sudo apt install -y bluez
+    $ sudo hciconfig
+    hci0:      Type: Primary  Bus: USB
+     BD Address: 90:E8:68:BC:88:A8  ACL MTU: 1021:6  SCO MTU: 255:12
+     UP RUNNING
+     RX bytes:1429 acl:0 sco:0 events:96 errors:0
+     TX bytes:3117 acl:0 sco:0 commands:96 errors:0
+    ```
  
  7.  Confirm that the display firmware has been loaded and verify visual
  output on the monitor (even after a suspend/resume cycle).
  
-    ```
-    # These messages are shown during early boot stage.
-    I> Successfully register DCE FW load task with MB2 loader
-    I> Partition name: A_dce-fw
-    I> Binary@ device:3/0 block-44800 (partition size: 0x500000), name: 
A_dce-fw
-    I> Ratchet: [A_dce-fw]: sw (BCH): 0, hw (BCT): 0
-    I> dce : oem authentication of header done
-    I> dce : meta-blob integrity check is success.
-    I> dce : will be decompressed at 0x836000000
-    I> dce : decompressed to 12075904 bytes
-    I> dce: plain binary integrity check is success
-    I> dce: Authentication Finalize Done
-    I> Binary dce loaded successfully at 0x836000000
-    (...)
-    DCE: FW Boot Complete
-    
-    # Check the tegra_dce boot_status in the Linux user space
-    $ sudo cat /sys/kernel/debug/tegra_dce/boot_status && echo ""
-    DCE_FW_BOOT_DONE
-    $ sudo rtcwake -d "/dev/rtc0" -m no -s 30 && sudo systemctl suspend
-    ```
+    ```
+    # These messages are shown during early boot stage.
+    I> Successfully register DCE FW load task with MB2 loader
+    I> Partition name: A_dce-fw
+    I> Binary@ device:3/0 block-44800 (partition size: 0x500000), name: 
A_dce-fw
+    I> Ratchet: [A_dce-fw]: sw (BCH): 0, hw (BCT): 0
+    I> dce : oem authentication of header done
+    I> dce : meta-blob integrity check is success.
+    I> dce : will be decompressed at 0x836000000
+    I> dce : decompressed to 12075904 bytes
+    I> dce: plain binary integrity check is success
+    I> dce: Authentication Finalize Done
+    I> Binary dce loaded successfully at 0x836000000
+    (...)
+    DCE: FW Boot Complete
+ 
+    # Check the tegra_dce boot_status in the Linux user space
+    $ sudo cat /sys/kernel/debug/tegra_dce/boot_status && echo ""
+    DCE_FW_BOOT_DONE
+    $ sudo rtcwake -d "/dev/rtc0" -m no -s 30 && sudo systemctl suspend
+    ```
  
  [ Where problems could occur ]
  
  * A firmware update can inherently introduce regressions. However, the
  impact is limited to Jetson Orin devices, and any issues should be
  identified by our automated test jobs during the SRU verification
  process.
  
  [ Other Info ]
  
  * 36.5 is related to Nvidia Jetpack 6.2.2 release:
  
https://docs.nvidia.com/jetson/archives/r36.5/ReleaseNotes/Jetson_Linux_Release_Notes_r36.5.pdf
  
- * Please note that this SRU is only for Jammy, as Noble and subsequent
- releases are already aligned with Jetson Linux v38.2.2.
+ * Please note that this SRU is only for Jammy, since Noble and
+ subsequent releases are already aligned with the Jetson Linux 38.2.2 BSP
+ release (the corresponding update was recently done as part of the LP:
+ #2127473 SRU).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2146610

Title:
   [SRU] Update linux-firmware-nvidia-tegra to 36.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nvidia-tegra/+bug/2146610/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to