Hi, I’m following the official documentation about enabling Secure Boot on Jetson Orin devices. I have tried to test burning the fuses with this command:
, which produces no errors. As far as I know, the Jetson Orin Nano Super model is the same as the Jetson Orin Nano model hardware-wise, so I wonder if using jetson-orin-nano-devkit-super instead of jetson-orin-nano-devkit for the <target_config> would be valid and provide any benefit here. Thank you.
Hi Jerry, thank you for the answer. I have burned the fuses and now am trying to do QSPI setup for the device. I used this command: sudo ./tools/kernel_flash/l4t_initrd_flash.sh \ --no-flash \ -u ~/keyvault/ecp521.pem -v ~/keyvault/sbk.key \ --uefi-keys ~/keyvault/uefi_keys/uefi_keys.conf \ --uefi-enc ~/keyvault/gen_ekb/sym_t234.key \ --network usb0 \ --showlogs \ -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \ jetson-orin-nano-devkit-super internal
Although I have tried multiple times, the script always stops at “Step 2: Generate rcm boot commandline” with the error:
ECID is
Error: No Board Spec. and no target connected, exit.
Cleaning up…
according to the error log.. Error: No Board Spec. and no target connected, exit.
did you have device connected to your host machine?
if yes,
it might be the issue of USB autosuspend function is enabled by default.
please try disable autosuspend on host machine with below command. sudo -s echo -1 > /sys/module/usbcore/parameters/autosuspend
Hi Jerry, the device was connected to the host machine all the time. Disabling USB auto-suspend function with your command works perfectly. Thank you so much for your help!