Hi Mattias,

By the way, please no top-posting on this list.

Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App> AT\r
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App< \r\nOK\r\n
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: AppFinally woke up the modem
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App> AT+XSYSTRACE=30\r
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App< \r\nOK\r\n
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: plugins/verimalto.c:trace_start_at_cb()
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App> AT+XSYSTRACE=40\r
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App< \r\nDecoder List 0 bytes sent\r\nOK\r\n Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: plugins/verimalto.c:trace_start_at_cb()
Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App> AT+XSYSTRACE=50\r

So this tells me that XSYSTRACE=40 command response was processed correctly (e.g. OK was detected) and we start the XSYSTRACE=50 command.

Jun 20 13:44:03 lev-26e7jvbe ofonod[16440]: App< \r\n\r\n


This tells me the modem is buggered and isn't responding with anything resembling a 'proper' response. The AT trace will still show anything that is being sent on the serial port, so if there's no 'OK' showing up, there isn't much that oFono can do.

But if I skip the AT+XSYSTRACE=40, the sequence runs fine:

Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: App> AT\r
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: App< \r\nOK\r\n
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: AppFinally woke up the modem
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: App> AT+XSYSTRACE=30\r
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: App< \r\nOK\r\n
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: plugins/verimalto.c:trace_start_at_cb()
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: App> AT+XSYSTRACE=50\r
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]: App< \r\nOK\r\n
Jun 20 13:54:04 lev-26e7jvbe ofonod[16598]:

Right, so something in the earlier XSYSTRACE sequence is screwing up the firmware. Get your vendor on the line.


So I'm suspecting that somehow the extra empty line from AT+XSYSTRACE=40 ends up as the response for the AT+XSYSTRACE=50, but as it is not an OK it expects more, which for some reason isn't read... Don't know why...

Nope. The socket is read and data is printed to debug output regardless of what the syntax state is. See gatio.c:received_data()

Regards,
-Denis
_______________________________________________
ofono mailing list
[email protected]
https://lists.ofono.org/mailman/listinfo/ofono

Reply via email to