On 15/02/18 15:12, Andreas Färber wrote: > Hi Jon, > > Am 15.02.2018 um 15:01 schrieb Jon Hunter: >> On 15/02/18 12:32, Andreas Färber wrote: >>> Am 15.02.2018 um 10:22 schrieb Jon Hunter: >>>> On 15/02/18 01:51, Andreas Färber wrote: >>>>> I would like to test the latest version of U-Boot on the Jetson TX1. >>> [...] >>>>> Here's what I have tried: >>>>> >>>>> $ sudo ./flash.sh p2371-2180-devkit mmcblk0p1 >>>> This should work. Which u-boot binary are you copying and where are you >>>> copying it? >>>> >>>> I copy the u-boot-dtb.bin over u-boot.bin in the L4T directory >>>> Linux_for_Tegra/bootloader/t186ref/p2771-0000/500/u-boot.bin. >>> >>> I downloaded the .rpm from >>> https://build.opensuse.org/package/show/hardware:boot/u-boot-p2371-2180 >>> extracting all of u-boot, u-boot.bin, u-boot.dtb and u-boot-dtb.bin to >>> bootloader/t210ref/p2371-2180/ - and as described it makes a difference >>> in that it then ceases to boot to a U-Boot prompt. >> >> Sorry, looks like I mixed TX1 and TX2. I see you are using TX1. However, >> I believe you are still booting the wrong u-boot file. >> >> If you look at the p2371-2180-devkit.conf you will see that it has ... >> >> DFLT_KERNEL_IMAGE="bootloader/${target_board}/p2371-2180/u-boot.bin >> >> For using the upstream u-boot, we need to use the u-boot-dtb.bin and not >> the u-boot.bin. So you can either ... >> >> 1. Update the p2371-2180-devkit.conf to use the u-boot-dtb.bin that you >> copied. >> 2. Move the u-boot-dtb.bin from your rpm to >> bootloader/t210ref/p2371-2180/u-boot.bin. > > Both in the Nvidia tarball and in our upstream based package builds, > u-boot.bin and u-boot-dtb.bin are identical. Since some time > u-boot-dtb.bin gets copied over as u-boot.bin for consistency upstream. Good to know! > Should this work with the vanilla upstream files, or do they need any > headers or signatures or something? Yes should work fine with vanilla upstream. > Do any of you have that upstream version booting successfully, or might > it be an upstream U-Boot regression? I was so far assuming it's a user > error, so haven't tried bisecting yet. I am using "U-Boot 2017.03". However, I realise that I am currently based upon L4T rel24.2.1 (as rel28.1 was not available when I started using L4T for testing upstream). I hope it would not matter, but you never know. I plan to move to rel28.2 once it is released. If we think it is a problem with rel28.1 I should be able to test my side. Cheers Jon -- nvpublic -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
