I tested already without massflash image, it also have the same behaviour. There is no error in image creation - both internal QSPI and external.
It has nothing to do with Disk encryption as this also has the same behaviour WITHOUT disk encryption and the boot stays in recovery mode after flashing is finished. When I don’t use --external-only flag in the command, the board can boot up successfully. But we don’t want to use --external-only flag, as we don’t want to flash emmc , but just nvme.
INFO: The board I am flashing to is a fused board so does it have anything to do with fusing while flashing appended images ?
This command works fine for setting Boot order by setting it to QSPI via BootOrderNvme and also generating image for nvme. However, in flash.sh, there is a check as shown below which fails:
if [[ "${rootdev_type}" == "external" && "${disk_enc_enable}" -eq 1 ]]; then
echo "Error: When disk encryption is enabled, root device cannot be ${target_rootdev}"
exit 1;
fi;
If we comment this check, the massflash image works successfully.
Could you please comment if it is fine to comment this check or should we generate the massflash image only via appending QSPI and external images for NVME as the --append solution doesn’t seem to work for us ?
is image flash actually done? could you please also attach the complete flash messages for reference.
do you have UART connection for gathering console logs for checking the status?
let’s narrow down this with single target only.
according to your flash command-line, do you have target fused with PKC+SBK?
Case 2: Jetson successfully get flashed and boots up from NVME ; however we have to comment the check for disk encryption and root device as mentioned before.
please helps me to understand the difference between case-1 and case-2.
don’t you comment-out the if condition within flash.sh for case-2? it should related to disk encryption.
case1 : we generate internal QSPI image and then using --append to use with external image ( --external-only) with disk encryption.
In this case, after flashing , jetson can’t boot up successully and stays in recovery mode. I didn’t comment the check in flash.sh in this case.
Case2 : we don’t use ( --append --external-only ) flags, we directly create massflash image but use " -c bootloader/t186ref/cfg/flash_l4t_t194_qspi_p3668.xml"
within -p option as below:
In this case, we do comment the check in flash.sh but that doesn’t stop creating massflash image and flashing it on jetson .
This works fine as expected and jetson could boot up successully with disk encryption enabled.