2008-10-09 21:20:55 Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63357
Please help,
I follow the website wiki procedure, and I could not make it to work.
here is my environment:
bfin> printenv
bootdelay=5
baudrate=57600
loads_echo=1
rootpath=/romfs
hostname=bf527-ezkit
loadaddr=0x1000000
ubootfile=u-boot.ldr
update=tftp $(loadaddr) $(ubootfile);protect off 0x20000000 0x2003FFFF;erase 0x20000000 0x2003FFFF;cp.b $(loadaddr) 0x20000000 $(filesize)
addip=set bootargs $(bootargs) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname):eth0:off
ramargs=set bootargs root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600
ramboot=tftp $(loadaddr) uImage;run ramargs;run addip;bootm
nfsargs=set bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath),tcp,nfsvers=3
nfsboot=tftp $(loadaddr) vmImage;run nfsargs;run addip;bootm
flashboot=bootm 0x20100000
ethaddr=00:E0:22:FE:B9:07
ethact=Blackfin EMAC
filesize=4f9fac
fileaddr=1000000
gatewayip=10.13.38.1
netmask=255.255.255.0
ipaddr=10.13.38.162
serverip=10.13.38.95
bootargs=root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600 ip=10.13.38.162:10.13.38.95:10.13.38.1:255.255.255.0:bf527-ezkit:eth0:off
bootfile=uImage
tftpl="tftp 0x1000000 uImage ; bootelf 0x1000000"
eth_a_host=00:01:9c:01:23:45
eth_a_gadget=00:01:9c:67:89:ac
eth_i_vendor="Dominic On"
eth_i_product="NewProduct"
bootcmd=run add_eth_args;bootm
eth_args=g_ether.host_addr=$(eth_a_host) g_ether.dev_addr=$(eth_a_gadget)
stdin=serial
stdout=serial
stderr=serial
add_eth_args=setenv bootargs g_ether.host_addr=$(eth_a_host) g_ether.dev_addr=$(eth_a_gadget) $(bootargs)
Environment size: 1452/8188 bytes
Here is the booting message log
U-Boot 1.1.6-svn1273 (ADI-2008R1.5) (Jul 21 2008 - 00:29:36)
CPU: ADSP bf527-0.0 (Detected Rev: 0.0)
Board: ADI BF527 EZ-Kit board
Support: http://blackfin.uclinux.org/
Clock: VCO: 525 MHz, Core: 525 MHz, System: 131 MHz
RAM: 64 MB
Flash: 4 MB
In: serial
Out: serial
Err: serial
Net: Blackfin EMAC
MAC: 00:E0:22:FE:B9:07
Hit any key to stop autoboot: 0
## Booting image at 01000000 ...
Image Name: Linux-2.6.22.19-ADI-2008R1.5-svn
Created: 2008-10-10 0:43:25 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 3821526 Bytes = 3.6 MB
Load Address: 00001000
Entry Point: 001a0000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 1a0000
Linux version 2.6.22.19-ADI-2008R1.5-svn5399 (dominic@Ottdev04) (gcc version 4.1.2 (ADI svn)) #35 Thu Oct 9 19:43:21 CDT 2008
early printk enabled on early_BFuart0
Hardware Trace Active and Enabled
Blackfin support (C) 2004-2007 Analog Devices, Inc.
Compiled for ADSP-BF527 Rev 0.0
Warning: Unsupported Chip Revision ADSP-BF527 Rev 0.0 detected
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 525 MHz core clock and 131 MHz System Clock
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
text = 0x00001000-0x0012e5d0
rodata = 0x0012f000-0x00189b18
data = 0x0018a000-0x001a0000
stack = 0x0018a000-0x0018c000
init = 0x001a0000-0x00733000
bss = 0x00733000-0x00742d10
available = 0x00742d10-0x03eff000
DMA Zone = 0x03f00000-0x04000000
NOMPU: setting up cplb tables for global access
Instruction Cache Enabled
Data Cache Enabled (write-through)
Built 1 zonelists. Total pages: 16002
Kernel command line: g_ether.host_addr=00:01:9c:01:23:45 g_ether.dev_addr=00:01:9c:67:89:ac root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600 ip=10.13.38.162:10.13.38.95:10.13.38.1:255.255.255.0:bf527-ezkit:eth0:off
Unknown boot option `g_ether.host_addr=00:01:9c:01:23:45': ignoring
Unknown boot option `g_ether.dev_addr=00:01:9c:67:89:ac': ignoring
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
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: 56496k/65536k RAM, (5708k init code, 1205k kernel code, 518k data, 1024k dma, 584k 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: 48 KB (41 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
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, pio, host, debug=0
musb_hdrc: kernel must blacklist external hubs
musb_hdrc: USB Host mode controller at ffc03800 using PIO, 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
hub 1-0:1.0: 1 port detected
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
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
bfin-t350mcqb: 320x240 24-bit RGB FrameBuffer initializing...
dma_alloc_init: dma_page @ 0x03bcf000 - 256 pages at 0x03f00000
bfin-otp: initialized
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 31) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
bfin_mac_mdio: 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: 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, regs_base@ffc00500, dma channel@7
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
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:
No soundcards found.
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 09:09:41 (32981)
IP-Config: Complete:
device=eth0, addr=10.13.38.162, mask=255.255.255.0, gw=10.13.38.1,
host=bf527-ezkit, domain=, nis-domain=(none),
bootserver=10.13.38.95, rootserver=10.13.38.95, rootpath=
Freeing unused kernel memory: 5708k 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-10-09 19:42:06 CDT) Built-in shell (msh)
Enter 'help' for a list of built-in commands.
root:/> PHY: 0:01 - Link is Up - 100/Half
root:/> modprob g_ether host_addr=00:01:9c:01:23:45 dev_addr=00:01:9c:67:89:ac
modprob: not found
root:/> modprobe g_ether host_addr=00:01:9c:01:23:45 dev_addr=00:01:9c:67:89:ac
bfin-gpio: GPIO 7 is already reserved as Peripheral by bfin-t350mcqb !
Hardware Trace:
0 Target : <0x000047f8> { _dump_stack + 0x0 }
Source : <0x000060e6> { _gpio_request + 0xbe }
1 Target : <0x000060e6> { _gpio_request + 0xbe }
Source : <0x0000d832> { _printk + 0x16 }
2 Target : <0x0000d82e> { _printk + 0x12 }
Source : <0x0000d6e4> { _vprintk + 0x1b8 }
3 Target : <0x0000d6d8> { _vprintk + 0x1ac }
Source : <0x0000d6ca> { _vprintk + 0x19e }
4 Target : <0x0000d6c6> { _vprintk + 0x19a }
Source : <0x0000d526> { _wake_up_klogd + 0x36 }
5 Target : <0x0000d522> { _wake_up_klogd + 0x32 }
Source : <0x00009878> { ___wake_up + 0x2c }
6 Target : <0x00009872> { ___wake_up + 0x26 }
Source : <0x00009864> { ___wake_up + 0x18 }
7 Target : <0x00009860> { ___wake_up + 0x14 }
Source : <0x0000984a> { ___wake_up_common + 0x52 }
8 Target : <0x0000983c> { ___wake_up_common + 0x44 }
Source : <0x00009832> { ___wake_up_common + 0x3a }
9 Target : <0x0000982c> { ___wake_up_common + 0x34 }
Source : <0x0001d57c> { _autoremove_wake_function + 0x2c }
10 Target : <0x0001d562> { _autoremove_wake_function + 0x12 }
Source : <0x0000a80c> { _try_to_wake_up + 0x3c }
11 Target : <0x0000a804> { _try_to_wake_up + 0x34 }
Source : <0x0000a7f6> { _try_to_wake_up + 0x26 }
12 Target : <0x0000a7f0> { _try_to_wake_up + 0x20 }
Source : <0x0000a81a> { _try_to_wake_up + 0x4a }
13 Target : <0x0000a816> { _try_to_wake_up + 0x46 }
Source : <0x0000a89c> { _try_to_wake_up + 0xcc }
14 Target : <0x0000a89a> { _try_to_wake_up + 0xca }
Source : <0x0000a888> { _try_to_wake_up + 0xb8 }
15 Target : <0x0000a86a> { _try_to_wake_up + 0x9a }
Source : <0x00009aae> { ___activate_task + 0x2e }
Stack from 007f7ce0:
007347d8 000060ea 00000000 00000007 00000008 00000007 007339b4 00008f32
007f7d20 00000007 00000008 00000007 0000a964 007f6000 00067662 0000004e
20515249 03003837 0002884c 00191a14 030613e0 001ee4e8 0000004e 030613e0
001e1400 0000ffff 00000000 0001a422 00067792 0002892c 00000000 0000004e
00000008 001e1400 001ea69c 00000020 001ee4f0 001ec0de 001ec0f8 001e1400
0018eaa0 001ed744 0018eaa8 001ee240 03e961c8 0018eaa8 001ee240 00000000
Call Trace:
[<000a2cd6>] _driver_probe_device+0x7a/0x17c
[<00089996>] _kobject_uevent_env+0x30e/0x398
[<0012c37c>] _klist_next+0x1c/0x60
[<0012c396>] _klist_next+0x36/0x60
[<000a2fb2>] ___driver_attach+0x102/0x10c
[<000a218e>] _bus_for_each_dev+0x36/0x64
[<000a2eb0>] ___driver_attach+0x0/0x10c
[<000893f6>] _kobject_register+0x2e/0x44
[<000a2b8e>] _driver_attach+0x1a/0x20
[<000a24ba>] _bus_add_driver+0x4e/0x164
[<000a2eb0>] ___driver_attach+0x0/0x10c
[<000a24d0>] _bus_add_driver+0x64/0x164
[<0002582c>] _sys_init_module+0xc0/0x10c8
[<00033e9e>] _do_mmap_pgoff+0x662/0x740
[<0002576c>] _sys_init_module+0x0/0x10c8
[<00007f50>] _free_dma+0xa0/0xa4
[<00008000>] _dma_disable_irq+0x40/0x6c
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
bfin-gpio: GPIO 7 is already reserved as Peripheral by bfin-t350mcqb !
Hardware Trace:
0 Target : <0x000047f8> { _dump_stack + 0x0 }
Source : <0x000060e6> { _gpio_request + 0xbe }
1 Target : <0x000060e6> { _gpio_request + 0xbe }
Source : <0x0000d832> { _printk + 0x16 }
2 Target : <0x0000d82e> { _printk + 0x12 }
Source : <0x0000d6e4> { _vprintk + 0x1b8 }
3 Target : <0x0000d6d8> { _vprintk + 0x1ac }
Source : <0x0000d6ca> { _vprintk + 0x19e }
4 Target : <0x0000d6c6> { _vprintk + 0x19a }
Source : <0x0000d514> { _wake_up_klogd + 0x24 }
5 Target : <0x0000d4f0> { _wake_up_klogd + 0x0 }
Source : <0x0000dc1c> { _release_console_sem + 0x1f4 }
6 Target : <0x0000dc0e> { _release_console_sem + 0x1e6 }
Source : <0x0000dc00> { _release_console_sem + 0x1d8 }
7 Target : <0x0000dbf6> { _release_console_sem + 0x1ce }
Source : <0x0000dbe8> { _release_console_sem + 0x1c0 }
8 Target : <0x0000dbc8> { _release_console_sem + 0x1a0 }
Source : <0x0000daae> { _release_console_sem + 0x86 }
9 Target : <0x0000da7e> { _release_console_sem + 0x56 }
Source : <0x0000dbaa> { _release_console_sem + 0x182 }
10 Target : <0x0000dba4> { _release_console_sem + 0x17c }
Source : <0x0000d3ea> { __call_console_drivers + 0x7e }
11 Target : <0x0000d3e4> { __call_console_drivers + 0x78 }
Source : <0x0000d3a6> { __call_console_drivers + 0x3a }
12 Target : <0x0000d396> { __call_console_drivers + 0x2a }
Source : <0x0000d386> { __call_console_drivers + 0x1a }
13 Target : <0x0000d36c> { __call_console_drivers + 0x0 }
Source : <0x0000dba0> { _release_console_sem + 0x178 }
14 Target : <0x0000db96> { _release_console_sem + 0x16e }
Source : <0x0000db34> { _release_console_sem + 0x10c }
15 Target : <0x0000db2e> { _release_console_sem + 0x106 }
Source : <0x0000d36a> { ___call_console_drivers + 0x52 }
Stack from 007f7ce4:
007347d8 000060ea 0000004e 00000007 00000000 00000007 007339b4 00008bc8
007f7d24 00000007 00000000 00000007 007f6000 00067662 0000004e 0000004e
20515249 00003837 00028874 00191a14 030613e0 0000004e 030613e0 001e1400
0000ffff 00000000 0001a422 00067792 0002892c 00000000 0000004e 00000008
001e1400 001ea69c 00000020 001ee4f0 001ec0de 001ec0f8 001e1400 0018eaa0
001ed744 0018eaa8 001ee240 03e961c8 0018eaa8 001ee240 00000000 001ed744
Call Trace:
[<000a2cd6>] _driver_probe_device+0x7a/0x17c
[<00089996>] _kobject_uevent_env+0x30e/0x398
[<0012c37c>] _klist_next+0x1c/0x60
[<0012c396>] _klist_next+0x36/0x60
[<000a2fb2>] ___driver_attach+0x102/0x10c
[<000a218e>] _bus_for_each_dev+0x36/0x64
[<000a2eb0>] ___driver_attach+0x0/0x10c
[<000893f6>] _kobject_register+0x2e/0x44
[<000a2b8e>] _driver_attach+0x1a/0x20
[<000a24ba>] _bus_add_driver+0x4e/0x164
[<000a2eb0>] ___driver_attach+0x0/0x10c
[<000a24d0>] _bus_add_driver+0x64/0x164
[<0002582c>] _sys_init_module+0xc0/0x10c8
[<00033e9e>] _do_mmap_pgoff+0x662/0x740
[<0002576c>] _sys_init_module+0x0/0x10c8
[<00007f50>] _free_dma+0xa0/0xa4
[<00008000>] _dma_disable_irq+0x40/0x6c
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
net2272: PLX NET2272 USB Peripheral Controller
net2272: irq 78, mapped mem 20300000, chip rev 00ff
net2272: running in 16-bit, byte swap local bus mode
net2272: version: 2005 Sept 8
net2272: 2272 not found!
bfin-gpio: GPIO 7 wasn't requested!
Hardware Trace:
0 Target : <0x000047f8> { _dump_stack + 0x0 }
Source : <0x00006204> { _gpio_free + 0xd0 }
1 Target : <0x00006204> { _gpio_free + 0xd0 }
Source : <0x0000d832> { _printk + 0x16 }
2 Target : <0x0000d82e> { _printk + 0x12 }
Source : <0x0000d6e4> { _vprintk + 0x1b8 }
3 Target : <0x0000d6d8> { _vprintk + 0x1ac }
Source : <0x0000d6ca> { _vprintk + 0x19e }
4 Target : <0x0000d6c6> { _vprintk + 0x19a }
Source : <0x0000d514> { _wake_up_klogd + 0x24 }
5 Target : <0x0000d4f0> { _wake_up_klogd + 0x0 }
Source : <0x0000dc1c> { _release_console_sem + 0x1f4 }
6 Target : <0x0000dc0e> { _release_console_sem + 0x1e6 }
Source : <0x0000dc00> { _release_console_sem + 0x1d8 }
7 Target : <0x0000dbf6> { _release_console_sem + 0x1ce }
Source : <0x0000dbe8> { _release_console_sem + 0x1c0 }
8 Target : <0x0000dbc8> { _release_console_sem + 0x1a0 }
Source : <0x0000daae> { _release_console_sem + 0x86 }
9 Target : <0x0000da7e> { _release_console_sem + 0x56 }
Source : <0x0000dbaa> { _release_console_sem + 0x182 }
10 Target : <0x0000dba4> { _release_console_sem + 0x17c }
Source : <0x0000d3ea> { __call_console_drivers + 0x7e }
11 Target : <0x0000d3e4> { __call_console_drivers + 0x78 }
Source : <0x0000d3a6> { __call_console_drivers + 0x3a }
12 Target : <0x0000d396> { __call_console_drivers + 0x2a }
Source : <0x0000d386> { __call_console_drivers + 0x1a }
13 Target : <0x0000d36c> { __call_console_drivers + 0x0 }
Source : <0x0000dba0> { _release_console_sem + 0x178 }
14 Target : <0x0000db96> { _release_console_sem + 0x16e }
Source : <0x0000db34> { _release_console_sem + 0x10c }
15 Target : <0x0000db2e> { _release_console_sem + 0x106 }
Source : <0x0000d36a> { ___call_console_drivers + 0x52 }
Stack from 007f7d10:
00008124 00006208 00000000 00000000 000a03e8 00000007 00000007 00008c1c
030613e0 00000007 0000ffff 001e141c 00000004 00066cd6 00028708 001e1400
001e1400 000a0728 001e141c 001ee4f0 001e9774 001e1400 0018eaa8 ffffffed
0018eaa8 0018eaa8 001ee240 03e961c8 001ee4f0 001ec208 001e1400 0018eaa8
0000d81c 0018eaa8 001ed744 00000020 20300000 000000ff 00000054 000a2cd6
0018eaa8 001ee240 0073f11c 000000d8 001ee240 00089996 0012c37c 0012c396
Call Trace:
[<000a2fb2>] ___driver_attach+0x102/0x10c
[<000a218e>] _bus_for_each_dev+0x36/0x64
[<000a2eb0>] ___driver_attach+0x0/0x10c
[<000893f6>] _kobject_register+0x2e/0x44
[<000a2b8e>] _driver_attach+0x1a/0x20
[<000a24ba>] _bus_add_driver+0x4e/0x164
[<000a2eb0>] ___driver_attach+0x0/0x10c
[<000a24d0>] _bus_add_driver+0x64/0x164
[<0002582c>] _sys_init_module+0xc0/0x10c8
[<00033e9e>] _do_mmap_pgoff+0x662/0x740
[<0002576c>] _sys_init_module+0x0/0x10c8
[<00007f50>] _free_dma+0xa0/0xa4
[<00008000>] _dma_disable_irq+0x40/0x6c
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
[<00007f50>] _free_dma+0xa0/0xa4
net2272: unbind
insmod: cannot insert '/lib/modules//2.6.22.19-ADI-2008R1.5-svn5399/kernel/drivers/usb/gadget/g_ether.ko': No such device (-1): No such device
modprobe: failed to load module g_ether
What's wrong with my setting?
Please HELP!!!!!
Thanks,
Dominic
QuoteReplyEditDelete
2008-10-10 00:25:19 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Mike Frysinger (UNITED STATES)
Message: 63363
it's already telling you the error:
bfin-gpio: GPIO 7 is already reserved as Peripheral by bfin-t350mcqb !
QuoteReplyEditDelete
2008-10-13 00:08:16 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Bryan Wu (CHINA)
Message: 63505
Why do you wanna to use NET2722 on BF527 which includes the built-in usb otg controller (musb)?
-Bryan
QuoteReplyEditDelete
2008-10-14 10:27:21 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63658
I just followed the wiki procedure! Do you know how to make the Ethernet over USB work on the BF-527-Ezkit work?
Thanks,
Dominic
QuoteReplyEditDelete
2008-10-14 14:00:22 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Mike Frysinger (UNITED STATES)
Message: 63667
the wiki covers the process in general ... you're expected to select the right host controller for your hardware, so selecting a NET2722 when you dont actually have one doesnt make much sense
QuoteReplyEditDelete
2008-10-14 17:29:53 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63669
Finally, I make it work.
The NET2722 is the default setting from the menuconfig, and all other default settings.
To change the configuration setting, use "make menuconfig"
Here is what I have to set:
Vendor/Product selection---> (AnalogDevice) Vendor and (BF-527-EZKIT) Product.
Kernel/Library/Default selection --> [*] Customize kernel settings
<Exit> <Exit>
"Do you wish to save your new kernel configuration?" <Yes>
compiler continue to generate config file, and then the menu config re-appear.
Device Drivers --> [*] Network device support --> USB Network Adapters --> [M] Multi-purpose USB Networking Framework --> [M] Host for RNDIS and Active Sync --> [M] Simple USB Network Links (CDC Ethernet subset)
Select ALL the subitems i.e.
[*] Ali M5632 based 'USB 2.0 Data Link' cables
[*] AnchorChips 2720 based cables (Xircom PGUNET, ...)
[*] eTEK based host-to-host cables (Advance, Belkin, ...)
[*] Embedded ARM Linux links (iPaq, ...)
[*] Epson 2888 based firmware (DEVELOPMENT)
[*] KT Technology KC2190 based cables (InstaNet)
<Exit> <Exit>
Device Drivers --> USB support --> [*] Rely on OTG targeted Peripherals List
Device Drivers --> USB support --> USB Gadget support --> [M] support for USB Gadgets --> [M] Ethernet Gadget (with CDC Ethernet support) --> [*] RNDIS support (EXPERIMENTAL).
<Exit><Exit><Exit><Exit>
"Do you wish to save your new kernel configuration?" <Yes>
then issue command "make dep", then "make".
QuoteReplyEditDelete
2008-10-16 11:38:59 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63794
I follow the website wiki procedure http://docs.blackfin.uclinux.org/doku.php?do=show&id=ethernet_over_usb
Here is the booting message log
Kernel command line: g_ether.host_addr=00:01:9c:01:23:45 g_ether.dev_addr=00:01:9c:67:89:ac root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600 ip=10.13.38.162:10.13.38.95:10.13.38.1:255.255.255.0:bf527-ezkit:eth0:off
Unknown boot option `g_ether.host_addr=00:01:9c:01:23:45': ignoring
Unknown boot option `g_ether.dev_addr=00:01:9c:67:89:ac': ignoring
The above warning is found in file uclinux-dist/linux-2.6.x/init/main.c line 281 as listed below:
if (strchr(param, '.') && (!val || strchr(param, '.') < val)) {
printk(KERN_ERR "Unknown boot option `%s': ignoring\n", param);
return 0;
}
Based on the code, the param must NOT contain a dot (.), the parser has bugs, or the procedure in the wiki has something wrong.
Please help, Thanks,
Dominic
---
QuoteReplyEditDelete
2008-10-16 12:25:26 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63796
Here is another problem with the Command Line, if I add 2 more parameters g_ether.iManufacturer=$(eth_i_vendor) and g_ether.iProduct=$(eth_i_product), ther are more errors
Here is the booting message log
Kernel command line: g_ether.host_addr=00:01:9c:01:23:45 g_ether.dev_addr=00:01:9c:67:89:ac g_ether.iManufacturer="JDSU" g_ether.iProduct="OPM2" root=/dev/mtdblock0 rw earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600 ip=10.13.38.162:10.13.38.95:setenv bootargs g_ether.host_addr=$(eth_a_host) g_ether.dev_addr=$(eth_a_gadget) g_ether.iManufacturer=$(eth_i_vendor)
Unknown boot option `g_ether.host_addr=00:01:9c:01:23:45': ignoring
Unknown boot option `g_ether.dev_addr=00:01:9c:67:89:ac': ignoring
Unknown boot option `g_ether.iManufacturer=JDSU': ignoring
Unknown boot option `g_ether.iProduct=OPM2': ignoring
Unknown boot option `g_ether.host_addr=$(eth_a_host)': ignoring
Unknown boot option `g_ether.dev_addr=$(eth_a_gadget)': ignoring
Unknown boot option `g_ether.iManufacturer=$(eth_i_vendor)': ignoring
Please note that, the extra repeat bootargs is shown (green text) in the incompleted command line settings !!!!
Please help, Thanks,
Dominic
---
---
QuoteReplyEditDelete
2008-10-16 12:29:42 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Bryan Wu (CHINA)
Message: 63797
g_ether.host_addr=00:01:9c:01:23:45' is not allowed in the kernel boot command line.
And I don't find any information abou the g_ether in kernel boot command line from our wiki URL you posted here.
-Bryan
QuoteReplyEditDelete
2008-10-16 12:36:50 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63798
g_ether.host_addr=00:01:9c:01:23:45' is not allowed in the kernel boot command line.
And I don't find any information abou the g_ether in kernel boot command line from our wiki URL you posted here.
-Bryan
---
I follow the website wiki procedure http://docs.blackfin.uclinux.org/doku.php?do=show&id=ethernet_over_usb
Here is the contents:
# manufacturing assigns Ethernet addresses; company id is xx:xx:xx
setenv eth_a_host xx:xx:xx:01:23:45
setenv eth_a_gadget xx:xx:xx:67:89:ac
setenv eth_i_vendor "Great Stuff, LLC"
setenv eth_i_product "Our Cool Thing"
setenv eth_args g_ether.host_addr=\$(eth_a_host)
setenv eth_args $(eth_args) g_ether.dev_addr=\$(eth_a_gadget)
setenv eth_args $(eth_args) g_ether.iManufacturer=\$(eth_i_vendor)
setenv eth_args $(eth_args) g_ether.iProduct=\$(eth_i_product)
# you can assign USB vendor/product/version codes too...
setenv add_eth_args setenv bootargs $(eth_args) \$(bootargs)
...
setenv bootcmd run add_eth_args\;bootm
Regards,
Dominic On
QuoteReplyEditDelete
2008-10-16 13:21:44 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Bryan Wu (CHINA)
Message: 63800
Did you modprobe successfully as bellow?
modprobe g_ether host_addr=00:dc:c8:f7:75:05 dev_addr=00:dd:dc:eb:6d:f1
If it is OK, I guess you need to built-in the g_ether to kernel image. We did not test passing g_ether parameters from u-boot to kernel with boot command line. As Mike said, our wiki is a generic for development.
-Bryan
QuoteReplyEditDelete
2008-10-16 14:24:09 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63803
Did you modprobe successfully as bellow?
modprobe g_ether host_addr=00:dc:c8:f7:75:05 dev_addr=00:dd:dc:eb:6d:f1
If it is OK, I guess you need to built-in the g_ether to kernel image. We did not test passing g_ether parameters from u-boot to kernel with boot command line. As Mike said, our wiki is a generic for development.
-Bryan
---
Hi Bryan,
It modrprobe OK. How do I make it as a built-in the g_ether to kernel image? I'm a newbies to this project.
Thanks,
Dominic
QuoteReplyEditDelete
2008-10-17 21:26:53 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
zc liang (CHINA)
Message: 63879
Hi Dominic,
When you make menuconfig ,choose * not M , you can make it as a built-in the g_ether to kernel image.
I have tested bf527 usb g_ether_gadget driver and found that it is not stable.
Could you test again and tell me the result?
Thanks!
QuoteReplyEditDelete
2008-10-20 14:27:26 Re: Ethernet over USB (Gadget) not success for BF-527-Ezkit
Dominic On (CANADA)
Message: 63951
Thank you ZC LIANG,
it works. Now I don't have to type modprobe g_ether <parameters> anymore, and the <parameters> settings for Kernel Command Line also works ONLY when there is no warning "ignoring", so I can only set g_ether.hostaddr and g_ether.devaddr in the environment. If Kernel Command Line string is too long, then it crew-ups everything, Do you have the same problem like I have? This is a bug, and should be fixed.
Now I'm testing this usbnet, Will let you know.
Many thanks,
Dominic