Hello,
sudo ./flash.sh -k DTB jetson-nano-devkit-emmc mmcblk0p1
It seems that there are cases when flashing DTB with the following command does not work well.
I have applied dtb flashing several times to activate spi.
It was applied in the beginning, but after that, it seems to not be applicable despite the change in dtb.
Could you please cross-check it?
I think I’ve done it more than 10 times in my experience.
Thank you.
Many developers can do the flash without issue.
What have you changed at the dtb file? Any flash logs? Or error message?
Hello,
I experienced firsthand that dtb does not apply.
sudo ./flash.sh -k DTB jetson-nano-devkit-emmc mmcblk0p1
Instead of flashing only the DTB with the above command
sudo ./flash.sh jetson-nano-devkit-emmc mmcblk0p1
I checked that it was applied when I flashed anew with the above command.
So my suggestion is to test the DTB flashing several times.
Thank you.
Hi,
If you are asking about pinmux setting, then do full flash instead of only updating one partition.
Also, you don’t need to ask duplicated question just for one topic. I know that you already filed several topics just for your spi issue.
Don’t forget that if the “/boot/extlinux/extlinux.conf” has the “FDT” entry naming a file-based device tree, then this gets used instead even if the partition was updated. The exeption being that if security fuses were burned, then it will never use the file-based tree.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.