How do I connect WP76xx without using ssh?

IoT Modules
1

We plan to control WP76xx from a small system which doesn’t have SSH functionality.
I think if I create a new port over USB, it would be possible to communicate between our APP in the WP76xx and our software in the small system.
Are there any sample code and such which achives a connection between WP76xx module and the external CPU without using SSH?
I’d appreciate any advice.
Regards,

2

You can use raw data port by setting at!usbcomp

3

@temaedashop2

Bit of a wide open question. A few options.

  • UART2 can be set to run either the Linux console out or to use with a Legato application (using at!mapuart) over which you can use whatever protocol you want.
  • USB enumerates an AT command port to the signaling core by default.
  • You can write a Legato application run the I2C or SPI busses.

As you can see there are a few options so it all comes down to what you want to acheive and what you have available.

Regards

Matt

4

Thank you for the information.
Because of the configuration of our target device, we prefer to use USB for this purpose.
We will study “at!USBCOMP” and the related commands some more.
Please allow my additional questions when necessary.
Regards,

5

I’ve checked “at!USBCOMP” and the related.
Following is my understanding.

  • AT commands can be sent to Modem via UART1 from external CPU.
  • Or, from Target app using " AT Commands Client" API.
    Is it correct?
    Thanks,
6

to use AT command on UART1, you need to first set AT!MAPUART=1,1

For sending command inside legato app, you can see here:

7

Thank you for the information.
Following is the result at the Target console.

root@swi-mdm9x28-wp:~# uartMode get 1
UART1 is being used for AT Commands.
root@swi-mdm9x28-wp:~# uartMode get 2
UART2 is being used for the /dev/console.

According to this result, I think we can send AT command via UART1.

If we add “RAWDATA” path on USB using at!USBCOMP, how can the target app access this USB port?
Regards,

8

if you use Linux, there will be one more /dev/ttyUSB3 port coming out for the raw data port.
If you use windows, there will be one more serial port in device manager.

9

I’ve confirmed the new raw data port in Device Manager on Windows. Thanks.

So far, I’ve not found the new port from ubuntu.
ubuntu says no such device for /dev/ttyUSB3.
Is the raw data port shown as /dev/ttyUSB*?
Regards,

10

What do you see for

ls /dev/ttyUSB*

What is your at!usbcomp setting now?

11

I’ve looked for the device on the console of target Android (root@swi-mdm9x28-wp:/dev#).
Should I look for /dev/ttyUSB3 in somewhere else?

Following is the current usb settings.

OK
at!usbcomp?
Config Index: 1
Config Type: 1 (Generic)
Interface bitmask: 0008014D (diag,nmea,modem,rmnet0,ecm,rawdat)

Regards,

12

then can you see the AT command port enumerated in the host platform?

You should check dmesg of the host platform

13

I’ve also checked the ubuntu host devices.
I’ve found ttyUSB0, ttyUSB1 and ttyUSB2 ports.
I’m sending AT commands using minicom over /dev/ttyUSB2 port.

Following is part of dmesg of ubuntu host.

[ 15.078558] usbserial: USB Serial support registered for Qualcomm USB modem
[ 15.082870] qcserial 3-3:1.0: Qualcomm USB modem converter detected
[ 15.082943] usb 3-3: Qualcomm USB modem converter now attached to ttyUSB0
[ 15.085518] qcserial 3-3:1.2: Qualcomm USB modem converter detected
[ 15.085575] usb 3-3: Qualcomm USB modem converter now attached to ttyUSB1
[ 15.088125] qcserial 3-3:1.3: Qualcomm USB modem converter detected
[ 15.088178] usb 3-3: Qualcomm USB modem converter now attached to ttyUSB2
[ 15.155256] usbcore: registered new interface driver cdc_wdm
[ 15.241380] qmi_wwan 3-3:1.8: cdc-wdm0: USB WDM device

Are there other possible devices that would correspond to the new raw data port on ubuntu?
Regards,

14

you can see here that other user makes it work after installing the GobiSerial driver instead of qcserial driver to have the /dev/ttyUSB3 as RAW data port:

You might need to modify “/etc/modprobe.d/blacklist-modem.conf” file and restart the host

blacklist qcserial 
blacklist qmi_wwan
15

Thank you for the information.
Because our host system is not Linux nor Windows, I’ll wait for the report of my colleague who are in charge of the host system.
If our host system does not recognize the additional raw data port, we need to find solution such as GobiSerial driver.
Thanks,