Re: [Ltib] Re: Sierra 3G modem not working on Phytec Board. (missing US

On Wed, Jul 21, 2010 at 2:50 AM, Kevin Wells <address@hidden> wrote:

Hi Quentin,

>However, on Phytec board (Using OHCI USB Host Controller) Sierra modem is reporting only 1 USB interface available.

You might need to ping Sierra Wireless about this specific issue – it sounds like all your ports aren’t enumerating and a tweak is needed somewhere.

I don’t think this is an issue with OHCI or EHCI. The outputted shown is only the enumerated output. What the modem is requesting may be different.

Have you tried building the usbserial and sierra code as modules? Then try manually installing the usbserial module with the vendor= and product= parameters.

address@hidden serial]# insmod -v usbserial vendor=0x1199 product=0x683c

Using /lib/modules/2.6.34/kernel/drivers/usb/serial/usbserial.ko

usbcore: registered new interface driver usbserial

USB Serial support registered for generic

usbcore: registered new interface driver usbserial_generic

usbserial: USB Serial Driver core

address@hidden serial]# insmod -v sierra.ko

Using sierra.ko

USB Serial support registered for Sierra USB modem

usbcore: registered new interface driver sierra

sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems

Sorry – I can’t physically try the modem here without sierra hardware.

thanks,

Kevin

Subject: [Ltib] Re: Sierra 3G modem not working on Phytec Board. (missing USB End Points, only ep00,ep01,ep81 created.)

Hi Sirnivas, Giri,

More Info about MC8790V not working on Phytec Board.

I tracked back to USB device level.
I found that Sierra modem on Linux PC (Using EHCI USB Host controller) is reporting 7 USB interfaces.

However, on Phytec board (Using OHCI USB Host Controller) Sierra modem is reporting only 1 USB interface available.

See attached file of 'sysfs directories' for Sierra USB Device. (OnPC_SierraModem_Has_7_USB_Interfaces.txt   OnPhytec_LPC3250_SierraModem_Just_1_USB_Interface.txt)

Any thoughts?

BTW, I haven't seen any 'usb debug msg' about the 'USB Interface enumeration''. Although I enabled the 'USB debugging message'.

In kernel '.config ' file (I attached kernel config for kernel_2.6.34.) ( GsnKernelPreConfig-2634.config )

#
# Console display driver support
#
# CONFIG_VGA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y
# CONFIG_SOUND is not set
# CONFIG_HID_SUPPORT is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
# CONFIG_USB_ARCH_HAS_EHCI is not set
CONFIG_USB=y
CONFIG_USB_DEBUG=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG_WHITELIST is not set
# CONFIG_USB_OTG_BLACKLIST_HUB is not set
CONFIG_USB_MON=y
# CONFIG_USB_WUSB is not set
# CONFIG_USB_WUSB_CBAF is not set

#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
# CONFIG_USB_OXU210HP_HCD is not set
# CONFIG_USB_ISP116X_HCD is not set
# CONFIG_USB_ISP1760_HCD is not set
# CONFIG_USB_ISP1362_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set
# CONFIG_USB_HWA_HCD is not set
# CONFIG_USB_MUSB_HDRC is not set

Regards,
Quentin

On Mon, Jul 19, 2010 at 12:30 PM, Quentin YANG <address@hidden> wrote:

Hi Srinivas&Bangaragiri,

After some troubles to get linux kernel 2.6.34 running on Phytec board (Rootfs mounting issue), which I will address in another email，Ｉ've noticed another interesting thing that might give us some clues why not all USB end points of Sierra 3G Modem MC8790 appeared.

On Linux PC (Sierre 3G modem can work smoothly.) Actually Sierra 3G modem is identified and connected to USB EHCI Host Controller (ehci-hcd.c) and treated as EHCI USB device.

However, on Phytec board Sierra 3G modem is identified and connected to USB OHCI Host Controller (ohci-hcd.c) and treated as OHCI USB device.
(LPC3250 on Phytec board only has OHCI USB Host Controller.)

See attached 'USB_EHCI_Vs_OHCI_3G_Sierra_Modem.txt' for details.

I am about to disable EHCI support on Linux PC by recompiling the kernel, and see whether Sierra 3G modem can still work on Linux PC.
If the result is it can. Then, ohci-pnx4008.c might not working properly.

What about your thoughts?

Regards,
Quentin

On Thu, Jul 15, 2010 at 4:19 PM, Quentin Yang <address@hidden> wrote:

Thanks very much.

It’s great.

I saw the ‘ Kernel 2.6.34 – Phytec ‘ option in LTIB.

Very quick work, Kernel 2.6.34 does come up very long.

Regards,

Quentin

From: Srinivas Bakki [mailto:address@hidden]
Sent: Thursday, 15 July 2010 16:07
To: Quentin Yang; Quentin YANG; address@hidden

Subject: RE: Sierra 3G modem not working on Phytec Board. (missing USB End Points, only ep00,ep01,ep81 created.)

Hi Quentin,

                     Just run"cvs update" in your ltib directory. It'll fetch the updates and in the ltib config you can see the 2.6.34 kernel support.

Let me know if you have any problems further.

Regards

Srinivas Bakki

From: Quentin Yang [mailto:address@hidden]
Sent: Thursday, July 15, 2010 11:32 AM
To: Srinivas Bakki; Quentin YANG; address@hidden
Subject: RE: Sierra 3G modem not working on Phytec Board. (missing USB End Points, only ep00,ep01,ep81 created.)

Hi Srinivas,

Thanks for the reply.

I think I’ve enabled USB debug. As in \ltib-qs\rpm\BUILD\linux-2.6.27.8\.config, I can see

“

#

# USB Input Devices

#

CONFIG_USB_HID=y

# CONFIG_USB_HIDINPUT_POWERBOOK is not set

# CONFIG_HID_FF is not set

# CONFIG_USB_HIDDEV is not set

CONFIG_USB_SUPPORT=y

CONFIG_USB_ARCH_HAS_HCD=y

CONFIG_USB_ARCH_HAS_OHCI=y

# CONFIG_USB_ARCH_HAS_EHCI is not set

CONFIG_USB=y

CONFIG_USB_DEBUG=y

CONFIG_USB_ANNOUNCE_NEW_DEVICES=y

”

Also, in ‘ \ltib-qs\rpm\BUILD\linux-2.6.27.8\include\linux\autoconf.h ‘

#define CONFIG_USB_DEBUG 1

But from the attached ‘console print’ from Phytec board UART5? (Phytec_Console_Log_Missing_UsbDebugMessage.txt)

I cannot see any ‘usb-debug’ message. I’ll keep working on this and get back to you soon.

One thing noticeable in the log is:

‘usbmon: debugfs is not available’ I don’t know why is this?? Seems again to do with File System.

---------------------------------------

I am quite new to LTIB.

But when I installed LTIB by ‘netinstall’, all kernel 2.6.27.8 source codes turned up automatically under ‘\ltib-qs\rpm\BUILD\linux-2.6.27.8\’ because I chose ‘Leave Kernel Source After build’.

In ‘ \ltib-qs\config\platform\phy3250\defconfig.dev ‘

#

# Choose your Kernel

#

CONFIG_PHY_KERNEL_2_6_27_8=y

# CONFIG_KERNEL_DIR_BUILD is not set

# CONFIG_KERNEL_NONE is not set

CONFIG_PKG_KERNEL="kernel-2.6.27.8-lpc32xx"

CONFIG_PKG_KERNEL_FORCE=y

# CONFIG_PKG_KERNEL_WANT_CSCOPE is not set

CONFIG_PKG_KERNEL_PRECONFIG="GsnKernelPreConfig.config"

CONFIG_PKG_KERNEL_WANT_HEADERS=y

CONFIG_PKG_KERNEL_WANT_CF=y

CONFIG_PKG_KERNEL_LEAVESRC=y

CONFIG_SYSCFG_KTARG="uImage"

CONFIG_SYSCFG_BOOT_KERNEL="arch/arm/boot/uImage"

CONFIG_DISTRO="dist/lfs-5.1"

Regarding your suggestion, all lpc3250 patches appear to target kernel 2.6.27.8, can I use these patches on Linux 2.6.34 ?

I can see

\ltib-qs\dist\lfs-5.1\kernel\kernel-2.6.27.8-lpc32xx.spec.in

\ltib-qs\dist\lfs-5.1\kernel\kernel-2.6.28.2-lpc313x.spec.in

\ltib-qs\dist\lfs-5.1\kernel\kernel-2.6.33-lpc313x.spec.in

Lpc313x got patches for both 2.6.28.2 and 2.6.33 kernel.

As attached screen shot, to use Kernel 2.6.34, it looks the only choice is to choose ‘( ) Local Linux Directory Build’.

PLEASE ADVISE WHAT I NEED TO DO TO USE KERNEL 2.6.34 ON Phytec board? Thanks. LTIB is very new to me at the moment.

---------------Some Info about my current Phytec Linux Build -------------------------------

‘ linux-2.6.27.8-lpc32xx_full_10_15_09.patch ’ is the patch that can be downloaded from http://ics.nxp.com/support/software/lpc32xx.bsp.linux/

But, in real, following patches under ‘ \ltib-qs\rpm\SOURCES\ ’ were used when building Phytec Linux Image with LTIB:

kernel-arm-2.6.27.8-lpc32xx_8250irqfix.patch

kernel-arm-2.6.27.8-lpc32xx_armtskit_update2.patch

kernel-arm-2.6.27.8-lpc32xx_dktskit_update3.patch

kernel-arm-2.6.27.8-lpc32xx_ea3250.patch

kernel-arm-2.6.27.8-lpc32xx_ea3250_update1.patch

kernel-arm-2.6.27.8-lpc32xx.patch

kernel-arm-2.6.27.8-lpc32xx_update2.patch

kernel-arm-2.6.27.8-lpc32xx_update3.patch

kernel-arm-2.6.27.8-lpc32xx_update4.patch

kernel-arm-2.6.27.8-lpc32xx_update5.patch

kernel-arm-2.6.27.8-lpc32xx_update6.patch

kernel-arm-2.6.27.8-lpc32xx_update7.patch

kernel-arm-2.6.27.8-update1.patch

Together with 2.6.27.8 Kernel

\ltib-qs\rpm\SOURCES\linux-2.6.27.8.tar.bz2

Are these patches the same, ‘ linux-2.6.27.8-lpc32xx_full_10_15_09.patch ‘ is just a combination of all patches under ‘\ltib-qs\rpm\SOURCES\’ ??

Best Regards,

Quentin

From: Srinivas Bakki [mailto:address@hidden]
Sent: Thursday, 15 July 2010 14:37
To: Quentin YANG; address@hidden
Cc: Quentin Yang
Subject: RE: Sierra 3G modem not working on Phytec Board. (missing USB End Points, only ep00,ep01,ep81 created.)

Hi Quentino,

                        I had a look at the sysfs tree and am not sure why other endpoint files are not being created. I would need more information

to proceed : enable USB debugs and send me the logs. I would want to look at the enumeration process.

Other things you could try - Update to linux 2.6.34 ( present in ltib) which already has MC8790 support built in.

Regards

Srinivas Bakki

From: Quentin YANG [mailto:address@hidden]
Sent: Thursday, July 15, 2010 4:24 AM
To: Srinivas Bakki; address@hidden
Cc: address@hidden
Subject: Sierra 3G modem not working on Phytec Board. (missing USB End Points, only ep00,ep01,ep81 created.)

Hi Srinivas,

I've attached the /sys/ tree structure on both Phytec board and on my Linux PC.
Anything else I can do, please let me know.

Thanks for helping me out. Kind of stuck now.

Regards,
Quentin

On Tue, Jul 13, 2010 at 6:52 PM, Srinivas Bakki <address@hidden> wrote:

Hi Quentin,

                     Find my response below.

Regards

Srinivas Bakki

From: Quentin YANG [mailto:address@hidden]
Sent: Tuesday, July 13, 2010 8:23 AM
To: Srinivas Bakki
Cc: address@hidden
Subject: Re: [Ltib] Sierra 3G modem not working on Phytec Board. (/proc/bus/usb directory not found.)

Hi Srinivas,

Thanks for the quick reply.

1. I solved the " ' /proc/bus/usb' directory not found " problem by reconfiguring the linux 2.6.27.8 kernel in LTIB.

Do not worry about the /proc/bus/usb file not found problem. It is there only if you need to access descriptors from the user space.

3. Now more important question is WHY THERE IS ONLY ONE PAIR OF USB END POINT APPEARED (i.e., ep01, ep81) ???
    It suppose to have 7 pairs of end-points for sierra MC8790 3G modem MiniCard.

On linux PC, I can see

/dev/usbdev1.2_ep00
/dev/usbdev1.2_ep01
/dev/usbdev1.2_ep02
/dev/usbdev1.2_ep03
/dev/usbdev1.2_ep04
/dev/usbdev1.2_ep05
/dev/usbdev1.2_ep06
/dev/usbdev1.2_ep07
/dev/usbdev1.2_ep81
/dev/usbdev1.2_ep82
/dev/usbdev1.2_ep83
/dev/usbdev1.2_ep84
/dev/usbdev1.2_ep85
/dev/usbdev1.2_ep86
/dev/usbdev1.2_ep87
/dev/usbdev1.2_ep88
/dev/usbdev1.2_ep89
/dev/usbdev1.2_ep8a
/dev/usbdev1.2_ep8b

I'll have a look at this and get back soon. Meantime can you send me your sysfs entries for usb ? Both on linux PC and phytec.

So I think the PROBLEM IS WITH "pnx4008 OHCI" DRIVER, which I guess is the routine to create USB endpoints.
Please correct me if I am wrong.

The endpoints files are created by the kernel NOT the " "pnx4008 OHCI DRIVER ". When the hub succesfully enumerates the device i.e reads the descriptors and configures the device, the endpoint files are created.

I attached the 'console log' from Phytec board. You can clearly see my board config information.

Looking forward to your reply.

Regards,
Quentin

On Mon, Jul 12, 2010 at 2:04 PM, Srinivas Bakki <address@hidden> wrote:

Hi Quentin,

                      Can you try running "mdev -s" after you insert usbserial and sierra mdules ?

Regards

Srinivas Bakki

From: ltib-bounces+srinivas.bakki=nxp.com@nongnu.org [mailto:ltib-bounces+srinivas.bakki=nxp.com@nongnu.org] On Behalf Of Quentin YANG
Sent: Monday, July 12, 2010 7:41 AM
To: address@hidden
Subject: [Ltib] Sierra 3G modem not working on Phytec Board. ()

Hi,

My Phytec board is running Linux (2.6.27.8) built from LTIB (LinuxTargetImageBuilder).

http://www.phytec.com/products/linux/bsp-LPC3250.html
http://ics.nxp.com/support/software/lpc32xx.bsp.linux/

http://www.bitshrine.org/ltib/

I can see usbserial, sierra modules are successfully compiled and created
using the console of Phytec board (using on board UART5 terminal as console)

./lib/modules/2.6.27.8/kernel/drivers/usb/serial/usbserial.ko
./lib/modules/2.6.27.8/kernel/drivers/usb/serial/sierra.ko

But after inserting 3G Modem MC8790V,

1. usbserial, sierra modules are not automatically installed after Kernel has detected new USB endpoints.

2. After manually installed the usbserial, sierra modules by 'insmod' command.
It shows 'ttyUSB0' is attached, but no 'ttyUSB0' node created under ' /dev '

3. Also, during boot-up, there is always message saying:

     '
          ............................
          Mounting filesystems
          mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
          .........................
    '

I attached all print (TargetPhytecBoardLinuxPrint.txt) from Phytec Linux Console.

I suspect that I didnot config the kernel properly.
Do you have the recommend '.config' for Linux kernel compiling
so that Sierra Modem can work smoothly?

I attached the one (.config) I used to build Phytec Target Linux Image.
(I enabled usbserial driver, sierra wireless driver to be compiled as modules.
What other packages I must enabled to get Sierra Wireless Modem work?)

Thanks and hope you can spot something I've done wrong.

Regards,
Quentin

From:	Quentin YANG
Subject:	Re: [Ltib] Re: Sierra 3G modem not working on Phytec Board. (missing USB End Points, only ep00,ep01,ep81 created.)
Date:	Wed, 21 Jul 2010 11:41:55 +1000