diff options
| author | Aleksander Morgado <aleksander@aleksander.es> | 2017-12-24 08:38:33 +0100 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@aleksander.es> | 2018-01-04 10:09:24 +0100 |
| commit | 30ea91e353ae58df2407f837979af39ed3b4a49b (patch) | |
| tree | 58776360f48c3e76de0095b3e8ffb8d6d015f640 /docs/reference/api | |
| parent | c97b9d99e3ca62ff7af3b74afe05a9d80f16b8bb (diff) | |
ublox: wait for READY URCs during port probing
The AT control TTYs in the u-blox modems may take some time to be
usable. In order to handle this issue, we configured some longer
timeouts during AT probing, but that may not be always enough.
The u-blox TTYs will report readiness via a "+AT: READY" URC, which
we can use during custom initialization to decide right away that the
port is AT. We use up to 20s as that is close to the worst case seen
during experimentation, happening after the module undergoes a full
NVM reset. If the timeout is reached without receiving the URC, we
still run standard AT probing afterwards. This new logic just tries
to make it sure we don't do any probing before the module is ready to
accept it.
If the module hasn't been hotplugged (i.e. it was already there when
ModemManager started) we do a quick first AT probing and if that fails
we run the "+AT: READY" URC wait as if it was hotplugged.
Diffstat (limited to 'docs/reference/api')
0 files changed, 0 insertions, 0 deletions