reboot_failed.txt (6.3 KB)
hello rd1,
those error show kernel partition is not found.
[0000.651] Using BFS PT to query partitions
[0000.655] PT: Partition LNX NOT found !
[0001.258] *** Failing over to KFS2.
you may review python pipeline to assign correct configuration files to generate encrypt binaries.
thanks
Hello JerryChang:
I will check it. I have some questions:
1.is BUP just for Bootloader? if I just modify kernel dtb ,used BUP update DTB , is it ok?
2.for kernel, its incluse Image,DTB and many ko files, you said Image can replaced,
DTB used dd refer LNX, for many ko ,is also used replace? do you have better methods?
hello rd1,
DTB and LNX are two different partitions for device tree blob and kernel images,
please check the flash configuration file for the partition layouts.
for example, flash_l4t_t210_emmc_p3448.xml
thanks
Dear JerryChang:
I checked our cfg,but not find why used ./flash.sh --no-flash -k DTB jetson-nano-emmc-smpsd mmcblk0p1 compile error. Please help again, Thank you (2.8 KB)
What kind of error did you hit when you flash with DTB partition?
Nothing is really “compiled” here.
*** Signing smpsd-tegra210-p3448-0002-p3449-0000-a02.dtb ***
./tegraflash.py --chip 0x21 --cmd “sign ./signed/smpsd-tegra210-p3448-0002-p3449-0000-a02.dtb.encrypt”
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0018 ] Generating signature
Error: Not supported
Failed to flash/read t210ref.
smpsd-tegra210-p3448-0002-p3449-0000-a02.dtb.encrypt is not right, it didn’t pad with zero.
hello rd1,
according to post #39, it shows that locally sign and encrypt binary files is not supported for t210 series. (i.e. Jetson Nano).
that’s why you’ll see Error: Not supported messages reported while generating signature.
hence,
it’s an alternative way in post #42, which has enable tegraflash.py to perform sign and encrypt locally.
you should also review the command-line and assign all correct cfg files accordingly.
thanks
Dear JerryChang:
in post #42, I could compile ok,but i check boot.img.encrypt, it also didn’t pad with zero. so ,the method is not work.
hello rd1,
it should be assuming zero key filled, may I know what’s the values padded,
please also check whether there’s any difference by add --key options?
for example,
$ sudo ./tegraflash.py --bct P3448_A00_4GB_Micron_4GB_lpddr4_204Mhz_P987.cfg --bl cboot.bin --cfg flash.xml --chip 0x21 --applet nvtboot_recovery.bin --key NULL --cmd "sign"
boot.img.encrypt (476 KB) generate_log.txt (5.2 KB)
Dear JerryChang:
Does support use “dd” to overwrite LNX partiton to update U-BOOT.
Becaues I manualy paded zero to boot.img.encrypt, and copy to target system,
then used dd if=boot.img.encrypt of=dev/mmcblk0p5 (LNX) and
dd if=boot.img.encrypt of=dev/mmcblk0p9(LNX-1)
after reboot ,but cann’t reboot ,it failed.
I find relevant problems from forum ,this Jetson Nano eMMC U-Boot Field Upgrade said not support dd LNX to update u-boot.
So ,please check it for US ,thank you!
I guess it is probably not support. Even I forget about that too. Sorry about it.
Please directly use BUP updater.
Thank you your reply.
if need update kernle dtb , also use BUP ? it is right?
or you can just add FDT field in extlinux.conf so that the dtb will be read from file system.
How to usd FDT ,I had saw it ,but didn’t remmber .
hello rd1,
please check this CBoot session,
you may update extlinux.conf file, to make CBoot functionality loads the kernel-dtb binary file from FDT entry, instead of partition.
thanks