Jetson Nano + 3G-4G/LTE Base Hat unable to get PPP connection

I recently purchased the 4G/LTE bundle- Base Hat + EC25-A for North American usage along with 2 antennas and a Twilio SIM card. I’m trying to interface it with my Jetson Nano via USB but running into problems.

Hardware setup - I followed the turotial, hooked up Antennas to EC25, then inserted the EC25 into the Hat

Activated the Twilio SIM card that came with the package - its status on the Twilio dashboard is “Active” so I’m not worried about the SIM being the point of failure.

I followed this tutorial to the letter and got the following output:

sudo pon
[sudo] password for jetson: 
pppd options in effect:
debug		# (from /etc/ppp/peers/provider)
updetach		# (from /etc/ppp/peers/provider)
dump		# (from /etc/ppp/peers/provider)
noauth		# (from /etc/ppp/peers/provider)
remotename 3gppp		# (from /etc/ppp/peers/provider)
/dev/ttyS0		# (from /etc/ppp/peers/provider)
115200		# (from /etc/ppp/peers/provider)
lock		# (from /etc/ppp/peers/provider)
connect chat -s -v -f /etc/chatscripts/chat-connect -T wireless.twilio.com	# (from /etc/ppp/peers/provider)
disconnect chat -s -v -f /etc/chatscripts/chat-disconnect		# (from /etc/ppp/peers/provider)
nocrtscts		# (from /etc/ppp/peers/provider)
modem		# (from /etc/ppp/peers/provider)
asyncmap 0		# (from /etc/ppp/options)
lcp-echo-failure 4		# (from /etc/ppp/options)
lcp-echo-interval 30		# (from /etc/ppp/options)
hide-password		# (from /etc/ppp/peers/provider)
novj		# (from /etc/ppp/peers/provider)
novjccomp		# (from /etc/ppp/peers/provider)
ipcp-accept-local		# (from /etc/ppp/peers/provider)
ipcp-accept-remote		# (from /etc/ppp/peers/provider)
ipparam 3gppp		# (from /etc/ppp/peers/provider)
noipdefault		# (from /etc/ppp/peers/provider)
ipcp-max-failure 30		# (from /etc/ppp/peers/provider)
defaultroute		# (from /etc/ppp/peers/provider)
usepeerdns		# (from /etc/ppp/peers/provider)
noccp		# (from /etc/ppp/peers/provider)
noipx		# (from /etc/ppp/options)
abort on (BUSY)
abort on (NO CARRIER)
abort on (NO DIALTONE)
abort on (ERROR)
abort on (NO ANSWER)
timeout set to 30 seconds
send (AT^M)
expect (OK)
alarm
Failed
Script chat -s -v -f /etc/chatscripts/chat-connect -T wireless.twilio.com finished (pid 7850), status = 0x3
Connect script failed

Running dmesg -w I see the following when I connect the USB cable

[  641.097139] usb 1-2.1: new high-speed USB device number 11 using tegra-xusb
[  641.129234] usb 1-2.1: New USB device found, idVendor=2c7c, idProduct=0125
[  641.129240] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  641.129244] usb 1-2.1: Product: Android
[  641.129247] usb 1-2.1: Manufacturer: Android
[  641.131724] option 1-2.1:1.0: GSM modem (1-port) converter detected
[  641.132013] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB0
[  641.132309] option 1-2.1:1.1: GSM modem (1-port) converter detected
[  641.132520] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB1
[  641.132990] option 1-2.1:1.2: GSM modem (1-port) converter detected
[  641.133369] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB2
[  641.134082] option 1-2.1:1.3: GSM modem (1-port) converter detected
[  641.136120] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB3
[  641.886924] usb 1-2-port1: disabled by hub (EMI?), re-enabling...
[  641.893502] usb 1-2.1: USB disconnect, device number 11
[  641.893894] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  641.893929] option 1-2.1:1.0: device disconnected
[  641.896197] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  641.896235] option 1-2.1:1.1: device disconnected
[  641.896795] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  641.896842] option 1-2.1:1.2: device disconnected
[  641.898714] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  641.898765] option 1-2.1:1.3: device disconnected
[  642.121184] usb 1-2.1: new high-speed USB device number 12 using tegra-xusb
[  642.153229] usb 1-2.1: New USB device found, idVendor=2c7c, idProduct=0125
[  642.153234] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  642.153237] usb 1-2.1: Product: Android
[  642.153240] usb 1-2.1: Manufacturer: Android
[  642.155751] option 1-2.1:1.0: GSM modem (1-port) converter detected
[  642.156006] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB0
[  642.156259] option 1-2.1:1.1: GSM modem (1-port) converter detected
[  642.156445] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB1
[  642.156787] option 1-2.1:1.2: GSM modem (1-port) converter detected
[  642.156979] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB2
[  642.157288] option 1-2.1:1.3: GSM modem (1-port) converter detected
[  642.157472] usb 1-2.1: GSM modem (1-port) converter now attached to ttyUSB3

So I tried defining the port as ttyUSB3, but got the same result. Also, when I disconnect the Hat entirely and run sudo pon I get the same result. LED behavior is a constant red power light, plus a blue stat light that blinks every ~2 sec, constantly.

Anyone have any idea what I’m doing wrong here?

Update: I unplugged my Wifi card (also connected via USB) and got the following output:

sudo pon
pppd options in effect:
debug		# (from /etc/ppp/peers/provider)
updetach		# (from /etc/ppp/peers/provider)
dump		# (from /etc/ppp/peers/provider)
noauth		# (from /etc/ppp/peers/provider)
remotename 3gppp		# (from /etc/ppp/peers/provider)
/dev/ttyUSB3		# (from /etc/ppp/peers/provider)
115200		# (from /etc/ppp/peers/provider)
lock		# (from /etc/ppp/peers/provider)
connect chat -s -v -f /etc/chatscripts/chat-connect -T wireless.twilio.com	# (from /etc/ppp/peers/provider)
disconnect chat -s -v -f /etc/chatscripts/chat-disconnect		# (from /etc/ppp/peers/provider)
nocrtscts		# (from /etc/ppp/peers/provider)
modem		# (from /etc/ppp/peers/provider)
asyncmap 0		# (from /etc/ppp/options)
lcp-echo-failure 4		# (from /etc/ppp/options)
lcp-echo-interval 30		# (from /etc/ppp/options)
hide-password		# (from /etc/ppp/peers/provider)
novj		# (from /etc/ppp/peers/provider)
novjccomp		# (from /etc/ppp/peers/provider)
ipcp-accept-local		# (from /etc/ppp/peers/provider)
ipcp-accept-remote		# (from /etc/ppp/peers/provider)
ipparam 3gppp		# (from /etc/ppp/peers/provider)
noipdefault		# (from /etc/ppp/peers/provider)
ipcp-max-failure 30		# (from /etc/ppp/peers/provider)
defaultroute		# (from /etc/ppp/peers/provider)
usepeerdns		# (from /etc/ppp/peers/provider)
noccp		# (from /etc/ppp/peers/provider)
noipx		# (from /etc/ppp/options)
abort on (BUSY)
abort on (NO CARRIER)
abort on (NO DIALTONE)
abort on (ERROR)
abort on (NO ANSWER)
timeout set to 30 seconds
send (AT^M)
expect (OK)
^M
OK
 -- got it

send (ATE0^M)
expect (OK)
^M
alarm
Failed
Script chat -s -v -f /etc/chatscripts/chat-connect -T wireless.twilio.com finished (pid 7770), status = 0x3
Connect script failed

How should I proceed from here?

Hi,

The error occurs as the proper driver are not installed.
This issue hasn’t been solve yet.

Thanks for the quick reply! So with RPi, there’s a kernel modification step in the installation. Is that where the driver installation happens normally?

And when do you think y’all will release a driver install script for Jetson devices?

Hi,

The Raspberry Pi kernel modification are upto date.
Yes. installation script for Jetson Nano is part of our plan.

Glad to hear - y’all have a target release date?

Hey all - any updates on this issue?

Hi It may need more time. may be around a month.

Hey Saeed - any updates?

Let me know if you want help with the code - I need this 4G setup working for one of my projects.

@saeed Hi! Is there any update on this? We are really in the need to have Base Hat 4G/LTE working with Jetson Nano. It’s working flawlessly with Raspberry Pi, but looks like it does need some work on Nano. Please, let us know

Regards

Hello,

The Jetson Nano doesn’t come with 4G driver support. You will need to reach the source code and make some modifications as mentioned in this Linux Driver Guide.

Thanks for the Reference! Is your team trying to implement that?

So far we have been working on the previous version of the Jetson Nano. Right now we will start implementing and testing with the modified version of the Jetson Nano.