• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 853 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.

c66x edma3 rm lib

Ganz
Intellectual 770 points
Other Parts Discussed in Thread: TMS320C6657

While building  my cfg project which uses the edma3 package, I noticed that it link the c6657-sim lib instead of the c6657_evm  lib.

Build console output:

.....

Inside EDMA3 Drv getLibs

    will link with ti.sdo.edma3.drv:lib/66/release/edma3_lld_drv.ae66

Inside EDMA3 RM getLibs

    will link with ti.sdo.edma3.rm:lib/c6657-sim/66/release/edma3_lld_rm.ae66

cle66 package/cfg/NextGen_pe66.c ...

'Finished building target: configPkg/linker.cmd'

Then I found in the RM package.xs devices list there are two 'TMS320C6657' extries.  The first  'TMS320C6657' correspons to 'c6657-sim/' in dir[], while the second 'TMS320C6657' correspons to 'c6657-evm/'. Since the first 'TMS320C6657' is encountered first during the search so that c6657-sim is used. Is there any different between the c5567-sim lib and the c6657-evm lib? If yes, should c6657-evm be used on the c5567 evm board?

 

edma3 version: edma3_lld_02_11_14_19

 

Regards

GanZ

  • 0
    TI__Mastermind 20790 points

    GanZ,

    I hope,Your test project is not simultor mode. Did you get any issue using RM lib import through .cfg file?
    TI mandated library for all EDMA3 peripheral users to acquire and configure EDMA3 hardware resources and DMA Interrupt Service Routines.

    The Low Level Driver consists of the following packages:
    ti.sdo.edma3.rm - EDMA3 Resource Manager.
    ti.sdo.edma3.rm.sample - Sample initialization library / OS abstraction layer for the Resource Manager.
    ti.sdo.edma3.drv - EDMA3 Driver.
    ti.sdo.edma3.drv.sample - Sample initialization library / OS abstraction layer for the Driver.
    When you run the RM based project code on the board, it should take the EVM based lib. You can find the some more details for EDMA3 Resource Manager,

    C:\ti\edma3_lld_02_11_05_xx\packages\ti\sdo\edma3\rm\docs\EDMA3_RM_User_Guide.pdf

  • 0 in reply to Pubesh
    Intellectual 770 points

    Pubesh,

    The test project is PDK_c6657_1_1_2_6 MCBSP_DigLpbkExampleProject, it is not simulator mode. The target is

    ti.targets.elf.C66.  I believe there is a bug in rm package.xs file under

    edma3_lld_02_11_14_19\packages\ti\sdo\edma3\rm.  It uses the Program.cpu.deviceName to find the platform directory. There are two TMS320C6657 entries. The first TMS320C6657 entry should be changed to reflect that it is simulator.

    1222.package.zip

    GanZ.

     

  • 0 in reply to Ganz
    TI__Mastermind 20790 points

    Ganz,

    The MCSDK_2_01_02_06 release was built and validated against using the following components:

    Will you check with C:\ti\edma3_lld_02_11_05_02\packages\ti\sdo\edma3\rm?

  • 0 in reply to Pubesh
    Intellectual 770 points

    Pubesh,

    EDMA3 v2.11.05.02 has the same problem as v2.11.14.19.

     

    GanZ