All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank <frannk_m1@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] fishing for ideas
Date: Fri, 1 Oct 2004 09:46:44 -0700 (PDT)	[thread overview]
Message-ID: <20041001164644.10508.qmail@web13821.mail.yahoo.com> (raw)
In-Reply-To: <1096646639.10111.115.camel@mhpajh5c>

It does look like your sdram isn't configured correctly or you
have a hardware problem. Try turning off cache and are you sure
you can trust the hardware guy's opinion that he saw nothing
wrong with the sdram init values. Since he wrote the original
bootloader, he may not want you to replace it with u-boot.:-)

--- Benjamin Collar <benjamin.collar@siemens.com> wrote:

> Greetings folks
> 
> Yesterday's problems have been overcome. Mostly I was just
> misunderstanding what was going on / what was supposed to be
> going on.
> Thanks for the clues overall.
> 
> But there is a bit more to it. At the end of the day
> yesterday, I
> performed exactly the same 'loads' command,  with exactly the
> same srec
> file, as I had done at the beginning of the day, and it
> worked. Talk
> about frustration!
> 
> Today I was working on it and loaded a linux kernel image.
> When I
> 'loads' it, using the u-boot command line, into ram, the 'md'
> command at
> the loaded area shows 
> 
> 00010000: 27051956 d3232bea 415d1e66 0005ba2c   
> '..V.#+.A].f...,
> 00010010: 7d8c5a14 3940ffff 914c0000 3bffffe0   
> }.Z.9 at ...L..;...
> 00010020: 4c696e75 782d322e 342e3138 00000000   
> Linux-2.4.18....
> 00010030: 00000000 00000000 00000000 00000000   
> ................
> 
> while objdump shows
> 
>  00000 27051956 d3232bea 415d1e66 0005ba2c  '..V.#+.A].f...,
>  00010 00000000 00000000 82847f95 05070201  ................
>  00020 4c696e75 782d322e 342e3138 00000000  Linux-2.4.18....
> 
> of course, you'll notice immediately that the 5th word is
> completely
> bogus, among others.
> 
> I've spoken with the board developer (who also wrote a
> bootloader for
> the board) and showed him the sdram initialization function,
> and he said
> it was correct. However, I've got the behavior shown above. Is
> there
> another reason why this sort of corruption would happen? (btw,
> using
> 'cu' to download the image into RAM).
> 
> Thanks for any tips
> Ben
> 
> -- 
> Benjamin Collar
> Siemens AG
> CT SE 2
> Embedded Linux
> 089-636-53711
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on
> ITManagersJournal
> Use IT products in your business? Tell us what you think of
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
> 



		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

  reply	other threads:[~2004-10-01 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 16:03 [U-Boot-Users] fishing for ideas Benjamin Collar
2004-10-01 16:46 ` Frank [this message]
2004-10-01 17:45 ` Tadas
2004-10-05 14:56   ` Benjamin Collar
2004-10-01 17:45 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-10-01 16:31 VanBaren, Gerald

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=20041001164644.10508.qmail@web13821.mail.yahoo.com \
    --to=frannk_m1@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.