• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 226 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.

Required to import DSPLink to debug OMAP3530 DSP application?

Eric Texley
Intellectual 320 points
Other Parts Discussed in Thread: CODECOMPOSER

So I spent several hours this afternoon pulling in all the include paths, all the #defines, and the DSP Source Tree into CCS4, to no avail.  Still lots of build problems.  Now with some research I think I can resolve these problems.  But then I started thinking...why am I doing this exercise?  I've already built DSP Link into library form using OE Bitbake, right?  So can't I simply make use of the include hierarchy that I've set up and build my own application, but link with the dsplink.lib that was built by the BitBake?  I'm really not interested in Debugging DSPLink, am I.  I want to "code compose" my own application.  What is the right way to do it?  How have you experts done it in the past?  It would be NICE to have all the source in Code Composer...but why?

 

Sincerely, Eric Texley

xG Firmware Engineer

  • 0
    Intellectual 320 points

    My build errors are resolved.  I've made a decision to build the DSPLink together with my application as a test build in code composer studio.    Now I'm getting a plethora of these:

    "C:/4_19_2011/dsplink_linux_1_65_00_03/dsplink/dsp/src/base/hal/hal_cache.h", line 82: warning:
       relocation type is static base-relative, but references symbol
       "_DSPLINK_shmBaseAddress" defined in section ".data"; references to section
       ".data" are not relative to any static base, so this relocation cannot be
       performed (type = 'R_C60BASE' (80), file = "./sma_pool.obj", offset =
       0x00000080, section = ".text")

    Taking a look at the map files with respect to my working BitBake build and Code Composer studio.

    CComposer

    1080d2f4   _DSPLINKDATA_ctrlPtr
    108034e0   _DSPLINKDATA_init
    10802e00   _DSPLINKIPS_init
    1080d2f8   _DSPLINKMQT_ctrlPtr
    10803520   _DSPLINKMQT_init
    1080ba40   _DSPLINKPOOL_ctrlPtr
    10802e80   _DSPLINKPOOL_init
    108029a0   _DSPLINK_init
    1080db00   _DSPLINK_shmBaseAddress
    1080db08   _DSPLINK_shmBaseAddress_pad

    vs. BitBake

    87e1bd78   _DSPLINKMQT_ctrlPtr
    87e18cc0   _DSPLINKMQT_init
    87e1ba70   _DSPLINKPOOL_ctrlPtr
    87e18840   _DSPLINKPOOL_init
    87e184a0   _DSPLINK_init
    87e20500   _DSPLINK_shmBaseAddress
    87e20508   _DSPLINK_shmBaseAddress_pad

    So I need to understand how to give CodeComposer specific linker directives.  Is there a good reference for linker cl6x linker controls via Code Composer?