references like (malloc) (free) (_abort_msg) are not allowed in codec engine

wind chen

Other Parts Discussed in Thread: DM3730

HI,

My developmen environment is Devkit8500(DM3730) and dvsdk4_03 and codec-engine_2_26_02_11

I using EMCV to write my algorihm in codec engine's codec side. when I use qualti ti test my codec .I get error messge as follow.

XDAIS Rules 8, 9, 10: Namespace compliance

Report: Failed

Test Description:

(Rule 8) All external definitions must be either API identifiers or API and vendor prefixed.

(Rule 9) All undefined references must refer either to the operations specified in Appendix B (a subset of C runtime support library functions and a subset of the DSP/BIOS HWI API functions), or TI's DSPLIB or IMGLIB functions or other XDAIS-compliant modules.

(Rule 10) All modules must follow the eXpressDSP naming conventions for those external declarations disclosed to the client.
Test Status Details:

Test failed. Problem: The algorithm makes the following disallowed external references:
- malloc
- free
- _abort_msg

Please check that these references are resolved via allowed functions in RTS, IMG, DSP, ACPYx libraries.

For your reference, the following external references are not allowed:
- malloc
- free
- realloc
- calloc
- printf
- open
- read
- write
- fopen
- fread
- fwrite
- sprintf
- ctime
- time
- _abort_msg
- _assert

Test Execution Log: XDAIS Rules 8, 9 and 10 execution log

How can I solve the problem ?Where can I find these RTS, IMG, DSP, ACPYx libraries file ?

thk.

over 11 years ago

0 Cvetolin Shulev-XID over 11 years ago

TI__Guru 65405 points

Hi Wind Chen,

The memory allocation and freeing in Codec engine is specific in some extend. There are set of function for memory management which can be used in the Codec engine as:

Memory_contigAlloc
Memory_contigFree
Memory_alloc
Memory_free

You can find description of these functions at the link:

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ce/2_25_04_15/exports/codec_engine_2_25_04_15/docs/html/group__ti__sdo__ce__osal___memory.html

Also for better understanding the programming under Codec engine read the Algorithm creator and Application developing user's guides at the links:

http://www.ti.com/lit/ug/sprued6c/sprued6c.pdf

http://www.ti.com/lit/ug/sprue67d/sprue67d.pdf

You can directly trace to the CCS console by GT_set() function. You can find a short description about how to do this at the link:

http://processors.wiki.ti.com/index.php/Codec_Engine_FAQ#Okay.2C_but_that_memory_window.27s_hard_to_read._Can_I_direct_trace_to_the_CCS_console_window_instead.3F

The CE_DEBUG feature should be useful for debugging and printing in your programs. You can obtain more info at:

http://processors.wiki.ti.com/index.php/Codec_Engine_Application_Developers_Guide

http://processors.wiki.ti.com/index.php/CE_DEBUG

Tsvetolin Shulev

0 wind chen over 11 years ago in reply to Cvetolin Shulev-XID

Prodigy 60 points

hi, Tsvetolin Shulev

thank you for you answer.

I use the Memory_contigAlloc and Memory_contigFree to replace malloc and free, and no error in complier, but I has other problem now.

I copy the whole foloder name videnc_copy in codec-engine-example-codecs for my own project. and one of my own c file has declared a array whose size is 80000*1 which is just decale and no alloc.

my array delare like this : const unsigned char VIDENCCOPY_TI_guoying2[] = { "here has 80000 data"};

And I get some message when I run my app_remo.xv5T as follow.

DSP MMU Error Fault! MMU_IRQSTATUS = [0x1]. Virtual DSP addr reference that generated the interrupt = [0x87f24fc0].

I realized that the error maybe caused by the big array which hasn't enough space.

so my quetion is:

Is the error because I just declare and didn't alloc a enough space?

How can I map my array to the DSP memory, Is it set in my codecs foloder or the servers foloder or the app foloder? and Does the max array declare in my function is set by the command “Server.threadAttrs.stackSize = 4096;” which is in all.cfg under the example-servers-all_codecs

thank you

0 Cvetolin Shulev-XID over 11 years ago in reply to wind chen

TI__Guru 65405 points

Hi Wind Chen,

You must be sure that the accessing memory without it has been allocated will cause errors. Some work around that I can suggest you is to try to read the data in parts using the maximum size of block which can be successfully allocated. Also you can try to use Memory_alloc instead of Memory_contigAlloc. This could solve the problem is there is enough free memory but it is fragmented.

Tsvetolin Shulev

0 wind chen over 11 years ago in reply to Cvetolin Shulev-XID

Prodigy 60 points

hi, Tsvetolin Shulev

Thank you for your reply.

I use the example codecs-videnc_copy without my own codec but the array that I thought it is no allocated. and I use the GT_1trace funtion to printf some data in it , and it is work that I can see the data by uart.

so , my last time error would no case by the array, I will try to find the error in my own codec.

wind chen

0 Feihu Sun over 11 years ago in reply to Cvetolin Shulev-XID

Prodigy 100 points

Hi Tsvetolin Shulev,

I also has a similar problem how to allocate memory on DSP based on codec engine in DM3730, The question was described the RTOS E2E forum at the link:

http://e2e.ti.com/support/embedded/tirtos/f/355/t/367286.aspx

I would be grateful if you provided some advice.

F.H. Sun

Processors

Processors forum

references like (malloc) (free) (_abort_msg) are not allowed in codec engine