ublox SARA-U260 not showing up in mmcli

[Einar Jón]

>
> Hello,
>
>
> I am using ModemManager version 1.7.0, and have checked out the master branch that has the ublox plugins.  I have compiled this using buildroot and installed on a custom i.MX6 board with the ublox SARA-U260 connected via USB.  The imx6 sees the USB device and creates 7 ttyACMx ports, but when I check ModemManager, there are no modems listed.  Thinking that maybe there wasn't support for the SARA-U260, I also tried adding a patch from here: https://github.com/Scypho/modemmanager-ublox/tree/sara-u270, which looks to add support for the U270.  I compiled again and still no luck.  Is there something else I need to do?
>
>
> # lsusb
>
> Bus 001 Device 003: ID 1546:1102 U-Blox AG
>
>
> # ls /dev/ttyACM*
>
> /dev/ttyACM0  /dev/ttyACM2  /dev/ttyACM4  /dev/ttyACM6
> /dev/ttyACM1  /dev/ttyACM3  /dev/ttyACM5
>
> # mmcli -V
> mmcli 1.7.0
> Copyright (2011 - 2016) Aleksander Morgado
>
> # mmcli -L
> No modems were found
>
> # dmesg | grep acm
> [    1.861414] usbcore: registered new interface driver cdc_acm
> [    1.865803] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
> [    4.856405] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
> [    4.894693] cdc_acm 1-1.1:1.2: ttyACM1: USB ACM device
> [    4.940068] cdc_acm 1-1.1:1.4: ttyACM2: USB ACM device
> [    4.956373] cdc_acm 1-1.1:1.6: ttyACM3: USB ACM device
> [    4.968178] cdc_acm 1-1.1:1.8: ttyACM4: USB ACM device
> [    4.985635] cdc_acm 1-1.1:1.10: ttyACM5: USB ACM device
> [    5.021563] cdc_acm 1-1.1:1.12: ttyACM6: USB ACM device
>
> I should note that when I try to send AT commands using screen or minicom, it behaves a little weird.  When I try to type in "AT+CGMI", it will type "@T*BFLH" instead.  Could this be the problem?  Any ideas why the letters on my keyboard don't mach up to what is shown on screen/minicom?

I'm not sure if this helps, but I noticed that all the letters in
"@T*BFLH" are off by one, except T.
In ascii, T is the only letter that is even.
So minicom sems to be zeroing out the last bit of your messages, (A =
ascii 0x41 -> ascii 0x40 = @ and I = ascii 0x49 -> ascii 0x48 -> I).
That's the "what", but I can't think of the "why"...

Have you tried other serial programs (microcom, miniterm.py etc?)

Cheers,
Einar Jón