Re: [Gumstix-users] USB problem on last Verdex GIT

[Ash C. <as...@gu...>]

Hi Momday,

Your machine should be specified as 'gumstix-verdex' in your
auto.conf; this is setup by the '$ cp -r
org.openembedded.dev/contrib/gumstix/build . ' command from the setup
instuctions.  Changing the machine type can certainly have dramatic
implications for what gets built.

In my recent commit, I pulled some updated packages from the overo
tree, fixed the partition table in linux to accommodate a larger
rootfs, setup the building of a 600MHz version of u-boot, specified
the verdex-specific version of u-boot as the version to be built (this
is probably the change to which you referred) and a few other changes
that are escaping my memory right now.

-Ash
On Mon, May 10, 2010 at 9:40 AM, mdok <md...@ka...> wrote:
> Hi Ash,
>
> Many thanks for your help!
> Is the only change you did was to explicitly specify the 'gumstix-verdex'
> machine?
> If that's the only change, I am jaw-dropping to see how much impact has such
> 'tiny' configuration change!
>
> The USB is working great now!
>
>
> Best regards,
> Momday
>
> Ash Charles wrote:
>>
>> Hi Momday,
>>
>>
>> On Wed, Apr 28, 2010 at 1:47 PM, mdok <md...@ka...> wrote:
>>
>>>
>>> Hi Ash,
>>>
>>> I added the recipe back and now it builds ok. Weird. I will do a fresh
>>> install of the OE and bitbake again to see if I can duplicate it still.
>>> Actually I am not doing anything special to build the image.
>>> I just took the verdex-console-image recipe and added one custom library
>>> (not related to u-boot though). I will give you more detail when I
>>> duplicate
>>> the build error.
>>>
>>
>> Okay---I got the u-boot on one occasion.  I think this is because I
>> wasn't explicitly specifying that 'u-boot-verdex' is the version of
>> u-boot to build for the 'gumstix-verdex' machine.  I've changed the
>> 'PREFERRED_PROVIDER_virtual/bootloader' and I don't see the error any
>> longer--hopefully, this is the appropriate method of fixing this.
>>
>>
>>>
>>> For the usb functionality, I just plug-in a keyboard or a mouse to take
>>> control over the console on the LCD.
>>> But for these latest builds, though they are detected, I can't type
>>> anything
>>> nor take control of the mouse cursor (in graphic mode).
>>> The boot sequence still shows:
>>> "logger: mount: mount point /proc/bus/usb does not exist"
>>>
>>> And when I plugged-in a keyboard I get the following:
>>> "root@gumstix-verdex:~# usb 1-2: USB disconnect, address 3
>>> usb 1-2: new full speed USB device using pxa27x-ohci and address 4
>>> usb 1-2: configuration #1 chosen from 1 choice
>>> "
>>>
>>> I reloaded some previous build (04/07) of the verdex-console-image and
>>> there
>>> is no such problem.
>>> For those older builds, when I plugged-in a USB keyboard, the following
>>> message is shown:
>>> "usb 1-2: USB disconnect, address 2
>>> usb 1-2: new full speed USB device using pxa27x-ohci and address 3
>>> usb 1-2: configuration #1 chosen from 1 choice
>>> input: Logitech Logitech Illuminated Keyboard as
>>> /devices/platform/pxa27x-ohci/usb1/1-2/1-2:1.0/input/input0
>>> generic-usb 0003:046D:C318.0001: input: USB HID v1.11 Keyboard [Logitech
>>> Logitech Illuminated Keyboard] on usb-pxa27x-2/input0
>>> input: Logitech Logitech Illuminated Keyboard as
>>> /devices/platform/pxa27x-ohci/usb1/1-2/1-2:1.1/input/input1
>>> generic-usb 0003:046D:C318.0002: input: USB HID v1.11 Device [Logitech
>>> Logitech Illuminated Keyboard] on usb-pxa27x-2/input1
>>> usbcore: registered new interface driver usbhid"
>>>
>>>
>>
>> I've just updated, rebuilt, and tested with a keyboard plugged in from
>> boot.  The keyboard was correctly detected and usable.  I'll push
>> these changes shortly; please test and let me know if it still is not
>> working for you.
>>
>>>
>>> Thanks for your help!
>>>
>>> Best regards,
>>> Momday
>>>
>>
>> -Ash
>>
>>>
>>> Ash Charles wrote:
>>>
>>>>
>>>> Hi Momday,
>>>>
>>>> I did a clean build of 'verdex-console-image' and 'u-boot-verdex' and
>>>> do not see errors related to u-boot-omap2430sdp_1.1.4.bb (though
>>>> admittedly, this recipe fails when I try to build it directly).  Could
>>>> you walk me through what you are doing/trying to build that gives this
>>>> errror?
>>>>
>>>> I tested my freshly built image and I can plug in and detect a USB hub
>>>> with a keyboard attached.  How are you testing functionality?
>>>> Normally I would either use a VNC session or just cat /dev/input/<usb
>>>> keyboard device> however /dev/input doesn't appear which seems
>>>> suspicious.
>>>>
>>>> -Ash
>>>>
>>>>
>>>> On Tue, Apr 27, 2010 at 12:10 PM, Momday DOK <mom...@ka...>
>>>> wrote:
>>>>
>>>>
>>>>>
>>>>> Hi Ash,
>>>>>
>>>>> For some unknown reasons, the  bitbake image build started to fail
>>>>> because
>>>>> of the recipe: u-boot-omap2430sdp_1.1.4.bb which got me suspicious
>>>>> since
>>>>> I
>>>>> am building for the Verdex.
>>>>> So I've just pulled the last OE and still get a build error.
>>>>> After I deleted that file from recipes folder, I am able to build
>>>>> again.
>>>>>
>>>>> However, now, the usb doesn't seem to work. When I plugged a mouse or a
>>>>> keyboard it seems to be detected but not functional.
>>>>> Have you seen the symptom w/ your latest build?
>>>>>
>>>>> This is the output of boot up:
>>>>>
>>>>> *Uncompressing
>>>>>
>>>>>
>>>>> Linux....................................................................................
>>>>> done, booting the kernel.
>>>>> Linux version 2.6.31 (mdok@kaneoh) (gcc version 4.3.3 (GCC) ) #1 Tue
>>>>> Apr
>>>>> 27
>>>>> 01:03:10 UTC 2010
>>>>> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f
>>>>> CPU: VIVT data cache, VIVT instruction cache
>>>>> Machine: Gumstix verdex
>>>>> Memory policy: ECC disabled, Data cache writeback
>>>>> Run Mode clock: 208.00MHz (*16)
>>>>> Turbo Mode clock: 416.00MHz (*2.0, active)
>>>>> Memory clock: 104.00MHz (/2)
>>>>> System bus clock: 104.00MHz
>>>>> Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
>>>>> 16256
>>>>> Kernel command line: console=ttyS0,115200n8 noinitrd
>>>>> init=/sbin/init.sysvinit root=/dev/mmcblk0p2 rw rootdelay=1
>>>>> PID hash table entries: 256 (order: 8, 1024 bytes)
>>>>> Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
>>>>> Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
>>>>> Memory: 64MB = 64MB total
>>>>> Memory: 62176KB available (2212K code, 252K data, 156K init, 0K
>>>>> highmem)
>>>>> NR_IRQS:192
>>>>> Console: colour dummy device 80x30
>>>>> Calibrating delay loop... 415.33 BogoMIPS (lpj=2076672)
>>>>> Mount-cache hash table entries: 512
>>>>> CPU: Testing write buffer coherency: ok
>>>>> NET: Registered protocol family 16
>>>>> Gumstix verdex udc is disabled
>>>>> Initializing Gumstix verdex i2c
>>>>> Initializing Gumstix verdex smsc911x
>>>>> Initializing Gumstix verdex pcmcia
>>>>> Not netCF-vx board: pcmcia using newer GPIO configuration
>>>>> CPLD responded with: ff
>>>>> found 1 CF slots
>>>>> Initializing Gumstix verdex FB info
>>>>> Initializing Gumstix platform_add_devices
>>>>> bio: create slab <bio-0> at 0
>>>>> NET: Registered protocol family 2
>>>>> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>>>>> TCP established hash table entries: 2048 (order: 2, 16384 bytes)
>>>>> TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
>>>>> TCP: Hash tables configured (established 2048 bind 2048)
>>>>> TCP reno registered
>>>>> NET: Registered protocol family 1
>>>>> msgmni has been set to 121
>>>>> alg: No test for stdrng (krng)
>>>>> Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
>>>>> io scheduler noop registered
>>>>> io scheduler cfq registered (default)
>>>>> Console: switching to colour frame buffer device 80x24
>>>>> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
>>>>> console [ttyS0] enabled
>>>>> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
>>>>> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
>>>>> Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit
>>>>> bankwidth)
>>>>> Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank
>>>>> Intel/Sharp Extended Query Table at 0x010A
>>>>> Intel/Sharp Extended Query Table at 0x010A
>>>>> Intel/Sharp Extended Query Table at 0x010A
>>>>> Intel/Sharp Extended Query Table at 0x010A
>>>>> Intel/Sharp Extended Query Table at 0x010A
>>>>> Using buffer write method
>>>>> Using auto-unlock on power-up/resume
>>>>> cfi_cmdset_0001: Erase suspend on write enabled
>>>>> Using static partitions on Gumstix Flash ROM
>>>>> Creating 3 MTD partitions on "Gumstix Flash ROM":
>>>>> 0x000000000000-0x000000040000 : "Bootloader"
>>>>> 0x000000040000-0x000000f00000 : "RootFS"
>>>>> 0x000000f00000-0x000001000000 : "Kernel"
>>>>> pxa-rtc pxa-rtc: rtc core: registered pxa-rtc as rtc0
>>>>> TCP cubic registered
>>>>> NET: Registered protocol family 17
>>>>> XScale iWMMXt coprocessor detected.
>>>>> pxa-rtc pxa-rtc: setting system clock to 2010-04-06 19:28:59 UTC
>>>>> (1270582139)
>>>>> Waiting 1sec before mounting root device...
>>>>> mmc0: host does not support reading read-only switch. assuming
>>>>> write-enable.
>>>>> mmc0: new SD card at address 8001
>>>>> mmcblk0: mmc0:8001 SU256 241 MiB
>>>>> mmcblk0: p1 p2
>>>>> kjournald starting.  Commit interval 5 seconds
>>>>> EXT3 FS on mmcblk0p2, internal journal
>>>>> EXT3-fs: mounted filesystem with writeback data mode.
>>>>> VFS: Mounted root (ext3 filesystem) on device 179:2.
>>>>> Freeing init memory: 156K
>>>>> INIT: version 2.86 booting
>>>>> Please wait: booting...
>>>>> Remounting root file system...
>>>>> logger: mount: mount point /proc/bus/usb does not exist
>>>>> Undefined users:
>>>>>
>>>>>
>>>>>>
>>>>>> pulse
>>>>>>
>>>>>>
>>>>>
>>>>> Skipping /etc/default/volatiles/04_pulse
>>>>> Undefined users:
>>>>>
>>>>>
>>>>>>
>>>>>> haldaemon
>>>>>>
>>>>>>
>>>>>
>>>>> Skipping /etc/default/volatiles/99_hal
>>>>> net.ipv4.conf.default.rp_filter = 1
>>>>> net.ipv4.conf.all.rp_filter = 1
>>>>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>>>>> Tue Apr 27 01:57:00 UTC 2010
>>>>> hwclock: can't open '/dev/misc/rtc': No such file or directory
>>>>> Checking for built-in Bluetooth: /etc/rcS.d/S97blueprobe: line 158:
>>>>> can't
>>>>> open /dev/ttyS1: no such file
>>>>> yes
>>>>> Configuring dbus.
>>>>> Adding system startup for /etc/init.d/dbus-1.
>>>>> Configuring hal.
>>>>> Undefined users:
>>>>>
>>>>>
>>>>>>
>>>>>> pulse
>>>>>>
>>>>>>
>>>>>
>>>>> Skipping /etc/default/volatiles/04_pulse
>>>>> Configuring pcsc-lite.
>>>>> Adding system startup for /etc/init.d/pcscd.
>>>>> Configuring busybox-syslog.
>>>>> Adding system startup for /etc/init.d/syslog.
>>>>> Configuring update-modules.
>>>>> Configuring i2c.
>>>>> Adding system startup for /etc/init.d/i2c.
>>>>> Configuring bonjour.
>>>>> Adding system startup for /etc/init.d/bonjour.
>>>>> Configuring ppp.
>>>>> Configuring ppp-dialin.
>>>>> Configuring portmap.
>>>>> Adding system startup for /etc/init.d/portmap.
>>>>> Configuring keymaps.
>>>>> Adding system startup for /etc/init.d/keymap.
>>>>> Configuring modutils-initscripts.
>>>>> Adding system startup for /etc/init.d/modutils.sh.
>>>>> Configuring hicolor-icon-theme.
>>>>> //usr/lib/opkg/info/hicolor-icon-theme.postinst: line 7: can't create
>>>>> /etc/gtk-2.0/gdk-pixbuf.loaders: nonexistent directory
>>>>> //usr/lib/opkg/info/hicolor-icon-theme.postinst: line 7:
>>>>> gdk-pixbuf-query-loaders: not found
>>>>> //usr/lib/opkg/info/hicolor-icon-theme.postinst: line 13:
>>>>> gtk-update-icon-cache: not found
>>>>> Configuring policykit.
>>>>> Configuring pulseaudio-server.
>>>>> addgroup: pulse: group already in use
>>>>>
>>>>> Configuring netbase.
>>>>> Adding system startup for /etc/init.d/networking.
>>>>> Configuring angstrom-libc-fixup-hack.
>>>>> Configuring libnss-mdns.
>>>>> Configuring avahi-daemon.
>>>>> Adding system startup for /etc/init.d/avahi-daemon.
>>>>> Configuring avahi-autoipd.
>>>>> Configuring libertas-cf-firmware.
>>>>> Adding system startup for /etc/init.d/cf8385.
>>>>> Configuring sudo.
>>>>> Configuring angstrom-zeroconf-audio.
>>>>> Configuring ntp.
>>>>> Adding system startup for /etc/init.d/ntpd.
>>>>> Configuring shadow.
>>>>> update-alternatives: Linking //usr/bin/passwd to passwd.shadow
>>>>> update-alternatives: Linking //usr/sbin/chpasswd to chpasswd.shadow
>>>>> update-alternatives: Linking //usr/bin/chfn to chfn.shadow
>>>>> update-alternatives: Linking //usr/bin/newgrp to newgrp.shadow
>>>>> update-alternatives: Linking //usr/bin/chsh to chsh.shadow
>>>>> update-alternatives: Linking //bin/login to login.shadow
>>>>> update-alternatives: Error: not linking //sbin/vipw to vipw.shadow
>>>>> since
>>>>> //sbin/vipw exists and is not a link
>>>>> update-alternatives: Linking //sbin/vigr to vigr.shadow
>>>>> Configuring ifupdown.
>>>>> Adding system startup for /etc/init.d/ifup.
>>>>> Configuring ntpdate.
>>>>> adding crontab
>>>>> Bluetooth: Core ver 2.15
>>>>> NET: Registered protocol family 31
>>>>> Bluetooth: HCI device and connection manager initialized
>>>>> Bluetooth: HCI socket layer initialized
>>>>> Bluetooth: L2CAP ver 2.13
>>>>> Bluetooth: L2CAP socket layer initialized
>>>>> Bluetooth: HIDP (Human Interface Emulation) ver 1.2
>>>>> usbcore: registered new interface driver usbfs
>>>>> usbcore: registered new interface driver hub
>>>>> usbcore: registered new device driver usb
>>>>> ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
>>>>> pxa27x-ohci pxa27x-ohci: PXA27x OHCI
>>>>> pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1
>>>>> pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c000000
>>>>> usb usb1: configuration #1 chosen from 1 choice
>>>>> hub 1-0:1.0: USB hub found
>>>>> hub 1-0:1.0: 3 ports detected
>>>>> usb 1-2: new full speed USB device using pxa27x-ohci and address 2
>>>>> Bluetooth: RFCOMM TTY layer initialized
>>>>> Bluetooth: RFCOMM socket layer initialized
>>>>> Bluetooth: RFCOMM ver 1.11
>>>>> smsc911x: Driver version 2008-10-21.
>>>>> eth%d: smsc911x_init: Driver Parameters:
>>>>> eth%d: smsc911x_init: LAN base: 0xC4A00000
>>>>> eth%d: smsc911x_init: IRQ: 163
>>>>> eth%d: smsc911x_init: PHY will be autodetected.
>>>>> eth%d: smsc911x_init: BYTE_TEST: 0x00000000
>>>>> eth%d: smsc911x_init: BYTE_TEST: 0x00000000
>>>>> eth%d: smsc911x_init: top 16 bits equal to bottom 16 bits
>>>>> eth%d: smsc911x_init: This may mean the chip is set for 32 bit while
>>>>> the
>>>>> bus
>>>>> is reading 16 bit
>>>>> usb 1-2: configuration #1 chosen from 1 choice
>>>>> Collected errors:
>>>>> * pkg_run_script: postinst script returned status 127.
>>>>> * opkg_configure: hicolor-icon-theme.postinst returned 127.
>>>>> INIT: Entering runlevel: 5
>>>>> Starting system message bus: dbus.
>>>>> Starting Hardware abstraction layer hald
>>>>> Starting ntpd: done
>>>>> Starting PCSC Daemon: pcscd.
>>>>> Starting syslogd/klogd: done
>>>>> * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
>>>>> [ ok ]
>>>>> Starting bonjour:
>>>>> Starting i2c...
>>>>> I2C: i2c-0: PXA I2C adapter
>>>>> I2C: i2c-1: PXA I2C adapter
>>>>> i2c /dev entries driver
>>>>> *
>>>>>
>>>>> Thanks for you help!
>>>>> Momday
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>