I’m trying to integrate the MC5728V on custom arm-based hardware, but am having some issues with SDK. Mainly, documentation says the SDK (v1.0.4.5) supports the MC5728V. However, the code in pkgs/us/usudefs.h does not include a Product ID entry for the MC5728V (0x0301). So when ddgetdevtype() is called - it returns 0 = SWI_DEVICE_None.
Any suggestions here?
Hi,
Can you share the kern log when connecting MC5728V?
According to sierra.c, PID 0x0301 belongs to 3G dongle and PID of MC5728V should be either 0x0028 or 0x0400.
Thanks.
L
My kernel log does not give vid:pid, but here are relevant parts…
[ 2.410000] USB Mass Storage support registered.
[ 2.410000] usbcore: registered new interface driver usbserial
[ 2.420000] usbserial: USB Serial Driver core
[ 2.420000] USB Serial support registered for Sierra USB modem
[ 2.430000] usbcore: registered new interface driver sierra
[ 2.440000] sierra: v.1.7.40:USB Driver for Sierra Wireless USB modems
…
[ 3.530000] usb 2-1: new full speed USB device using fsl-ehci and address 3
[ 3.700000] sierra 2-1:1.0: Sierra USB modem converter detected
[ 3.720000] usb 2-1: APM supported, enabling autosuspend.
[ 3.730000] usb 2-1: Sierra USB modem converter now attached to ttyUSB0
[ 3.750000] usb 2-1: Sierra USB modem converter now attached to ttyUSB1
[ 3.760000] usb 2-1: Sierra USB modem converter now attached to ttyUSB2
[ 3.780000] usb 2-1: Sierra USB modem converter now attached to ttyUSB3
And here is output from log while executing “aptest -v -n t1 -p /sbin/swisdk”
Feb 16 22:07:20 devjb user.err SWI SDK Process: USDT:usdet: Modem detected. VID 1199, PID 301
The MC5728V (as far as I know) is a 3G modem, in mincard form-factor, with USB interface. The labelling on the module reads:
MC5728V FCC ID: N7N-MC5728 IC: 2417C-MC5728
Thanks.
Has anyone run into this? An added detail is that when the modem enumerates on my linux laptop (linux-2.6.37, v1.7.40 sierra driver), the Product ID is reported as 0x0028. But when the modem enumerates on custom hardware (linux-2.6.35, v1.7.40 sierra driver), the Product ID is reported as 0x0301. Can anyone explain this behavior?
Hi,
So PID 0x0301 only happens on your ARM board and I believe you already verified that SDK is working on your Linux desktop with that particular MC5728V module.
Have you tried to send AT command to ttyUSB interface and see if it works on your ARM platform with MC5278V?
Do you aware any USB issue on the ARM’s USB host controller?
What’s firmware version is running on that MC5728V?
Maybe bad idea, can you try to add the define for “SWI_MC5728GM = 0x0301” in usudefs.h and see what happens?
Thx.
L
Have successfully sent AT commands. Here are results of ATI…
Manufacturer: Sierra Wireless, Inc.
Model: MC5728V Rev 1.0 (5)
Revision: p3013301,61083 [Jun 24 2010 12:18:30]
QCOM: SWI6085_FP.01.28
BOOT: SWI6085_PP.01.33.01 2010/06/24 15:02:12
APPL: SWI6085_PP.01.33.01 2010/06/24 15:02:12
USBD: SWI6085_GENERIC.00.01
USB VID: 0x1199 PID: 0x0301
ESN: 09613621432
0x60CFD8B8
+GCAP: +CIS707-A, CIS-856, CIS-856-A, +MS, +ES, +DS, +FCLASS
SKU: 0x82BC3
OK
However, with identical module inserted in Sierra EVK and connected via USB to windows, ATI result is…
Manufacturer: Sierra Wireless, Inc.
Model: MC5728V Rev 1.0 (5)
Revision: p2813301,61083 [Jun 24 2010 12:18:30]
QCOM: SWI6085_FP.01.28
BOOT: SWI6085_PP.01.33.01 2010/06/24 15:02:12
APPL: SWI6085_PP.01.33.01 2010/06/24 15:02:12
USBD: SWI6085_GENERIC.00.01
USB VID: 0x1199 PID: 0x0028
ESN: 09613621493
0x60CFD8F5
+GCAP: +CIS707-A, CIS-856, CIS-856-A, +MS, +ES, +DS, +FCLASS
SKU: 0x82BC3
OK
We have no other known USB issues on our host controller. I tried adding support for PID=0301 into SDK code and got the same result.
Any ideas what signals to the MC5728V cause it to report itself as 0301 instead of 0028?
Hi,
Have you verified the SDK functionality using desktop linux with that MC5728 module?
Do you have another MC5728 module to test on your embedded board?
Also, how do you connect MC5728 to your embedded board and PC? Are you using same MC devkit?
Any extra hardware pin was connected between your MC5728 and embedded board?
thx
Yes, SDK functionality has been verified using a different model of modem.
Have tried two different MC5728V modules on our hardware and both behaved the same.
On our hardware, MC5728V is connected via standard minicard connector (mPCIe) and communicates via USB signals (not UART). When connecting with PC, the MC5728V is inserted into Sierra EVK and connected to PC via USB.
Not sure what you mean by extra hardware pin - we connect to all appropriate signals defined on the MC5728 module connector, including all UART signals, W_DISABLE, RESET, all power, all gnd.