Is there any solution to config module “USBCOMP” value without ttyUSB*
when my module USBCOMP value changed, the ttyUSB* port disappear, and i can not make any communication with module.
i’ll need to config this module in windows machine, this make a lot effort to me.
The information is not clear,
Which module are you using?
What value before you config?
What value are you setting in at! usbcomp
Which module are you using?
i have several different module, include EM7511, MC7430, EM7455
What value before you config?
each module have different setting, for example MC7430 is “10D”
i won’t config it, if it is function well.
but some how the config value seems changed by different driver.
such as windows driver or qmi driver. and it caused the ttyUSB* disappear.
similar to
https://forum.sierrawireless.com/t/my-mc7710-cant-work-on-linux-after-plug-in-it-to-windows8/7986
https://forum.sierrawireless.com/t/why-the-ttyusb-disappear-only-cdc-wdm0-interface-left/8591/6
because of the ttyUSB* disappear i won’t be able to recover the config value.
What value are you setting in at! usbcomp
after this issue happened, i found the only solution is to set the original setting under windows system.
i don’t know why, but it works!
although it can be fixed by this way, it still caused a lot of time doing this, i’m hoping there is some other solution under linux system
What do you set for “the only solution is to set the original setting under windows system”?
i’ll use putty send AT command to communicate with com port under windows system.
AT!ENTERCND=“A710”
AT!UDUSBCOMP=?
AT!UDUSBCOMP=7(i’ll select item support AT and avoid MBIM,QMI)
AT!RESET
after these step, the ttyUSB* and module will works well in linux system
(i’m not sure if this is the correct solution or maybe it just effect some other setting through these step.)
thanks for your reply
here says you can stop WNDOWS forcing module to MBIM mode:
I remember it worked for Build4297