<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none;"></style> </head> <body dir="ltr"> <div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr"> <p><span style="font-size: 10pt;">> Oh, that's weird. Which serial port settings are you using when</span><br> </p> <div style="color: rgb(0, 0, 0);"><font size="2"><span style="font-size:10pt;"> <div class="PlainText">> opening the TTY on minicom?</div> <div class="PlainText"><br> </div> <div class="PlainText">I'm using 115200 8N1<br> <br> > Could you get ModemManager debug logs as well to see where/how the<br> > port probing fails?<br> > <a href="https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/" id="LPlnk954037" previewremoved="true">https://www.freedesktop.org/wiki/Software/ModemManager/Debugging/</a><br> <br> Here is where ModemManager seems to fail. It looks like it sends "AT", but never gets a response. I does properly select the ublox plugin though.</div> <div class="PlainText"><br> </div> <div class="PlainText"> <div>ModemManager[705]: <debug> [1494042020.639634] [mm-port-serial.c:1114] mm_port_serial_open(): (ttyACM0) opening serial port...</div> <div>ModemManager[705]: <debug> [1494042020.641101] [mm-port-serial.c:415] real_config_fd(): (ttyACM0): setting up baudrate: 57600</div> <div>ModemManager[705]: <debug> [1494042020.641367] [mm-port-serial.c:1244] mm_port_serial_open(): (ttyACM0) device open count is 1 (open)</div> <div>ModemManager[705]: <debug> [1494042020.642450] [mm-port-serial.c:393] internal_tcsetattr(): (ttyACM0): port attributes not fully set</div> <div>ModemManager[705]: <debug> [1494042020.645462] [mm-port-serial-at.c:459] debug_log(): (ttyACM3): --> 'AT<CR>'</div> <div>ModemManager[705]: <debug> [1494042020.645737] [mm-port-serial-at.c:459] debug_log(): (ttyACM2): --> 'AT<CR>'</div> <div>ModemManager[705]: <debug> [1494042020.740322] [mm-port-serial-at.c:459] debug_log(): (ttyACM1): --> 'AT<CR>'</div> <div>ModemManager[705]: <debug> [1494042020.744884] [mm-port-serial-at.c:459] debug_log(): (ttyACM0): --> 'AT<CR>'</div> <div>ModemManager[705]: <debug> [1494042027.618007] [mm-port-probe-at.c:43] mm_port_probe_response_processor_is_at(): Parsing AT got: 'Serial command timed out'</div> <div>ModemManager[705]: <debug> [1494042027.618729] [mm-port-probe-at.c:43] mm_port_probe_response_processor_is_at(): Parsing AT got: 'Serial command timed out'</div> <br> Any thoughts?<br> <br> > The patch in the github repo could help, but first you need to have<br> > the TTYs properly detected.<br> <br> > -- <br> > Aleksander<br> > <a href="https://aleksander.es" id="LPlnk223489" previewremoved="true">https://aleksander.es</a><br> <br> </div> </span></font></div> </div> </body> </html>