qmicli working for EM7455
Brandon Lee
blee0518 at gmail.com
Mon Mar 30 17:17:26 UTC 2020
Sorry for the off topic reply. Got it mixed up with another issue.
But to further the response from the previous person, my wda error occurs
well after the modem is powered up. I guess a step in a script on the start
up causing it, could be to state if error occurs sleep 5s and try again.
My MC7455 has a sleep time of 8s from boot to give enough time for modem to
boot and run startup checks. This script is in my startup dir:
/etc/rc.local. running Raspbian Buster.
On Mon, Mar 30, 2020, 10:08 AM Brandon Lee <blee0518 at gmail.com> wrote:
> Doing some research, getting referred a link that didnt help, and a some
> rest landed me to think of using a different format. I will try this later
> today.
> Previous format i tried:
> # assign module1 to cdc-wdm0
> KERNEL=="cdc-wdm0", \
> ATTR{idProduct}=="9071", \
> SYMLINK+="cdc-wdm0"
>
> Looking to try:
> KERNEL=="cdc-wdm*", KERNELS=="1-4:1.0", SYMLINK+="cdc-wdm"
>
> What i was reading from had this:
> KERNEL=="ttyACM*", KERNELS=="1-4:1.0", SYMLINK+="sensor_0"
>
> I am not sure if mine will work as this read also said KERNEL will be
> tty*** every time bc thats how its seen. Im not sure but if it works it
> will be assigning the physical port to cdc-wdm*
>
>
>
> On Mon, Mar 30, 2020, 2:58 AM Tor Rune Skoglund <trs at fourc.eu> wrote:
>
>> This seems to be quite similar to our issue with Sierra Wireless MC7304.
>> See my post yesterday:
>> https://lists.freedesktop.org/archives/libqmi-devel/2020-March/003252.html
>>
>> I have no "proper" fix, but really interested in finding one. Our very
>> temporary fix was to keep resetting the USB port to make the modem also
>> reset until we by pure luck gets it to work.
>>
>> Best regards,
>>
>> Tor Rune Skoglund
>> Den 30.03.2020 07:40, skrev Brandon Lee:
>>
>> I am having issues with EM7455.
>> I used `.rules` to make sure device ATTRs use qmi_wwan driver
>> it shows in `lsusb -t` that modem is using these drivers.
>> Running latest firmware update for ATT, and have tried GENERIC
>>
>> When running `qmi-network /dev/cdc-wdmX start` I get :
>> ```Checking data format with 'qmicli -d /dev/cdc-wdm2
>> --wda-get-data-format '...
>> error: couldn't create client for the 'wda' service: CID allocation
>> failed ine CTL client: Transaction timed out
>> Device link layer protocol not retrieved: WDA unsupported
>> Starting network with 'qmicli -d /dev/cdc-wdm2
>> --wds-start-network=apn='broadd' --client-no-release-cid '...
>> error: couldn't create client for the 'wds' service: CID allocation
>> failed ine CTL client: Transaction timed out
>> error: network start failed, client not allocated
>> ```
>>
>>
>> When I try to run Start-network manually, i get this response:
>> ```
>> error: couldn't create client for the 'wds' service: CID allocation
>> failed ine CTL client: Transaction timed out
>> ```
>>
>> If I remove the .rules file from running giving the port mbim_wwan, I
>> have been able to run `mbim-network /dev/cdc-wdmX start` and get a network
>> start successfully, but I am not able to get an IP address.
>> `ifconfig` shows the interface up but does not give it an IP address.
>>
>> This modem would be the second modem I am running on my Debian device,
>> the primary(working) one now is MC7455 with qmi and raw-ip. I am able to
>> get DHCP address with this modem fine.
>>
>> I have read that you need to get DHCP address from another source, i am
>> using systemd-networkd retrieve an IP, just as I do with my MC7455.
>> Can you help with fixing in either way?
>>
>> _______________________________________________
>> libqmi-devel mailing listlibqmi-devel at lists.freedesktop.orghttps://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libqmi-devel/attachments/20200330/0d416841/attachment.htm>
More information about the libqmi-devel
mailing list