[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] uclinux-auto ETHERNET?
On Fri, 25 Mar 2005 18:04:47 -0800, David Banas <dbanas@nuhorizons.com> wrote:
> What you want to do is download through the MDM, via an FSL connection to
> the MicroBlaze. In order to do this, you need to add (if you don't already
> have) a FSL bus to your design, and make the MicroBlaze a slave on it and
> the MDM the master. Make sure you override the "C_FSL_LINKS" parameter of
> the MicroBlaze instance to "1" and the "C_WRITE_FSL_PORTS" parameter of the
> debug module to "1" also.
>
> You'll know you've got things set up right if, when you invoke XMD, you see
> the following line in the initialization output:
>
> MBsfsl(0)-MDMmfsl(0) Connected............Yes
Gotcha! Need to keep climbing that learning curve (only official got
this started less than 24hr ago).
John, uclinux-auto is a brilliant tool. I was able to take a basic
system generted from an .xbd file, add a timer, hook it up to the
interrupt handler; to then compile and upload a kernel (doesn't work
yet.. see below)
I must confess though, I am building this system from the ground up,
instead of modifying the provided "default" system (the one which uses
DDR memory). Since I have no experience with the EDK it's probably the
best way for me to go. (Although I must say, I have some good
experience with ELF, Linux, Wishbone, HDL, etc.)
Anyhow, in the kernel config, I only removed the support for GPIO,
ETHERNET and SYSTEMACE , everything else was left alone. I tried twice
and got the attached result:
<...>
MBVanilla flash probe(0xff000000,8388608,4): 800000 at ff000000
CFI: Found no Flash device at location zero
Search for id:(00 00) interleave(2) type(2)
<...>
Search for id:(00 00) interleave(4) type(1)
JEDEC: Found no Flash device at location zero
MBVanilla ram probe(0x818d28fc,-1131278336,4): bc921000 at 818d28fc
Creating 1 MTD partitions on "RAM":
0x00000000-0xbc921000 : "Romfs"
Kernel panic: VFS: Unable to mount root fs on 1f:00
Could this have to do with having downloaded image.elf, instead of
image.bin? (re: Troubleshooting FAQ), if so, how do you locate the
kernel link address?.. Would this be the start symbol when doing
mb-objdump -d image.elf? (I'm trying it now, but it's a 15min
process... till I get that fixed)
Ed
Linux version 2.4.29-uc0 (coen490@scratchy) (gcc ve
Build EDK_Gmm.12.2) #5 Fri Mar 25 22:46:35 EST 2005
On node 0 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
CPU: MICROBLAZE
Console: xmbserial on UARTLite
Kernel command line:
Calibrating delay loop... 3.95 BogoMIPS
Memory: 8MB = 8MB total
Memory: 7252KB available (642K code, 199K data, 36K init)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 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: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Microblaze UARTlite serial driver version 1.00
ttyS0 at 0x81000300 (irq = 0) is a Microblaze UARTlite
Starting kswapd
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
MBVanilla flash probe(0xff000000,8388608,4): 800000 at ff000000
CFI: Found no Flash device at location zero
Search for id:(00 00) interleave(2) type(2)
Search for id:(00 00) interleave(2) type(2)
Search for id:(00 00) interleave(2) type(2)
Search for id:(00 00) interleave(2) type(1)
Search for id:(00 00) interleave(2) type(1)
Search for id:(00 00) interleave(2) type(1)
Search for id:(00 00) interleave(4) type(2)
Search for id:(00 00) interleave(4) type(2)
Search for id:(00 00) interleave(4) type(2)
Search for id:(00 00) interleave(4) type(1)
Search for id:(00 00) interleave(4) type(1)
Search for id:(00 00) interleave(4) type(1)
JEDEC: Found no Flash device at location zero
MBVanilla ram probe(0x818d28fc,-1131278336,4): bc921000 at 818d28fc
Creating 1 MTD partitions on "RAM":
0x00000000-0xbc921000 : "Romfs"
Kernel panic: VFS: Unable to mount root fs on 1f:00