Really stuck on this one and cant figure out what the problem is, a friend of mine witch has the exact same revision (B04) on his tx2 (28.2) as i do, but he can not use a “image” file and dtb created on my tx2.
I tar’d down my newly compiled image file from /boot and my dtb, he copy’s the image manually to /boot on the tx2 (and check the permissions) and flashes the dtb from the host with:
sudo ./flash.sh -r -k kernel-dtb -d ./dtb/tegra186-quill-p3310-1000-a00-00-base.dtb jetson-tx2 mmcblk0p1
(like to have it in it’s own folder, faster to flash back the original if something goes wrong).
Flash successfully finished.
This work just like it should on my system, i boots up, finds my Auvideo J20 and finds the IMX219, it also
works on his system, captures video without any problem so that shows the dtb and imx219 driver s working.
But, he losses wifi (my wifi is just fine) , it’s no where to be found, nothing in system settings / network and does not seem to be started at all in dmesg.
So, i decided to send him a more resent version of my dtb and image today, that i fix some imx219 problems in (again works perfect on my tx2) but now he got to the nvidia login screen and it he pressed the password box the screen turn blue, and is now blue on every reboot.
easily fixed by doing a:
sudo ./flash.sh -k kernel jetson-tx2 mmcblk0p1
and a :
sudo ./flash.sh -r -k kernel-dtb jetson-tx2 mmcblk0p1
in recovery, but why does this happen ? copying the kernel and flashing only that dtb should be fine, or am i missing something ? :)
btw, i build the kernel by using https://github.com/jetsonhacks/buildJetsonTX2Kernel and then i build the dtb by doing a sudo make all in src/kernel/kernel4.4
Include the dmesg from his system,dont mind the J20 / imx219 errors, he had video, and the errors are now fixed, but it got worse as you can read…
mydmesg.log (85.5 KB)