|
Message
From: Flavio M. De Paula<depaulfm@c...>
Date: Tue Jul 22 05:31:06 CEST 2008
Subject: [openrisc] What tag version of the RTL should I use that matches
the or1k-sim?
Hi Jeremy,I assumed you're original architect/developer of or1ksim. OK, in this
case I will also share whatever I find.
You can download the linux image and the sim.cfg file used from:
www.cs.ubc.ca/~depaulfm/or1ksim_files.tar.bz2
Please, let me know if you have any issue accessing them.
The command I used was pretty straight forward:
or32-uclinux-sim -f sim.cfg vmlinux
> Your description of FLASH is correct - there is no address translation
> on load. However I've never used logging, so I don't know if it works.
> Can you single step the simulator, so you can see the successive
> changes? That will show immediately if the PC is changing to 0xf0000118.
I think the cpu is outputting 0xf0000118. As far as I understand now,
or1ksim is really tied to the 'mc' module (memory controller).
Unless, there is another config option that I need to set up and that I'm
not aware of.
If I disable 'mc' nothing happens -- the executed.log outputs
fetched addresses 0x100 and 0x104 in an endless loop fashion. I've even
tried simple code to test this argument.
Please, let me know if this is really true or just some misunderstanding
in my part.
> I'm not aware of any default initialization of either MMU. Linux boot up
> has code which sets it up for Linux, so I guess that is what you will
> need to do.
Rich Daddio suggested me to take a look at the *.ld files. That's the
place where we can set up the final addresses for the relocatable code. But I'm
a little bit concerned that it won't matter given that it seems or1ksim
needs 'mc' always enabled. I'll see how far I can go...
> I've fixed some bugs and written up what I did, so others can learn from
> it. I'm very happy to share what I've learned about Or1ksim, but there's
> still a great deal about it which I do not know.
Let me know if you want me to try something for you.
Thanks for all the help.
|
 |
Browse
