3:56 a.m.
I am currently trying to get the cellular connection up via connman/ofono. We are using
Telit HE910 device.
I am currently able to do the following ,
1. Run daemon in background
2. Execute enable-modem app
3. List-contexts, set APN to required value
However, while executing 'activate-context 0' I am not able to proceed further.
I get the following error message,
"DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken."
We are using ofono version 1.16 now.
Regards,
<Ram>
4:09 a.m.
Hi,
try to add the following line to he910 plugin:
g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
Moreover change
g_at_chat_send(data->chat, "AT#AUTOATT=0", none_prefix, NULL, NULL, NULL);
to
g_at_chat_send(data->chat, "AT#AUTOATT=1", none_prefix, NULL, NULL, NULL);
and move it to he910_post_online function.
I have a Telit HE910 with working connection.
Enrico
2015-03-05 12:56 GMT+01:00 Kallumari Nagaraja Rao, RammohanX <
rammohanx.kallumari.nagaraja.rao(a)intel.com>:
I am currently trying to get the cellular connection up via
connman/ofono. We are using Telit HE910 device.
I am currently able to do the following ,
1. Run daemon in background
2. Execute enable-modem app
3. List-contexts, set APN to required value
However, while executing ‘activate-context 0’ I am not able to proceed
further.
I get the following error message,
“DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.”
We are using ofono version 1.16 now.
*Regards,*
*<Ram>*
_______________________________________________
ofono mailing list
ofono(a)ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
8:02 a.m.
Hi Enrico,
Please do not top-post on this mailing list.
On 03/05/2015 06:09 AM, Enrico Sau wrote:
Hi,
try to add the following line to he910 plugin:
g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
Was this change required? I didn't think Telit suffered from dropping
carrier issue. If so, feel free to send a patch.
Moreover change
g_at_chat_send(data->chat, "AT#AUTOATT=0", none_prefix,NULL, NULL, NULL);
to
g_at_chat_send(data->chat, "AT#AUTOATT=1", none_prefix,NULL, NULL, NULL);
oFono expects auto-attach to be disabled. So this change is actually
incorrect. What was going wrong that was fixed by this change?
Regards,
-Denis
8:30 a.m.
Hi Denis,
sorry, I forgot the top-post rule.
g_at_chat_send(data->modem, "AT&C0", NULL, NULL,
NULL, NULL);
>
Was this change required? I didn't think Telit suffered from dropping
carrier issue. If so, feel free to send a patch.
>
> This change was necessary because the he910 was putting the DCD signal
to low
after ppp session, so it was impossible to connect again to that
port.
Setting &C0 in the modem port forces DCD to stay high.
oFono expects auto-attach to be disabled. So this change is actually
incorrect. What was going wrong that was fixed by this change?
Regarding the AUTOATT change, I had to move it to post_online section
because it was issued too early in modem startup and it always returned an
error.
Then I changed it to 1 because there was some misalignment between modem
attachment status and ofono variables.
I didn't go to deep in this problem but putting AUTOATT to 1 solved my
problem and is good for me.
Enrico
1:18 a.m.
with these changes as mentioned above I am not even be able to enable modem/create
context.
static void he910_post_online(struct ofono_modem *modem)
{
struct he910_data *data = ofono_modem_get_data(modem);
struct ofono_message_waiting *mw;
struct ofono_gprs *gprs;
struct ofono_gprs_context *gc;
DBG("%p", modem);
g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
ofono_voicecall_create(modem, 0, "atmodem", data->chat);
ofono_netreg_create(modem, OFONO_VENDOR_TELIT, "atmodem",
data->chat);
ofono_ussd_create(modem, 0, "atmodem", data->chat);
ofono_call_forwarding_create(modem, 0, "atmodem", data->chat);
ofono_call_settings_create(modem, 0, "atmodem", data->chat);
ofono_call_meter_create(modem, 0, "atmodem", data->chat);
ofono_call_barring_create(modem, 0, "atmodem", data->chat);
mw = ofono_message_waiting_create(modem);
if (mw)
ofono_message_waiting_register(mw);
gprs = ofono_gprs_create(modem, OFONO_VENDOR_TELIT, "atmodem",
data->chat);
gc = ofono_gprs_context_create(modem, 0, "atmodem", data->modem);
//g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
//g_at_chat_send(data->chat, "AT#AUTOATT=1", none_prefix, NULL, NULL,
NULL);
if (gprs && gc)
ofono_gprs_add_context(gprs, gc);
}
Regards,
<Ram>
From: ofono [mailto:ofono-bounces@ofono.org] On Behalf Of Enrico Sau
Sent: Thursday, March 05, 2015 10:01 PM
To: ofono(a)ofono.org
Subject: Re: telit he910 activate-context issue
Hi Denis,
sorry, I forgot the top-post rule.
g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
Was this change required? I didn't think Telit suffered from dropping carrier issue.
If so, feel free to send a patch.
This change was necessary because the he910 was putting the DCD signal to low after ppp
session, so it was impossible to connect again to that port.
Setting &C0 in the modem port forces DCD to stay high.
oFono expects auto-attach to be disabled. So this change is actually incorrect. What was
going wrong that was fixed by this change?
Regarding the AUTOATT change, I had to move it to post_online section because it was
issued too early in modem startup and it always returned an error.
Then I changed it to 1 because there was some misalignment between modem attachment status
and ofono variables.
I didn't go to deep in this problem but putting AUTOATT to 1 solved my problem and is
good for me.
Enrico
4:35 a.m.
ofonod[7030]: plugins/he910.c:cfun_enable_cb() 0x81bb258
ofonod[7030]: src/modem.c:modem_change_state() old state: 0, new state: 1
ofonod[7030]: plugins/he910.c:he910_pre_sim() 0x81bb258
ofonod[7030]: Aux: > AT&C0\r
ofonod[7030]: src/sim.c:ofono_sim_add_state_watch() 0x81bf408
ofonod[7030]: src/sim.c:ofono_sim_add_state_watch() 0x81bf408
ofonod[7030]: src/sim.c:ofono_sim_add_state_watch() 0x81bf408
ofonod[7030]: Aux: < \r\nOK\r\n
ofonod[7030]: Aux: > AT+GCAP\r
ofonod[7030]: Aux: < \r\n
ofonod[7030]: Aux: < +GCAP: +CGSM,+DS,+FCLASS,+MS,+ES\r\n\r\nOK\r\n
ofonod[7030]: Aux: > AT$GPSP=?\r
ofonod[7030]: Aux: < \r\n
ofonod[7030]: Aux: < $GPSP: (0,1)\r\n\r\nOK\r\n
ofonod[7030]: Aux: > AT#AUTOATT=0\r
ofonod[7030]: Aux: < \r\nOK\r\n
ofonod[7030]: Aux: > AT#QSS=2\r
ofonod[7030]: Aux: < \r\nOK\r\n
ofonod[7030]: Aux: > AT#QSS?\r
ofonod[7030]: Aux: < \r\n
ofonod[7030]: Aux: < #QSS: 2,3\r\n\r\nOK\r\n
ofonod[7030]: plugins/he910.c:qss_query_cb() 0x81bb258
ofonod[7030]: plugins/he910.c:switch_sim_state_status() 0x81bb258, SIM status: 3
Should the SIM state returned by the modem with QSS command should be 3 or 1 ?
With the above stuff context was not getting created.
Regards,
<Ram>
From: ofono [mailto:ofono-bounces@ofono.org] On Behalf Of Enrico Sau
Sent: Thursday, March 05, 2015 10:01 PM
To: ofono(a)ofono.org
Subject: Re: telit he910 activate-context issue
Hi Denis,
sorry, I forgot the top-post rule.
g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
Was this change required? I didn't think Telit suffered from dropping carrier issue.
If so, feel free to send a patch.
This change was necessary because the he910 was putting the DCD signal to low after ppp
session, so it was impossible to connect again to that port.
Setting &C0 in the modem port forces DCD to stay high.
oFono expects auto-attach to be disabled. So this change is actually incorrect. What was
going wrong that was fixed by this change?
Regarding the AUTOATT change, I had to move it to post_online section because it was
issued too early in modem startup and it always returned an error.
Then I changed it to 1 because there was some misalignment between modem attachment status
and ofono variables.
I didn't go to deep in this problem but putting AUTOATT to 1 solved my problem and is
good for me.
Enrico
7:15 a.m.
Enrico,
Waiting for your valuable inputs.
Regards,
<Ram>
From: ofono [mailto:ofono-bounces@ofono.org] On Behalf Of Enrico Sau
Sent: Thursday, March 05, 2015 10:01 PM
To: ofono(a)ofono.org
Subject: Re: telit he910 activate-context issue
Hi Denis,
sorry, I forgot the top-post rule.
g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
Was this change required? I didn't think Telit suffered from dropping carrier issue.
If so, feel free to send a patch.
This change was necessary because the he910 was putting the DCD signal to low after ppp
session, so it was impossible to connect again to that port.
Setting &C0 in the modem port forces DCD to stay high.
oFono expects auto-attach to be disabled. So this change is actually incorrect. What was
going wrong that was fixed by this change?
Regarding the AUTOATT change, I had to move it to post_online section because it was
issued too early in modem startup and it always returned an error.
Then I changed it to 1 because there was some misalignment between modem attachment status
and ofono variables.
I didn't go to deep in this problem but putting AUTOATT to 1 solved my problem and is
good for me.
Enrico
7:39 a.m.
Hi,
I will send a patch with my modifications to he910 plugin.
Denis, please, can you link me the patch submission guidelines?
Thank you.
Enrico
2015-03-06 16:15 GMT+01:00 Kallumari Nagaraja Rao, RammohanX <
rammohanx.kallumari.nagaraja.rao(a)intel.com>:
Enrico,
Waiting for your valuable inputs.
*Regards,*
*<Ram>*
*From:* ofono [mailto:ofono-bounces@ofono.org] *On Behalf Of *Enrico Sau
*Sent:* Thursday, March 05, 2015 10:01 PM
*To:* ofono(a)ofono.org
*Subject:* Re: telit he910 activate-context issue
Hi Denis,
sorry, I forgot the top-post rule.
g_at_chat_send(data->modem, "AT&C0", NULL, NULL, NULL, NULL);
Was this change required? I didn't think Telit suffered from dropping
carrier issue. If so, feel free to send a patch.
This change was necessary because the he910 was putting the DCD signal
to low after ppp session, so it was impossible to connect again to that
port.
Setting &C0 in the modem port forces DCD to stay high.
oFono expects auto-attach to be disabled. So this change is actually
incorrect. What was going wrong that was fixed by this change?
Regarding the AUTOATT change, I had to move it to post_online section
because it was issued too early in modem startup and it always returned an
error.
Then I changed it to 1 because there was some misalignment between modem
attachment status and ofono variables.
I didn't go to deep in this problem but putting AUTOATT to 1 solved my
problem and is good for me.
Enrico
_______________________________________________
ofono mailing list
ofono(a)ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
9:48 a.m.
Hi Enrico,
No top posting please :)
On 03/06/2015 09:39 AM, Enrico Sau wrote:
Hi,
I will send a patch with my modifications to he910 plugin.
Denis, please, can you link me the patch submission guidelines?
These are described in the HACKING document inside the ofono git tree.
Also please review the oFono coding style rules in doc/coding-style.txt.
Regards,
-Denis
8:07 a.m.
Hi Ram,
On 03/05/2015 05:56 AM, Kallumari Nagaraja Rao, RammohanX wrote:
I am currently trying to get the cellular connection up via
connman/ofono. We are using Telit HE910 device.
I am currently able to do the following ,
1.Run daemon in background
2.Execute enable-modem app
3.List-contexts, set APN to required value
Are you running with root permissions? Telit uses PPP for its context
driver, which requires us to create a TUN/TAP device.
Can you enable AT command tracing:
export OFONO_AT_DEBUG=1
and run oFono with debug information enabled:
sudo ofonod -n -d
Then share this log.
However, while executing ‘activate-context 0’ I am not able to proceed
further.
I get the following error message,
“DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.”
Hard to say without an AT command trace, but sounds like the modem is
not responding to the context activation. Would need additional
information to say more.
Regards,
-Denis
8:20 p.m.
Hello Denis,
First of all I am trying these on DK300 device.
Yes I am on root. I have added tun.conf into /etc/init.d & have checked tun getting
loaded via lsmod.
I have tried enabling OFONO_AT_DEBUG=1, but will send out the log for reference.
Regards,
<Ram>
-----Original Message-----
From: ofono [mailto:ofono-bounces@ofono.org] On Behalf Of Denis Kenzior
Sent: Thursday, March 05, 2015 9:37 PM
To: ofono(a)ofono.org
Subject: Re: telit he910 activate-context issue
Hi Ram,
On 03/05/2015 05:56 AM, Kallumari Nagaraja Rao, RammohanX wrote:
I am currently trying to get the cellular connection up via
connman/ofono. We are using Telit HE910 device.
I am currently able to do the following ,
1.Run daemon in background
2.Execute enable-modem app
3.List-contexts, set APN to required value
Are you running with root permissions? Telit uses PPP for its context driver, which
requires us to create a TUN/TAP device.
Can you enable AT command tracing:
export OFONO_AT_DEBUG=1
and run oFono with debug information enabled:
sudo ofonod -n -d
Then share this log.
However, while executing 'activate-context 0' I am not able to proceed
further.
I get the following error message,
"DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the
message bus security policy blocked the reply, the reply timeout
expired, or
the network connection was broken."
Hard to say without an AT command trace, but sounds like the modem is not responding to
the context activation. Would need additional information to say more.
Regards,
-Denis
_______________________________________________
ofono mailing list
ofono(a)ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
12:28 a.m.
Denis,
PFA the logs with AT&C0 & without. With &C0 it is not even creating a
context.
Regards,
<Ram>
-----Original Message-----
From: ofono [mailto:ofono-bounces@ofono.org] On Behalf Of Denis Kenzior
Sent: Thursday, March 05, 2015 9:37 PM
To: ofono(a)ofono.org
Subject: Re: telit he910 activate-context issue
Hi Ram,
On 03/05/2015 05:56 AM, Kallumari Nagaraja Rao, RammohanX wrote:
I am currently trying to get the cellular connection up via
connman/ofono. We are using Telit HE910 device.
I am currently able to do the following ,
1.Run daemon in background
2.Execute enable-modem app
3.List-contexts, set APN to required value
Are you running with root permissions? Telit uses PPP for its context driver, which
requires us to create a TUN/TAP device.
Can you enable AT command tracing:
export OFONO_AT_DEBUG=1
and run oFono with debug information enabled:
sudo ofonod -n -d
Then share this log.
However, while executing 'activate-context 0' I am not able to proceed
further.
I get the following error message,
"DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the
message bus security policy blocked the reply, the reply timeout
expired, or
the network connection was broken."
Hard to say without an AT command trace, but sounds like the modem is not responding to
the context activation. Would need additional information to say more.
Regards,
-Denis
_______________________________________________
ofono mailing list
ofono(a)ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
10:28 a.m.
Hi Ram,
Please do not top-post on this mailing list.
On 03/06/2015 02:28 AM, Kallumari Nagaraja Rao, RammohanX wrote:
Denis,
PFA the logs with AT&C0 & without. With &C0 it is not even creating a
context.
I have just tried my HE910 with unmodified oFono 1.16 and I am able to
successfully activate the context.
My firmware version is 12.00.003, but 12.00.004 is recommended.
What you should be seeing is something like this:
ofonod[19130]: drivers/atmodem/gprs-context.c:at_gprs_activate_primary()
cid 1
ofonod[19130]: Modem: > AT+CGDCONT=1,"IP",""\r
ofonod[19130]: Modem: < AT+CGDCONT=1,"IP",""\r
ofonod[19130]: Modem: < \r\nOK\r\n
ofonod[19130]: drivers/atmodem/gprs-context.c:at_cgdcont_cb() ok 1
ofonod[19130]: Modem: > AT+CGDATA="PPP",1\r
ofonod[19130]: Modem: < AT+CGDATA="PPP",1\r
ofonod[19130]: Modem: < \r\nCONNECT\r\n
ofonod[19130]: drivers/atmodem/gprs-context.c:at_cgdata_cb() ok 1
ofonod[19130]: drivers/atmodem/gprs-context.c:setup_ppp()
ofonod[19130]: drivers/atmodem/gprs-context.c:ppp_connect()
What you are seeing is this:
ofonod[6586]: drivers/atmodem/gprs-context.c:at_gprs_activate_primary()
cid 1
ofonod[6586]: Aux: < \r\n
ofonod[6586]: Aux: < +CIEV: rssi,5\r\n
ofonod[6586]: src/network.c:ofono_netreg_strength_notify() strength 100
ofonod[6586]: Aux: < \r\n
ofonod[6586]: Aux: < +CIEV: rssi,4\r\n
ofonod[6586]: src/network.c:ofono_netreg_strength_notify() strength 80
ofonod[6586]: Terminating
That tells me that the port detected as the 'Modem' port is incorrect.
ofonod[6586]: plugins/udevng.c:setup_he910() modem=/dev/ttyACM0
aux=/dev/ttyACM3 gps=/dev/ttyACM5
Please check that those TTYs are indeed live and can accept AT commands.
If not, then you need to update firmware, set the appropriate PORTSEL
setting or update plugins/udevng.c logic for detecting your particular
variant of HE910.
Regards,
-Denis
2:05 a.m.
Denis,
Sorry if I am doing something wrong in posting my queries.
Not sure on top-posting stuff.
Regards,
<Ram>
-----Original Message-----
From: ofono [mailto:ofono-bounces@ofono.org] On Behalf Of Denis Kenzior
Sent: Friday, March 06, 2015 11:59 PM
To: ofono(a)ofono.org
Subject: Re: telit he910 activate-context issue
Hi Ram,
Please do not top-post on this mailing list.
On 03/06/2015 02:28 AM, Kallumari Nagaraja Rao, RammohanX wrote:
Denis,
PFA the logs with AT&C0 & without. With &C0 it is not even creating a
context.
I have just tried my HE910 with unmodified oFono 1.16 and I am able to successfully
activate the context.
My firmware version is 12.00.003, but 12.00.004 is recommended.
What you should be seeing is something like this:
ofonod[19130]: drivers/atmodem/gprs-context.c:at_gprs_activate_primary()
cid 1
ofonod[19130]: Modem: > AT+CGDCONT=1,"IP",""\r
ofonod[19130]: Modem: < AT+CGDCONT=1,"IP",""\r
ofonod[19130]: Modem: < \r\nOK\r\n
ofonod[19130]: drivers/atmodem/gprs-context.c:at_cgdcont_cb() ok 1
ofonod[19130]: Modem: > AT+CGDATA="PPP",1\r
ofonod[19130]: Modem: < AT+CGDATA="PPP",1\r
ofonod[19130]: Modem: < \r\nCONNECT\r\n
ofonod[19130]: drivers/atmodem/gprs-context.c:at_cgdata_cb() ok 1
ofonod[19130]: drivers/atmodem/gprs-context.c:setup_ppp()
ofonod[19130]: drivers/atmodem/gprs-context.c:ppp_connect()
What you are seeing is this:
ofonod[6586]: drivers/atmodem/gprs-context.c:at_gprs_activate_primary()
cid 1
ofonod[6586]: Aux: < \r\n
ofonod[6586]: Aux: < +CIEV: rssi,5\r\n
ofonod[6586]: src/network.c:ofono_netreg_strength_notify() strength 100
ofonod[6586]: Aux: < \r\n
ofonod[6586]: Aux: < +CIEV: rssi,4\r\n
ofonod[6586]: src/network.c:ofono_netreg_strength_notify() strength 80
ofonod[6586]: Terminating
That tells me that the port detected as the 'Modem' port is incorrect.
ofonod[6586]: plugins/udevng.c:setup_he910() modem=/dev/ttyACM0
aux=/dev/ttyACM3 gps=/dev/ttyACM5
Please check that those TTYs are indeed live and can accept AT commands.
If not, then you need to update firmware, set the appropriate PORTSEL setting or update
plugins/udevng.c logic for detecting your particular variant of HE910.
Regards,
-Denis
_______________________________________________
ofono mailing list
ofono(a)ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
1910
days inactive
1914
days old
13 comments
3 participants
participants (3)
-
Denis Kenzior -
Enrico Sau -
Kallumari Nagaraja Rao, RammohanX