• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 250 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DSP/Link & Code composer support

Christopher Fury
Expert 1130 points
Other Parts Discussed in Thread: OMAP-L137

We are using an OMAP-L137 evaluation board to build our next generation controller system.  The toolchain that comes with the SDK is code composer 3.3, DSPBios 5.33 and DSPLink 1.61.   All of this software is old.  Code composer 3.3, according to your support technicians, is not supported on windows 7.   DSPLink appears to have been replaced with something called SysLink and IPS in Code composer 4.

What I'd like to know is this:

1) Is there a set of up-to-date tools for OMAPL137,or at least, a procedure or listing of software that is compatible?

2) Assuming a 10 year life span for our next generation controller system, what versions of the tools would you recommend?

3) What do you recommend folks generally do for long term product life cycle support in the embedded world?

Thanks,

Chris

  • 0
    TI__Mastermind 27585 points

    Code Composer 4.x, DSP/BIOS (5.41) and DSPLink (1.65) are supported on the OMAP-L137. These components have to be individually downloaded since there is no updated SDK at the moment. The links can be found here:

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/index.html

    We would recommending using the latest versions that are supported on the OMAP-L137, listed above.

    Jeff


  • 0 in reply to jc-ti
    Expert 1130 points

    Jeff,

    Thank you!

    In section 1.2.1.1 of the Install_Linux_OMAPL1xx_Guide.pdf located in dsplink_linux_1_65_00_03.tar.gz, there is this text:

    For compilation of DSP-side sources and applications, the CGTools version 6.1.5 can
    be used. This release has been validated with DSP/BIOS™ version 6.20.00.37, IPC
    1.00.00.40 and XDC version xdctools_3_15_00_50.    :

    This presents the following:

    1) The DSP/BIOS (6.x) version is different than what you mentioned (5.41.x)

    2) I don't have any product called "IPC" in my sdk bundle.  Do i need this?

    3) I have cg6x_6_1_9, which I assume is ok (it's higher than 6.1.5)

    4) I have xdctools_3_10_05_61, should I upgrade that?

    Thanks,
    Chris

  • 0 in reply to Christopher Fury
    TI__Expert 6860 points

    Chris,

    There seems to be a documentation issue in the Install_Linux_OMAPL1xx_Guide.pdf.  DSPLink 1.65.03 for OMAP-L137 is supported using DSP/BIOS 5.33.03 or greater.  Take a look at the Release Notes in the DSPLink installation docs directory.  In Section 3,  you'll find the minimum requirements needed (e.g. BIOS 5.33.03, CGTools 6.15) for DSPLink support on the OMAP-L1xx devices.

    In addition to the DSPLink platform specific Installation guide and the generic User's and Programmer's Guide,  there is also some useful information on how to configure and build DSPLink for the OMAP-L137 at the following location on the TI Wiki site:

    http://processors.wiki.ti.com/index.php/Building_The_OMAP-L137_SDK#DSPLink

    Note: Versions of both CCS 4.x and CCS 5.x come with DSP/BIOS 5.x and CGtools that meet these minimum requirements so you don't have to download newer version of these components separately  , if you opt go with a newer version of CCS other than CCS 3.3.