linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "André Schwarz" <Andre.Schwarz@matrix-vision.de>
Cc: linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: Re: simple MPC5200B system
Date: Sun, 16 Mar 2008 14:01:24 -0600	[thread overview]
Message-ID: <fa686aa40803161301r1685f2cale75d67b8a203cca3@mail.gmail.com> (raw)
In-Reply-To: <47DD71D0.2010203@matrix-vision.de>

On Sun, Mar 16, 2008 at 1:15 PM, Andr=E9 Schwarz
<Andre.Schwarz@matrix-vision.de> wrote:
> All,
>
>  I'm quite stuck in getting our MPC5200B based systems work on 2.6.24+
>  ... maybe someone could give me some hints.
>  Up to now the systems have been running on 2.6.19 without any problems.
>
>  This is what I've done so far :
>
>  - get a recent system with 2.6.19 running and keep the toolchain (gcc
>  4.0) including RFS uImage.
>  - latest bootloader (u-boot 1.3.2) is running fine with dtb support.
>  - Kernel and RFS images are available via bootp/tftp
>  - device tree blob seems ok, i.e. u-boot can display the blob and fill
>  in all clocks correctly.
>  - Kernel gets called with Kernel, RFS and dtb on suitable adresses
>  (0x100000, 0x600000, 0x5F0000).
>  - nothing more happens. It looks like the console isn't working properly
>  - maybe worse ...

Can you either halt the processor or reset the board and access memory
after this point?  You should see if you can access __log_buf (Look in
System.map for the address and subtract 0xc0000000 to get the physical
address).   __log_buf should give you clues about how far booting
progresses.

>  The kernel has been build using the "MPC5200 simple" setup. I've added
>  our board identifier "mv,mvbluecougar" to the list of supported boards
>  in the "mpc52xx_simple.c" file. This identifier is used in the dtb as
>  well of course. This should be enough along with a valid device tree
>  blob, isn't it ? Did I miss anything already ?

Yes, this should be enough (on a side note; it should probably be
"matrix-vision,bluecougar" unless of''mv' is your company's stock
ticker symbol).

>
>  As far as I did understand by reading the docs it should be possible
>  running a general MPC52xx kernel with a custom dtb ? Is this correct ?

That is correct.

>  The dts file has already been reduced to a minimum, i.e. only the cpu,
>  pic, xlb and a few nodes like psc1 and psc2 are present. No bestcomm,
>  pci, ata or "advanced" features like mtd partitions. All I want to get
>  working is the serial console on "/dev/ttyPSC0".

Cheers,
g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-03-16 20:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 19:15 simple MPC5200B system André Schwarz
2008-03-16 20:01 ` Grant Likely [this message]
2008-03-17  9:35   ` André Schwarz
2008-03-18  8:49   ` Andre Schwarz
2008-03-18 10:34     ` Andre Schwarz
2008-03-18 14:31       ` Grant Likely
2008-03-18 15:14         ` Andre Schwarz
2008-03-18 16:21           ` Grant Likely
2008-03-18 16:44             ` Andre Schwarz
2008-03-20  0:14     ` Wolfgang Denk
2008-03-20  0:21       ` David Gibson
2008-03-20  7:48         ` André Schwarz
2008-03-20  8:20           ` David Gibson
2008-03-20  9:11             ` André Schwarz
2008-03-20  9:29             ` Stefan Roese

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=fa686aa40803161301r1685f2cale75d67b8a203cca3@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=Andre.Schwarz@matrix-vision.de \
    --cc=linuxppc-dev@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).