We are using the sample app that comes with the QMI SDK to test the device. We are using the ‘Connection_Manager’ sample app.
We are testing this using Ubuntu 12.04 with Kernel 3.2
We bring up the program and create a profile for AT&T and attempt to connect it, all it says is, “DATA CONNECTION SUCCESSFUL” and returns us to the main menu
So… it didn’t create us an interface to use. Typically I see (with other cellular cards) a ppp interface is brought up, or even in some rare cases another eth interface is created.
So far we haven’t seen anything like that.
One person mentioned to us that we have to compile the pkgs directory in the QMI SDK? How do we do that? all I see in that directory is ‘slqcompile.mak’ and I attempt to call ‘make -f pkgs.mak complete’ and that doesn’t work.
We are looking at Section 4.1 in the Sierra Wireless Linux Application Developers Guide (see attachment for screenshot)
In the QMI SDK from Sierra, there exists a pkgs directory, but nothing there builds as stated in the guide. Is it outdated?
I’m having exactly this same problem. I’ve not found any “ah ha’s” elsewhere in these forums. Does anyone have some points on how to proceed?
When you plug the unit into your system it should create two additional eth interfaces (typically 0 and 2 which straddle the eth1 for the PC ethernet interface). I have attached a zip file with some text files in which both show a terminal, hopefully they are self explanatory, but
- Interfaces.txt - Shows the inferfaces that are up prior to a session started and then after it has been started.
- Connection manager.txt - Shows starting the application and a data session in the middle of the above.
MC73 QMI IP connection_manager termials - No dhclient.zip (3.15 KB)
Hello mlw, Your post and attached connection manager and interface.txt files are very helpful.
In my case after LTE Data Session successful connection through connection manager I need to make discover dhcp manually.
Is there a way we can get ip address through auto dhcp setting while making connection itself?
So do you mean you do not want to us dhclient?
I guess you could stick a hard rule in somewhere to replicate the functionality but no too sure how to do that.
I have the same issue. There is no pkgs.mak file in the pkgs directory to compile at all…
I have re read the thread. The pkgs.mak file is a hang over in the documentation for re building the actual SDK executable process itself which is unnecessary due to the fact that Sierra supply it pre compiled for most of the architectures, it is also not possible since we do not make the source for the SDK public.
You do not need the pkgs.mak to rebuild any of the applications if you want to do this there are individual make files in the projects themselves, I have had problems in the past where using these files resulted in problems finding header files, etc but this is down to the individual system and the way it is set up, also it could be down to the fact that the application wants you to build it as a 32 bit machine and not 64 which quite a few default to.