From: Wolfgang Denk <wd@denx.de>
To: Sylvain Munaut <tnt@246tnt.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on MPC5200 - LITE5200EVAL
Date: Sat, 14 Feb 2004 15:53:03 +0100 [thread overview]
Message-ID: <20040214145308.9E915C108D@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 14 Feb 2004 12:59:08 +0100." <402E0D8C.4080801@246tNt.com>
In message <402E0D8C.4080801@246tNt.com> you wrote:
>
> The weird problem with u-boot ( not booting If I set bootargs manually )
> and the kernel crash are both solved. It was a compiler issue. I used a
> toolchain I used to build binaries for a "normal" mac based on gcc 3.4 (
> cvs ) and it was a really bad idea.
I see.
> - The PCI slot is 3.3 v and apparently I don't have a single PCI card
> that seems to work on it ... When I plug one ( that I thought was 3.3v
> ), nothing boot, sometimes even the led don't power on ...
Be careful to put it correctly. The slot bracket has to be on the
side where the UART / USB / CAN connctors are. Do not insert the card
with the slot bracket pointing to the IDE connector.
Also be VERY carefully which card you insert. make sure it is
_really_ a 3.3V compatible card. [I fried a board by trying a Digitus
"DC SER2 Rev. 2.0 Serial PCI I/O Card" - this card has the key slots
for a 3.3/5V combi card, but the V_I/O pins are connected to the 5V
rail. The RAM chips didn't like to see 5V ...]
> - When I change options in the kernel to support new stuff I need, like
> activating USB host & IDE controller, the kernel don't boot at all ( or
> at least, I don't see on the serial console it does ). It's the same
> problem with activating drivers for the PCI bus ... What is weird is
> that it's not an error on boot, it's just that after u-boot messages,
> there is nothing at all.
Can you attach a debugger? Or even try a post-mortem dump of the
logbif area? Both PCI and USB are working fine for me.
> I'm not sure my hardware is fully OK, but I did mtest on u-boot for
> about 10 hours and it didn't complained. It's a fresh new board from
> motorola...
Maybe you can ask for a replacement. Your problems don't look normal
to me.
Best regards,
Wolfgang Denk
--
See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Being schizophrenic is better than living alone.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2004-02-14 14:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <402E0D8C.4080801@246tNt.com>
2004-02-14 14:53 ` Wolfgang Denk [this message]
2004-02-14 18:04 ` Linux on MPC5200 - LITE5200EVAL Sylvain Munaut
2004-03-03 7:34 ` Linux on MPC5200 - LITE5200EVAL & New bestcomm code ? Sylvain Munaut
2004-03-03 8:03 ` Wolfgang Denk
2004-02-17 1:08 ` Linux on MPC5200 - LITE5200EVAL Dale Farnsworth
2004-02-10 21:19 Sylvain Munaut
2004-02-10 22:00 ` Wolfgang Denk
2004-02-11 4:48 ` Andrew Dennison
2004-02-11 9:19 ` Gerrit Van de Velde
2004-02-11 9:53 ` Peter Falk
2004-02-11 10:14 ` Wolfgang Denk
2004-02-11 10:28 ` Gerrit Van de Velde
2004-02-11 13:09 ` Wolfgang Denk
2004-02-11 13:17 ` Peter Falk
2004-02-11 18:33 ` Sylvain Munaut
2004-02-11 20:08 ` Wolfgang Denk
2004-02-11 23:58 ` Sylvain Munaut
2004-02-12 12:30 ` Sylvain Munaut
2004-02-14 0:16 ` Wolfgang Denk
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=20040214145308.9E915C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tnt@246tnt.com \
/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).