-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cellular: UBLOX socket write data error #12461
Comments
There is an architectural bug in the Mbed AT driver where it assumes that all responses from the modem will be terminated with an end-of-line character like '\n'. This assumption is false for the Ublox AT interface, meaning the Mbed AT framework will need a small but fundamental change to properly support Ublox modems. I don't know how such a disastrous bug got past any kind of QA testing. I've never seen the Mbed Ublox driver work at all. Fortunately, the driver posted by Ublox in the contributed code section (https://os.mbed.com/teams/ublox/) works fine (once you get the APN etc. sorted out). |
Internal Jira reference: https://jira.arm.com/browse/MBOTRIAGE-2553 |
cc @ARMmbed/team-ublox @ARMmbed/cellular-team Please review |
Need to read |
PR created #12499. |
Description of defect
When trying to write to a TCP socket, AT command will trigger binary syntax mode meaning it sends socker_id + number of bytes and than
<CR>
which is fine.But then the lib should wait until character
@
is received. And this is where the problem is - current implementation doesn't wait and sends it straight after AT command resulting in-3012
error because library is waiting for a response from mdm, but mdm is waiting for that binary data.Target(s) affected by this defect ?
SARA-G350
Toolchain(s) (name and version) displaying this defect ?
GCC-ARM 8.3.1
What version of Mbed-os are you using (tag or sha) ?
3d038e5
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.1
How is this defect reproduced ?
The text was updated successfully, but these errors were encountered: