• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1]
1  Hardware and U-Boot firmware / Hardware / usb connect-debounce failed, port 1 disabled on: May 24, 2009, 12:34:05 PM
Hi,

one of my usb sticks won't work, when I plug them directly into the sheeva plug. The stick works however, when I put a powered usb hub inbetween.
At uboot, it's just not recognized; when linux (2.6.30rc6) is running, it periodically outputs:
hub 1-0:1.0: connect-debounce failed, port 1 disabled

Also strange is, that I cannot use the hub without power supply with the sheeva at all.

I thought, that it may have something to do with the amount of power, that is drawn via usb, but the Toshiba stick that works reports a higher maximum power consumption than the Transcend stick and the Genesys hub that don't work.

I also tested this without the console cable connected.

Does anybody have an idea regarding this problem?

Thanks,
Peter

Here is the lsusb output for the three devices:
Code:
Bus 001 Device 028: ID 1307:0165 Transcend Information, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x1307 Transcend Information, Inc.
  idProduct          0x0165
  bcdDevice            1.00
  iManufacturer           1
  iProduct                2
  iSerial                 3
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               98mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               8


Bus 001 Device 027: ID 0930:6529 Toshiba Corp. TravelDrive
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0930 Toshiba Corp.
  idProduct          0x6529 TravelDrive
  bcdDevice            1.00
  iManufacturer           1
  iProduct                2
  iSerial                 3
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              200mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk (Zip)
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               4


Bus 001 Device 026: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 Unused
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x05e3 Genesys Logic, Inc.
  idProduct          0x0608 USB-2.0 4-Port HUB
  bcdDevice            7.02
  iManufacturer           0
  iProduct                1
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           25
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              1
2  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 24, 2009, 11:57:09 AM
Anyhow, I fixed the script (attached initrd, please replace the one you are using), please try it with the non-working USB stick.

Yes, this works!
Very good.  Smiley
I tried it with both sticks, just to be sure.
3  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 24, 2009, 08:41:49 AM
It works!

I tried a different usb stick, that does work with uboot without putting a powered hub inbetween. And that worked.
The contents (the files from the installer directory) and partition type (W95 FAT32 LBA) are exactly the same. I don't really know what the difference is  Undecided. The alternative stick was 512mb while the former was 4gb, but this can't be it.

The first one seems to be ok since there is no /dev/sda1, but only /dev/sda (no partitions on the USB stick).

Are you sure that there are no partitions on the USB stick? I tried to make a USB stick without partition table, but uboot seems to need one.

While installing it now says:
mount: mounting /dev/sda on /mnt1 failed: Invalid argument
instead of:
mount: mounting /dev/sda1 on /mnt1 failed: Device or resource busy

Thanks for your help. If you are interested in more information regarding my sticks or if I can try something for you, let me know.
4  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 22, 2009, 03:08:15 PM
ok, it seems that uboot on my plug will only talk to my usb-stick if i put a powered usb hub inbetween and plug it all in before booting.
Now I see that installation copies and flashes the files, but now there is another error:

Code:
ubiformat: formatting eraseblock 4054 -- 99 % complete 
ubiformat: formatting eraseblock 4055 -- 100 % complete 
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "rootfs"
UBI: MTD device size:            507 MiB
UBI: number of good PEBs:        4040
UBI: number of bad PEBs:         16
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             3996
UBI: total number of reserved PEBs: 44
UBI: number of PEBs reserved for bad PEB handling: 40
UBI: max/mean erase counter: 4/1
UBI: background thread "ubi_bgt0d" started, PID 556
UBI device number 0, total 4040 LEBs (521256960 bytes, 497.1 MiB), available 3996 LEBs (515579904 bytes, 491.7 MiB), LEB size 129024 bytes (126.0 KiB)
Set volume size to 515579904
Volume ID 0, size 3996 LEBs (515579904 bytes, 491.7 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs", alignment 1
**** Mounting root filesystems
mount: mounting /dev/sda1 on /mnt1 failed: Device or resource busy
UBIFS: default file-system created
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   513644544 bytes (501606 KiB, 489 MiB, 3981 LEBs)
UBIFS: journal size:       25675776 bytes (25074 KiB, 24 MiB, 199 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  4952683 bytes (4836 KiB)
****** ERROR - no rootfs.tar.gz file found on USB stick
UBIFS: un-mount UBI device 0, volume 0

The system is going down NOW!

[.....]

usb 1-1: new high speed USB device using orion-ehci and address 2
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
[<c00309c0>] (unwind_backtrace+0x0/0xe0) from [<c003db20>] (panic+0x50/0x120)
[<c003db20>] (panic+0x50/0x120) from [<c002b53c>] (init_post+0xd4/0xfc)
[<c002b53c>] (init_post+0xd4/0xfc) from [<c0008738>] (kernel_init+0xc4/0xec)
[<c0008738>] (kernel_init+0xc4/0xec) from [<c0040b18>] (do_exit+0x0/0x6ac)



I attached the complete log of this command line
( sudo ./runme.sh ; cu --nostop -s 115200 --line /dev/ttyUSB1 ) 2>&1 | tee install.log
5  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 22, 2009, 12:11:30 PM
While looking around, it seemed to me, that usb does not work at all:

Code:
Marvell>> usb start

(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
Marvell>> fatload usb 0 0x00200000 uImage

** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **
6  General Category / General Discussion / Re: Sheevaplug installer - alpha-5 release - Testers needed on: May 22, 2009, 11:34:52 AM
Hi, here are my first-time experiences with the installer:

I formattet a USB-Stick and copied the files from the installer directory.
Connected the Terminal-Cable and USB-Stick and turned on the Plug.
I started "sudo ./runme.sh" and everything went fine.
After opening the console as advised, there was lots of stuff going on including erasing and writing until it ended with:

Code:
...
Writing data at 0x4f5800 --  99% complete.
Writing data at 0x4ff800 -- 100% complete.
 4194304 bytes written: OK
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
## Booting image at 00200000 ...
Bad Magic Number
Marvell>>

What can I do to boot the new system?
I have attached my current environment, but let me know if you need more info.
Thanks,
Peter

Code:
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
ethaddr=00:62:81:a0:00:00
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00200000 0x00100000 0x003ff000; bootm 0x00200000
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions); bootm 0x00200000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00200000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00200000 uImage; fatload usb 0 0x01100000 initrd
arcNumber=2097
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00200000 0x00100000 0x003ff000; bootm 0x00200000
bootargs=console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
Pages: [1]