Hello.
Can I avoid the UEFI setup screen when my orin starts up? I’ve noticed that this screen uses a lot of power, and since I’m using a battery to turn on the orin , it’s causing it to not start up properly.
My battery had the capacity to supply 10A.
Below is the reply from the carrier board vendor.
For the power issue, unfortunately it looks like the battery that you’re using to power the board cannot sufficiently supply current to boot the AGX Orin module. The UEFI bootloader handling is done by NVIDIA with the Orin module and we are unable to do anything to reduce the current being requested from the Orin.
Are you using the custom carrier board for AGX Orin?
What’s your Jetpack version in use?
Which screen do you mean? Could you share the image for the screen you mean?
UEFI is the bootloader for the board to load the kernel and it could not be disabled or removed.
If you mean the UEFI menu (which could be entered through press ESC during boot up), it could be disabled through modifying the UEFI binary.
From your serial console log, it seems stuck in UEFI. Could you boot up the board successfully?
Hi, Kevin.
Yes. The board is a custom carrier board(AGX202)
Currently, when I boot up using a battery(12V10A,15AH), sometimes the orin will not able to boot into the system, it will stuck at the UEFI due to the voltage issue.
(Video show Battery Power Issue)
The serial log is the log that when I power up the orin by battery, the orin board is unable to boot up. This is due to during the UEFI process, the orin may have performed some self-checking, during this checking, it will consume a lot of current which causes the voltage drop.
So my inquiry is want to know if we can turn off this ‘self-checking’ thing so that when we start up with the battery, it doesn’t use up a lot of current and make the voltage go down.
Hi, Kevin.
I think the stuck is due to high current consumption and causing voltage drop during the boot process. The voltage drops causing the orin unable to power up and then shut down. I looking for a regulator to let it work. Since currently, if I want to power orin successfully, I have to use a steady dc source. I don’t think I am able to build the UEFI when in battery mode. Since unable to power up with the battery source.
Hi, Kevin.
So, after updating to debug UEFI, we use the battery to power the board. Then, we check which part of UEFI gets stuck. Am I correct？
Thanks for your help again.
And after installing debug UEFI, how do I create the log data for investigation? Is it just plug in the serial monitor cable on the carrier board and record the serial log like what I had sent before in this topic?
After the UEFI build, I just had to replace the uefi_jetson.bin file inside the AGX202 Carrier Board BSP file(AGX Orin L4T r35.4.1 BSP) with the build UEFI and flash it? After flashing, and monitoring the serial log, should I had to reflash back to the original BSP file? Will it affect the normal use of the orin with agx202 carrier board when is using custom UEFI built without flashing back to the original BSP file?
Below is the link for the carrier board BSP for your information. L4T Carrier Board BSP
Hi, Kevin.
For the clone, does it mean to copy the current UEFI Source first before flashing the built UEFI?
Can I just reflash the BSP from Connect Tech AGX 202 without any modification after the Debug? If yes, then should I clone for the UEFI source?
I installed the regulator and the problem was solved.
The regulator spec is 8-40V input with 12V20A output. The battery spec is 12V15Ah(9-12V Voltage when using), maximum output of 10A.