[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] ML401 update
John,
thanks for the reply (sorry for all the newbie questions).
- I did try the specific Intel Flash option and that is why I am writing; it did not work. Can I look at the code to see what the deal is?
- FSL Link: Are you using the download commands in Linux not windows? I sent this problem to Xilinx and they could not get it to work iether (FSL link). They told me it was broken for V4 and could not get it to work. They also said they do not know when it will be fixed....
-The problem is that Linux is not reconizing the PHY... Sometimes. Below it did. However when I plug in a network cable, it crashes. Here is a printout of my boot: That is why I was wondering about the system setup. What is a basic system setup that can be used with net woeking to teest this. with your options, I assume it is supposed to pull an IP address?
If I boot with the cable plugged it, it dies. (Cannot type). If I have the interrupt for the eithernet in above the uart, it will die on boot... It seems to see the carrier however.
n node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
CPU: MICROBLAZE
Console: xmbserial on UARTLite
Kernel command
line:
Calibrating delay loop... 49.66 BogoMIPS
Memory: 32MB = 32MB total
Memory: 30524KB available (1121K code, 759K d
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
ttyS1 at 0xffff4000 (irq = 2) 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: Xilinx EMAC #0 at 0xC0000000 mapped to 0xC0000000,
irq=3
uclinux[mtd]: RAM probe address=0x80153654 size=0x83000
uclinux[mtd]: root filesystem
index=0
MBVanilla flash probe(0xff000000,8388608,4): 800000 at ff000000
CFI: Found no Flash device at loc
Search for id:(17 fffc) interleave(2)
type(2)
Search for id:(17 fffc) interleave(2) type(2)
Search for id:(17 fffc) interleave(2) type(2)
Search for id:(17 17) interleave(2)
type(1)
Search for id:(17 17) interleave(2) type(1)
Search for id:(17 17) interleave(2) type(1)
Search for id:(17 ffc7) interleave(4)
type(2)
Search for id:(17 ffc7) interleave(4) type(2)
Search for id:(17 ffc7) interleave(4) type(2)
Search for id:(17 fc) interleave(4)
type(1)
Search for id:(17 fc) interleave(4) type(1)
Search for id:(17 fc) interleave(4) type(1)
JEDEC: Found no Flash device at location
zero
MBVanilla ram probe(0x80153654,536576,4): 83000 at 80153654
Creating 1 MTD partitions on "RAM":
0x00000000-0x00083000 :
"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: Has!
h tables
configured (established 2048 bind 2048)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (romfs filesystem)
readonly.
Freeing init memory: 44K
Shell invoked to run file: /etc/rc
Command: hostname microblaze1
Command: ifconfig lo
127.0.0.1
Command: ifconfig eth0 192.168.1.1
eth0: Could not read PHY control register; error 1003
Command: /bin/expand /etc/ramfs.img
/dev/ram0
Command: /bin/expand /etc/ramfs.img /dev/ram1
Command: mount -t proc proc /proc
Command: mount -t ext2 /dev/ram0
/var
Command: mount -t ext2 /dev/ram1 /usr
eth0: Could not read PHY control register; error 1003
eth0: Terminating link monitoring.
Command: portmap &
[17]
Command: mkdir /var/tmp
Command: mkdir /var/log
Command: mkdir /var/run
Command: mkdir /var/lock
Command: cat /etc/motd
Welcome to
____ _
_
_ _ / ___| (_)_ __ _ _ _ _
| | | | | | | | '_ \| | | < \/ >
| |_| | |___| | | | | | |_| |> <
| __,_|\____|_|_|_| |_|\__,_/_/\_>
|_)
on Microblaze.
Execution Finished, Exiting
Sash command shell (version 1.1.1)
/>
John Williams <jwilliams@itee.uq.edu.au> wrote:
Hi Greg,
Greg Miller wrote:
> what was the thing that made the FSL link work? I am having trouble with
> mine...
I had the C_EXT_RESET_HIGH set to zero - it should be just the default
value.
> Also, did anyone read me last e-mail about the Ethernet access? I need
> to know what can and cannot work. I am not afraid to read, I just need
> some guidance for a newbie on this issue. Specifically I am looking into
> what I can do and how I can set it up. For instance, should the DHCP
> experimental driver work?
I'm not sure about this experimental DHCP you mention - I just use the
"dhcpcd" application that's part of the dist. Note you have to enable
the packet socket interface in the kernel networking confirugation menu
as well.
> Also, Linux is not seeing the Intel Flash properly. It !
is not
> recognized. I specifically specified Intel strata Flash. Am I missing
> something obvious? I know these are newbie questions, I just need to be
> pointed in the right direction.
In the main kernel config menu, under MTD, you need to explicitly enable
support for the Intel devices. It shuold work OK after that.
I'm working on an MTD mapping driver for the ML401 - it'
s in CVS now, but it still needs some work. Should be finished early
next week.
John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/