Re: [SPAM] - Re: [Gumstix-users] USB, MMC and I2C problems in build 315 - Email found in subject

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

I'll have to check this when I get home, but I'm betting you are right. 
Last night on a lark I recompiled 319 with everything in the kernel 
instead of modules. It still didn't work; it locked up when it got to 
the USB driver loading but I did notice that when I plugged/unplugged 
the USB cable I got a message on the console and Windows saw the device 
even though it was not ready. This makes me think there is a problem 
with the module, or with the loading order or something like that. When 
I use it in module mode I never get the console messages and Windows 
never sees the device.

Jason

Heilpern, Mark wrote:

>I'm curious here Jason - after you've started the USB networking on the
>gumstix, type "ifconfig". Does the line beginning with UP also say
>RUNNING, or is that missing?
>
>The reason I ask - I've had some troubles similar to what you describe.
>When things were supposedly up for me, but there was no connection to my
>Windows host, RUNNING was not displayed in ifconfig. (I don't know if
>this is closer to the symptom or the problem.) The modules that should
>have been in memory all were but I got no connection. I was only able to
>solve this by rebuilding the kernel to have the USB network components
>statically linked in rather than left as modules.
>
>-----Original Message-----
>From: gum...@li...
>[mailto:gum...@li...] On Behalf Of Jason
>von Nieda
>Sent: Tuesday, January 04, 2005 6:44 PM
>To: gum...@li...
>Subject: [SPAM] - Re: [Gumstix-users] USB, MMC and I2C problems in build
>315 - Email found in subject
>
>Criag,
>
>Okay, got home and tried some new stuff.
>I built r306 and that seems to solve the MMC problem but not the USB
>one.
>Here is the module listing before I try to bring up the USB interface:
># lsmod
>Module                  Size  Used by
>unix 15636 6 - Live 0xbf01d000
>gumstix_bluetooth 352 0 - Live 0xbf01b000
>nls_cp437 4320 1 - Live 0xbf018000
>nls_iso8859_1 2784 1 - Live 0xbf016000
>vfat 7968 1 - Live 0xbf013000
>fat 29224 1 vfat, Live 0xbf00a000
>nls_base 4384 4 nls_cp437,nls_iso8859_1,vfat,fat, Live 0xbf007000 pxamci
>3200 0 - Live 0xbf005000 mmc_block 3048 2 - Live 0xbf003000 mmc_core
>7876 2 pxamci,mmc_block, Live 0xbf000000
>
>Now I try to bring up USB:
># ifup usb0
>pxa2xx_udc: version 14-Dec-2003
>usb0: Ethernet Gadget, version: St Patrick's Day 2004
>usb0: using pxa2xx_udc, OUT ep2out-bulk IN ep1in-bulk STATUS ep6in-bulk
>usb0: MAC 0a:00:be:3f:e5:02
>usb0: HOST MAC 0a:00:be:3f:e5:02
>usb0: RNDIS ready
>NET: Registered protocol family 17
>udhcpc (v0.9.9-pre) started
>Backgrounding
>
>And the modules after bringing up the interface:
># lsmod
>Module                  Size  Used by
>af_packet 11304 10 - Live 0xbf02d000
>g_ether 14840 0 - Live 0xbf028000
>pxa2xx_udc 11332 1 g_ether, Live 0xbf024000 gumstix_gadget 448 1
>pxa2xx_udc, Live 0xbf022000 unix 15636 12 - Live 0xbf01d000
>gumstix_bluetooth 352 0 - Live 0xbf01b000
>nls_cp437 4320 0 - Live 0xbf018000
>nls_iso8859_1 2784 0 - Live 0xbf016000
>vfat 7968 0 - Live 0xbf013000
>fat 29224 1 vfat, Live 0xbf00a000
>nls_base 4384 4 nls_cp437,nls_iso8859_1,vfat,fat, Live 0xbf007000 pxamci
>3200 0 - Live 0xbf005000 mmc_block 3048 0 - Live 0xbf003000 mmc_core
>7876 2 pxamci,mmc_block, Live 0xbf000000
>
>Everything looks pretty good, but the USB interface never powers up. I
>never get the "ding" in Windows and the device never shows up in Network
>Connections. If I revert back to r162 everything works perfectly.
>
>One note, on r315 if I change my bootcmd in U-Boot to add mmcinit then
>MMC comes up fine in Linux every time. Without that it won't come up. 
>I'm going to try to run some diffs on the drivers and see if I can come
>up with anything, but I hope you'll take a look too as you are much
>better at this than I am :)
>
>Jason
>
>
>________________________________________________________
>NOTE: The information in this message is intended for the personal and confidential use
>of the designated recipient(s) named above. To the extent the recipient(s) is/are bound
>by a non-disclosure agreement, or other agreement that contains an obligation of
>confidentiality, with AuthenTec, then this message and/or any attachments shall be
>considered confidential information and subject to the confidentiality terms of that
>agreement.  If the reader of this message is not the intended recipient named above, you
>are notified that you have received this document in error, and any review, dissemination,
>distribution or copying of this message is strictly prohibited. If you have received this
>document in error, please delete the original message and notify the sender immediately.
>Thank you.
>
>AuthenTec, Inc.  http://www.authentec.com
>
>
>
>
>
>
>-------------------------------------------------------
>The SF.Net email is sponsored by: Beat the post-holiday blues
>Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
>It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
>_______________________________________________
>gumstix-users mailing list
>gum...@li...
>https://lists.sourceforge.net/lists/listinfo/gumstix-users
>  
>