Retrieving file: /boot/rootfs.img
406904035 bytes read in 326996 ms (1.2 MiB/s)
Retrieving file: /boot/Image
20280368 bytes read in 537 ms (36 MiB/s)
append: console=ttyS0,115200n8 console=tty0 OS=l4t console=ttyS0,115200n8 console=tty0 OS=l4t fbcon=map:0 net.ifnames=0 net.ifnames=0 memtype=0 video=tegrafb no_console_suspend=1 earlycon=uart8250,mmio32,0x03100000 nvdumper_reserved=0x2772e0000 gpt tegraid=18.1.2.0.0 tegra_keep_boot_clocks maxcpus=6 androidboot.serialno=0320318054817 bl_prof_dataptr=0x10000@0x277240000 sdhci_tegra.en_boot_part_access=1 initrd=/boot/rootfs.img rw rootwait
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
starting USB...
No controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No controllers found
ethernet@2490000 Waiting for PHY auto negotiation to complete...... done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.100.48 (355 ms)
*** Warning: no boot file name; using 'C0A86430.img'
Using ethernet@2490000 device
TFTP from server 0.0.0.0; our IP address is 192.168.100.48; sending through gateway 192.168.100.1
Filename 'C0A86430.img'.
Load address: 0x80080000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: /boot/extlinux/pxelinux.cfg/01-00-04-4b-a8-1c-d4
ethernet@2490000 Waiting for PHY auto negotiation to complete...... done
:
:
I tried
“sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1”
result was the same
FDT worked until the R28.1 release when the TX1 and TX2 began using a unified sample rootfs configuration. The boot itself got somewhat more complicated since the two boot differently, and device tree content was moved into other partitions (see “gdisk -l /dev/mmcblk0” for a list of partitions). Part of device tree is used for different stages of boot, e.g., there is a cboot stage device tree, U-Boot stage device tree, Linux kernel device tree, and so on (it actually gets a bit finer than that, but I haven’t read that deeply). Each stage will of course inherit the prior stage to some extent because the hardware will have been set up. The flash script puts the right content in the right place. Details differ depending on release (see the R28.1 customization docs).
Device tree is supported, FDT as a method of using it is not (yes, it is inconvenient). In R28.1 you are probably interested in flashing the “DTB” partition (mmcblk0p13 under R28.1).
The story behind this is from cboot. dtb is picked from DTB partition, and cboot would add some key entries before passing to u-boot. Earlier BSP does not have such change and thus it was working.
For your usecase, plugin-manager seems lose lots of info from DTB. I believe those missing info is added by cboot.