For the PHY problem, I do not believe that
it is a problem with the cable not being connected. If it was, the Xilinx EMAC
driver would report something like “No link”.
This sounds more like a connection problem
to the PHY chip. I am unfamiliar with this eval board, but you should check that
the FPGA pins are properly connected to the PHY chip, especially making sure
that these pins are not floating. We had a similar problem with a Spartan 3
design last fall.
Steve
From: Ujwal
[mailto:ujwal.mailinglist@xxxxxxxxx]
Sent: Wednesday, May 31, 2006 1:30
AM
To:
microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux]
Ethernet Interface on the v2mb1000 eval board
this error results wn u
have not connected ur
ethernet/lan cable to the board.. or if there is some prob with the lan cable
On 5/31/06, subash
bohra <subash_bohra@xxxxxxxxx>
wrote:
I am trying to port uClinux onto v2mb1000 _eval board.So far I have
been able to succesfully compile and bring the board up. The output looks like
this:
J-Boot Menu
1. Execute Flash image
2. Execute RAM image
3. Erase Flash
4. Write image into Flash
5. Set kernel cmdline
Make your choice>2
Linux version 2.4.32-uc0 ( subash@localhost)
(gcc version 3.4.1 ( Xilinx EDK 8.1 Build EDK_I.17 090206 )) #14 Mon May 29
16:09:33 PDT 2006
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
CPU: MICROBLAZE
Kernel command line:
Console: xmbserial on UARTLite
Calibrating delay loop... 33.07 BogoMIPS
Memory: 32MB = 32MB total
Memory: 30260KB available (1082K code, 1062K data, 48K init)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea
University Computer
Society NET3.039
Initializing RT netlink socket
Microblaze UARTlite serial driver version 1.00
ttyS0 at 0xffff2000 (irq = 1) is a Microblaze UARTlite
Starting kswapd
xgpio #0 at 0xFFFF5000 mapped to 0xFFFF5000
Xilinx GPIO registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
eth0: using fifo mode.
eth0: No PHY detected. Assuming a
PHY at address 0.
eth0: Xilinx EMAC #0 at 0xC0000000
mapped to 0xC0000000, irq=2
eth0: id 2.0h; block id 7, type 1
MicroBlaze auto-config flash probe(0xff000000,8388608,2): 800000 at
ff000000
Flash: Found an alias at 0x200000 for the chip at 0x0
Flash: Found an alias at 0x400000 for the chip at 0x0
Flash: Found an alias at 0x600000 for the chip at 0x0
Amd/Fujitsu Extended Query Table v1.0 at 0x0041
Flash: JEDEC Device ID is 0xC0. Assuming broken CFI table.
Flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling fast programming due to code brokenness.
Creating 8 MTD partitions on "Flash":
0x00000000-0x00004000 : "Bootloader"
0x00004000-0x00008000 : "Bootargs"
0x00008000-0x0000c000 : "MAC"
0x00010000-0x00020000 : "Config"
0x0000c000-0x00010000 : "Spare"
0x00100000-0x00400000 :
"Image"
mtd: partition "Image"
extends beyond the end of device "Flash" -- size truncated to
0x100000
0x00400000-0x00800000 :
"JFFS2"
mtd: partition "JFFS2" is out
of reach -- disabled
0x00000000-0x00200000 :
"Flash"
MicroBlaze auto-config ram probe(0x801470a0,860160,4): d2000 at
801470a0
Creating 1 MTD partitions on "RAM":
0x00000000-0x000d2000 : "Romfs"
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 48K
Mounting proc:
Mounting var:
Populating /var:
Running local start scripts.
Mounting /etc/config:
Populating /etc/config:
flatfsd: invalid header magic
flatfsd: Nonexistent or bad flatfs (-183), creating new one...
flatfsd: Wrote 288 bytes to flash in 63 seconds
flatfsd: Created 4 configuration files (183 bytes)
Setting hostname:
Setting up interface lo:
Starting DHCP client:
Starting thttpd:
eth0: Link carrier lost.
uclinux-auto login:
Can someone help me with the following:
Why the eth0 interface stays down. Is there some compile option I am
missing.
Should I turn on the ethernet controller option in Kernel Settings. If
yes what type
of controller should I select. The board uses a bcm5641 device.
Why the Image MTD partition is less than the flash partition.
your help is appreciated.
|