We run that script and following is the output
Linux_for_Tegra$ sudo ./l4t_create_default_user.sh -u nvidia -p nvidia
Creating: Username - nvidia, Password - nvidia, Autologin - false
Adding user 'nvidia' to group `gdm' ...
Adding user nvidia to group gdm
Adding user 'gdm' to group 'video' ...
Adding user gdm to group video
later we ran SDK Manager for further steps (image flash and component install). Flashing went well and again we reached to the component install page. Here, by default 192.168.1.55 is given to connect over USB. But it is failing always as TX2 gets reset after flashing and comes out of recovery mode. But what we found is TX2 has picked old IP (192.168.1.138) and we are able to login through SSH.
Question: In JetPack v3.3, SDK Maganer used to provide IP details but in v4.2.1 we are not seeing that, could you let us know how to get it?
Since, 192.168.1.138 was working we used it instead of 192.168.55.1. It worked to some extent and failed with some errors (probably due to “dpkg: error: dpkg frontend is locked by another process”).
So, we thought of doing entire process one more to make sure if it is working. But this time things were little strange. For IP 192.168.55.1, SDK manager is trying with SSH and for 192.168.1.138 it is looking for USB connection. Following are logs:
15:37:29 INFO : Flash Jetson TX2 : command finished successfully
15:37:29 INFO : install 'Flash Jetson TX2' success
15:39:46 DEBUG : running command < [ `lsusb | grep -c "NVidia Corp"` -ne 1 ] >
15:39:47 INFO : command finished successfully
15:39:47 DEBUG : running command < [ `lsusb | grep -c "NVidia Corp"` -gt 1 ] >
15:39:47 ERROR : command terminated with error
15:39:48 ERROR : Could not detect Nvidia Jetson device connected to USB. *To validate if the device is in connected correctly, run 'lsusb' command on your host, and look for "0955:7c18: NVidia Corp".
15:40:04 DEBUG : running command < nc -z -vv -w 5 192.168.55.1 22 >
15:40:09 INFO : nc: connect to 192.168.55.1 port 22 (tcp) timed out: Operation now in progress
15:40:09 ERROR : command terminated with error
15:40:09 ERROR : Cannot connect to the device via SSH.