M2 USB-to-PC Jetson Xavier AGX Error

Reach Module / M+ / M2 Hardware integration
1

Hello,

I am trying to use the M2 with the Jetson Xavier AGX Development Board. I am connecting the M2 through the usb cable but the M2 is not starting up correctly. The only LED status that is on is the Orange one and the others are off.

Using dmesg I can see the following:

[ 1196.312143] usb 1-2.4.4: new high-speed USB device number 13 using tegra-xusb
[ 1196.333013] usb 1-2.4.4: New USB device found, idVendor=3032, idProduct=0013
[ 1196.333025] usb 1-2.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1196.333031] usb 1-2.4.4: Product: ReachM2
[ 1196.333036] usb 1-2.4.4: Manufacturer: Emlid
[ 1196.333041] usb 1-2.4.4: SerialNumber: 82432C9511E58D09
[ 1196.343070] cdc_ether 1-2.4.4:1.0 usb1: register ‘cdc_ether’ at usb-3610000.xhci-2.4.4, CDC Ethernet Device, 6a:ae:ce:d9:88:65
[ 1196.344895] cdc_acm 1-2.4.4:1.2: ttyACM0: USB ACM device
[ 1196.408207] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[ 1196.408732] cdc_ether 1-2.4.4:1.0 usb1: kevent 12 may have been dropped
[ 1196.442109] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[ 1196.814863] IPv6: ADDRCONF(NETDEV_CHANGE): usb1: link becomes ready
[ 1211.721131] cdc_acm 1-2.4.4:1.2: failed to set dtr/rts

Also I can see the serial port but no data is accessible from it.

crw-rw---- 1 root dialout 166, 0 Mar 5 13:00 /dev/ttyACM0

The M2 works on x86_64 Ubuntu 18.04 system correctly but not on the Xavier. i am only interested in reading the NMEA serial position output from the M2. Any ideas what I can do to solve it?

I have tried also disabling the ModemManger but still the M2 is not starting up correctly.

systemctl stop ModemManager.service

Let me know if you need any more information. Happy to provide as much as i can as I was not expecting to have any issues with it and it is blocking me now.

Thank you very much

3

Hi Spyros,

Sorry for the delayed reply.

If only the red LED lights up, it usually means that Reach M2 doesn’t get enough power to boot. It might be useful to check it with other available ports on your device.

Reach doesn’t output any messages until it boots completely. That’s why it wasn’t possible to read any data from the port.

I’d also suggest checking whether your Reach can be switched on while connected to other power sources. It’ll help us to make sure that it works properly.

5

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.