Skip to contentSkip to conversation

What is the current USB support status on DB1550?

DISCUSSION rolf liu 3 participants 7 messages Jul 14, 2005 MIPS

lore
Share & tools
lore

rolf liu

author
#0 lore raw

Are both usb host and usb gadget support as well? And the On the Go feature?

Thanks

rolf

#1 lore raw
Quoted 1 line · rolf liu

Are both usb host and usb gadget support as well? And the On the Go feature?

Host only. We couldn't make gadget work due to interrupt latency requirements by the HW that couldn't be reliably achieved with Linux. But gadget does work on the Au1200.

Pete

author
#2 lore raw

Is there big difference between Au1200 and Au1550? Any constrant on Au1550 ? Thanks

Quoted 11 lines · Pete Popov
Quoted 1 line · rolf liu

Are both usb host and usb gadget support as well? And the On the Go feature?

Host only. We couldn't make gadget work due to interrupt latency requirements by the HW that couldn't be reliably achieved with Linux. But gadget does work on the Au1200.

Pete

#3 lore raw
Quoted 1 line · rolf liu

Is there big difference between Au1200 and Au1550?

Sure. Take a look at the marketing pdfs from AMD, they provide a concise description.

Pete

Quoted 17 lines

Any constrant on Au1550 ?
Thanks

Quoted 11 lines · Pete Popov
Quoted 1 line · rolf liu

Are both usb host and usb gadget support as well? And the On the Go feature?

Host only. We couldn't make gadget work due to interrupt latency requirements by the HW that couldn't be reliably achieved with Linux. But gadget does work on the Au1200.

Pete

#4 lore raw
In reply to Pete Popov
Quoted 3 lines · Pete Popov

Host only. We couldn't make gadget work due to interrupt latency requirements by the HW that couldn't be reliably achieved with Linux. But gadget does work on the Au1200.

Is the Au1500 in the same boat as the DB1550? Do the hardware requirements apply to all boards with that SOC, or is it somewhat board-dependent?

Thanks,

- Kevin

Signature · 1 line
The moon is first quarter, 49.5% illuminated, 7.3 days old.
#5 lore raw
Quoted 6 lines · Kevin Turner
Quoted 3 lines · Pete Popov

Host only. We couldn't make gadget work due to interrupt latency requirements by the HW that couldn't be reliably achieved with Linux. But gadget does work on the Au1200.

Is the Au1500 in the same boat as the DB1550?

The Db1550 is the reference board for the Au1550.

Quoted 3 lines

Do the hardware
requirements apply to all boards with that SOC, or is it somewhat board-dependent?

All boards with the 1100, 1500, or 1550. The Au1200 gadget works, but the usb controller on the SOC is different. We've made the other CPUs work before but it was on top of RTLinux, different/proprietary usb stack, and a lot of debug and tuning.

Pete

author
#6 lore raw

The drive is identified in the file "devices".
Pete,
I can't get my netac flash drive working on db1550. Could you tell me what went wrong?

I mount the usbfs as "mount none /proc/bus/usb -t usbfs". In /proc/bus/usb, I don't see "drivers", only "001" and "devices".

Under /proc/scsc/usb-storage, there is file "0", which gives the information for this drive:
Host scsi0: usb-storage
Vendor: Netac
Product: OnlyDisk
Serial number: None
Protocol: Transparent SCSI
Transport: Bulk

The output from usb-storage debug keeps showing
"Bad target number", since the device->id is not 0 and the flags is 0. Any suggestion on this part?

...
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (2:0)
usb-storage: scsi cmd done, result=0x40000
...

Thanks

Quoted 23 lines · Pete Popov
Quoted 6 lines · Kevin Turner
Quoted 3 lines · Pete Popov

Host only. We couldn't make gadget work due to interrupt latency requirements by the HW that couldn't be reliably achieved with Linux. But gadget does work on the Au1200.

Is the Au1500 in the same boat as the DB1550?

The Db1550 is the reference board for the Au1550.

Quoted 3 lines

Do the hardware
requirements apply to all boards with that SOC, or is it somewhat board-dependent?

All boards with the 1100, 1500, or 1550. The Au1200 gadget works, but the usb controller on the SOC is different. We've made the other CPUs work before but it was on top of RTLinux, different/proprietary usb stack, and a lot of debug and tuning.

Pete