• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 612 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.

edm:a3 example build

Tim Whipple
Intellectual 450 points

I'm trying to build the edma 3 example project:

edma3_drv_bios6_c6678_st_sample

but keep getting an error:

<Linking>
error: symbols in the reserved far sections cannot be accessed as near; symbol
"numEdma3Instances" in the far section
"C:/ti/edma3_lld_02_11_14_18/packages/ti/sdo/edma3/drv/sample/lib/c6678-evm/

Searches have provided nothing.  The debug version gives me this right out of the gate.  The release version needs the edma lld libraries added and then gives me the exact same error.  How do I resolve this?  Are there any examples that actually compile?  I'm not finding much information searching for this error.

  • 0
    TI__Mastermind 20790 points

    Tim,

    Please double check the paths as mentioned in the env.mk are proper.
    Like bios_PATH, xdc_PATH, CODEGEN_PATH_DSP.

    Go through the section "2.4.1 Building EDMA3 Libraries" at EDMA3 Driver User Guide.
    You can find the EDMA3 LLD documentation in the folder as follows:
    C:\ti\edma3_lld_02_11_xx_xx\packages\ti\sdo\edma3\drv\docs

    This release was built and validated against using the following components:

    • CCS 5.5.0
    • C6x Code Generation Tools version 7.4.4
    • SYS/BIOS 6.37.01.24
    • XDC Tools 3.25.05.94

    You can also post at TI-RTOS E2E forum to get fast repsonse from expert.
    http://e2e.ti.com/support/embedded/f/355.aspx

  • 0 in reply to Pubesh
    Intellectual 450 points

    Thanks.  That may indeed be the issue.  I tried changing the library search path to an older version of the edma3 lld and the error is gone.  I will try to rebuild the edma3 lld to see if it solves the issue as well.

  • 0 in reply to Tim Whipple
    Expert 2335 points

    Hi,

    I am experiencing the same error .and am it did not get resolve by modifying the env.mk file .

    Can you suggest any other way to get rid of this .I posted my more or less same question here :

    Please answer this if you know it .