I would like to re-flash my jetson to use uboot. I am learning about all the intricate details of linux now, so I am still somewhat of a newbie. I have seen several discussions on uboot in the forum. For example, in this post (https://devtalk.nvidia.com/default/topic/762653/?comment=4270358) linux_dev mentions that 19.3 now supports the ability to flash uboot, but I have not yet found any description of how to actually do it. I tried looking through the flash.sh file to see if that would give me some hints. It seems to need to be pointed to a uboot script, but I have no idea where that would be or if there are other options I would need. Does anyone have a detailed set of steps for how to flash uboot to the jetson and test it?
The “Getting started” section in the documentation package has quite detailed info.
This should do it (it deletes everything, so take a backup first, if needed):
sudo ./flash.sh -S 14GiB -L bootloader/ardbeg/u-boot.bin jetson-tk1 mmcblk0p1
The -S 14GiB option makes a 14GB partition instead of the default 4GB (IIRC). It takes ages to flash.
Thanks, I will give that a shot. As for the documentation, perhaps that is something I have been missing. I have read through the quick start guide, the technical reference manual, and looked at the documents available on the TK1 support site and Linux for Tegra site, but did not see the info you are talking about. It sounds like I have missed an important chunk of documentation. Can you point me to the docs you are talking about so I can read through those as well? Thanks for your help.
Check the “Documentation” link under the “Additional Information” section.
DOH! I downloaded that at one point, but did not actually read through the Tegra_Linux_Driver_Package_Developers_Guide.pdf file because I thought it was just about driver development. Thanks, I will give that a read.
For hints on flash.sh, run it with no arguments…it’ll print a help summary. Also be aware that the L4T version of Ubuntu has been around for quite some time and has covered other nVidia hardware and not just Jetson…so some of it was generalized or not tweaked for Jetson. Even going from release R19.2 to R19.3 has produced changes which documentation does not reflect.