public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Thorsten Lueck <T.Lueck@IfEN.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problem starting u-boot on Xilinx V2P
Date: Wed, 06 Jul 2005 17:16:10 +0200	[thread overview]
Message-ID: <42CBF5BA.5040409@IfEN.com> (raw)
In-Reply-To: <20050706080114.22A56353A4E@atlas.denx.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wolfgang Denk wrote:
> In message <42CB7E35.8090805@IfEN.com> you wrote:
>>My board is not as different to ml300 as one may think - indeed, it uses
> 
> Even minimal diffeences can have significant effects.  Feel  free  to
> ignore  my advice, but please don't complain if you run into problems
> later.
> 
>>>You missed to port U-Boot to your hardware. Go back to square 0. Read
>>>the README (porting guide section) and do what needs to be done.
>>Well - I _did_ port it (in the sense of using the appropriate BSP) -
> 
> No, you did not. For example, you missed to adapt the SDRAM initialization.
> 
>>PowerPC code may hang immediatley _after_ "DRAM:" printout. This led me
>>to the assumption, that my problem may be well known ...
> 
> It is. It is actually a FAQ.
> 
> Best regards,
> 
> Wolfgang Denk
> 

Whatsoever - I started using Xilinx application note XAPP542, which
advised to start using ml300 design and generate a new BSP using EDK.
Unfortunately the DRAM size was hardcoded in the board driver source
ml300.c instead of using (the available) hash-defines. I fixed this and
can therefore provide a patch if wanted.

I realized, that the uboot-1.1.1 version supplied by Xilinx within the
attachment of XAPP542 is not identical to the original version. Several
patches and improvements has been made by Xilinx, which I cannot find in
the acutal source (even 1.1.2 or cvs; indeed, 1.1.2 and cvs are almost
the same for the xilinx board support package).

One problem when using EDK is, that variables within the tcl-script
uboot_v2_1_0.tcl are declared "global" instead of "variable", which
leads to errors of "unknown variables" in EDK. Xilinx fixed this to
"variable" in their distributed version. Are there any reasons (wrt
ELDK) why to use "global" instead of "variable"?

However, it seems, that the Xilinx version runs almost well (after some
minor adoptations).

Thanks for your help and worthwhile hints,

Thorsten



- --
IfEN - Gesellschaft f?r Satellitennavigation mbH

  Dipl. Ing. Thorsten L?ck
  Tel.:  +49 8121 2238-25
  Fax :  +49 8121 2238-11
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCy/W4QDwjNlk95KYRAhPZAJwLqJqNJw/qVbBSs6M7x6f0Ycib5QCglMjf
XBlu7e1SmHSzHDH5fYsL76Q=
=FZsE
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-07-06 15:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05 15:52 [U-Boot-Users] Problem starting u-boot on Xilinx V2P Thorsten Lueck
2005-07-05 16:08 ` Wolfgang Denk
2005-07-06  6:46   ` Thorsten Lueck
2005-07-06  8:01     ` Wolfgang Denk
2005-07-06 15:16       ` Thorsten Lueck [this message]
2005-07-06 19:58         ` Wolfgang Denk
2005-07-06  6:33 ` Antwort: " andreas_schmidt at ifm-electronic.com
     [not found] ` <c8f1005070512292aebd358@mail.gmail.com>
2005-07-06  6:52   ` Thorsten Lueck

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=42CBF5BA.5040409@IfEN.com \
    --to=t.lueck@ifen.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