”smsC hat.txt” was not created after app runProc modemDemo1 send --exe = send – 1234567“ Sim”

[12214]

We try to do data connection with reference to below URL using modemDemo1.

Command line connection works, but le_data does not in application

I’m using an external sim card with which I have use the command line cm data connect and use netcat to reach my server correctly, however when I try to create an app that uses le_data API it indicates the connection is stablished but cant reach my server. I have tried these things: 1.- Remove le_data API from my application. Start the connection with command line cm data connect, then start my app just to verify that application can reach my server which is done correctly. 2.- Remove the co…

- Target: FX30 - OS: Virtual Linux 18.04 - Package: swi-fx30-catm_2.0.0 *If you need more information, please tell us.

We completed Build and Install of modemDemo1 and executed the following command on FX30 according to URL.

However, ”smsC hat.txt” was not created.
We want to know the way that ”smsC hat.txt” is created.
Is our procedure wrong?

We attached logs, so please see the attached logs and help us to solve it.

20210910_log.txt (23.7 KB)

[jyijyi]

probably the compiled version of the application is not matching with the legato version on your module:

Sep 10 09:22:51 fx30 user.err Legato: =ERR= | serviceDirectory[881]/serviceDirectory T=main | serviceDirectory.c DispatchToServer() 713 | Client (uid 1005 'appmodemDemo1', pid 21410) disagrees with server (uid 0 'root', pid 1020) on protocol ID of service 'modemDem
Sep 10 09:22:51 fx30 user.emerg Legato: *EMR* | _UNKNOWN_[21410]/framework T=main | messagingSession.c ReceiveSessionOpenResponse() 699 | Unexpected server response: -6 (LE_FAULT).
Sep 10 09:22:51 fx30 user.info Legato:  INFO | supervisor[857]/supervisor T=main | proc.c proc_SigChildHandler() 2079 | Process 'modemDemo' (PID: 21410) has exited with exit code 1.
Sep 10 09:22:51 fx30 user.warn Legato: -WRN- | supervisor[857]/supervisor T=main | app.c app_SigChildHandler() 4066 | Process 'modemDemo' in app 'modemDemo1' faulted: Ignored.

[12214]

Hi jyijyi,

Our legato version is below.

root@fx30:/legato/systems/current/appsWriteable/modemDemo1# legato version
19.11.5_f20cfbe645fc4a7f0c8762e04672e3f9_modified

Do you have an application supported this legato version?

[jyijyi]

Have you tried

fx30-catm_3.0.0

[12214]

Hi Jyijyi,

We installed fx30-catm_3.0.0 and retested.
Unfortunately, ”smsC hat.txt” was not created.

20210913_log.txt (3.4 KB)

Could you provide success sequence log in your environment?

Thank you.

[jyijyi]

I don’t see problem, you can use my application binary which is compiled by swi-fx30-catm_3.0.0.

modemDemo1.wp77xx.update (196.3 KB)

root@fx30:~# app status
[running] atAirVantage
[running] atQmiLinker
[running] atService
[running] audioService
[running] avcService
[running] cellNetService
[running] columbiaAtService
[running] dataConnectionService
[running] factoryRecoveryService
[running] fwupdateService
[running] gpioService
[running] modemService
[running] portService
[running] positioningService
[running] powerMgr
[running] qmiAirVantage
[running] secStore
[stopped] smsInboxService
[stopped] spiService
[stopped] tools
[stopped] voiceCallService
[stopped] wifi
[stopped] wifiApTest
[stopped] wifiClientTest
[running] wifiService
[stopped] wifiWebAp
[running] modemDemo1
root@fx30:~# app runProc modemDemo1 send --exe=send -- 1234567 "Sim"
root@fx30:~# cat /legato/systems/current/appsWriteable/modemDemo1/smsChat.txt 
## SIM 1 is absent. ##
root@fx30:~# app runProc modemDemo1 send --exe=send -- 1234567 "Sim"
root@fx30:~# cat /legato/systems/current/appsWriteable/modemDemo1/smsChat.txt 
## SIM 1 is absent. ##
## SIM 1 is absent. ##
root@fx30:~# legato version
19.11.5.a1621d58_27c4cd8552e17e79fdc3b0c91ff8bce9_modified
root@fx30:~# cm info
Device:                        WP7702
IMEI:                          352653090002791
IMEISV:                        6
FSN:                           VU735370340201
Firmware Version:              SWI9X06Y_02.36.06.00 63d944 jenkins 2020/12/10 19:12:28
Bootloader Version:            SWI9X06Y_02.36.06.00 63d944 jenkins 2020/12/10 19:12:28
MCU Version:                   002.015
PRI Part Number (PN):          9907365
PRI Revision:                  001.001 
Carrier PRI Name:              GENERIC
Carrier PRI Revision:          001.071_001
SKU:                           1103530
Last Reset Cause:              Reset, User Requested
Resets Count:                  Expected: 380	Unexpected: 28
root@fx30:~#

[12214]

Hi Jyijyi,

Thank you for providing update file.
Fortunately, we could create “smsC hat.txt”.

And we sent app runProc modemDemo send --exe=send – 1234567 “Online” and module returned “Requesting data connection”.(ping is success from fx30 to 8.8.8.8)

We connected fx30 to Linux OS PC via Ethernet cable.
However, in Linux PC, we can’t open web browser.

Do we need more setting in fx30?
Or is this a problem in Host side?

Thank you.

[jyijyi]

what is the IP address on ethernet interface on FX30?
What is the IP address on ethernet interface on PC?
Can they ping each other?

BTW, are you using ethernet IOT card or the ethernet port is default already on the device?

I saw that some one says it is not working with FX30+ ethernet IOT card:

FX30 Ethernet IoT board

Hi Caio Porto, I suspect the issue is due to U1 on the Talon ethernet card. The issue is the bi-directional level shifter leakage reverse drives the RESET_OUT line. The part needs to be replaced with a pin compatible part such as: 74AVC1T45 The reason you don’t see the issue on the mangOH red is the the RESET_OUT circuit is buffered. BR, Chris

[12214]

Hi Jyijyi,

what is the IP address on ethernet interface on FX30?

It’s default setting.
192.168.13.31

What is the IP address on ethernet interface on PC?

It is 192.168.13.1.

Can they ping each other?

From PC to FX30(192.168.13.31)
=>Success

From FX30(192.168.2.2) to PC
=>Fail

From FX30(192.168.13.31) to PC
=>Fail
We can’t access 192.168.13.31.

BTW, are you using ethernet IOT card or the ethernet port is default already on the device?

We doesn’t use ethernet IOT card.
We use ethernet port is default already on the device.

Thank you.

[jyijyi]

Please capture wireshark log on FX30 ethernet interface and PC ethernet interface, then you will know why it is failed on this case:

From FX30(192.168.13.31) to PC
=>Fail

BTW, are you pinging from FX30 to PC by “ping 192.168.13.31 -I eth0” ?

[12214]

We collect wireshark log.
Please see the attached “Ethernet_wireshark.pcapng”.
Do you know anything from this log?

Ethernet_wireshark.pcapng (14.5 KB)

BTW, are you pinging from FX30 to PC by “ping 192.168.13.31 -I eth0” ?

We tried pinging.
But we can’t send ping packet to 192.168.13.31

root@fx30:~# ping 192.168.13.31 -I eth0
PING 192.168.13.31 (192.168.13.31): 56 data bytes
^C
— 192.168.13.31 ping statistics —
6 packets transmitted, 0 packets received, 100% packet loss
root@fx30:~#

Thank you.

[jyijyi]

I don’t see any packet coming from 192.168.13.31 from your wireshark log captured in PC.

Btw, your fx30 is having ip address 192.168.13.31, then why are you ping yourself but not pc?
Didn’t you should " ping192.168.13.1 -I eth0" in module?

Have you captured the wireshark log in FX30?
View pings sent from an external device to mangoh red - #3 by Cada

[12214]

Hi Jyijyi,

Btw, your fx30 is having ip address 192.168.13.31, then why are you ping yourself but not pc?
Didn’t you should " ping192.168.13.1 -I eth0" in module?

I’m sorry. You are right.
We tried “ping192.168.13.1 -I eth0” but we can’t send ping packet to 192.168.13.1.

root@fx30:~# ping 192.168.13.1 -I eth0
PING 192.168.13.1 (192.168.13.1): 56 data bytes
^C
— 192.168.13.1 ping statistics —
5 packets transmitted, 0 packets received, 100% packet loss

And we captured the wireshark log in FX30 using tcpdump command.
Please see the attached “FX30_tcpdump.log”
FX30_tcpdump.log (12.3 KB)

Thank you.

[jyijyi]

please see here on how to capture wireshark log (not xxx.log) in module:

View pings sent from an external device to mangoh red

You can have a look here: https://www.wireshark.org/docs/wsug_html_chunked/AppToolstcpdump.html Download a ARM version of TCPDUMP and transfer to the module static-binaries/tcpdump at master · andrew-d/static-binaries · GitHub chmod 777 tcpdump_arm /home/root/tcpdump_arm -s0 -i eth0 -w /tmp/test.pcap

[12214]

Hi Jyijyi,

We collected pcap log.

fx30_wireshark.pcap (11.0 KB)

Thank you

[jyijyi]

I don’t see any activity about 192.168.13.31 which is your FX30 eth0 IP address.
Have you tried to “ping 192.168.13.1 -I eth0” from FX30 when you capture the wireshark log?
Have you tried to ping from PC to FX30 when you capture the wireshark log? ( as you said this is successfully done, I expect it will be shown in the wireshark log)

[jyijyi]

Also please open a new topic as this is no longer related to modemdemo