Hoping Jurgen from auvidea sees this…
The auvidea_j120 device tree is causing u-boot to fail on recent TX1s with a build date of 12-07-2016 (as indicated by the sticker on the TX1’s heat sink).
We have been successfully using auvidea_j120.dtb with our J100’s and TX1 modules with a build date of 07-05-2016.
However, with recently purchased TX1s, and the auvidea dtb specified in extlinux.conf, u-boot fails with the output below. Seems there must be hardware differences in the newer ones.
Scanning mmc 0:1…
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
1014 bytes read in 150 ms (5.9 KiB/s)
p2371-2180 eMMC boot options
1: primary kernel
Enter choice: 1: primary kernel
Retrieving file: /boot/initrd
6902654 bytes read in 456 ms (14.4 MiB/s)
Retrieving file: /boot/Image
19414736 bytes read in 797 ms (23.2 MiB/s)
append: fbcon=map:0 console=tty0 console=ttyS0,115200n8 androidboot.modem=none androidboot.serialno=P2180A00P00940c003fd androidboot.security=non-secure tegraid=21.1.2.0.0 ddr_die=2048M@2048M ddr_die=2048M@4096M section=256M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 debug_uartport=lsport,0 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff2bf000 nvdumper_reserved=0xff23f000 core_edp_mv=1125 core_edp_ma=4000 gpt android.kerneltype=normal androidboot.touch_vendor_id=0 androidboot.touch_panel_id=63 androidboot.touch_feature=0 androidboot.bootreason=pmc:software_reset,pmic:0x0 net.ifnames=0 root=/dev/mmcblk0p1 rw rootwait pcie_aspm=off
Retrieving file: /boot/auvidea_j120.dtb
250594 bytes read in 564 ms (433.6 KiB/s)
Flattened Device Tree blob at 82000000
Booting using the fdt blob at 0x82000000
reserving fdt memory region: addr=80000000 size=20000
Using Device Tree in place at 0000000082000000, end 00000000820402e1
Can’t create DT prop nvidia,emc-training-mod-regs to copy
Can’t create DT prop compatible to copy
Can’t create DT node emc-table@204000 to copy
Can’t create DT prop reg to copy
ERROR: could not update sku property FDT_ERR_NOSPACE.
ERROR: board-specific fdt fixup failed: FDT_ERR_NOSPACE
- must RESET the board to recover.
FDT creation failed! hanging…### ERROR ### Please RESET the board ###