[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [microblaze-uclinux] Petalinux with EDK 10.1
> -----Original Message-----
> From: owner-microblaze-uclinux@xxxxxxxxxxxxxx
> uclinux@xxxxxxxxxxxxxx] On Behalf Of Royce Liao
> Sent: Saturday, July 05, 2008 10:31 PM
> To: microblaze-uclinux@xxxxxxxxxxxxxx
> Subject: RE: [microblaze-uclinux] Petalinux with EDK 10.1
> > Date: Tue, 17 Jun 2008 09:54:00 +1000
> > From: jwilliams@xxxxxxxxxxxxxx
> > To: microblaze-uclinux@xxxxxxxxxxxxxx
> > Subject: Re: [microblaze-uclinux] Petalinux with EDK 10.1
> > Sebastian wrote:
> >> is it possible to use Xilinx ISE/EDK 10.1 eval with the current
> >> petalinux-release (0.30rc1).
> >> I'm using a 1600 Spartan3E dev kit.
> > Yes it is, however the reference designs in
> > have are still targetting 9.2. The S3E1600 reference design should
> > rev-up quite nicely if you just copy it and open in XPS.
> > you could use Base System Builder to create a new design for the
> > and do a custom bringup guided by the doco at
> > http://developer.petalogix.com/wiki/BoardGuides/Custom/Tutorial
> I've found two minor issues in EDK 10.1 (SP2):
> 1) the Microblaze "CPU_driver (1.11b)" in Webpack 10.1.02 + EDK
> removed some #defines needed by Petalinux's auto-config system.
> In the EDK 10.1.SP2 (XPS) gui, "Software"-> "Software Platform
> Under the tab "Software platform", I can't find the entry for
> CORE_CLOCK_FREQ_HZ.. It is no longer there! When I generate the
> libraries, the following files are damaged:
> a) microblaze_0/include/auto-config.h file contains a broken
> #define CONFIG_XILINX_CPU_CLOCK_FREQ () // should contain a #
> config XILINX_CPU_CLOCK_FREQ
> default <-- should contain a #!
> define_int CONFIG_XILINX_CPU_CLOCK_FREQ <-- should contain a #
The parameter has not been removed, but deprecated. Deprecated
parameters do not show up in the GUI.
The missing #define value is due to a bug in EDK, where TCL queries for
the value of a deprecated parameter are turning up empty. The bug will
be fixed in SP3. An answer record (31278) will be available for this
issue by tomorrow.
The workaround is to explicitly instantiate the parameter in the
processor block of the MSS file and give it the right value frequency
PARAMETER CORE_CLOCK_FREQ_HZ = 100000000
Also, note that the reason for deprecating the parameter is that the
clock frequency information is now directly accessible from the hardware
database by reading attributes (if defined in the MHS) off the clock
port. Please see the cpu_v1_11_b driver TCL for an example of how to
retrieve this value when it is available.
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/