linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ryser <Peter.Ryser@xilinx.com>
To: Andreas Weder <andreas@lowtexx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: EDK 6.2 genace.tcl problem (solaris)
Date: Thu, 06 May 2004 18:17:45 -0700	[thread overview]
Message-ID: <409AE3B9.1070209@xilinx.com> (raw)
In-Reply-To: <200405062241.37808.andreas@lowtexx.de>


Currently, ACE file generation under Solaris is not supported. Please
use a Linux machine or a Windows machine to generate the ACE file.

- Peter


Andreas Weder wrote:

>I'm trying to build a ace file to boot linux on a ml300-board. I have
>the system.bit and the linux kernel  zImage.embedded.
>
>Documentation told me to do this:
>xmd genace.tcl -hw implementation/system.bit -elf zImage.embedded -board
>ml300 -ace out.ace
>
>This doesn't work. Genace.tcl aborted with the message  that it can't generate
>the svf-file for the kernel. (Doesn't work for smaller files like
>hello_gpio.elf ...)
>Problem is the xconnect command in genace.tcl. It does nothing (I don't
>get any return value) and generation fails. I tried to exchange
>xconnect with the (new?) ppcconnect command --> same result.
>Why do I have to use xconnect/ppcconnect to generate a svf file from elf
>file?
>Does the ML300 Board have to be connected to the computer I use to execute
>genace.tcl? (Not possible in my case ...)
>
>Board: ML300
>OS: solaris 2.8
>EDK: 6.2
>PPC-Kernel: 2.4.18
>
>cu
>Andreas Weder
>
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-07  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-06 20:41 EDK 6.2 genace.tcl problem (solaris) Andreas Weder
2004-05-07  1:17 ` Peter Ryser [this message]
2004-05-10 10:29 ` Roberto Farina

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=409AE3B9.1070209@xilinx.com \
    --to=peter.ryser@xilinx.com \
    --cc=andreas@lowtexx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).