2008-01-30 11:30:38     Ethernet over USB (Gadget)

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

2008-01-30 11:30:38     Ethernet over USB (Gadget)

Bill Fassler (UNITED STATES)

Message: 50381    The wikidoc only talks about configuring and building this support as a module.  Is this mandatory, so that you can pass in arguments like g_ether host, etc?

 

Can I assume that I could build it in if I had the appropriate environment variables set?

 

Bill

QuoteReplyEditDelete

 

 

2008-01-30 12:11:05     Re: Ethernet over USB (Gadget)

Bryan Wu (CHINA)

Message: 50384    Bill,

 

I didn't try built-in g_ether, because we set some MAC address when insmod.

But it should be ok for you to try it, please share your result with us.

 

Thanks

-Bryan

QuoteReplyEditDelete

 

 

2008-01-30 13:19:18     Re: Ethernet over USB (Gadget)

Bill Fassler (UNITED STATES)

Message: 50387    How do I enable USB_B5 connector for my Ethernet over USB test/demo?

 

I intended to try this initially with the BF537-STAMP board using the ADDS-USB-EZEXT1.  I have the cypress USB working.  I think based on what  see in the schematics that I should be able to just pull jumper 12 and change to SLAVE mode.  Does this also change the connector to the USB_B5? I assume USB_A5 and USB_B5 are not active at the same time and I have only used USB_A5 (host) in the past.

 

Sorry for the question, but of all the ADI development/evaluation and ADD ON daughter boards I have.   I only have one ADDS-USB-EZEXT1 and am a little uncertain and don't want to damage the board.

 

I have several (at least 4) of the ADZS-USBLAN_EZEXT daughter boards that I was using on the BF561-EZKIT, but these don't seem to be compatible at all with the BF537-STAMP.

 

Bill

QuoteReplyEditDelete

 

 

2008-01-30 15:22:16     Re: Ethernet over USB (Gadget)

Bill Fassler (UNITED STATES)

Message: 50393    I decided to pull jumper 12 and give it a try.  Once the sparks stopped and the smoke cleared and I made sure my dog was no longer on fire I captured the standard output.

 

(Here is the what I really experienced

 

Pulling jumper 12 on the USB-ADD-ON card doesn't seem to be the only thing I have to do. I was trying to use my mega-multimedia BF537-STAMP board where I had console enabled, of course pulling jumper 12 means I lost my host USB and had no HID, so I removed console.  Then I had a peripheral 13 conflict apparently with the LCD, so I disabled graphics support altogether.  Then I still had a GPIO 6 conflict with the ad1836 daughter board, so I disabled sound support altogether.

 

After this, I no longer experienced any sort of stack dump, but the SL811 Slave still has errors reading and writing. I gather this excerpt is the problem:

net2272: PLX NET2272 USB Peripheral Controller

net2272: irq 57, mapped mem 20300000, chip rev 00f9

net2272: running in 16-bit, no byte swap local bus mode

net2272: version: 2005 Sept 8

net2272: 2272 not found!

net2272: unbind

So all in all no luck yet and I am not sure what to do next.

 

Any thoughts?

 

Here is the first output with all my multi-media drivers in tact:

<pre id="line44">bfin> bootm 0x1000000

## Booting image at 01000000 ...

Image Name: Linux-2.6.22.14-ADI-2007R2-pre-s

Created: 2008-01-30 19:32:18 UTC

Image Type: Blackfin Linux Kernel Image (gzip compressed)

Data Size: 3197498 Bytes = 3 MB

Load Address: 00001000

Entry Point: 001da000

Verifying Checksum ... OK

Uncompressing Kernel Image ... OK

Starting Kernel at = 1da000

Linux version 2.6.22.14-ADI-2007R2-pre-svn3974 (vocal@Grumpy) (gcc version 4.1.2

(ADI svn)) #6 Wed Jan 30 14:32:13 EST 2008

Hardware Trace Active and Enabled

Warning: limiting memory to 56MB due to hardware anomaly 05000263

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

Compiled for ADSP-BF537 Rev 0.2

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

Processor Speed: 500 MHz core clock and 100 MHz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

text = 0x00001000-0x0015fbc0

rodata = 0x00160000-0x001c3d00

data = 0x001c4000-0x001da000

stack = 0x001c4000-0x001c6000

init = 0x001da000-0x005ad000

bss = 0x005ad000-0x005c19a4

available = 0x005c19a4-0x037ff000

DMA Zone = 0x03e00000-0x04000000

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists. Total pages: 14224

Kernel command line: root=/dev/mtdblock0 rw

Configuring Blackfin Priority Driven Interrupts

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)

Physical pages: 37ff

Memory available: 50808k/63728k RAM, (3916k init code, 1402k kernel code, 82k da

ta, 2048k dma)

Blackfin Scratchpad data SRAM: 4 KB

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

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

Blackfin Instruction SRAM: 48 KB (39 KB free)

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

Generic PHY: Registered new driver

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

NET: Registered protocoIP route cache hash table entries: 1024 (order: 0, 4096 b

ytes)

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

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

bf537-lq035: FrameBuffer initializing...<6>dma_alloc_init: dma_page @ 0x0357c000

- 512 pages at 0x03e00000

Done.

Dynamic Power Management Controller Driver v0.1: major=10, minor = 254

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

Serial: Blackfin serial driver

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

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

SMSC LAN83C185: Registered new driver

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1)

bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver

peripheral_request: Peripheral 13 is already reserved as GPIO by bf537-lq035 !

Hardware Trace:

0 Target : <0x000045ac> { _dump_stack + 0x0 }

Source : <0x0000600a> { _peripheral_request + 0x11a }

1 Target : <0x0000600a> { _peripheral_request + 0x11a }

Source : <0x0000d6a2> { _printk + 0x16 }

2 Target : <0x0000d69e> { _printk + 0x12 }

Source : <0x0000d554> { _vprintk + 0x1b8 }

3 Target : <0x0000d548> { _vprintk + 0x1ac }

Source : <0x0000d53a> { _vprintk + 0x19e }

4 Target : <0x0000d536> { _vprintk + 0x19a }

Source : <0x0000d384> { _wake_up_klogd + 0x24 }

5 Target : <0x0000d360> { _wake_up_klogd + 0x0 }

Source : <0x0000da8c> { _release_console_sem + 0x1f4 }

6 Target : <0x0000da7e> { _release_console_sem + 0x1e6 }

Source : <0x0000da70> { _release_console_sem + 0x1d8 }

7 Target : <0x0000da66> { _release_console_sem + 0x1ce }

Source : <0x0000da58> { _release_console_sem + 0x1c0 }

8 Target : <0x0000da38> { _release_console_sem + 0x1a0 }

Source : <0x0000d91e> { _release_console_sem + 0x86 }

9 Target : <0x0000d8ee> { _release_console_sem + 0x56 }

Source : <0x0000da1a> { _release_console_sem + 0x182 }

10 Target : <0x0000da14> { _release_console_sem + 0x17c }

Source : <0x0000d25e> { __call_console_drivers + 0x7e }

11 Target : <0x0000d258> { __call_console_drivers + 0x78 }

Source : <0x0000d21a> { __call_console_drivers + 0x3a }

12 Target : <0x0000d20a> { __call_console_drivers + 0x2a }

Source : <0x0000d1fa> { __call_console_drivers + 0x1a }

13 Target : <0x0000d1e0> { __call_console_drivers + 0x0 }

Source : <0x0000da10> { _release_console_sem + 0x178 }

14 Target : <0x0000da06> { _release_console_sem + 0x16e }

Source : <0x0000d9a4> { _release_console_sem + 0x10c }

15 Target : <0x0000d99e> { _release_console_sem + 0x106 }

Source : <0x0000d1de> { ___call_console_drivers + 0x52 }

Stack from 0065fe30:

03576600 0000600e 00000000 0000800d 00000000 001607dc 0000000d 037c10d0

0357667c 03576600 000060a4 001c9480 035766a0 001c8e74 000000a4 00000000

0019770c 00000000 00000000 03576600 001eed06 001eed1a 035766c8 000000a4

001c8e6c 00000000 0000a1ff 00000020 000b5d50 001c8e74 001d1b6c 00000000

001c8edc 00000054 000b5e4e 001c8e74 001d1b6c 005ba274 000000d8 001d1b6c

001d1b6c 0009a9f2 0015e024 0015e03e 001c8d60 000b612a 001c8f4c 001c8e74

 

Call Trace:

[<000b5306>] _bus_for_each_dev+0x36/0x64

[<000b6028>] ___driver_attach+0x0/0x10c

[<0009a452>] _kobject_register+0x2e/0x44

[<000b5d06>] _driver_attach+0x1a/0x20

[<000b5632>] _bus_add_driver+0x4e/0x164

[<000b6028>] ___driver_attach+0x0/0x10c

[<000b5648>] _bus_add_driver+0x64/0x164

[<000b7652>] _platform_driver_probe+0xe/0x58

[<001da674>] _kernel_init+0x88/0x234

[<001da5ec>] _kernel_init+0x0/0x234

[<00001686>] _kernel_thread_helper+0x6/0xc

 

bfin-spi bfin-spi.0: : Requesting Peripherals failed

bfin-spi: probe of bfin-spi.0 failed with error -16

sl811: driver sl811-hcd, 19 May 2005

sl811-hcd sl811-hcd.0: SL811HS v1.5

sl811-hcd sl811-hcd.0: new USB bus registered, assigned bus number 1

sl811-hcd sl811-hcd.0: irq 55, io mem 0x20340000

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

bfin-gpio: GPIO 6 is already reserved as Peripheral by ad1836-spi !

Hardware Trace:

0 Target : <0x000045ac> { _dump_stack + 0x0 }

Source : <0x00006234> { _gpio_request + 0xbc }

1 Target : <0x00006234> { _gpio_request + 0xbc }

Source : <0x0000d6a2> { _printk + 0x16 }

2 Target : <0x0000d69e> { _printk + 0x12 }

Source : <0x0000d554> { _vprintk + 0x1b8 }

3 Target : <0x0000d548> { _vprintk + 0x1ac }

Source : <0x0000d53a> { _vprintk + 0x19e }

4 Target : <0x0000d536> { _vprintk + 0x19a }

Source : <0x0000d384> { _wake_up_klogd + 0x24 }

5 Target : <0x0000d360> { _wake_up_klogd + 0x0 }

Source : <0x0000da8c> { _release_console_sem + 0x1f4 }

6 Target : <0x0000da7e> { _release_console_sem + 0x1e6 }

Source : <0x0000da70> { _release_console_sem + 0x1d8 }

7 Target : <0x0000da66> { _release_console_sem + 0x1ce }

Source : <0x0000da58> { _release_console_sem + 0x1c0 }

8 Target : <0x0000da38> { _release_console_sem + 0x1a0 }

Source : <0x0000d91e> { _release_console_sem + 0x86 }

9 Target : <0x0000d8ee> { _release_console_sem + 0x56 }

Source : <0x0000da1a> { _release_console_sem + 0x182 }

10 Target : <0x0000da14> { _release_console_sem + 0x17c }

Source : <0x0000d25e> { __call_console_drivers + 0x7e }

11 Target : <0x0000d258> { __call_console_drivers + 0x78 }

Source : <0x0000d21a> { __call_console_drivers + 0x3a }

12 Target : <0x0000d20a> { __call_console_drivers + 0x2a }

Source : <0x0000d1fa> { __call_console_drivers + 0x1a }

13 Target : <0x0000d1e0> { __call_console_drivers + 0x0 }

Source : <0x0000da10> { _release_console_sem + 0x178 }

14 Target : <0x0000da06> { _release_console_sem + 0x16e }

Source : <0x0000d9a4> { _release_console_sem + 0x10c }

15 Target : <0x0000d99e> { _release_console_sem + 0x106 }

Source : <0x0000d1de> { ___call_console_drivers + 0x52 }

Stack from 0065fe88:

00006190 00006238 001c8d18 00000006 0019c008 00000006 037c1060 000d2650

000000d8 001c8d18 005ba8d0 000b5d50 001c8d18 001d2644 00000000 001c8d80

00000054 000b5e4e 001c8d18 001d2644 005ba274 000000d8 001d2644 001d2644

0009a9f2 0015e024 0015e03e 001c8c04 000b612a 001c8df0 001c8d18 001d2644

000000d8 001d0ce8 001d2644 00000000 000b5306 000b6028 001d0ce8 00000000

0065ff38 00000000 00000054 0009a452 001d0dd4 001d0dd4 001c8d60 000b5d06

 

Call Trace:

[<000b5632>] _bus_add_driver+0x4e/0x164

[<000b6028>] ___driver_attach+0x0/0x10c

[<000b5648>] _bus_add_driver+0x64/0x164

[<000b7696>] _platform_driver_probe+0x52/0x58

[<000b7696>] _platform_driver_probe+0x52/0x58

[<001da674>] _kernel_init+0x88/0x234

[<001da5ec>] _kernel_init+0x0/0x234

[<00001686>] _kernel_thread_helper+0x6/0xc

 

net2272: Failed to request GPIO_6

net2272: probe of net2272 failed with error -16

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

i2c /dev entries driver

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller Driver, Ve

rsion 1.8, regs_base@ffc01400

usb 1-1: new full speed USB device using sl811-hcd and address 2

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -62

usb 1-1: new full speed USB device using sl811-hcd and address 3

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -62

usb 1-1: new full speed USB device using sl811-hcd and address 4

usb 1-1: device not accepting address 4, error -62

usb 1-1: new full speed USB device using sl811-hcd and address 5

usb 1-1: device not accepting address 5, error -62

usbcore: registered new interface driver usbhid

drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver

Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50

2006 UTC).

ALSA device list:

#0: ADI ad1836 at PF4 SPORT0 rx/tx dma 3/4 err irq 45

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-01-01 00:43:46 (2626)

Freeing unused kernel memory: 3916k 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.4.1 (2008-01-30 14:07:10 EST) Built-in shell (msh)

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

 

root:~>

 

*******************************************************

<== I plugged the USB network cable in at this point and get endless

errors

***********************************************************

 

root:~> usb 1-1: new full speed USB device using sl811-hcd and address 6

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 7

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 8

usb 1-1: device not accepting address 8, error -108

hub 1-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?

usb 1-1: new full speed USB device using sl811-hcd and address 10

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 11

usb 1-1: device descriptor read/64, error -62

*****************************************************************************************

Last attempt with graphics and sound support disabled

*****************************************************************************************

 

bfin> bootm 0x1000000

## Booting image at 01000000 ...

   Image Name:   Linux-2.6.22.14-ADI-2007R2-pre-s

   Created:      2008-01-30  19:53:22 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    3114233 Bytes =  3 MB

   Load Address: 00001000

   Entry Point:  001b8000

   Verifying Checksum ... OK

   Uncompressing Kernel Image ... OK

Starting Kernel at = 1b8000

Linux version 2.6.22.14-ADI-2007R2-pre-svn3974 (vocal@Grumpy) (gcc version 4.1.2

(ADI svn)) #12 Wed Jan 30 14:53:16 EST 2008

Hardware Trace Active and Enabled

Warning: limiting memory to 56MB due to hardware anomaly 05000263

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

Compiled for ADSP-BF537 Rev 0.2

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

Processor Speed: 500 MHz core clock and 100 MHz System Clock

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  text      = 0x00001000-0x00144e20

  rodata    = 0x00145000-0x001a2590

  data      = 0x001a3000-0x001b8000

    stack   = 0x001a4000-0x001a6000

  init      = 0x001b8000-0x0058b000

  bss       = 0x0058b000-0x0059efa4

  available = 0x0059efa4-0x037ff000

  DMA Zone  = 0x03e00000-0x04000000

Instruction Cache Enabled

Data Cache Enabled (write-through)

Built 1 zonelists.  Total pages: 14224

Kernel command line: root=/dev/mtdblock0 rw

Configuring Blackfin Priority Driven Interrupts

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)

Physical pages: 37ff

Memory available: 50948k/63860k RAM, (3916k init code, 1295k kernel code, 79k da

ta, 2048k dma)

Blackfin Scratchpad data SRAM: 4 KB

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

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

Blackfin Instruction SRAM: 48 KB (39 KB free)

Security Framework v1.0.0 initialized

Mount-cache hash table entries: 512

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

Generic PHY: Registered new driver

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

NET: Registered protIP route cache hash table entries: 1024 (order: 0, 4096 byte

s)

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

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

Dynamic Power Management Controller Driver v0.1: major=10, minor = 254

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

Serial: Blackfin serial driver

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

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

SMSC LAN83C185: Registered new driver

bfin_mac_mdio: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1)

bfin_mac: Version 1.1, Blackfin BF53[67] BF527 on-chip Ethernet MAC driver

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, r

egs_base@ffc00500, dma channel@7

sl811: driver sl811-hcd, 19 May 2005

sl811-hcd sl811-hcd.0: SL811HS v1.5

sl811-hcd sl811-hcd.0: new USB bus registered, assigned bus number 1

sl811-hcd sl811-hcd.0: irq 55, io mem 0x20340000

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

net2272: PLX NET2272 USB Peripheral Controller

net2272: irq 57, mapped mem 20300000, chip rev 00f9

net2272: running in 16-bit, no byte swap local bus mode

net2272: version: 2005 Sept 8

net2272: 2272 not found!

net2272: unbind

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

i2c /dev entries driver

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller Driver, Ve

rsion 1.8, regs_base@ffc01400

usb 1-1: new full speed USB device using sl811-hcd and address 2

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -62

usb 1-1: new full speed USB device using sl811-hcd and address 3

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -62

usb 1-1: new full speed USB device using sl811-hcd and address 4

usb 1-1: device not accepting address 4, error -62

usb 1-1: new full speed USB device using sl811-hcd and address 5

usb 1-1: device not accepting address 5, error -62

usbcore: registered new interface driver usbhid

drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver

TCP cubic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting the system clock to 1970-01-01 00:57:53 (3473)

Freeing unused kernel memory: 3916k freed

dma_alloc_init: dma_page @ 0x00588000 - 512 pages at 0x03e00000

                           _____________________________________

        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.4.1 (2008-01-30 14:07:10 EST) Built-in shell (msh)

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

 

root:~> usb 1-1: new full speed USB device using sl811-hcd and address 6

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -62

usb 1-1: new full speed USB device using sl811-hcd and address 7

usb 1-1: device descriptor read/64, error -108

usb 1-1: device descriptor read/64, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 8

usb 1-1: device not accepting address 8, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 9

usb 1-1: device not accepting address 9, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 10

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 11

usb 1-1: device descriptor read/64, error -62

usb 1-1: device descriptor read/64, error -108

usb 1-1: new full speed USB device using sl811-hcd and address 12

usb 1-1: device not accepting address 12, error -108

hub 1-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

QuoteReplyEditDelete

 

 

2008-01-30 15:58:28     Re: Ethernet over USB (Gadget)

Michael Hennerich (GERMANY)

Message: 50396   

 

Bill,

 

I remember I noticed this before:

(plug and play can be often be plug and pray - embedded developers handing should be aware...)

 

1) There is NO USB Device driver for the SL811HST. The feature on the SL811, ISP1362 USB combo Card is JUST a feature (this applies for both controllers), not a tested option - however electrically it's considered as functional and bullet proof, as long as you set/remove the right jumpers.

 

2) The only devices where we feature USB Device functionality is PLX2272 aka NET 2272 (USB_LAN externder) or the BF548/BF527 on-chip USB peripheral.

 

This card should also work with the BF537-STAMP aka more or less EZkit. (Check the jumper/switch options)

 

-Michael

QuoteReplyEditDelete

 

 

2008-01-30 16:44:31     Re: Ethernet over USB (Gadget)

Bill Fassler (UNITED STATES)

Message: 50402    Michael - I did notice that the USB_LAN extender had the NET2272.  I guess I thought the USB was a 'standard' and 'ethernet' was a 'standard' and I didn't expect a special chip would be necessary to get ethernet over USB to work.

 

I did swap over to a BF561-EZKIT with the extender card in place and it didn't even attempt to probe for the NET2272.  It didn't work either.  Even if I didn't have the dip switches and/or jumpers set correctly I thought it should at least look and tell me it failed to find NET2272 like the software did on the BF537-STAMP.  I set the same gadget configuration that I used on the BF537-STAMP.

 

I initially tried with the 2.3 BOM of the BF561-EZKIT, but since there has been some reported power issues, I also tried the 2.6 BOM with no better results.

 

I am now swapping the USB cards and putting the USB_LAN extender onto my BF537-STAMP board and see if that works.

 

I don't care where or how I get it to work, but I simply must get it to work by tomorrow. Your help as always is appreciated.

 

Bill

QuoteReplyEditDelete

 

 

2008-01-30 17:20:33     Re: Ethernet over USB (Gadget)

Michael Hennerich (GERMANY)

Message: 50405   

 

Bill,

 

 

 

 

 

It’s now almost midnight on my side –

 

 

 

I guess you have to wait a few hours …

 

 

 

 

 

Cheers or better Prost

 

 

 

Michael

 

 

 

QuoteReplyEditDelete

 

 

2008-01-30 17:29:13     Re: Ethernet over USB (Gadget)

Bill Fassler (UNITED STATES)

Message: 50406    No problem.  I have it working now on the BF537-STAMP with the USB_LAN.  Like I mentioned before I had to disable all other daughter cards (sound and graphic) to avoid conficts, but it is up and running.

 

I was using the exact same daughter board on the BF561-EZKIT which didn't work (although like I mentioned it didn't even probe for the NET2272 - perhaps I overlooked a config setting?).

 

Anyway, one more milestone behind me.

 

This is all new to me and I am not sure what to expect when I have an eth0 and a usb0 so I bring down the eth0 just to avoid confusion.  Is it possible to have both of these enabled and up at the same time?  I would assume so, since if I'm not mistaken VPN tunnels work in tandem with other ethernet devices without conflict.

 

Thanks for your help,

Bill

QuoteReplyEditDelete

 

 

2008-02-01 10:48:34     Re: Ethernet over USB (Gadget)

Bill Fassler (UNITED STATES)

Message: 50577    Mike H.

 

Do you think the reason I got this to work on the BF537-STAMP and not the BF561-EZKIT might be related to the SMSC91111 driver on the BF561?

 

I say this because both the regular Ethernet and the USB are both on the add on card.  The BF537-STAMP board however has the built in MAC in the DSP and only only a phy connector, whereas the BF561-EZKIT has the SMSC91111 chip and I need regular internet in order to boot the uClinux using TFTP.  So on the BF561-EZKIT I was building both regular Ethernet and Ethernet over USB and perhaps this caused the problem/conflict?

 

Not that this is overly important at the moment, but I would like to understand the difficulties I encountered trying to get this to work on the BF561-EZKIT.

 

Bill

QuoteReplyEditDelete

 

 

2008-02-01 10:59:54     Re: Ethernet over USB (Gadget)

Michael Hennerich (GERMANY)

Message: 50578    Bill,

 

from a Software point of view - No.

I will give this a spin here.

-Michael

QuoteReplyEditDelete

 

 

2008-02-01 11:58:54     Re: Ethernet over USB (Gadget)

Michael Hennerich (GERMANY)

Message: 50579    Bill,

 

I checked in a bunch of fixes/BF561-Ezkit board support into the 2008R1 Release branch -

 

On my side it works quite well – see below

 

 

-Michael

 

 

Linux version 2.6.22.16-ADI-2008R1-svn4196 (michael@mhenneri-D02) (gcc version 4.1.2 (ADI svn)) #268 Fri Feb 1 17:44:29 CET 2008

 

Hardware Trace Active and Enabled

 

Warning: limiting memory to 56MB due to hardware anomaly 05000263

 

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

 

Compiled for ADSP-BF561 Rev 0.3

 

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

 

Processor Speed: 600 MHz core clock and 100 MHz System Clock

 

Board Memory: 64MB

 

Kernel Managed Memory: 64MB

 

Memory map:

 

text = 0x00001000-0x000f2c40

 

rodata = 0x000f3000-0x0013753c

 

data = 0x00138000-0x00148000

 

stack = 0x00138000-0x0013a000

 

init = 0x00148000-0x0039a000

 

bss = 0x0039a000-0x003a9630

 

available = 0x003a9630-0x037ff000

 

DMA Zone = 0x03f00000-0x04000000

 

Instruction Cache Enabled

 

Data Cache Enabled (write-through)

 

Built 1 zonelists. Total pages: 14224

 

Kernel command line: root=/dev/mtdblock0 rw ip=10.44.2.37:10.44.2.88:192.168.0.1:255.255.255.0:ezkit561:eth0:off

 

Configuring Blackfin Priority Driven Interrupts

 

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 available: 53012k/65536k RAM, (2376k init code, 967k kernel code, 402k data, 1024k dma, 7756k reserved)

 

Blackfin Scratchpad data SRAM: 4 KB

 

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

 

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

 

Blackfin Instruction SRAM: 16 KB (8 KB free)

 

Security Framework v1.0.0 initialized

 

Mount-cache hash table entries: 512

 

NET: Registered protocol family 16

 

Blackfin GPIO Controller

 

Blackfin DMA Controller

 

ezkit_init(): registering device resources

 

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

 

BF561 Core B driver v0.1 initialized.

 

io scheduler noop registered

 

io scheduler anticipatory registered (default)

 

io scheduler cfq registered

 

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

 

Serial: Blackfin serial driver

 

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

 

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

 

smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <nico@cam.org>

 

eth0: SMC91C11xFD (rev 2) at 2c010300 IRQ 82 [nowait]

 

eth0: Ethernet addr: 00:e0:22:fe:b1:28

 

bfin-spi bfin-spi.0: Blackfin BF5xx on-chip SPI Contoller Driver, Version 1.0, regs_base@ffc00500, dma channel@16

 

net2272: PLX NET2272 USB Peripheral Controller

 

net2272: irq 83, mapped mem 2c000000, chip rev 0011

 

net2272: running in 16-bit, no byte swap local bus mode

 

net2272: version: 2005 Sept 8

 

ether gadget: using random self ethernet address

 

ether gadget: using random host ethernet address

 

usb0: Ethernet Gadget, version: May Day 2005

 

usb0: using net2272, OUT ep-b IN ep-a STATUS ep-c

 

usb0: MAC 82:47:fc:24:55:fd

 

usb0: HOST MAC 4e:85:2a:b3:e9:cf

 

usb0: RNDIS ready

 

TCP cubic registered

 

NET: Registered protocol family 1

 

NET: Registered protocol family 17

 

eth0: link down

 

IP-Config: Gateway not on directly connected network.

 

Freeing unused kernel memory: 2376k freed

 

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

 

_____________________________________

 

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...

 

eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

 

 

BusyBox v1.4.1 (2008-02-01 16:58:23 CET) Built-in shell (msh)

 

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

 

 

root:/> usb0: high speed config #1: 100 mA, Ethernet Gadget, using CDC Ethernet

 

 

On my Host machine, when I plug in the USB cable ...

 

 

dmesg:

 

 

usb 5-1.3: new high speed USB device using ehci_hcd and address 21

 

usb 5-1.3: new device found, idVendor=0525, idProduct=a4a2

 

usb 5-1.3: new device strings: Mfr=1, Product=2, SerialNumber=0

 

usb 5-1.3: Product: RNDIS/Ethernet Gadget

 

usb 5-1.3: Manufacturer: Linux 2.6.22.16-ADI-2008R1-svn4196/net2272

 

usb 5-1.3: configuration #1 chosen from 2 choices

 

usb0: register 'cdc_ether' at usb-0000:00:1d.7-1.3, CDC Ethernet Device, 96:e3:bb:38:b6:28

 

michael@mhenneri-D02:~/devel/svn/uclinux-dist-2008R1>

QuoteReplyEditDelete

 

 

2008-02-01 12:10:18     Re: Ethernet over USB (Gadget)

Bill Fassler (UNITED STATES)

Message: 50580    Thanks Michael.  I look forward to upgrading to 2008R1 when it is stable and available!

 

Bill

Attachments

    Outcomes