Re: [microblaze-uclinux] uclinux-auto ETHERNET?

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Edmond,

Edmond Coté wrote:

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

Thanks for your encouraging words.  The whole motivation of auto-config 
was to stop people wasting weeks (literally, in some cases) getting the 
board booting, and rather concentrate on the intersting bits.

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

That's exactly what it is.  Unfortuantely, xmd's ELF reader/loader 
ignores the .romfs section.  Search this list and uclinux-dev for 
numerous discussions over whether it's a bug or feature of elf et al.

The way I do it is

$ dow -data image.bin 0x80000000
$ con 0x80000000

or whatever start address is appropriate.

Regards,

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/