All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Pow, Christopher (SWCOE)" <Christopher.Pow@honeywell.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: TI SysLink for am180-evm target
Date: Mon, 13 May 2013 15:20:21 -0400	[thread overview]
Message-ID: <20130513192021.GL17907@edge> (raw)
In-Reply-To: <7B8A37CE7777314D9B931CDD3BA8C83B1B9F6A72@de08ex3002.global.ds.honeywell.com>

On Mon, May 13, 2013 at 05:57:03PM +0000, Pow, Christopher (SWCOE) wrote:
> I am trying to integrate the TI Syslink package into a Yocto BSP.  So far I 
> have not been successful.  I have found and downloaded the cgt_c6000 binary 
> installer, but can't figure out how to modify the BitBake recipe to point to 
> it.  [bitbake ti-syslink errors on the fetch phase even though the SRC URI 
> has been modified to point to the downloaded installer binary.]  Also I am 
> unable to find a download link for the TMS470 compiler, which seems to be 
> another dependency for SysLink.  Has anyone successfully integrated the TI 
> SysLink recipe?  Would it be easier to download and build SysLink separately 
> and just install it on top of the targetfs?
> 
> I am trying to meet a very demanding schedule so I'd appreciate any help 
> anyone can provide.

Well, strictly speaking none of AMx devices have DSPs in them. That would 
require DMx devices, which are not currently supported in meta-ti.

-- 
Denys


  reply	other threads:[~2013-05-13 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.0.1368467467.29286.meta-ti@yoctoproject.org>
2013-05-13 17:57 ` TI SysLink for am180-evm target Pow, Christopher (SWCOE)
2013-05-13 19:20   ` Denys Dmytriyenko [this message]
2013-05-13 20:02     ` Pow, Christopher (SWCOE)
2013-05-14 17:11       ` Denys Dmytriyenko
2013-05-14 17:34         ` Pow, Christopher (SWCOE)

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=20130513192021.GL17907@edge \
    --to=denys@ti.com \
    --cc=Christopher.Pow@honeywell.com \
    --cc=meta-ti@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.