Hi, All

I just download the orpsoc and orpsoc-cores and mkdir a directory name orpsoc
and try to build orpsoc simulation with
orpsoc sim generic

But there raise error by python script: orpsoc.coremanager.DependencyError: 'wb_utils'

Then I try to find the root cause, I found there is no RTL files in orpsoc-cores, just some description files.

My question is do I need to download the RTL files manually and put it somewhere?
Or orpsoc will do it for me?

You got a bit unlucky here. The "generic" system has been unmaintained for a while and hasn't kept up with the internal changes in orpsoc. I advice you to use or1200-generic instead, which does basically the same thing. (I also just removed the generic system to avoid further confusion)

The other thing to note is that I renamed the project from orpsoc to fusesoc just a few days ago, Since there is nothing in the python code that is OpenRISC-specific, I wanted a more generic name for the project. It's available at https://github.com/olofk/fusesoc or as a .tar.gz on the opencores FTP

So, to answer your question, yes, orpsoc (or rather fusesoc now) will sort out all the dependencies and download the needed files for you.

Hope this helps, and feel free to ask again if you get stuck somewhere. We are also available at #openrisc on irc.freenode.net

Best Regards,
Olof Kindgren

Thanks, I git the fusesoc now, and use command:
fusesoc sim or1200-generic

It seems simulation starts, since vvp takes up most of cpu time
But there is no log or anything else, except there is one message:
No ELF file specified

I am think if I miss something to tell the simulation env which ELF should it use.
But I do not know how

Great! That means that everything works. What happens is that you are running a simulation without a program, so the CPU is just racing freely around in memory.

The easiest way to get it to do something is to add --elf-load=/path/to/an/openrisc/elf to the argument list.

You might also want to add --vcd to generate a VCD file, or --timeout= to make it abort after a certain time

As a sidenote, you can see which parameters that each system accepts by adding a dummy parameter to the argument list e.g. fusesoc sim or1200-generic --dummyparam (Yes, I know that this isn't very user-friendly. I have tried to get it to list all parameters when you add --help, but haven't gotten that to work reliably yet)

Regards, Olof