Hi Frank,

both TOBYL2_COMPATIBLE_MODE and  TOBYL2_HIGH_THROUGHPUT_MODE behave the
same in the code.
(TOBYL2_MEDIUM_THROUGHPUT_MODE is recognized but discarded later in the
code)
Please replace the two attached files in the plugins directory.
Let me know if it works (it would be good to know which functionalities you
try out), and if so I can submit the changes as patches.

You don't need the udev rule for usb modems, it is recognized automatically.

Best Regards,
Giacinto





On Thu, Sep 13, 2018 at 10:51 PM Frank Vasquez <[email protected]> wrote:

> Hi Giancito,
>
> I modified ublox.c as follows.
>
> enum supported_models {
>         SARA_G270                       = 1102,
>         TOBYL2_COMPATIBLE_MODE          = 1141,
>         TOBYL2_MEDIUM_THROUGHPUT_MODE   = 1143,
>         TOBYL2_HIGH_THROUGHPUT_MODE     = 1107,  /* was 1146 */
> };
>
> And still no luck.
>
> # ./list-modems
> #
>
> I see no evidence that oFono's ublox driver is being loaded even though I
> added the following line to 60-serial-rules in
> /etc/udev/rules.d/60-serial-rules.
>
> KERNEL=="ttyACM0", ENV{OFONO_DRIVER}="ublox"
>
> I want TOBYL2_HIGH_THROUGHPUT_MODE because that's the mode that uses LTE.
>
> Cheers,
> Frank
>
>
> On Thu, Sep 13, 2018 at 12:18 PM Frank Vasquez <[email protected]> wrote:
>
>> Hi Giacinto,
>>
>> The TOBY-R200 is an LTE module.  I see that the ublox oFono plugin
>> supports LTE on the TOBY-L2 so maybe it will work on the TOBY-R200 as
>> well.  I think many of the AT commands are the same across ublox cellular
>> modems so yes let's give testing a shot.
>>
>> I am using Buildroot to build oFono for my Linux device.
>>
>>
>> ################################################################################
>> #
>> # ofono
>> #
>>
>> ################################################################################
>>
>> OFONO_VERSION = 1.21
>> OFONO_SOURCE = ofono-$(OFONO_VERSION).tar.xz
>> OFONO_SITE = $(BR2_KERNEL_MIRROR)/linux/network/ofono
>> OFONO_LICENSE = GPL-2.0
>> OFONO_LICENSE_FILES = COPYING
>> OFONO_DEPENDENCIES = \
>> host-pkgconf \
>> dbus \
>> libglib2 \
>> libcap-ng \
>> mobile-broadband-provider-info
>>
>> OFONO_CONF_OPTS = \
>> --disable-test \
>> --with-dbusconfdir=/etc \
>> $(if $(BR2_INIT_SYSTEMD),--with-systemdunitdir=/usr/lib/systemd/system)
>>
>> # N.B. Qualcomm QMI modem support requires O_CLOEXEC; so
>> # make sure that it is defined.
>> OFONO_CONF_ENV += CFLAGS="$(TARGET_CFLAGS) -D_GNU_SOURCE"
>>
>> define OFONO_INSTALL_INIT_SYSV
>> $(INSTALL) -m 0755 -D package/ofono/S46ofono
>> $(TARGET_DIR)/etc/init.d/S46ofono
>> endef
>>
>> define OFONO_INSTALL_INIT_SYSTEMD
>> mkdir -p $(TARGET_DIR)/etc/systemd/systemd/multi-user.target.wants
>> ln -fs ../../../../usr/lib/systemd/system/ofono.service \
>> $(TARGET_DIR)/etc/systemd/system/multi-user.target.wants
>> endef
>>
>> ifeq ($(BR2_PACKAGE_HAS_UDEV),y)
>> OFONO_CONF_OPTS += --enable-udev
>> OFONO_DEPENDENCIES += udev
>> else
>> OFONO_CONF_OPTS += --disable-udev
>> endif
>>
>> ifeq ($(BR2_PACKAGE_BLUEZ_UTILS),y)
>> OFONO_CONF_OPTS += --enable-bluetooth
>> OFONO_DEPENDENCIES += bluez_utils
>> else
>> OFONO_CONF_OPTS += --disable-bluetooth
>> endif
>>
>> $(eval $(autotools-package))
>>
>> I can modify the downloaded oFono source code (plugins and drivers
>> directories) and rebuild it as needed to test the TOBY-R200.
>>
>> $ ls -l output/build/ofono-1.21
>> total 2528
>> -rw-r--r--  1 frank frank    835 Oct  5  2017 acinclude.m4
>> -rw-r--r--  1 frank frank 360491 Oct  5  2017 aclocal.m4
>> -rw-r--r--  1 frank frank   5356 Oct  5  2017 AUTHORS
>> drwxr-xr-x  2 frank frank   4096 Oct  5  2017 btio
>> -rw-r--r--  1 frank frank  30811 Oct  5  2017 ChangeLog
>> -rwxr-xr-x  1 frank frank   7333 Oct  5  2017 compile
>> -rwxr-xr-x  1 frank frank  43765 Sep 13 11:39 config.guess
>> -rw-r--r--  1 frank frank   2775 Sep 13 11:39 config.h
>> -rw-r--r--  1 frank frank   2492 Oct  5  2017 config.h.in
>> -rw-r--r--  1 frank frank  42877 Sep 13 11:39 config.log
>> -rwxr-xr-x  1 frank frank  67571 Sep 13 11:39 config.status
>> -rwxr-xr-x  1 frank frank  36171 Sep 13 11:39 config.sub
>> -rwxr-xr-x  1 frank frank 467689 Oct  5  2017 configure
>> -rw-r--r--  1 frank frank   8223 Oct  5  2017 configure.ac
>> -rw-r--r--  1 frank frank  18011 Jul 10  2009 COPYING
>> -rwxr-xr-x  1 frank frank  23566 Oct  5  2017 depcomp
>> drwxr-xr-x  2 frank frank   4096 Oct  5  2017 doc
>> drwxr-xr-x 25 frank frank   4096 Oct  5  2017 drivers
>> drwxr-xr-x  2 frank frank   4096 Sep 13 11:39 dundee
>> drwxr-xr-x  2 frank frank   4096 Oct  5  2017 examples
>> drwxr-xr-x  4 frank frank   4096 Sep 13 11:39 gatchat
>> drwxr-xr-x  4 frank frank   4096 Sep 13 11:39 gdbus
>> drwxr-xr-x  3 frank frank   4096 Sep 13 11:39 gisi
>> drwxr-xr-x  3 frank frank   4096 Sep 13 11:39 gril
>> drwxr-xr-x  3 frank frank   4096 Sep 13 11:39 include
>> -rw-r--r--  1 frank frank   9478 Jul 10  2009 INSTALL
>> -rwxr-xr-x  1 frank frank  14431 Oct  5  2017 install-sh
>> -rwxr-xr-x  1 frank frank 294282 Sep 13 11:39 libtool
>> -rw-r--r--  1 frank frank 283940 Sep 13 11:39 ltmain.sh
>> -rw-r--r--  1 frank frank 283672 Oct  5  2017 ltmain.sh.orig
>> -rw-r--r--  1 frank frank 185608 Sep 13 11:39 Makefile
>> -rw-r--r--  1 frank frank  28755 Oct  5  2017 Makefile.am
>> -rw-r--r--  1 frank frank 204311 Oct  5  2017 Makefile.in
>> -rwxr-xr-x  1 frank frank   6872 Oct  5  2017 missing
>> -rw-r--r--  1 frank frank      0 Jul 10  2009 NEWS
>> -rw-r--r--  1 frank frank    310 Sep 13 11:39 ofono.pc
>> -rw-r--r--  1 frank frank    325 Feb  6  2011 ofono.pc.in
>> drwxr-xr-x  3 frank frank   4096 Sep 13 11:39 plugins
>> -rw-r--r--  1 frank frank    886 Jul 19  2012 README
>> drwxr-xr-x  4 frank frank   4096 Sep 13 11:39 src
>> -rw-r--r--  1 frank frank     23 Sep 13 11:39 stamp-h1
>> drwxr-xr-x  2 frank frank   4096 Oct  5  2017 test
>> -rwxr-xr-x  1 frank frank   4287 Sep 13  2015 test-driver
>> -rw-r--r--  1 frank frank  17996 May  3  2016 TODO
>> drwxr-xr-x  2 frank frank   4096 Oct  5  2017 tools
>> drwxr-xr-x  4 frank frank   4096 Sep 13 11:39 unit
>>
>> Cheers,
>> Frank
>>
>>
>>
>> On Thu, Sep 13, 2018 at 11:48 AM Giacinto Cifelli <[email protected]>
>> wrote:
>>
>>> hi Frank,
>>>
>>> your modem doesn't seem to be supported.
>>> There are these models:
>>> SARA_G270 = 1102,
>>> TOBYL2_COMPATIBLE_MODE = 1141,
>>> TOBYL2_MEDIUM_THROUGHPUT_MODE = 1143,
>>> TOBYL2_HIGH_THROUGHPUT_MODE = 1146,
>>> If your model is compatible with any of them, I can add  the 1107 for
>>> you for a test.
>>>
>>> from the PID, I would say it should be intermediate between the
>>> SARA_G260 and the TOBYL2_COMPATIBLE_MODE.
>>> Most likely it will work this latter, but maybe not all features...
>>>
>>> Are you willing to test?
>>>
>>> Best regards,
>>> Giacinto
>>>
>>>
>>>
>>> On Thu, Sep 13, 2018 at 7:48 PM Frank Vasquez <[email protected]> wrote:
>>>
>>>> Hi Giacinto,
>>>>
>>>> > can you send the result of "lsusb" and "lsusb -t"?
>>>>
>>>> The usbutils version of lsusb is somewhat better.
>>>>
>>>> # lsusb
>>>> Bus 002 Device 001: ID 1d6b:0003
>>>> Bus 001 Device 002: ID 1546:1107
>>>> Bus 001 Device 001: ID 1d6b:0002
>>>> # lsusb -t
>>>> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
>>>> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
>>>>     |__ Port 1: Dev 2, If 0, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 1, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 2, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 3, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 4, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 5, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 6, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 7, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 8, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 9, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 10, Class=, Driver=cdc_acm, 480M
>>>>     |__ Port 1: Dev 2, If 11, Class=, Driver=cdc_acm, 480M
>>>>
>>>> And here is a relevant excerpt from lsusb -v.
>>>>
>>>> Bus 001 Device 002: ID 1546:1107
>>>> Device Descriptor:
>>>>   bLength                18
>>>>   bDescriptorType         1
>>>>   bcdUSB               2.00
>>>>   bDeviceClass          239
>>>>   bDeviceSubClass         2
>>>>   bDeviceProtocol         1
>>>>   bMaxPacketSize0        64
>>>>   idVendor           0x1546
>>>>   idProduct          0x1107
>>>>   bcdDevice           17.29
>>>>   iManufacturer           1 u-blox
>>>>   iProduct                2 u-blox Cellular Module
>>>>   iSerial                 3 352848080392646
>>>>   bNumConfigurations      1
>>>>   Configuration Descriptor:
>>>>     bLength                 9
>>>>     bDescriptorType         2
>>>>     wTotalLength          405
>>>>     bNumInterfaces         12
>>>>     bConfigurationValue     1
>>>>     iConfiguration          0
>>>>     bmAttributes         0xe0
>>>>       Self Powered
>>>>       Remote Wakeup
>>>>     MaxPower              100mA
>>>>     Interface Association:
>>>>       bLength                 8
>>>>       bDescriptorType        11
>>>>       bFirstInterface         0
>>>>       bInterfaceCount         2
>>>>       bFunctionClass          2
>>>>       bFunctionSubClass       2
>>>>       bFunctionProtocol       1
>>>>       iFunction               4 CDC ACM
>>>> ...
>>>>
>>>> Cheers,
>>>> Frank
>>>>
>>>>
>>>> On Thu, Sep 13, 2018 at 10:21 AM Frank Vasquez <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi Giacinto,
>>>>>
>>>>> > can you send the result of "lsusb" and "lsusb -t"?
>>>>>
>>>>> # lsusb -t
>>>>> Bus 001 Device 001: ID 1d6b:0002
>>>>> Bus 001 Device 002: ID 1546:1107
>>>>> Bus 002 Device 001: ID 1d6b:0003
>>>>>
>>>>> I am running BusyBox's stripped down version of lsusb that's why
>>>>> information is so lacking.
>>>>> I'll install usbutils on my device's Buildroot image and rerun the
>>>>> commands.
>>>>>
>>>>> Cheers,
>>>>> Frank
>>>>>
>>>>> On Thu, Sep 13, 2018 at 3:49 AM Giacinto Cifelli <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> hi Frank,
>>>>>>
>>>>>> can you send the result of "lsusb" and "lsusb -t"?
>>>>>>
>>>>>> Giacinto
>>>>>>
>>>>>> On Thu, 13 Sep 2018, 00:41 Frank Vasquez, <[email protected]> wrote:
>>>>>>
>>>>>>> Greetings,
>>>>>>>
>>>>>>> I have an embedded device with a ublox TOBY-R200 on it.  I want to
>>>>>>> use connman to manage any cellular connection on that modem since 
>>>>>>> connman
>>>>>>> is already managing ethernet and wifi connectivity.  oFono seems like 
>>>>>>> the
>>>>>>> best option.  I see that there is already a ublox plugin for oFono but I
>>>>>>> don't think the TOBY-R200 is supported.  The cell module is soldered 
>>>>>>> onto
>>>>>>> the board and appears as a USB device.
>>>>>>>
>>>>>>> [    6.519190] usb 1-1: New USB device strings: Mfr=1, Product=2,
>>>>>>> SerialNumber=3
>>>>>>> [    6.519197] usb 1-1: Product: u-blox Cellular Module
>>>>>>> [    6.519204] usb 1-1: Manufacturer: u-blox
>>>>>>> [    6.519211] usb 1-1: SerialNumber: 352848080392646
>>>>>>>
>>>>>>> I can send AT commands to the modem over /dev/ttyACM0.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Frank
>>>>>>> _______________________________________________
>>>>>>> ofono mailing list
>>>>>>> [email protected]
>>>>>>> https://lists.ofono.org/mailman/listinfo/ofono
>>>>>>>
>>>>>>

Attachment: ublox.c
Description: Binary data

Attachment: udevng.c
Description: Binary data

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

Reply via email to