• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 272 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.

TDA2PXEVM: TDA2PXEVM

Likhith C
Intellectual 270 points
Part Number: TDA2PXEVM


Hi All,

 

In one of the linker command file related to the BAM app .vcop_parameter_block section is mapped to EXTDMEM as shown below

 .vcop_parameter_block > EXTDMEM PAGE 1

Since VCOP cannot access memory other than WMEM, IBUFH and IBUFL, how this .vcop_parameter_block is being loaded into VCOP memory during runtime ??

Please let me know.

Regards

Likhith

[attached linker command file and generated map file ]

test_eveFeatureMatching.eve.out.map.zip

  • 0
    TI__Guru 56820 points

    Hi Likhith,
        I am not sure which linker you are referring here, but as far as BAM is concerned, it doesnt use .vcop_parameter_block  section. BAM allocates the parameter block memory by its internal memory management module.


    Regards,

    Anshu

  • 0 in reply to Anshu Jain
    Intellectual 270 points

    Hi Anshu,

    Thanks for Reply.

    If .vcop_parameter_block is not used, does the BAM stores parameters any of the memory other than WMEM, IBUFH and IBUFL ??

    And if it is stored in any other memory how is the data being sent to VCOP memory at runtime ??

    Please let me know.

    -Regards

    Likhith

  • 0 in reply to Likhith C
    TI__Guru 56820 points

    Hi Likhith,

         During process call BAM calls the kernel_init function with the memory allocated for parameter blocks in WBUF. And hence the parameters are directly updated in the WBUF memory and no external memory is required.


    Regards,

    Anshu