Hi,
Could you please kindly answer my below questions?
-
Why NVIDIA did not choose UDS-based Flash bootloader solution for firmware update on Aurix MCU in the first place (I am not talking about Xaiver side FW update)?
-
In NVIDIA DRIVE OS 5.2 QNX PDK Developer Guide - MCU Porting Guide, who will provide this “Update Firmware” source code? NVIDIA, Tier 1, or customer?
-
Compared to solution with UDS and Flash bootloader from vector, how to justify the security and safety? MCU porting guide does not talk about security of FW update at all. The proposed“Update Firmware” seems to have full write access to entire memory address of flash memory, which does not seem to be functional safe.
-
Does “Update Firmware” support cold boot/reboot from “secure boot chain”? Vector Flash boot loader does.
-
If we chose UDS-based firmware update, will it have side effects to Xavier side firmware update? We want to know if we have to stick with this NVIDIA “update firmware” solution? If not, what things do we need to pay attention to, so that it will not have side effects to Xavier side firmware update.
Thanks
Y
Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other
Target Operating System
Linux
QNX
other
Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other
SDK Manager Version
1.5.0.7774
other
Host Machine Version
native Ubuntu 18.04
other