Does anyone know the origin of xparameter_ml300.h? The
Xilinx EDK generates an xparameters.h file for each design, but the
structure of the file changes between releases.
I want to know if xparameters_ml300.h is the exact output produced by
EDK or if stuff was changed before it was submitted to the mainline
tree. (ie. all the stuff under the "linux redefines" comment block)
Also, where can I get the bitstream/systemace file that matches
xparameters_ml300.h? I've got a custom ml300 image that I'm regression
testing against, but I'd like to also test against some form of 'stock'
image. :)
Thanks,
g.
Grant Likely wrote:
Does anyone know the origin of xparameter_ml300.h? The
Xilinx EDK generates an xparameters.h file for each design, but the
structure of the file changes between releases.
I want to know if xparameters_ml300.h is the exact output produced by
EDK or if stuff was changed before it was submitted to the mainline
tree. (ie. all the stuff under the "linux redefines" comment block)
EDK can also generate the "Linux BSP".
In this case EDK uses the scripts from (depending on your setup)
/opt/xilinx/edk/7.1/sw/ThirdParty/bsp/linux_v2_00_b/data/
In particular, linux_v2_1_0.tcl adds those "linux redefines"
and renames xparameters.h to xparameters_ml300.h.
Also, where can I get the bitstream/systemace file that matches
xparameters_ml300.h?
The most reliable way is to generate both (bitstream and
xparameters_ml300.h) by yourself. :)
But if you are speaking about the xparameters_ml300.h in the community
trees (linuxppc-2.4 and the 2.6 one from kernel.org), this file
is for the reference design by Xilinx:
http://www.xilinx.com/ise/embedded/edk6_2docs/ml300_edk3.zip
I've got a custom ml300 image that I'm regression
testing against, but I'd like to also test against some form of 'stock'
image. :)
Thanks,
g.
Thanks,
Andrei
On Wed, Aug 24, 2005 at 05:55:06PM +0400, Andrei Konovalov wrote:
Grant Likely wrote:
quoted
I want to know if xparameters_ml300.h is the exact output produced by
EDK or if stuff was changed before it was submitted to the mainline
tree. (ie. all the stuff under the "linux redefines" comment block)
EDK can also generate the "Linux BSP".
In this case EDK uses the scripts from (depending on your setup)
/opt/xilinx/edk/7.1/sw/ThirdParty/bsp/linux_v2_00_b/data/
In particular, linux_v2_1_0.tcl adds those "linux redefines"
and renames xparameters.h to xparameters_ml300.h.
Ahh; I've been using the standalone option. I didn't know about the tcl
script.
quoted
Also, where can I get the bitstream/systemace file that matches
xparameters_ml300.h?
The most reliable way is to generate both (bitstream and
xparameters_ml300.h) by yourself. :)
That's how I've gotten as far as I have :)
But if you are speaking about the xparameters_ml300.h in the community
trees (linuxppc-2.4 and the 2.6 one from kernel.org), this file
is for the reference design by Xilinx:
http://www.xilinx.com/ise/embedded/edk6_2docs/ml300_edk3.zip
Thanks!
g.
Please have a look at XAPP765
(http://direct.xilinx.com/bvdocs/appnotes/xapp765.pdf) and the EDK
documentation to see how this works. The latest MLD to create a BSP for
a linuxppc-2.4 kernel is linuxppc_mvl31_v1_01_a. linuxppc_mvl31_v1_00_a
works too but everything else is not up-to-date.
The documentation and tutorials for the ML310 board are also an
excellent source of information how to get a Linux kernel up and running
on Virtex-II Pro (see http://www.xilinx.com/ml310).
The reference design for the ML403 is yet another source of information
(http://www.xilinx.com/ml403). Have a look at the reference design users
guide.
Using the MLD (tcl script) is much less error-prone than any other
method that involves changing the files by hand. It's a little bit of a
learning curve but once mastered it just works.
- Peter
Andrei Konovalov wrote:
Grant Likely wrote:
quoted
Does anyone know the origin of xparameter_ml300.h? The
Xilinx EDK generates an xparameters.h file for each design, but the
structure of the file changes between releases.
I want to know if xparameters_ml300.h is the exact output produced by
EDK or if stuff was changed before it was submitted to the mainline
tree. (ie. all the stuff under the "linux redefines" comment block)
EDK can also generate the "Linux BSP".
In this case EDK uses the scripts from (depending on your setup)
/opt/xilinx/edk/7.1/sw/ThirdParty/bsp/linux_v2_00_b/data/
In particular, linux_v2_1_0.tcl adds those "linux redefines"
and renames xparameters.h to xparameters_ml300.h.
quoted
Also, where can I get the bitstream/systemace file that matches
xparameters_ml300.h?
The most reliable way is to generate both (bitstream and
xparameters_ml300.h) by yourself. :)
But if you are speaking about the xparameters_ml300.h in the community
trees (linuxppc-2.4 and the 2.6 one from kernel.org), this file
is for the reference design by Xilinx:
http://www.xilinx.com/ise/embedded/edk6_2docs/ml300_edk3.zip
quoted
I've got a custom ml300 image that I'm regression
testing against, but I'd like to also test against some form of 'stock'
image. :)
Thanks,
g.
Thanks,
Andrei
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded