Xa.NX SOM Production Module is not identified .Refer attachment :Xavier NX SOM not detecting.pdf (attachment.zip|attachment Xavier NX SOM Ethernet Port Issue (609.0 KB) ) .
Request you to guide us to resolve this issues.
Meantime , can anyone support us by giving the Problem Escalation Matrix with contact details and to get in touch with INDIA region NVIDIA technical support guys and resolve this issues .
Best Regards,
R.Ramesh
Mobile: ( +91 9600005089).
Email: ramesh@lookman.in
Some information may be useful to you, but this is not in any particular order…
When flashing the Jetson has to be in recovery mode, but steps of adding optional software requires the Jetson to be fully booted. After a flash the Jetson should self-reboot to make it possible to add optional software, but you must first complete the first boot setup (ssh cannot add software if there is no account to log in with).
The IP address for adding optional software can be any valid address of the Jetson. If the flash succeeded and the Jetson fully rebooted, then the micro-B cable attaching between Jetson and host PC (which was used for flash) will begin to show up as a network device. In this case the host PC will have address 192.168.55.100, and the Jetson will have address 192.168.55.1. As a result the host PC should be able to “ping 192.168.55.1”.
If the address does not work, then it could be that your host PC has security enabled such that randomly plugging in a USB network device (which is what the Jetson will appear to be) may be refused. In that case you might watch “dmesg --follow”, and then examine the log lines which appear as a result of plugging in the micro-B USB cable. The MAC address could be used to identify which ethernet device to configure. The use of either the standard Ubuntu network configuration tools could enable this, or my favorite tool, “nm-connection-editor” could enable this. If you don’t have nm-connection-editor, then try “sudo apt-get install network-manager-gnome”.
You could also log in (assuming you completed first boot setup) and use “ifconfig eth0” to see what the wired ethernet address is, and use that address instead of 192.168.55.1.
Hi Wayne,
Please note that there is no issue in USB but Ethernet Port is having connectivity issues and the device ( IP ADD) cannot identified,
FYI- Find the attached reference.
This issue sounds only happen to your carrier board. Could you elaborate what are A1/A2/B1/B2/B3 boards and what “patches” are needed for your board to have working etherent?
Does this issue happen if you put the module on nv devkit?
Those are the real info you should share but not some unclear description.
You cannot expect other people here to understand your own project in the beginning.
Bootlog dmesg.docx (353.2 KB)
Hi Wayne,
Find the attached details related to the bootlog dmesg.
Further i am adding my engineer to respond on the further queries.
Mr.Gnana Prakash