|
Message
From: Jeremy Bennett<jeremy.bennett@e...>
Date: Fri Sep 19 09:13:37 CEST 2008
Subject: [openrisc] Problem booting linux-2.6.19
On Thu, 2008-09-18 at 17:30 +0000, Γιώργος Γράσσος wrote:> I use ubuntu ultimate 1.4 and i have build the oprnrisc toolchain
> using the sript MOF_ORSOC_TCHN_v3b.sh from opencores.org . I had some
> problems but i've read previous e-mails from the list and where
> solved . But i have now the following error message , maybe the answer
> is easy but i just started to deal with this project. i need to work
> with that for my univercity.
>
> Copying Linux... Ok, booting the kernel.
> ****************** counters reset ******************
> cycles 145614826, insn #10008203
> ****************** counters reset ******************
<Lots of Linux boot-up snipped>
> Freeing unused kernel memory: 104k freed
> init started: BusyBox v1.7.5 (2008-09-18 17:58:46 EEST)
> starting pid 22, tty '': '/etc/init.d/rcS'
>
> Please press Enter to activate this console.
>
>
> starting pid 24, tty '': '/bin/sh'
>
>
> BusyBox v1.7.5 (2008-09-18 17:58:46 EEST) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> /bin/sh: can't access tty; job control turned off
I think these are just the messages from the terminal (window) where you
are running Or1ksim. What you are missing is the terminal (window)
connected to the Or1ksim UART interface.
The UART connects to a *separate* console. Look for the "section uart"
part of sim.cfg. In there you will see a line, something like:
channel="tcp:10084"
This means the UART interface is on port 10084. In a separate terminal
use:
telnet localhost 10084
And you will be connected to the UART. You'll see the same message about
BusyBox, and when you hit return will get a the "#" prompt (actually
you'll get two, due to a known bug when using telnet).
If you prefer, you can change the "section uart" entry to read:
channel="xterm:"
Or1ksim will then start up a separate xterm connected to the UART.
Personally I always uses this arrangement, since it is simpler.
The message about "/bin/sh: can't access tty; job control turned off" is
a known bug. This message always appears but can be ignored.
Or1ksim suffers from a lack of documentation to make these things clear.
I'm working on a user guide, which I hope will be released shortly.
Input from others to improve this will be much appreciated.
HTH,
Jeremy
--
Tel: +44 (1202) 416955
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@e...
Web: www.embecosm.com
|
 |
Browse
