Jetson tk1 flashing

After flashing my jetsontk1 device, GUI is not show on display , and when i am taking access from minicom , network adapter is unavailable, can any one one please tell me which is the best way to flash the jetsontk1 with graphics and network drivers.

Thanks
Saurabh

Flash normally has all graphics and networking. If you use command line the “sudo ./apply_binaries.sh” step is what adds this in (note that without “sudo” it won’t work right). So the question occurs, do you use JetPack or command line? I actually recommend command line if you have any issues, and then run JetPack after for additional packages.

In the case of command line I’ll summarize. Download driver package, unpack, this will have “rootfs” subdirectory. In that directory unpack sample rootfs using “sudo” (not using sudo will cause failure). Then from rootfs:

cd ..
sudo ./apply_binaries.sh
# Make sure the JTK1 is in recovery mode and micro-B USB connected.
sudo ./flash.sh -S 14580MiB jetson-tk1 mmcblk0p1

I was follow above steps , but still network adapter is not showing , and result of ifconfig -a is given below

ubuntu@tegra-ubuntu:~$ ifconfig -a
dummy0 Link encap:Ethernet HWaddr a6:23:ee:b2:f1:6d
BROADCAST NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ip6tnl0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1452 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1600 errors:0 dropped:0 overruns:0 frame:0
TX packets:1600 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:127360 (127.3 KB) TX bytes:127360 (127.3 KB)

rmnetctl Link encap:IPIP Tunnel HWaddr
NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

That is unexpected to not see eth0 with the “-a” option…the adapter should definitely show up there even if not configured. One reason to not show up is a lack of driver, but if your flash was correct then I’d expect the driver to be there.

Just to verify that the flash image was not truncated on your host, within the “Linux_for_Tegra/bootloader/” look for file “system.img.raw”. Use “ls -l”, what is the exact byte size of that file?

Following are the size of system.ing.rwa

-rw-rw-rw- 1 root root 15032385536 Mar 16 20:06 system.img.raw
-rwxr–r-- 1 root root 2369111428 Mar 16 20:07 system.img

Today i also trying with jetpack but still network adapter and GUI iss not showing .

Is there any option to install network drivers manually?

Your image size corresponds correctly to flash parameter “-S 14GB”, so image is not truncated. There is no chance that a correct flash would not include the driver for the ethernet, I have to conclude that there is an error.

What is the output from this:

dmesg | egrep -i '(r8169|eth0|ethernet|link up|link down)'

dmesg | egrep -i ‘(r8169|eth0|ethernet|link up|link down)’

Result is following

[ 3.870678] ata1: SATA link down (SStatus 0 SControl 300)
[ 10.519900] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Looks like the hardware was never detected (there would have at least been an attempt to load a driver or mention the lack of a driver). I doubt the flash was responsible for it, and I hate to say it, but it seems ethernet hardware is gone. At this point all I can suggest is RMA (I believe no amount of flashing will change this, something as simple as a power surge could have done the damage). The RMA instructions can be found near the top of this URL:
https://devtalk.nvidia.com/default/topic/793798/embedded-systems/some-jetson-web-links/