|
Message
From: Jeremy Bennett<jeremy.bennett@e...>
Date: Mon Aug 18 09:23:09 CEST 2008
Subject: [openrisc] Re: Running TLM 2.0 example in Cygwin
On Mon, 2008-08-18 at 00:03 +0430, Alireza Haghdoost wrote:
> Dear Mr.Bennett
>
> Thanks again for your excellent case study on TLM 2.0, I am trying to
> run it in cygwin, but in the procedure of application note 2 I have
> encountered to the problem which described in the attached file, I
> will appreciate you if you can help me to solve this problem.
Hi Alireza,
I've moved this question to the TLM forum and the OpenRISC forum, in
case anyone else can share ideas (the issue covers both SystemC TLM and
building the model for OpenRISC).
The failure is not in the SystemC, but in cross compiling the Linux
kernel for the target architecture. The command:
make menuconfig ARCH=or32 CROSS_COMPILE=/opt/or32/bin/or32-uclinux
starts the Linux configuration tool. The error messages are about
missing symbols, because some library routines needed by the Linux
configuration tool (which is compiled native, i.e. on Cygwin) are
missing.
It can be done. If you put "linux kernel build under cygwin" into
Google, you'll see lots of mailing list discussion about how to build
Linux kernels under Cygwin. If you work out how to do it for the case
study, I'll be happy to add the instructions to the application note.
The good news is you do not need this for most of the TLM 2.0 case
study. It's only for the last example bringing up the Linux kernel. All
the other examples need just the OpenRISC architectural simulator,
Or1ksim and binutils/GCC from the tool chain. They don't even need the
uClibc library, since they use their own tiny bootloader (start.s).
HTH,
Jeremy
--
Tel: +44 (1202) 416955
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@e...
Web: www.embecosm.com
|
 |
Browse
