Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other
Target Operating System
Linux
QNX
other
Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other
SDK Manager Version
2.1.0
other
Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other
Issue Description
I have an Orin dev kit, and I want to deploy a new kernel I built.
I don’t want to deploy any other partitions. Is there a simplified process I can use?
In the past, I have used the Nvidia docker, copied a whole bunch of images into seemingly arbitrary locations in the docker, run bind_partitions
, and then bootburn
. This is complicated, error-prone, and takes a long time.
I realize that those tools are very flexible. But I don’t need flexibility, I need simplicity.
Can someone direct me to a low-level tool that will allow me to just copy a single partition?
Are there instructions for manually editing partitions and copying files over USB?
Dear @dwuertele,
Updated the topic description by removing unused sections(Error string and Logs).
Did you follow Compiling the Kernel (Kernel 5.15) | NVIDIA Docs,
Is it like you want to avoid reflashing and update the target directly to get new changes?
I am not using the Compiling the Kernel (Kernel 5.15) | NVIDIA Docs, I built my own kernel. My problem is not building the kernel. My problem is that bind_partitions and bootburn are more general than I need.
Regarding whether I want to avoid “reflashing”. I want to use USB to update just the target flash kernel partition with my newly built kernel image. Is that not reflashing? I guess it is not reflashing everything, it is reflashing just the kernel.
Dear @dwuertele,
The flashing is supported only via bootburn command. Please see the usage at Bootburn Usage | NVIDIA Docs
It means you have kernel image in USB and wants to flash the image from USB? If so, it is not supported
What does “have kernel image in USB” mean? I have the kernel image on my workstation storage in a filesystem. I want to transfer that kernel image to the Orin kernel partition over USB. I believe this is possible. Bootburn does it by calling nvimage and adb. But bootburn does so many things that I do not need it to do. I can see it running many thousands of programs, and it does this for all of the partitions. I don’t need to modify any of the other partitions, just the kernel. I could reverse engineer bootburn but it would save me a lot of time to just call the sequence required for the kernel. Probably something like tegrasign, nvimage, and adb.
Dear @dwuertele,
did you check bootburn -u option. please see Bootburn Usage | NVIDIA Docs
How do I find the partition name?