qc-linux-modems

qc-linux-modems@lists.osmocom.org

53 discussions

EC25 password for the Debug uart interface
by Florian Eckert 07 Feb '19

07 Feb '19

Hello, I am working on a EC25-1 which has problem with the USB communication with a dwc2 usb host controller [1]. To find the problem my next step was to connect to the EC25 debug UART on pin 11/12. But the system needs a root password! The one you have on your wiki does not work anymore [2]. I think I have the same version "msm LNX.LE.5.0.1-57031-9x40 mdm9607-perf /dev/ttyHSL0" Do you have another password for this interface or where did you get this information from? Thanks for help Flo [1] https://www.spinics.net/lists/linux-usb/msg176613.html [2] https://osmocom.org/projects/quectel-modems/wiki/EC25_Linux#root-password

3 3

Quectel EC25-J Dial up failure
by Mashkur Ahmad 07 Feb '19

07 Feb '19

Hi All, i found the problem to start the qmi dial up, can someone help me out. sudo qmi-network /dev/cdc-wdm0 start Loading profile at /etc/qmi-network.conf... APN: isp.docomoiot.net APN user: unset APN password: unset qmi-proxy: yes Checking data format with 'qmicli -d /dev/cdc-wdm0 --wda-get-data-format --device-open-proxy'... [07 Feb 2019, 09:52:49] -Warning ** [/dev/cdc-wdm0] requested auto mode but no MBIM QMUX support available Device link layer protocol retrieved: raw-ip Getting expected data format with 'qmicli -d /dev/cdc-wdm0 --get-expected-data-format'... [07 Feb 2019, 09:52:49] -Warning ** [/dev/cdc-wdm0] requested auto mode but no MBIM QMUX support available Expected link layer protocol retrieved: 802-3 Updating kernel link layer protocol with 'qmicli -d /dev/cdc-wdm0 --set-expected-data-format=raw-ip'... [07 Feb 2019, 09:52:49] -Warning ** [/dev/cdc-wdm0] requested auto mode but no MBIM QMUX support available error: cannot set expected data format: Expected data format not updated properly to 'raw-ip': got '802-3' instead Error updating kernel link layer protocol Starting network with 'qmicli -d /dev/cdc-wdm0 --wds-start-network=apn=' isp.docomoiot.net' --client-no-release-cid --device-open-proxy'... [07 Feb 2019, 09:52:49] -Warning ** [/dev/cdc-wdm0] requested auto mode but no MBIM QMUX support available error: couldn't start network: QMI protocol error (26): 'NoEffect' Saving state at /tmp/qmi-network-state-cdc-wdm0... (CID: 20) error: network start failed, no packet data handle [07 Feb 2019, 09:52:49] -Warning ** [/dev/cdc-wdm0] requested auto mode but no MBIM QMUX support available Clearing state at /tmp/qmi-network-state-cdc-wdm0... Thanks Mashur Khadmi

1 0

Addme
by Mashkur Ahmad 07 Feb '19

07 Feb '19

Hi Addme

1 0

Adding some info to the wiki pages
by Tomcsányi, Domonkos 15 Aug '18

15 Aug '18

Hi all, I've been looking into Qualcomm based devices mainly for collecting radio traces using Holger's diag-parser tool. I'd like to add the information I was able to collect to the Wiki pages (one new device, and some info on the Sierra EM7455 found in Thinkpads mainly). I've already registered an account in redmine, I'd like to know what's the next step to get to contributing. Thank you! Regards, Domi

2 2

RFC: new type for NAS/EPS in gsmtap.h and question
by Shinjo Park 27 Nov '17

27 Nov '17

Hi list, While I was experimenting with osmo-qcdiag and other LTE stuff, I want to add NAS/EPS as a new payload type for gsmtap.h. Unlike GSM and UMTS, LTE introduced separate layer for encryption of NAS and RRC. As a result, while NAS messages are piggybacked to LTE RRC, but after NAS security had been activated only encrypted NAS messages are available at RRC layer. This is reflected into the baseband diagnostics of various makers: Qualcomm provides separate diagnostic item for LTE NAS (both encrypted and plain) and RRC. Separate payload type for LTE RRC and LTE NAS will solve this issue. I can submit a patch if this looks positive. Also, I have a question regarding ARFCN field. Currently (in version 2) ARFCN is a 16-bit integer, with 2-bit of flags (PCS band, uplink) therefore making 14-bits available for raw value. This causes some problem in LTE: 1) EARFCNs for uplink are starting from 18000, which is larger than 2^14 2) There are EARFCNs even larger than 2^16 (Bands 65+, LTE-U frequencies) 3) No separate indicator for ARFCNs used by UMTS/LTE-TDD network Also in UMTS, there are overlapping UARFCNs between bands, which necessitates a separate field for band indicator. Changes regarding these will break the GSMTAP header structure, therefore I want to discuss about how these could be addressed. Best Regards, Shinjo -- Shinjo Park <pshinjo(a)sec.t-labs.tu-berlin.de> Security in Telecommunications <sec.t-labs.tu-berlin.de> TU Berlin / Telekom Innovation Laboratories Ernst-Reuter-Platz 7, Sekr TEL 17 / D - 10587 Berlin, Germany Phone: +49 30 8353 58272

2 2

build failure explained?
by Jean Pierre TOSONI 25 Sep '17

25 Sep '17

To whoever updates the osmocom wiki: This page: http://osmocom.org/projects/quectel-modems/wiki/Qualcomm_OE_MSM seems to complain about "forward-slashes in the CFLAGS ?!?" code: export EXTRA_CFLAGS="${CFLAGS/Os/O2}" This syntax is a bash shell substitution construct that replaces "Os" with "O2" in CFLAGS, result in EXTRA_CFLAGS. Probably to adapt to a flavor of gcc. Maybe that busybox was not compiled with the bash compatibility option? Regards, Jean-Pierre

1 0

qmiserial2qmuxd: proxying serial QMI requests to qmuxd
by Joey Hewitt 31 Aug '17

31 Aug '17

Hello, Some of you might like to know about a project I released: https://github.com/scintill/qmiserial2qmuxd It's a small Linux/Android program to allow projects such as libqmi to work with qmuxd. It emulates the serial cdc-wdm interface and passes QMI messages back and forth between qmuxd and a client. There's a README on Github with more information. It hasn't been tested very thoroughly yet (I've done several QMI requests on my Samsung GS4 Mini phone), so I'd welcome your feedback, contributions, and questions. For me it's a stepping stone in creating a free Android RIL (early-stage code at https://github.com/scintill/android_frameworks_opt_telephony_ril_ofono ), but hopefully some others can get good use out of it too! Cheers, Joey

1 0

Getting IMEI of modem in ADB-shell
by poldi871＠web.de 22 Aug '17

22 Aug '17

1 0

Quectel EC20EQAR02A08E2G FW Image
by Can Selcik 20 Jan '17

20 Jan '17

Hi, I've recently picked up a Quectel EC20 after hearing about the AT+QLINUXCMD command. While looking around, I somehow managed to get my device stuck in QDL mode where I have only one ttyUSB available and lsusb shows the device in QDL Mode. I have the flashing utility but I don't have an image at hand. Could anyone send it to me or let me know where I can get it? While searching I saw ftp://ftp2.quectel.com but that has the kernel source rather than what I'm looking for, Thanks.

1 0

SIMCom modems
by Petr Štetiar 15 Jan '17

15 Jan '17

Hi, just FYI, I've been told recently, that SIMCom also uses MDM9225 in their SIM72xx (miniPCIe) and MDM9215 in SIM7100x (SMT format) products. So I've updated wiki with some basic details at http://osmocom.org/projects/quectel-modems/wiki/SIMCom -- ynezz

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

qc-linux-modems