why my jetson can’t detect any usb anymore in uefi
that inculdes keyboard, mouse, usb stick…
only in ubuntu it can detect but i dont want to use uart to modify settings in uefi
is this a bug??? how to reflash uefi without reflash whole system?
and reflash jetpack is not working (i see some log like it didn’t reflash it for some reason)
Hi leonpano,
Are you using the devkit or custom board for AGX Xavier?
What’s your Jetpack version in use?
You could refer to the following instruction to build UEFI.
Build without docker · NVIDIA/edk2-nvidia Wiki · GitHub
It seems a known issue and has been fixed in r35.3.1-updates branch.
You could use the following command to clone it.
edkrepo clone nvidia-uefi-r35.3.1-updates NVIDIA-Platforms r35.3.1-updates
latest version
newly flashed
i get a error when i am building
BUILDLOG_Jetson.txt (59.9 KB)
fixed by installing sudo apt install acpica-tools
how to flash it?
(builded on jetson and how to flash on jetson?)
@WayneWWW help (可以用中文台灣)
Please just replace Linux_for_Tegra/bootloader/uefi_jetson.bin with your built uefi_Jetson_RELEASE.bin and re-flash the board to apply it.
it works
but is there a way to flash without reflash ubuntu?
or how to update uefi(in normal pc update uefi will not erase your system installation and data)
You can clone the rootfs. Then, during flash, name the clone as the operating system instead of generating a default image from scratch.
It is a good idea to have a backup anyway. Incidentally, clone produces a “raw” file which is a bit-for-bit exact copy of the rootfs, plus it produces a smaller “sparse” file (the size of which is basically the non-empty filesystem content, and the size approaches the raw image size as the filesystem fills up). Raw files are enormous, and take a long time just to copy from one place to another; sparse files are still at least a couple of GB on an empty system, so those are significant as well. It is a really good idea (™) to save the raw filesystem somewhere safe. Either raw or sparse can be used if you flash with the option to “reuse rootfs” when the clone is renamed as “Linux_for_tegra/bootloader/system.img”. The sparse file is faster to flash, but the raw filesystem can be loopback mounted, examined, and modified or updated (e.g., you could later use rsync to update the raw clone).
usb 2.0 speed
are you kidding me?
spicaly i have 2TB nvme ssd
it would be much easier when is able to flash uefi directly
I’m not sure what the question is from “usb 2.0 speed”.
Because you ask me to backup drive
But to backup my nvme on board via that micro usb port is only usb2.0
Issue here is is way too much time consuming
Yes, there isn’t much I can do about time. The size of images will be quite large, and you are correct that if you could use USB3 instead of USB2 it would be faster. There isn’t anything which can be done to use a faster USB spec on the micro-OTG port, the wiring just doesn’t exist other than for USB2. Now if this board supports flash over the USB-C, I don’t know…but if it does, then this would be dramatically faster. I’m thinking an AGX Xavier should use the micro-OTG only for serial console, and the USB-C for flash.
There is a second issue though, and that might be one of signal quality. When USB plugs in, it tries to run at the max speed the USB from the external device announces, but if it cannot, then it’ll back off to a lower speed. Can I verify you’re using the USB-C (or tried it)?
That is agx Xavier
But I have Xavier nx
linuxdev via NVIDIA Developer Forums <notifications@nvidia.discoursemail.com>於 2023年6月23日 週五，上午12:08寫道：
This is the AGX forum so I thought this was an AGX. An NX is “much” the same, but the connectors are not as “abundant” on the NX, so that is a problem. For those connectors which are USB2 there really is no way around it unless you can switch to a USB3 connector, but if for some reason USB3 is throttled back to USB2, then sometimes a different cable or going through a HUB as a kind of RF “adapter” will work. It just depends.
I think I was not found Xavier nx in option
You could use the following command to update uefi partition only.
sudo ./flash.sh -r -k cpu-bootloader jetson-xavier mmcblk0p1
I have nvme drive not sd card
There are two models of Xavier NX modules out there (well, more if you consider memory sizes, but the basics are two models): One has onboard eMMC memory, and requires a third party manufacturer’s carrier board; the other is the dev kit, which has no eMMC, and must use an SD card to boot. eMMC models with third party carrier boards have any SD card slot on the carrier board, whereas an SD card model of dev kit has the SD card slot on the module itself. The model of SD card being on carrier board versus on the module changes things, but most people here are speaking of the SD card dev kit. You’ll want to be very specific when asking about NVMe drive questions in stating the exact model you have.
FYI, this is the forum I speak of for the Xavier NX:
https://forums.developer.nvidia.com/c/agx-autonomous-machines/jetson-embedded-systems/jetson-xavier-nx/258
(we know you are using the NX now, but it isn’t certain which model you are using)
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.