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: Tue, 14 May 2013 13:11:12 -0400	[thread overview]
Message-ID: <20130514171112.GA31835@denix.org> (raw)
In-Reply-To: <7B8A37CE7777314D9B931CDD3BA8C83B1B9F6B39@de08ex3002.global.ds.honeywell.com>

Christopher,

Can you please identify the TI SDK you received with the board - it's name and
the version.

DA850, OMAP-L138 and AM180x are slightly different boards, even though very 
similar. As a matter of fact, from ARM GPP perspective they are pretty much 
the same, but the difference is in the peripherals, including the availability 
of DSP. Hence, you can build the am180x-evm (non-DSP) from meta-ti and run it 
on any of the above boards. BTW, why do you need SysLink just for ARM?

-- 
Denys


On Mon, May 13, 2013 at 08:02:25PM +0000, Pow, Christopher (SWCOE) wrote:
> Denys,
> 
> Thanks for the reply.  I have a TI OMAP L138 devkit [with a touch screen].  
> The TI SDK that came with it indicates it is a Davinci 
> DA850/OMAP-L138/AM18xx EVM.  When I took a look at the machines available in 
> meta-ti, I saw am180x-evm so I picked that one.  It didn't seem right to 
> pick omap3 or omap5.  The Yocto am180x-evm image I built does run on the 
> devkit.
> 
> The TI SDK comes with DSP/Link.  I have been asked to change that to 
> SysLink.  I noticed that the latest available SysLink package indicates 
> support for OMAPL1XX targets.
> 
> Are OMAP-L138 devices supported in meta-ti?  My interpretation from a recent 
> conversation [on IRC] was that they were, with the am180x-evm target.  I am 
> only interested [at the moment] in building and installing the ARM-side of 
> the SysLink package.  Someone else is doing the DSP work.
> 
> Sorry for the confusion.  I thought I had all my pieces lined up but it 
> seems that there's still much for me to learn!  Thanks again for your help 
> in this!
> 
> Christopher S. Pow
> Senior Engineer, Systems
> Honeywell SWCOE - RTOS
> o: 612-951-5852
> c: 612-910-1271
> 
> 
> -----Original Message-----
> From: Denys Dmytriyenko [mailto:denys@ti.com] 
> Sent: Monday, May 13, 2013 2:20 PM
> To: Pow, Christopher (SWCOE)
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] TI SysLink for am180-evm target
> 
> 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
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
> 


  reply	other threads:[~2013-05-14 17:11 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
2013-05-13 20:02     ` Pow, Christopher (SWCOE)
2013-05-14 17:11       ` Denys Dmytriyenko [this message]
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=20130514171112.GA31835@denix.org \
    --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.