linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Leonardo Pereira Santos" <lsantos@pd3.com.br>
To: "James Don" <JDon@spacebridge.com>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re:  kernel 2.4 smc1 problems ... advice please ...
Date: Mon, 16 Dec 2002 10:28:57 -0200	[thread overview]
Message-ID: <003101c2a4fe$b4cf05f0$1764a8c0@leonardo> (raw)
In-Reply-To: DB0585C9F6F9D411BE8F00D0B7896A4CC05F11@SNCMAIL


    Well we managed to make a MPC850 FADS work. But we haven't got any
problems with the console, but with the ethernet. My guess is that you have
a kernel configuration problem, problably at the MPC8xx CPM Options. There,
the only two selected options are the very first one, CPM SCC Ethernet, and
the the second one, SCC2 used of the ethernet. All the other options aren't
selected. After that, if you find out that the kernel is not initializing
the ethernet too (it'll complain that it can't mount the root FS if you're
using NFS), then you'll vahe to copy some definitions for the EPLD's
registers for the FADS boards. The kernel's one are outdated, I think. But
PPCBoot, as you already noticed, are correct, so edit asm-ppc/fads.h our
platforms/fads.h and change the BCSRs definitions found that for the
PPCBoot's ones. That solved our problems.
Cheers.
----- Original Message -----
From: "James Don" <JDon@spacebridge.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Saturday, December 14, 2002 5:37 PM
Subject: kernel 2.4 smc1 problems ... advice please ...


>
> Hello,
>
> I am cuurently trying to boot up the linux kernel using ppcboot 1.16 and
the
> 2.4 kernel with only smc1 uart support as a start on an MPC860 FADS
derived
> board.
>
> So far I have:
> - ppcboot running great
> - tftpboot graps my kernel puts in RAM
> - bootm starts my kernel ... BUT no serial activity ...
>
> I am using the vision ICE currently to debug the kernel start up but it
has
> a problem stepping through the 'rfi' etc when memory protection is
running.
>
> So currently I can only really peek at the PC and see that I am indeed
> excuting kernel code.
>
> I believe my memory map is ok:
> MEM        VIRT        PHYS
> RAM        0xc0000000  0x00000000
> IMMR       0xff000000  0xff000000
>
> My pc seems to get beyond start_kernel ... but I don't see the kernel
banner
> printed or anything ... with an ocillioscope I don't see any serial
activity
> at all after I exit ppcboot ...
>
> I have check the following so far to the best of my abilities (until I get
a
> BDI 2000) ... and the MMU looks ok ... and my SMC port B settings are ok
as
> well.
>
> Does anyone have any tips that could help me out? For some reason I think
> either my MMU is not set to what I think it is ... or my SMC config has
> tanked ...
>
> Regards,
> Jim
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-12-16 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-14 19:37 kernel 2.4 smc1 problems ... advice please James Don
2002-12-14 21:13 ` Wolfgang Denk
2002-12-16 12:28 ` Leonardo Pereira Santos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-14 21:08 James Don

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='003101c2a4fe$b4cf05f0$1764a8c0@leonardo' \
    --to=lsantos@pd3.com.br \
    --cc=JDon@spacebridge.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).