I only use “cat” command to monitor /dev/ttyUSB2.
Because I use AC341U USB dongle, and it has receive responses.
So I need to use minicom replace “cat” command?
If yes, I will build minicom to test it.
I have seen this symptom on the MC7455 and EM7455 a few times without yet being able to pinpoint the actual problem. What I have found is that a “usb device reset” (not a modem reset - that does not help) “fixes” the problem. At least it has for me. No guarantees, but worth trying.
I am sure you are right. But I still wish they would share those problems so that the problems could be fixed. Using GobNet and GobiSerial is definitely correct for anyone who wants to develop a Sierra supported solution. Or for anyone having problems with the qcserial/qmi_wwan drivers. Or simply to eliminate drivers as a source of any observed problem.
But even if one set of working drivers is enough, it would still be nice to have any known issues with the qcserial/qmi_wwan drivers fixed as well. Don’t you think so?
Frankly, I do not see why you cannot qualify these problems if you “know” about them. There never is much point in referring to problems you are unable to describe. It just looks like FUD. At least to me. Sorry.
We don’t ‘know’ about them, we have seen them and pushed customers to use software we know works and we are able to support. It is not our place to support open source software, particularly software that is used in direct competition to the hardware that we sell.
As I am sure you know, every system is different and as such something that affect one system will have no effect on another (I ran with qcserial for a couple of years without realising it until I plugged a unit with a specific combination of firmware in and it all went wrong).
I am sorry if you do not like this approach but we do have a business to run.
But I take any reports of problems seriously. If you have a problem and want it fixed, then please give details. If you have a problem and don’t want it fixed, tben please don’t tell me that you have a problem in the first place
This makes me very sorry to hear.
And I sincerely believe you are wrong. The Sierre Wireless QMI SDK is a unique product which in no way can be replaced by any community developed and unsupported software. There just is no competition there. On the contrary: Those “products” complete each other by making Sierra Wireless modems available to a larger set of end users.
Yes, I know. Which is why I wanted to know more details. We can only improve if we know about the specific cases where it goes wrong.
GobiSerial is open source too. Of course you do not need to support qcserial, but if you happen to find problems, then you can report them and they will be fixed. This is not “supporting”.
Also you hopefully have an endeavour that the devices you sell are working correctly. And since qcserial is in the kernel (as opposed to GobiSerial) you have a direct advantage if the devices are working with this driver. The modems you sell are in various Laptops and dongles, people who are using them are most likely not to use GobiNet and GobiSerial for their standard usecase of “Internet access”.
For OP: I am using screen for accessing the serial ports. You need to make sure that only one program is accessing the serial port at the same time.
Ok so you are using Open WRT and not pure Linux then? The drivers are intended specifically for Linux and while they are close as OS’s they aren’t exactly the same, I do not know why you are unable to send the AT commands. I know there are people who have got it working but I do not know how.
Thanks for your help.
I have some questions about:
1.If EM7430 is not have firmware, it might probe successfully?
Because I am not sure that EM7430 has firmware or not.
2.I found electronic SPEC in datasheet, and hardware issue might cause ttyUSB abnormally?