From: Thomas Kastner <thomas.kastner@marekmicro.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SDRAM init problem? Was Re: uboot 1.1.2 problem
Date: Wed, 25 May 2005 12:58:25 +0200 [thread overview]
Message-ID: <42945A51.8010203@marekmicro.de> (raw)
In-Reply-To: <42944F6B.5020400@anagramm.de>
Hello Sam,
cooler spray might help find the cause, too.
For example I once had a similar problem that looked like a SDRAM
problem. In the end I found out that the oscillator sourcing the CPU's
PLL input was a little weak and the CPU's internal PLL sometimes went
crazy, causing this strange behaviour. Cooler spray on the oscillator
marginally raised the slew rate and the system ran stable.
Check the clocks, especially termination.
If you have any chance to reduce the SDRAM clock rate, try that. Maybe
by changing dividers in software or replacing a hardware oscillator.
Generally speaking cooler spray has saved me a lot of time finding the
cause of timing problems, so this really might be worth a try.
Kind regards,
Thomas
Clemens Koller wrote:
> Hi, Sam!
>
> As Wolfgang said, check the voltages, caps, terminations...
>
> You might also try to actively lower/rise the voltages of
> your board/ram/... a bit. If your problem changes, I would
> bet it's a hardware problem.
>
> Greets,
>
> Clemens
>
> Sam Song wrote:
>
>>-- Wolfgang Denk <wd@denx.de> wrote:
>>
>>
>>>>Thanks. Actually, it involves the grey area which
>>>>a probelm was supposed to produce by hardware or
>>>>software. The golden role is to check SW first.
>>>
>>>You must be one of these hardware guys who always
>>>blame the software.
>>
>>
>>Firmware guys is better to me. I amn't willing to
>>be an native HW fellow although I come from HW
>>field. To blame right is my hope. SW is only one
>>side:-)
>>
>>[snip]
>>
>>
>>>We've seen lots of "funny" problems with the many
>>>boards we lay hands on. Three more things to check:
>>>
>>>* Check the voltages on your system: tolerances ok?
>>>spikes or other noise on the lines? especially
>>>close to the CPU?
>>>* Check the clocks. Check the clocks again.
>>>* check for unconnected pins, missing pull-ups or
>>>-downs, or incorrect resistor values
>>
>>
>>Ummm, this is really what I want. It seems I should
>>look back more to take case HW side:-)
>>
>>Thanks so much,
>>
>>Sam
>>
>
>
--
Thomas Kastner
Dipl.-Ing. (FH)
Entwicklung Hard- und Software
MarekMicro GmbH
Fuggerstr. 9
D-92224 Amberg
Tel: +49 96 21 / 97 32 - 124
Fax: +49 96 21 / 97 32 - 199
eMail: thomas.kastner at marekmicro.de
http://www.marekmicro.de
PGP: http://pgpkeys.pca.dfn.de/pks/lookup?search=0xA197D41B
next prev parent reply other threads:[~2005-05-25 10:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 9:44 [U-Boot-Users] SDRAM init problem? Was Re: uboot 1.1.2 problem Sam Song
2005-05-25 10:11 ` Clemens Koller
2005-05-25 10:58 ` Thomas Kastner [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-27 8:59 Sam Song
2005-05-25 8:33 Sam Song
2005-05-25 9:10 ` Wolfgang Denk
2005-05-23 14:02 [U-Boot-Users] " Jerry Van Baren
2005-05-24 4:50 ` [U-Boot-Users] SDRAM init problem? Was " Sam Song
2005-05-24 13:43 ` Scott McNutt
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=42945A51.8010203@marekmicro.de \
--to=thomas.kastner@marekmicro.de \
--cc=u-boot@lists.denx.de \
/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