The Jetson TK1 SoC is a tegra124, the TX1 SoC is the tegra210. In default configs you will find tegra21_defconfig (there variations of K1, those are tegra12x, while variations of TX1 would be tegra21x). There is also a tegra_t210ref_gnu_linux_defconfig, but I’m unsure what the differences are…maybe it is related to some of the 32-bit runtime stuff.
I have not yet looked at the u-boot source, but this may be named after the board the tegra210 sits on, and not just the tegra210. In the TX1’s “/boot/extlinux/extlinux.conf”, notice that the firmware file is named “tegra210-jetson-tx1-p2597-2180-a01-devkit.dtb”. The “p2597-2180-a01-devkit” refers to the module board sitting on the developer carrier board. When you look at u-boot I suspect naming will include these board names if there is a board-specific config required (I have not checked, but boot support is about handing off working infrastructure…everything outside the SoC…to the kernel).
Looking at the u-boot source, I see “arch/arm/”, but I do not see “arch/aarch64/”. This would suggest that u-boot has not been updated for 64-bit. Although u-boot hands off to a 64-bit kernel, there would be no reason why u-boot itself needs to be 64-bit unless u-boot is setting up memory/hardware exceeding 32-bit range. My guess would be to try with only 32-bit “ARCH=arm”. There is still a choice between bare metal and gnueabihf compilers…I’m guessing both would work, but I’d suggest trying each starting with the gnueabihf (this is because this is a compiler you’ve already installed from an Ubuntu repository if you followed the kernel cross-compile docs).
Where is "p2597-2180_defconfig" ?
I am also try to build u-boot for TX1, I was able to use tag name "tegra-l4t-r23.1" to "source_sync" u-boot but was unable to find "p2597-2180_defconfig" in configs directory of u-boot.
Thanks you for your help.