hi,all

from the docs of openrisc project, i find this project has about 3 different simulation schemes.

1. or1ksim, architecture simulator
2. orpsoc, make rtl-test, it is rtl and software co-simulation
3. orpsoc, make vlt-test, it is verilator generated C model simulation

am i right on this?

if i am wrong, please correct me, if i am right, i have several questions:

1: architecture simulation means that it can mimic the hardware to make program behave as if it is running on hardware. if my code print "hello world", then the or1ksim can show me the string, right?

2: how to use or1ksim. i have installed or1ksim, and i get the user-guide, but i still feel it's far from enough to make me know how to use it.

now, if i wrote a piece of code, how can i use or1ksim to verify that it is right? what the steps.

3: in orpsoc project, i can run: make rtl-test TEST=uart-simple but i find the printf function is from a seperate file, rather than from a libary. several days ago, i have compiled newlibc, and i can use printf from the newlibc, and even malloc function, but it can not be used in the project here. then my questions is: how to use newlibc in orpsoc enviroment.

4: make rtl-test co-simulation is too slow for a actual program, right? it takes about 2 mins to display "hello" in uart-simple code.

5: make vlt-test c-model simulation, because i have problem running make prepare-vlt, so i have not successfully ran this yet, but i want to ask, how fast it is compared to co-simulation, how to guarantee the generated model is correct, verilator can generate C model from any given RTL?

thank you jeremybennett and olof :)

i can run or32-elf-sim now as you told me, it feels so good when see myprog give me a nice "Hello world!" :)

and i also tried the debug function, it can work well on my hello world program.

then i come to several new questions.

1: i find that in gdb6.8 directory, there is a user guide about how to use or1k specific gdb,(or1k.pdf after make pdf), but gdb7.2 no longer has that file. maybe it is not changed much between these 2 versions, but i think it's better to keep it. further more, i do my debug test according to this file, and i find it is quite useful, except 2 points:

a): "gdb_enabled and server_port" in section debug in sim.cfg file is no longer that name, it has changed to "rsp_enabled and rsp_port"

b):the "hello world"example in the file can not be compiled successfuly if directly copy those code into a file, but reporting "NOP_EXIT NOP_PUTC" undefined, so there must be some other file missing. so maybe it's better to complete this example or replace it.

2: or32-elf-gdb must be used together with or1ksim? and also must first start a RSP? it can not be used standalone right?

3: when debug, firstly must modify sim.cfg to enable debug section, but if i do not use debug, then is this sim.cfg needed? in my hello world program, i donnot even specify the uart port, i just use printf funciton, then, do i need to keep section uart in sim.cfg? or each section in the cfg file corresponds to actual hardware module, if no hardware then it can be omitted, right.

4: when using or32-elf-sim run elf or vmem files generated when make rtl-test in orpsoc project, i find it always halt there, no output for a long time. after ctrl+c, it show a promt like this: (sim),means it also goes to interactive mode, but why executive file generated by orpsoc can not be run by or32-elf-sim. orpsoc make rtl-test can also give expected result, what the method it used? not or1ksim?

5: or32-elf-sim interactive mode, it can set break, can run 1 or N instructions, but i can not find a "continue" which run until it meets a breakpoint. so it may be inconvinent if if must one instruction by one or calculte how many instructions are between 2 break points? or i have missed something?

thank you,jeremybennett

the "hello world" program i said is in the or1k.pdf file which is generated after make pdf. for my case, i compiled source code in a directory bld_gdb68, then make pdf, then in ./gdb/doc there is or1k.pdf

in orpsoc project, i can generate elf files too, using make uart-simple.elf for example. but this elf file can not be run by or1ksim. could it be because of the different libraries used? e.g, printf function.