[U-Boot-Users] Does Uboot do lowlevel clock settings if it is in RAM?

[U-Boot-Users] Does Uboot do lowlevel clock settings if it is in RAM?

[arun c]

Hi all,

I am downloading the uboot.bin file through JTAG using CCS.
its downloading sucessfully. But after running it nothing comes
in the serial port of my omap2430sdp.

we did not port uboot yet thats why we are using a working uboot
with the clock settings done by CCS

we checked the clock settings. its going wrong after we start
running uboot(its fine untill we download through JTAG).

But what i understood that uboot won't change any clock settings
if it is running from RAM.

I want to know whether uboot changes clock settings if its
running from RAM??

please somebody help me out.

Regards
Arun

[U-Boot-Users] Does Uboot do lowlevel clock settings if it is in RAM?

[Wolfgang Denk]

In message <c656a4d20707030815w36ca94cck46f68bf43665e4ca@mail.gmail.com> you wrote:
> 
> we did not port uboot yet thats why we are using a working uboot
> with the clock settings done by CCS

This is an oxymoron. If you did not port  U-Boot  to  your  platform,
than you DON'T have a working U-Boot.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Brain fried - Core dumped

[U-Boot-Users] Does Uboot do lowlevel clock settings if it is in RAM?

[arun c]

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

On 7/4/07, Wolfgang Denk <wd@denx.de> wrote:
> In message <c656a4d20707030815w36ca94cck46f68bf43665e4ca@mail.gmail.com> you wrote:
> >
> > we did not port uboot yet thats why we are using a working uboot
> > with the clock settings done by CCS
>
> This is an oxymoron. If you did not port  U-Boot  to  your  platform,
> than you DON'T have a working U-Boot.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> Brain fried - Core dumped
>

[U-Boot-Users] Does Uboot do lowlevel clock settings if it is in RAM?

[Jerry Van Baren]

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