How to display the boot menu?

I checked on Linux, Windows and Mac with 2 different cables. When connected to the Micro-USB port I do not get any USB device to connect to.

I connected the cable from the Xavier Micro-USB port to an USB-Hub with indicator lights. You can see all indictors light blue except the cable coming from the devkit micro-usb. Looks like there is no power on that micro-usb port. If you connect the Devkit Micro-USB to the common USB the Xavier cannot find its own serial console on ttyUSB.

Hi,

Just to clarify… is this your first time using device after flash the board?

Do you finish the user account configuration?

I don’t understand why you can do any “login” on ttyACM0. It does not provide such function.

Also, to save both of our time, how about you paste the log you see?

And please do not connect to a usb hub… it is a UART interface. Just directly connect micro usb cable from xavier to your ubuntu host.

I did the direct connection to Ubuntu, Windows and Mac but there is no ttyUSB or COM-Port to connect to. No even the Xavier itself can see any /dev/ttyUSB after connecting the Micro-USB port to the regular USB port.

The sdkmanager reported “finished succesfully” in step 4. So account configuration is finshed, all the NVIDIA packages installed and the device got rebooted several times after flashing. I just checked. When connecting the fully installed Xavier to the host via the USB-C cable of the flash port I still see “NVIDIA Corp” when issuing “lsusb” on the host. So the obviously the network bridge sdkmanager is using to install the packages is still active. I mean it is extremly useful for headless configurations. So please keep it.
Which log you mean? I never see any log on the USB-C serial port.

Hi,

Err… just want to confirm, so do you know you have to configure user account through monitor or OEM config after you flash the board?

The sdkmanager reported “finished succesfully” in step 4. So account configuration is finshed

Which log you mean? I never see any log on the USB-C serial port.

You said "On Linux I see it as /dev/ttyACM0. I can again login ". I want to check what kind of login do you see on ttyACM0…

Yes, I wouldn’t know how to login without user configuration.

I see no other messages than the login. As soon as I reboot the USB-C flashport connection via /dev/ttyACM0 is lost which probably should not happen for a debug port.

Hi,

I just tried on my device

  1. Yes, /dev/ttyACM0 is able to login. Not sure if this is a new function added in latest release. I didn’t use this before. However, this interface only prints after kernel is ready. And the boot menu is in bootloader, so this interface does not help.

  2. I can still see /dev/ttyUSBx interface on my side.

  3. May I ask what was your method to configure user account? Are you using ttyACM0 too?

  4. Does this micro usb cable directly connect to host? There should be no hub in-betwen.

I notice your lsusb does not show FTDI serial device there. But we have it on our host.
And it would be mounted as /dev/ttyUSBx device on our side.

1.) Brilliant feature for headless systems!
My guess is that they didn’t disable the network bridge after installing the NVIDIA packages during the sdkmanager setup.
2.) Maybe mine is broke? Can you connect a USB-Tester to it?
3.) No, I use the on-monitor configuration steps after flashing the basic L4T base os, before installing the NVIDIA packages like CUDA, TensorRt etc.
4.) Yes, the same way as the cable to the USB-C flashport

Hi,

2.) Maybe mine is broke? Can you connect a USB-Tester to it?

Could you check the dmesg on host before and after you plug the micro usb cable to xavier? Want to see what log is printed there.

Can you show me the line of the device with lsusb?

There should be something like below when you connect the micro usb to host and Xavier.

Bus 001 Device 034: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC

Could you grep lsmod on your host and see if there is a kernel module named “usbserial”?

By default no usbserial module is loaded on my host. I loaded it via "modprobe ftdi_sio`
After that with lsmod I see “usbserial 53248 1 ftdi_sio”.
With dmesg -w I dont see any change in when connecting to the micro-usb debug port different to the flash USB-C port. (Output below is connection to USB-C flashport)

[ 4887.535859] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2: link is not ready
[ 4887.544795] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2i5: link is not ready
[ 4887.544966] IPv6: ADDRCONF(NETDEV_UP): enp0s20u2i5: link is not ready
[ 4887.589434] cdc_ncm 3-2:1.5 enp0s20u2i5: 425 mbit/s downlink 425 mbit/s uplink
[ 4887.621455] cdc_ncm 3-2:1.5 enp0s20u2i5: 425 mbit/s downlink 425 mbit/s uplink
[ 4887.653446] cdc_ncm 3-2:1.5 enp0s20u2i5: network connection: connected
[ 4887.653484] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s20u2i5: link becomes ready
[ 4888.436151] scsi 10:0:0:0: Direct-Access Linux File-Stor Gadget 0409 PQ: 0 ANSI: 2
[ 4888.436607] sd 10:0:0:0: Attached scsi generic sg4 type 0
[ 4888.437097] sd 10:0:0:0: [sdd] 32768 512-byte logical blocks: (16.8 MB/16.0 MiB)
[ 4888.437294] sd 10:0:0:0: [sdd] Write Protect is on
[ 4888.437297] sd 10:0:0:0: [sdd] Mode Sense: 0f 00 80 00
[ 4888.437432] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4888.438741] sdd:
[ 4888.439730] sd 10:0:0:0: [sdd] Attached SCSI removable disk
[ 4916.906890] usb 3-2: USB disconnect, device number 3
[ 4916.907004] rndis_host 3-2:1.0 enp0s20u2: unregister 'rndis_host' usb-0000:00:14.0-2, RNDIS device
[ 4916.960814] cdc_ncm 3-2:1.5 enp0s20u2i5: unregister 'cdc_ncm' usb-0000:00:14.0-2, CDC NCM
[ 4917.497004] usb 5-1: reset high-speed USB device number 2 using xhci_hcd

Do you mean the log give no response after you plug the cable?

Sounds like the port is broken…

Yes, exactly. Do you have an USB-Tester at hand to confirm the assumption? When you connect the tester to the port I would expect it to show some voltage.

No, I don’t have it. I think it does not help to do this on my side. Do you have other xavier module or devkit to check?

Just try to compare if you can see ttyUSB on other device.

I had another Xavier in the car. And guess what. The /dev/ttyUSB0 came alive once before also this one died. There is 4.997V on the host PC USB cable. I see no reason do die.
Funny enough the 2nd Xavier is running Jetpack 4.2.2 but also I get a login on /dev/ttyACM0 when connecting to the flash-port USB-C

[  465.473041] usb 3-2: Manufacturer: FTDI
[  465.473451] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
[  465.473484] usb 3-2: Detected FT4232H
[  465.473620] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
[  465.473740] ftdi_sio 3-2:1.1: FTDI USB Serial Device converter detected
[  465.473769] usb 3-2: Detected FT4232H
[  465.473878] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB1
[  467.558891] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[  467.558927] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[  467.558931] ftdi_sio 3-2:1.2: FTDI USB Serial Device converter detected
[  467.558983] usb 3-2: Detected FT4232H
[  467.559006] ftdi_sio ttyUSB0: urb failed to clear flow control
[  467.559046] ftdi_sio ttyUSB2: Unable to read latency timer: -71
[  467.559140] ftdi_sio ttyUSB2: Unable to write latency timer: -71
[  467.559173] ftdi_sio ttyUSB0: failed to get modem status: -71
[  467.559207] ftdi_sio ttyUSB0: urb failed to clear flow control
[  467.559266] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB2
[  467.559439] ftdi_sio 3-2:1.3: FTDI USB Serial Device converter detected
[  467.559485] usb 3-2: Detected FT4232H
[  467.559524] ftdi_sio ttyUSB3: Unable to read latency timer: -71
[  467.559598] ftdi_sio ttyUSB3: Unable to write latency timer: -71
[  467.559694] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB3
[  467.559827] usb usb3-port2: disabled by hub (EMI?), re-enabling...
[  467.559835] usb 3-2: USB disconnect, device number 4
[  467.559940] ftdi_sio ttyUSB0: error from flowcontrol urb
[  467.560045] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[  467.560058] ftdi_sio 3-2:1.0: device disconnected
[  467.560206] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[  467.560221] ftdi_sio 3-2:1.1: device disconnected
[  467.560328] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
[  467.560342] ftdi_sio 3-2:1.2: device disconnected
[  467.560445] ftdi_sio ttyUSB3: FTDI USB Serial Device converter now disconnected from ttyUSB3
[  467.560460] ftdi_sio 3-2:1.3: device disconnected
[  468.101067] usb 5-1: reset high-speed USB device number 2 using xhci_hcd