From: Scott Wood <scottwood@freescale.com>
To: Dan.Geer@faa.gov
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: BSE-IP
Date: Mon, 01 Feb 2010 12:24:13 -0600 [thread overview]
Message-ID: <4B671C4D.5070806@freescale.com> (raw)
In-Reply-To: <OF7C180968.43598D84-ON852576BD.006286D6-852576BD.0063AC38@faa.gov>
Dan.Geer@faa.gov wrote:
> I'm hoping someone can offer some advice on this:
>
> I'm working with an embedded platform that does not pass anything from
> firmware. I'm just trying to get some activity out the serial console at
> this stage. simpleImage.bseip compiled with the following bseip.dts seems
> to freeze before anything is written to the console. I'm assuming the
> standard 8xx code will pickup this device tree, and work from there. Is
> this correct? Shouldn't I see some output?
Has your firmware already set up the serial port? cpm-serial doesn't make
assumptions about specific addresses, but it does assume that the BRG, pins,
etc. have been set up for the serial port to work.
If this isn't the case, you'll need to do it from a custom bootwrapper platform
file.
> d-cache-line-size = <8>; // 8 bytes
> per line
> i-cache-line-size = <8>; // 8 bytes
> per line
Shouldn't this be 16 bytes?
> soc@ff000000 {
Is this the correct IMMR address for your firmware?
-Scott
next prev parent reply other threads:[~2010-02-01 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 18:08 BSE-IP Dan.Geer
2010-02-01 18:24 ` Scott Wood [this message]
2010-02-01 18:59 ` BSE-IP Dan.Geer
2010-02-01 19:06 ` BSE-IP Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2010-01-26 20:30 BSE-IP Dan.Geer
2010-01-26 21:03 ` BSE-IP Scott Wood
2010-01-26 22:04 ` BSE-IP Dan.Geer
2010-01-26 22:17 ` BSE-IP Scott Wood
2010-01-26 23:28 ` BSE-IP Dan.Geer
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=4B671C4D.5070806@freescale.com \
--to=scottwood@freescale.com \
--cc=Dan.Geer@faa.gov \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).