From: Daniel Mack <daniel@caiaq.de>
To: buildroot@busybox.net
Subject: [Buildroot] Problems connecting to AT91SAM9260
Date: Thu, 3 Dec 2009 17:03:19 +0100 [thread overview]
Message-ID: <20091203160319.GF29442@buzzloop.caiaq.de> (raw)
In-Reply-To: <20091203154314.237790@gmx.net>
On Thu, Dec 03, 2009 at 04:43:14PM +0100, Jens Kleinhans wrote:
> I want to connect to the ARM board mentioned in the subject with
> minicom.
> So I connected the board with the RS232 interface and the USB_D
> interface to my host PC and configured minicom with the following
> parameters:
> 115200, 8bits, 1stop, no parity, no flow
> Then I powered up the board. It started sending some datas to minicom
> about the boot process. Then it ended up with the lines:
> Uncompressing Linux...RomBOOT
> >RomBOOT
>
> I don't get the chance to communicate with the board. How can I
> communicate with minicom?
Your problem is not related to minicom. It's not related to buildroot
either. Most probably, your kernel simply doesn't boot, and there's a
huge load of possible reasons for that. You should really follow the
instructions found at the place or from the people you got the patchset
from. Or in last instance, go to linux-arm-kernel and ask for help
there. But I doubt that there will be much ambition to support such an
old version.
Again, this is the wrong list for that. And please don't cross-post
again. Everyone answering to your mails will get a bounce from rtai.org.
Daniel
> --
> Sarah Kreuz, die DSDS-Siegerin der Herzen, mit ihrem eindrucksvollen
> Deb?talbum "One Moment in Time". http://portal.gmx.net/de/go/musik
OMFG.
prev parent reply other threads:[~2009-12-03 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 15:43 [Buildroot] Problems connecting to AT91SAM9260 Jens Kleinhans
2009-12-03 15:49 ` Peter Korsgaard
2009-12-03 15:53 ` Jonathan dumaresq
2009-12-03 16:03 ` Daniel Mack [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091203160319.GF29442@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox