Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 13 Mar 2019 10:47:05 -0400
From:      Mike Tancsa <mike@sentex.net>
To:        Hans Petter Selasky <hps@selasky.org>, freebsd-usb@FreeBSD.org
Subject:   Re: strange USB timing issue with u3g
Message-ID:  <def35d07-7e02-77dc-e97b-92b21fc301f5@sentex.net>
In-Reply-To: <2476a53c-e223-1c81-165c-73fa884f30da@selasky.org>
References:  <3377e001-f035-acec-765c-aee7113f20d4@sentex.net> <2476a53c-e223-1c81-165c-73fa884f30da@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 3/12/2019 5:43 PM, Hans Petter Selasky wrote:
> On 3/12/19 9:49 PM, Mike Tancsa wrote:
>>
>
> Hi,
>
> Maybe the device expects some kind of BIOS to enumerate it quickly and
> if not, goes into sleep mode.
>
> Try setting:
> hw.usb.ehci.no_hs=3D1
>
> In /boot/loader.conf .
>
> Does this change anything?

usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_IOERROR
usbd_setup_device_desc: getting device descriptor at addr 2 failed,
USB_ERR_IOERROR
usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_IOERROR,
ignored)
usbd_req_re_enumerate: addr=3D2, set address failed! (USB_ERR_IOERROR,
ignored)

seems to reliably come up with this setting on when loading u3g out of
loader.conf and letting devd do it later.

The other variable that can trigger it is if I load a bunch of other
klds like umodem, ucom,uplcom and uftdi.=C2=A0


>
> USB devices are not allowed to return with a STALL-PID on set-address
> messages, so this is violation of established USB standards. Maybe you
> need a USB wire-analyzer to nail this issue.
>
> There are a bunch of tunables for example:
> hw.usb.timings


Although testing a bit with

hw.usb.timings.extra_power_up_time=3D990

seems to make the error on dmesg just up come up at a different, later
point.

setting

hw.usb.timings.port_powerup_delay=3D1000

does seem to help!=C2=A0 At least I was able to boot up 50% of the time.=C2=
=A0
Trying with 2000 however, does not seem to make it better.=C2=A0 still 50=
/50


>
> Which affect how the USB device is enumerated.
>
> Is your device running the latest firmware from HUAWEI?

Not sure. I have never upgraded the firmware in these guys before.

Manufacturer: Huawei Technologies Co., Ltd.
Model: ME909u-523
Revision: 11.430.63.00.00
IMEI: xxxxx
+GCAP: +CGSM

Do you know of any references on how to do this ?=C2=A0 Looking at the AT=

command manual


AT^FOTADET
OK

^FOTASTATE: 11

^DEND: 1,33,IPV4


and tried again

AT^FOTADET
OK

^FOTASTATE: 11

^FOTASTATE: 13,13

^HCSQ: "LTE",50,41,94,10

^HCSQ: "LTE",44,41,137,22

AT^FOTADLQ
^FOTADLQ: 1,"FIRMWARE1",0,0

I think 13 means "New version query failed"

My guess is that I need to setup some specific APN data to talk to
Huawei ?=C2=A0 The modem is not specifically designed for the carrier, so=
 I
dont know if the carrier usually has stuff behind the scenes for such
updates.

Although the command AT^FWLOAD=3D<update_type>

This command is used to specify the upgrade type, transmit the upgrade
file into the
module using 1K-Xmodem, and start the upgrade. The following table lists
the ports
supported by the full and differential upgrades.

So if I can find a firmware file, I can do an old school xmodem-1k
upload. I will see if I can find one from Huawei.


>
> --HPS
>
>

--=20
-------------------
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, mike@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada  =20





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?def35d07-7e02-77dc-e97b-92b21fc301f5>