public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Microblaze: how to generate correct xparameters.h file
Date: Mon, 07 Mar 2011 12:38:25 +0100	[thread overview]
Message-ID: <4D74C3B1.8090708@monstr.eu> (raw)
In-Reply-To: <4D7272D4.5060605@dave-tech.it>

Hi,

llandre wrote:
> Hi all,
> a colleague is facing the following problem.
> When using ISE/EDK 12.4 to build a microblaze-based system, the 
> xparameters.h file that is generated do not match u-boot sources so I 
> can't build U-Boot. In fact #defines included in this file are prefixed 
> by XPAR_ while U-Boot sources expect them to be prefixed by XILINX_. So 
> how to generate correct xparameter.h file? I suspect we have some 
> misconfigured flag in ISE/EDK environment ...
> Any help would be appreciated.

Some years ago I have created one page for it.
http://www.monstr.eu/wiki/doku.php?id=uboot:uboot

No everything is up2date but most of things should work.
I am using u-boot BSP to generate xparameters.h and config.mk which are used for u-boot 
configuration. This approach is also integrated to PetaLinux.

If you want to use xparameters.h from edk then you should look at git.xilinx.com.
Their version uses huge xparameters.h.

The name is the same which could be a reason why you are confused.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

      reply	other threads:[~2011-03-07 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 17:28 [U-Boot] Microblaze: how to generate correct xparameters.h file llandre
2011-03-07 11:38 ` Michal Simek [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=4D74C3B1.8090708@monstr.eu \
    --to=monstr@monstr.eu \
    --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