[#4740] A usb harddisk box cannot be identified on BF548-EZkit

Submitted By: Yi Li

Open Date

2008-12-22 22:13:35 Close Date

2008-12-29 03:54:01

Priority:

Medium Assignee:

Bryan Wu

Status:

Closed Fixed In Release:

N/A

Found In Release:

N/A Release:

svn

Category:

N/A Board:

EZKIT Lite

Processor:

BF549 Silicon Revision:

0.1

Is this bug repeatable?:

Yes Resolution:

Under Debugging

Uboot version or rev.:

Toolchain version or rev.:

svn

App binary format:

N/A

Summary: A usb harddisk box cannot be identified on BF548-EZkit

Details:

A usb hard disk box (usb-to-ide) cannot be identified on BF548-EZkit, while it can be identified on a PC (ubuntu).

BF548-EZkit:

usb 1-1: new high speed USB device using musb_hdrc and address 2

usb 1-1: configuration #1 chosen from 1 choice

scsi1 : SCSI emulation for USB Mass Storage devices

usb-storage: device found at 2

usb-storage: waiting for device to settle before scanning

usb 1-1: reset high speed USB device using musb_hdrc and address 2

root:/> usb 1-1: reset high speed USB device using musb_hdrc and address 2

usb 1-1: reset high speed USB device using musb_hdrc and address 2

scsi 1:0:0:0: Device offlined - not ready after error recovery

PC:

[ 3859.561760] usb 1-8: new high speed USB device using ehci_hcd and address 4

[ 3863.044199] usb 1-8: configuration #1 chosen from 1 choice

[ 3863.145207] usbcore: registered new interface driver libusual

[ 3863.168661] Initializing USB Mass Storage driver...

[ 3863.169910] scsi2 : SCSI emulation for USB Mass Storage devices

[ 3863.171140] usbcore: registered new interface driver usb-storage

[ 3863.171150] USB Mass Storage support registered.

[ 3863.171320] usb-storage: device found at 4

[ 3863.171324] usb-storage: waiting for device to settle before scanning

[ 3868.168881] usb-storage: device scan complete

[ 3868.169385] scsi 2:0:0:0: Direct-Access Generic USB Disk 9.02 PQ: 0 ANSI: 2

[ 3868.171139] sd 2:0:0:0: [sdc] 117210240 512-byte hardware sectors (60012 MB)

[ 3868.180865] sd 2:0:0:0: [sdc] Write Protect is off

[ 3868.180872] sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00

[ 3868.180877] sd 2:0:0:0: [sdc] Assuming drive cache: write through

[ 3868.182603] sd 2:0:0:0: [sdc] 117210240 512-byte hardware sectors (60012 MB)

[ 3868.183729] sd 2:0:0:0: [sdc] Write Protect is off

[ 3868.183735] sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00

[ 3868.183739] sd 2:0:0:0: [sdc] Assuming drive cache: write through

[ 3868.184378] sdc: sdc1 sdc2 sdc3 < sdc5 sdc6 sdc7 sdc8 >

[ 3868.261931] sd 2:0:0:0: [sdc] Attached SCSI disk

[ 3868.261997] sd 2:0:0:0: Attached scsi generic sg3 type 0

[ 3869.058436] kjournald starting. Commit interval 5 seconds

[ 3869.062515] EXT3 FS on sdc6, internal journal

[ 3869.062525] EXT3-fs: mounted filesystem with ordered data mode.

[ 3869.241524] kjournald starting. Commit interval 5 seconds

[ 3869.241536] EXT3-fs warning: checktime reached, running e2fsck is recommended

[ 3869.242650] EXT3 FS on sdc8, internal journal

[ 3869.242659] EXT3-fs: mounted filesystem with ordered data mode.

[ 3869.291534] kjournald starting. Commit interval 5 seconds

[ 3869.292129] EXT3 FS on sdc7, internal journal

[ 3869.292140] EXT3-fs: mounted filesystem with ordered data mode.

[ 4171.092897] usb 1-8: USB disconnect, address 4

Bryan thinks this may be caused by power issue.

Follow-ups

--- Bryan Wu 2008-12-28 22:28:14

I gave Yi a new USB cable which can provide more power. This issue should be

gone.

-Bryan

--- Yi Li 2008-12-29 03:53:22

Thanks Bryan.

Close. Lesson is that a hard disk requires 5V/1A power supply cannot be used

here.

Files

Changes

Commits

Dependencies

Duplicates

Associations