2009-04-22 11:06:04     Renesas USB HC with BF527 Issues

Document created by Aaronwu Employee on Aug 15, 2013
Version 1Show Document
  • View in full screen mode

2009-04-22 11:06:04     Renesas USB HC with BF527 Issues

Appalayagari Sreedhar (INDIA)

Message: 73065   

 

Hi,

 

I am working with uClinux trunk distribution and BF527 Ezkit board.

 

We have interfaced the Renesas USB HC to BF527. When we build and boot the kernel the Renesas Internal USB Hub is detected and two ports are enumerated.

 

When we connect the external USB device it is not enumerated.

 

Please find the log details. Please let us know how to solve this issue.

 

## Booting image at 01000000 ...

   Image Name:   Linux-2.6.28.7-ADI-2009R1-pre

   Created:      2009-04-22  15:26:32 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    3594766 Bytes =  3.4 MB

   Load Address: 00001000

   Entry Point:  001f351c

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 1f351c

Linux version 2.6.28.7-ADI-2009R1-pre (sreecha@linux-hms-jasmin) (gcc version 4.1.2 (ADI svn)) #55 Wed Apr 22 20:56:22 IST 2009

console [early_BFuart0] enabled

early printk enabled on early_BFuart0

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x0014e150

  rodata    = 0x0014e150-0x001ba718

  bss       = 0x001ba720-0x001cd248

  data      = 0x001cd248-0x001e6000

    stack   = 0x001e4000-0x001e6000

  init      = 0x001e6000-0x0069a000

  available = 0x0069a000-0x03eff000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 1

Blackfin support (C) 2004-2009 Analog Devices, Inc.

Compiled for ADSP-BF527 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 525 MHz core clock and 131 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

Data Cache Enabled for CPU0 (write-back)

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 16001

Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

Console: colour dummy device 80x25

console [tty0] enabled

Linux version 2.6.28.7-ADI-2009R1-pre (sreecha@linux-hms-jasmin) (gcc version 4.1.2 (ADI svn)) #55 Wed Apr 22 20:56:22 IST 2009

console [early_BFuart0] enabled

early printk enabled on early_BFuart0

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x0014e150

  rodata    = 0x0014e150-0x001ba718

  bss       = 0x001ba720-0x001cd248

  data      = 0x001cd248-0x001e6000

    stack   = 0x001e4000-0x001e6000

  init      = 0x001e6000-0x0069a000

  available = 0x0069a000-0x03eff000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 1

Blackfin support (C) 2004-2009 Analog Devices, Inc.

Compiled for ADSP-BF527 Rev 0.2

Blackfin Linux support by http://blackfin.uclinux.org/

Processor Speed: 525 MHz core clock and 131 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

Data Cache Enabled for CPU0 (write-back)

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 16001

Kernel command line: root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

Console: colour dummy device 80x25

console [tty0] enabled

console handover: boot [early_BFuart0] -> real [ttyBF0]

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory available: 57164k/65536k RAM, (4816k init code, 1332k kernel code, 608k data, 1024k dma, 588k reserved)

Calibrating delay loop... 1046.52 BogoMIPS (lpj=2093056)

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

Blackfin L1 Data A SRAM: 16 KB (15 KB free)

Blackfin L1 Data B SRAM: 16 KB (16 KB free)

Blackfin L1 Instruction SRAM: 48 KB (42 KB free)

PDA for CPU0 reserved at 001bb650

net_namespace: 288 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

ezkit_init(): registering device resources

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

musb_hdrc: version 6.0, musb-dma, host, debug=0

musb_hdrc: USB Host mode controller at ffc03800 using DMA, IRQ 59

musb_hdrc musb_hdrc.0: MUSB HDRC host driver

musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

dma_alloc_init: dma_page @ 0x03e88000 - 256 pages at 0x03f00000

hub 1-0:1.0: 1 port detected

usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb1: Product: MUSB HDRC host driver

usb usb1: Manufacturer: Linux 2.6.28.7-ADI-2009R1-pre musb-hcd

usb usb1: SerialNumber: musb_hdrc.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 111

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bfin-t350mcqb: 320x240 24-bit RGB FrameBuffer initializing...

Console: switching to colour frame buffer device 40x30

bfin-otp: initialized

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 31) is a BFIN-UART

brd: module loaded

bfin_mii_bus: probed

bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=25)@sclk=131MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

Driver 'sd' needs updating - please use bus_type methods

bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7

r8a66597_hcd: driver r8a66597_hcd, 10 Apr 2008

r8a66597_hcd: driver r8a66597_probe

r8a66597_hcdusb_create_hcd

r8a66597_hcdhcd_to_r8a66597

r8a66597_hcdusb_add_hcd

r8a66597_hcd r8a66597_hcd: USB Host Controller

r8a66597_hcd r8a66597_hcd: new USB bus registered, assigned bus number 2

r8a66597_hcd r8a66597_hcd: irq 88, io base 0x20200000

usb usb2: configuration #1 chosen from 1 choice

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 2 ports detected

usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb2: Product: USB Host Controller

usb usb2: Manufacturer: Linux 2.6.28.7-ADI-2009R1-pre r8a66597_hcd

usb usb2: SerialNumber: r8a66597_hcd

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver libusual

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

usbcore: registered new interface driver usbhid

usbhid: v2.6:USB HID core driver

TCP cubic registered

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting system clock to 1970-01-01 00:56:05 UTC (3365)

Freeing unused kernel memory: 4816k freed

                           _____________________________________

        a8888b.           / Welcome to the uClinux distribution \

       d888888b.         /       _     _                         \

       8P"YP"Y88        /       | |   |_|            __  __ (TM)  |

       8|o||o|88  _____/        | |    _ ____  _   _ \ \/ /       |

       8'    .88       \        | |   | |  _ \| | | | \  /        |

       8`._.' Y8.       \       | |__ | | | | | |_| | /  \        |

      d/      `8b.       \      \____||_|_| |_|\____|/_/\_\       |

     dP   .    Y8b.       \   For embedded processors including   |

    d8:'  "  `::88b        \    the Analog Devices Blackfin      /

   d8"         'Y88b        \___________________________________/

  :8P    '      :888

   8a.   :     _a88P         For further information, check out:

._/"Yaa_:   .| 88P|            - http://blackfin.uclinux.org/

\    YP"    `| 8P  `.          - http://docs.blackfin.uclinux.org/

/     \.___.d|    .'           - http://www.uclinux.org/

`--..__)8888P`._.'  jgs/a:f    - http://www.analog.com/blackfin

 

Have a lot of fun...

 

 

BusyBox v1.13.2 (2009-04-18 16:57:15 IST) built-in shell (msh)

Enter 'help' for a list of built-in commands.

 

Once I connect the USB device into the renesas USB port I got the following error messges

 

root:/> usb 2-2: new high speed USB device using r8a66597_hcd and address 2

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 4

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 6

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 8

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 10

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 12

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 14

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 16

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 18

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 20

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 22

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 24

usb 2-2: device descriptor read/64, error -104

usb 2-2: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 2

usb 2-2: new full speed USB device using r8a66597_hcd and address 26

usb 2-2: device descriptor read/64, error -104

 

root:/>

root:/> hub 2-0:1.0: unable to enumerate USB device on port 2

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

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 29

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 31

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 33

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 35

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 37

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 39

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 41

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 43

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 45

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 47

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 49

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 51

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 53

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 55

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 57

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 59

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 61

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 63

usb 2-1: device descriptor read/64, error -104

usb 2-1: device descriptor read/64, error -104

hub 2-0:1.0: unable to enumerate USB device on port 1

usb 2-1: new full speed USB device using r8a66597_hcd and address 65

 

Please send your comments and suggestions.

 

Best Regards, Sreedhar

QuoteReplyEditDelete

 

 

2009-04-22 11:31:38     Re: Renesas USB HC with BF527 Issues

Robin Getz (UNITED STATES)

Message: 73066   

 

Sreedhar:

 

Disconnect the Renesas part - we don't support it. Then try troubleshooting things. If you only have problems with that driver - ask the author - which is not us.

 

-Robin

Attachments

    Outcomes