From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Does Uboot do lowlevel clock settings if it is in RAM?
Date: Thu, 05 Jul 2007 09:24:01 -0400 [thread overview]
Message-ID: <468CF0F1.4050701@smiths-aerospace.com> (raw)
In-Reply-To: <c656a4d20707032138s7bfad0cfwd0617396f64df789@mail.gmail.com>
arun c wrote:
> Hi,
>
> Sorry for the confusion,I mean i did not port uboot completely.
>
> with a working uboot i mean, a uboot that able to access RAM,
> serial port etc. ie basic functionalities only.
>
> My case is like this
> 1)on an old board we have a working uboot(Everything fine).
>
> 2)we replaced the RAM on the old board(same mapping but
> different manufacturer)
>
> 3)we did not modify uboot(Thats why we are setting the timings
> in a debugger(CCS), downloading uboot to RAM and running it
> there.)
>
> 4)we are doing this with an assumption that uboot not change
> clocks if it knows its running from RAM
>
> But we are observing clock changes.
>
> Does uboot change clock if its running from RAM?
>
> Regards
>
> Arun
Hi Arun,
It shouldn't, but you have to check your code and fix it if it does. We
cannot say for sure, not having your code. Running from RAM is a
"non-standard" configuration so it may or may not be supported on your
board. Sounds like not. On the positive side, you have the source
(including examples of proper support), so you can add the support.
Theoretically, adding the support is easy because you simply #ifdef out
the SDRAM initialization. In practice, there are lots of sharp edges to
cut yourself on, which is why it is a non-standard configuration.
Best regards,
gvb
prev parent reply other threads:[~2007-07-05 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 15:15 [U-Boot-Users] Does Uboot do lowlevel clock settings if it is in RAM? arun c
2007-07-03 20:38 ` Wolfgang Denk
2007-07-04 4:38 ` arun c
2007-07-05 13:24 ` Jerry Van Baren [this message]
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=468CF0F1.4050701@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--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