NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Codec Engine StackMemIds

From Texas Instruments Wiki
Jump to: navigation, search

Codec Engine Stack Mem IDs

Introduction[edit]

Note that algs.threadAttrs in a Server.algs[] array has a .stackMemId config param assignable in the server integrator's .cfg script. This id corresponds to the memory/heap segment where DSP/BIOS is to allocate the task (TSK) stack for the task running a specific codec instance. It is also commonly referred to as a memory id or heap id.

How do I determine the correspondence between a heap and its id[edit]

To determine the id for a given heap, there are two possibilities:

1. If you are familiar with connecting to the DSP using JTAG, you can run the application, bring up CCS and look at the Kernel Object View to find out the heap id associated with each heap defined by the DSP/BIOS .tcf configuration file. This topic might help.

2. Another approach is to look at the autogenerated <executable_name>cfg.s62 file in the package\cfg\<platform>\ directory in the area where you build the DSP executable or server. Search for “MEM_Obj”. You will find a list of memory objects defined. BIOS goes through this list when assigning heap ids, using the following logic:

  • The heap used to allocate the DSP/BIOS objects (ie. the heap assigned to prog.module("MEM").BIOSOBJSEG in the DSP/BIOS configuration file) always has ID 0.
  • Look up all the memory objects (MEM_Obj) listed in the *cfg.s62 that has a heap defined. The first one in the list that has a heap defined has ID 1, the 2nd one has ID 2, etc. Ignore/Skip the one corresponding to the DSP/BIOS object segment which is already assigned ID 0.
E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article Codec Engine StackMemIds here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article Codec Engine StackMemIds here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article Codec Engine StackMemIds here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article Codec Engine StackMemIds here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article Codec Engine StackMemIds here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article Codec Engine StackMemIds here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article Codec Engine StackMemIds here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article Codec Engine StackMemIds here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article Codec Engine StackMemIds here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity