We finally figured out our serial issue, here is the serial output.
orin_boot_debug.txt (18.1 KB)
If this is custom board, then you need to disable the cvb eeprom read because most of custom board does not have eeprom on it. That is what your serial output told.
Our latest serial output.
Where can I look up these error codes?
[0048.465] I> Task: Load MB2/Applet/FSKP (0x5000ca55)
[0048.470] I> Loading MB2 Applet
[0048.473] I> Slot: 1
[0048.476] E> BLOCK_DEV: Failed to open blockdev.
[0048.481] E> LOADER: Failed to open blockdev 0(0).
[0048.486] E> LOADER: Failed to get storage info for binary 21 from loader.
[0048.493] C> LOADER: Could not read binary 21.
[0048.498] E> Failed to load MB2
[0048.501] C> Task 0x0 failed (err: 0x27228311)
[0048.505] E> Top caller module: MB2_PARAMS, error module: LOADER, reason: 0x11, aux_info: 0x83
[0048.513] C> Boot Info Table status dump :
1
Any reason for this. Also our flash issue seems to be related to:
/sys/class/udc/3550000.xudc directory, 3550000.xudc hardware not being initialized
I think you are talking about 2 questions here.
If your board directly got failure in " Failed to load MB2", then you won’t see anything from 3550000.xudc.
Thus, please clarify why you are talking about 3550000.xudc here.
And it does not matter to analyze the error code. Even I shared you the error code, there is nothing you can do. How you flashed the board matters but not the error code.
Did not mean to confuse the issue. The 3550000.xudc issue is related to some problem we will have once we get past this error. I am more interested in why my MB2 load failed. I got rid of the eeprom read sizes but am still seeing this MB2 error.
Then you should clarify how you flash the board now. I remembered that we had another post and you could flashed board at that time?
Something went wrong with the board I was using so I tried another one of our carrier boards and it would flash using:
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --network usb0 --showlogs jetson-orin-nx-varmint-ai external
I noticed now after flashing it and booting I get no cooling fan running and here is my serial log. Not sure why I am not booting, any input would be very helpful.
seriallog.txt (84.8 KB)
From your log:
[ 16.359248] Please complete system configuration setup on the serial port provided by Jetson’s USB device mode connection. e.g. /dev/ttyACMx where x can 0, 1, 2 etc.
First boot requires user to configure the user account. Otherwise the boot will not proceed.
I am getting a UEFI boot shell> prompt now, not sure what to do with that?
Connect the flash cable to the flash port and open /dev/ttyACM0 on your host side to configure the account.
It could be display not able to show GUI so you are not able to configure user account.
If even /dev/ttyACM0 does not appear, then we will have other alternatives to configure.
But one more thing here is, I think this issue is already not related to your topic. I mean, it looks like your flash issue is already gone.
Yes we are flashing now. I just need to figure out how to get Linux to boot from the UEFI.
Your board is already booting from UEFI in previous comment on 6/15. I don’t know how you ruined it …