ORPSoC has finally received an overhaul. Thanks for bearing with me while I was checking things in incrementally over the past few weeks.

The major changes are the following:

• The main design is a simple reference design focusing on being a testbench for OpenRISC processors
• Builds of ORPSoC for specific boards are now in their own mini-project, and it should be very easy to do your own board build and contribute to the project.
• Two working board build examples are included - one for the Actel FPGA-based ORSoC development board (ORDB1) and one for the Xilinx ML501 board.
• Improved project layout
• Documentation included with project

The main goal was to make it easy to develop your own board port and contribute it to the project. Another focus was to provide a basic system (reference design) to help develop and test OpenRISC processors. In the past there was a single design full of `defines and the like, but now builds full of peripherals have their own set of top level files and defines, leaving the reference design clean and simple.

The documentation is now in the project itself. The contents on the webpages in the OpenRISC project will be altered to indicate this. The only thing the in-project documentation lacks is the tool installation instructions but these will come. Feel free to contribute any sections you think are missing.

Getting ORPSoC and building the new documentation can be done by:

Your system might require the tools to build the PDF.

Under Ubuntu you will need to run:

Under CentOS you will need to run:

will you please help me with the following :


saurabh@bhaismachine:~/testing/orpsocv2/sim/run$ make rtl-test

### Compiling software ###

make[1]: Entering directory `/home/saurabh/testing/orpsocv2/sw/tests/or1200/sim'
../../../drivers/or1200/crt0.o:(.vectors+0x510): undefined reference to `timer_ticks'
../../../drivers/or1200/crt0.o: In function `_start':
(.text+0x128): undefined reference to `main'
../../../drivers/or1200/crt0.o: In function `_start':
(.text+0x134): undefined reference to `exit'
../../../drivers/or1200/crt0.o: In function `default_exception_handler':
(.text+0x1b0): undefined reference to `default_exception_handler_c'
collect2: ld returned 1 exit status
make[1]: *** [or1200-simple.elf] Error 1
make[1]: Leaving directory `/home/saurabh/testing/orpsocv2/sw/tests/or1200/sim'
make: *** [/home/saurabh/testing/orpsocv2/sim/run/../../sw/tests/or1200/sim/or1200-simple.vmem] Error 2
saurabh@bhaismachine:~/testing/orpsocv2/sim/run$

I have compiled the toolchain using MOS script and its version is 0.4.0.

The following test seems to be working though : make rtl-test TEST=or1200-basic

I should have mentioned this, you will need to use the script to build and install the version 1.0 release candidate toolchain.

http://opencores.org/openrisc,gnu_toolchain#1.0rc1install

When the version 1.0 toolchain is released there will be no more confusion about which toolchain to build.

Trying to install the toolchain v1.0rc. After the script is done building the toolchaing the make check command fails with following errors. Kindly help me.


/home/saurabh/testing/toolchain/crossbuild-build/or1ksim-0.5.0rc2/compile: 123: -DHAVE_CONFIG_H: not found
make[4]: *** [int.lo] Error 1
make[4]: Leaving directory `/home/saurabh/testing/toolchain/crossbuild-build/build-or1ksim/testsuite/test-code-or1k/support'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory `/home/saurabh/testing/toolchain/crossbuild-build/build-or1ksim/testsuite/test-code-or1k/support'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/saurabh/testing/toolchain/crossbuild-build/build-or1ksim/testsuite/test-code-or1k'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/home/saurabh/testing/toolchain/crossbuild-build/build-or1ksim/testsuite'
make: *** [check-recursive] Error 1
saurabh@bhaismachine:~/testing/toolchain/crossbuild-build/build-or1ksim$

Hi saurabhgupta

This looks like the configure of Or1ksim has not specified "--target=or32-elf". I am a little surprised that the script got this wrong.

Julius Baxter is the script expert, perhaps he could advise.

Jeremy

--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com

Hello Jeremy,

Thank you for the response. I don't know how to pass those options while running the script.

@Julius : Can you help me ?

regards,
Saurabh.

First thing is that this is a thread on the ORPSoC update. In future please either post in a thread better related to your issue, or if none exists start a new thread. Posting to unrelated threads makes it harder to follow the actual thread, and harder to track down your post in future as it's under an unrelated topic.


I get this error, too. Thanks for pointing it out - I will log it as a bug for now and deal with it when I can.

Dear Julius
I fixed a bug in the latest version orpsocv2, please update orpsocv2 package link:

1. add lowercase letter compile ruler. in Makefile.inc, you only give the ruler for "%.o: %.S" , but forget "%.o: %.s"
2. another fix, you can also change "crt0.s" to "crt0.S"
3. if you don't modify this, crt0.s won't be compiled with or32-elf-gcc, but "as" tool.
BTW: in the latest version, "or32-utils.h" has been changed into "or1200-utils.h", all the examples using "or32-utils.h" should be changed to "or1200-utils.h"

B.R.
Michael Yan

Hello Julius,

My apologies . I should have started a new post. But for now should I assume that I cannot install it on my system using the script and wait for the debugging ?

regards
Saurabh.

Hi Saurabh

Thanks for the feedback. Would you file the changes as bugs in the OpenRISC bug tracker. That way we have a chance of tracking them, and making sure they get fixed.

In my SVN tree, the file is already crt0.S. Are you using Cygwin, in which case this could be a problem with it being case insensitive (since it is based on the Windows file system)?

Eventually the ORPSoC tests should migrate to using the newlib library. Then there won't be any need for custom boot loader code.

ATB

Jeremy

--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com

Hello Jeremy,

Those changes are proposed by Michael Yan .

Saurabh.

That is strange. There is no assembly file with a .s (lowercase) extension - only the file sw/drivers/or1200/crt0.S which is an uppercase 'S'. What operating system are you on?
I think I've fixed all references to or32-utils.h to cpu-utils.h

Thanks for the feedback.

Hi Julius
"uart-echo.c" is using "or32-utils.h", I double check this.
and i download source code from win7 and copy to another PC (Fedora 11), "crt0.S" is changed into "crt0.S".

thanks
Michael Yan

Hi Julius
"uart-echo.c" is using "or32-utils.h", I double check this.
and i download source code from win7 and copy to another PC (Fedora 11), "crt0.S" is changed into "crt0.s". only this file. other .S file keep silent.

thanks
Michael Yan

Just now, I download the latest version, and found "\sw\tests\sim\uart-echo.c" has been deleted. I think Julius should have found this issue.

thanks