[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] error when compile

Hi Eric

I just check up your mhs file, there is one thing, i don't  really get how it works.
The mhs shows the I/D cache address from  0x20100000 to 0x201FFFFF and there is no device that mapped to 0x20100000 to 0x201FFFFF. This is why you getting pipeline stalled error.

Normally D/I cache should map to memory device. The only memory device is SRAM_256Kx32 and mapped to 0x80000000 to 0x0803FFFFF. Did you  manually SRAM_256Kx32's address in the mhs file? or this is generated by edk bsb?

I think it will be a good idea that you recreate your hardware platform and kernel image, both auto-config.in and mhs shows wrong mapping address for I/D cache.

Regards,

Jason


Eric Lynum wrote: 
Hi John thanks,

I haven't done the cvs update yet but I took the image files that were
created and I'm still having problems getting the kernel to boot.  I've
enclosed my auto-config file which I have used to make the kernel now and
now after running dow -data image5.bin 0x80000000 and con 0x80000000, I get
this error Microblaze pipeline stalled executing instruction at >> PC:
0x80000000c. Try resetting the processor to continue.  I tried to follow
Emile's document on changing the testmem.c file and changing the microblaze
version from 4 to 3.00. Should I do that or is that unneeded.


  

-----Original Message-----
From: owner-microblaze-uclinux@itee.uq.edu.au
[mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of John Williams
Sent: Saturday, October 08, 2005 11:41 PM
To: microblaze-uclinux@itee.uq.edu.au
Subject: Re: [microblaze-uclinux] error when compile

Hi Eric,



Eric Lynum wrote:
  
I have no idea why this happened but I commented out in mmap.c under the
mmnomu directory this section calling for a romptr and I was able to build
the image.bin and elf files.  Any ideas on what this code was doing?
    

OK, so this one's beyond your control :)  There's been some work going
on in the MM part of the CVS lately, looks like microblaze got affected.

Change to uClinux-2.4.x/arch/microblaze/platforms and do

$ cvs update Rules.make

That will pick up a one-liner fix that I just committed to CVS, and you
should be back in business.

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/