linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Wade Maxfield" <wmaxfield@gmail.com>
To: "Peter Ryser" <peter.ryser@xilinx.com>
Cc: ppc <linuxppc-embedded@ozlabs.org>
Subject: Re: system ace programming xf60
Date: Thu, 14 Dec 2006 13:46:10 -0600	[thread overview]
Message-ID: <45a1b53e0612141146x307bf30au7ec3317255ccda53@mail.gmail.com> (raw)
In-Reply-To: <4581A3F2.3010901@xilinx.com>

[-- Attachment #1: Type: text/plain, Size: 2882 bytes --]

Hi Peter,

  Thanks, we had that already.  The 8.1i development environment refused to
build until we fixed that.

  See my other reply to let you know how we did it.  The genace.tcl file
shipped with 8.1i (service pack 3) has an incorrect ID code for the xf60
part.  That threw us off for over a day, as the tool can't find an irlength
for that invalid part (since the part ID does not exist.)  Rather than
erroring with an "invalid id code," it gives an "invalid instruction length"
error, which was not useful at that time.

thanks,
wade

On 12/14/06, Peter Ryser <peter.ryser@xilinx.com> wrote:
>
>  Wade,
>
> the v4fx60 has two PPC405. Please make sure that both PPC405 are connected
> to the jtagppc_cntrl in your MHS hardware project file. You might want to
> compare your setup with the ML410 reference design available at
> http://www.xilinx.com/products/boards/ml410/designs/ml410_bsb_design.zip.
>
> The JTAG IR length of the v4fx60 is 14 (6 for the FPGA + 4 for each
> PPC405, i.e. for the 4vfx60 it's 6+4+4=14)
>
> - Peter
>
>
> Wade Maxfield wrote:
>
> Hi,
>
>   We are trying to generate a system ace file that will program an xf60
> using Xilinx scripts,
> (and even their impact GUI), using 8.1i, service pack 3 EDK.
>
>   Unfortunately, if we choose the ml410 board from Xilinx's genace.tclscript
> in their EDK/data/xmd directory, it errors with an invalid instruction
> register length.
> The irlength is listed as 14 in the xilinx script files.  I looked and
> googled and could
> not find the irlength listed for that xf60 part in any literature.
>
>   Also, if we try to include the zImage.elf file, the script errors out.
>
>   Conversely, if we choose an ml403 board (and switch the project to the
> xf12 chip),
> we can combine the zImage.elf file and generate a system.ace file that
> loads on an
> ml403 board.
>
>   We can take the download.bit file that refuses to load when combined
> into the system.ace,
> and load it over the jtag port.  It programs the xf60 just fine.
>
>   If we create an empty system.ace file,  the system ace chip on our board
> signals everything is ok,
> but of course, the xilinx chip is not programmed.  If we pull the compact
> flash out of the board,
> the system ace chip signals that is can't find the compact flash by
> flashing the error light.
>
>   Has anyone on this list had any experience with this that could lead us
> in a right direction?  We've
> tried about 10 different combinations so far with no luck.
>
> thanks,
> wade
>
> ------------------------------
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.orghttps://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>

[-- Attachment #2: Type: text/html, Size: 4282 bytes --]

  reply	other threads:[~2006-12-14 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 16:05 system ace programming xf60 Wade Maxfield
2006-12-14 19:20 ` Peter Ryser
2006-12-14 19:46   ` Wade Maxfield [this message]
     [not found] <8506C3905ED0764F889ADEB33E3A9E8062CF8A@MAIA.scopus.net>
2006-12-14 19:14 ` Wade Maxfield
2006-12-14 19:41   ` Wade Maxfield

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=45a1b53e0612141146x307bf30au7ec3317255ccda53@mail.gmail.com \
    --to=wmaxfield@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=peter.ryser@xilinx.com \
    /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;
as well as URLs for NNTP newsgroup(s).