* TI SysLink for am180-evm target
[not found] <mailman.0.1368467467.29286.meta-ti@yoctoproject.org>
@ 2013-05-13 17:57 ` Pow, Christopher (SWCOE)
2013-05-13 19:20 ` Denys Dmytriyenko
0 siblings, 1 reply; 5+ messages in thread
From: Pow, Christopher (SWCOE) @ 2013-05-13 17:57 UTC (permalink / raw)
To: meta-ti@yoctoproject.org
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.
Thanks!
Christopher S. Pow
Senior Engineer, Systems
Honeywell SWCOE - RTOS
o: 612-951-5852
c: 612-910-1271
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: TI SysLink for am180-evm target
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)
0 siblings, 1 reply; 5+ messages in thread
From: Denys Dmytriyenko @ 2013-05-13 19:20 UTC (permalink / raw)
To: Pow, Christopher (SWCOE); +Cc: meta-ti@yoctoproject.org
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: TI SysLink for am180-evm target
2013-05-13 19:20 ` Denys Dmytriyenko
@ 2013-05-13 20:02 ` Pow, Christopher (SWCOE)
2013-05-14 17:11 ` Denys Dmytriyenko
0 siblings, 1 reply; 5+ messages in thread
From: Pow, Christopher (SWCOE) @ 2013-05-13 20:02 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti@yoctoproject.org
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: TI SysLink for am180-evm target
2013-05-13 20:02 ` Pow, Christopher (SWCOE)
@ 2013-05-14 17:11 ` Denys Dmytriyenko
2013-05-14 17:34 ` Pow, Christopher (SWCOE)
0 siblings, 1 reply; 5+ messages in thread
From: Denys Dmytriyenko @ 2013-05-14 17:11 UTC (permalink / raw)
To: Pow, Christopher (SWCOE); +Cc: meta-ti@yoctoproject.org
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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: TI SysLink for am180-evm target
2013-05-14 17:11 ` Denys Dmytriyenko
@ 2013-05-14 17:34 ` Pow, Christopher (SWCOE)
0 siblings, 0 replies; 5+ messages in thread
From: Pow, Christopher (SWCOE) @ 2013-05-14 17:34 UTC (permalink / raw)
To: Denys Dmytriyenko; +Cc: meta-ti@yoctoproject.org
There's a file in the START_HERE partition of the SD card. dvsdk_omapl138-evm_4_01_00_09_setuplinux. Is that what you mean?
Thanks for the explanation RE the similar boards. It sounds like you are saying that I am out of luck with regard to finding support for OMAP-L138 within meta-ti? Do I have it right that DA850 and AM180x boards are just boards with ARM core processors on them, while the OMAP-L138 board is a board with an OMAP-L138 processor on it [ARM and DSP core]? So the support that I'll get from meta-ti is *only* support for the ARM-core. That makes sense, if I've got it right.
I am only responsible for the ARM-core side of the OMAP-L138. I'm thus only concerned with building things that need to run on the ARM core, which includes the Linux BSP and ARM-core SysLink components. Someone else is doing the DSP-core work [using SYS/BIOS] so I believe they will be integrating the DSP-core SysLink components.
From the perspective of the meta-ti capabilities, is there really anything above and beyond it that I need to have here? My understanding of the OMAP-L138 is that the ARM-core is "in charge" and brings the DSP-core out of reset. Once that's done they should be independent [except, of course, for SysLink communications].
Thanks for your helpful replies!
-----Original Message-----
From: Denys Dmytriyenko [mailto:denys@ti.com]
Sent: Tuesday, May 14, 2013 12:11 PM
To: Pow, Christopher (SWCOE)
Cc: meta-ti@yoctoproject.org
Subject: Re: [meta-ti] TI SysLink for am180-evm target
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
>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-05-14 17:34 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2013-05-14 17:34 ` Pow, Christopher (SWCOE)
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.