Compiler/TDA4VMXEVM: Running the program on R5F will crash

And I now open up a heap space to store this string, but I found that if I search in this large string, I can't find the corresponding content (the content exists).Why?

What is the size of the string that you are trying to allocate? 

Yes, please use Heap to allocate the large memory.. 

It might be in cache, can you write back the cache memory?

Rgds,

Brijesh

Hi

The size of the string is 80 * 1024, but when I look for some content in it, he cannot find it (the content exists).I don't need to write to the cache, I use this string to simulate the operation after reading the file.

Thanks

And when I use heap space, I find that I haven't finished reading my string, but read a part (the program is correct, verified on x86).

Hi,

so does it work when you use heap memory?

Rgds,

Brijesh

Hi,

It doesn't work!

Thanks

  Hi

My memory allocation uses this kind of appMemAlloc (APP_MEM_HEAP_DDR, 80*1024, 0). I checked that the pointer returned by it is not empty.
Then I used memcpy to assign a value to the content inside. I found that it could not read After getting the following data, only a part of the data can be read. Is there any problem with this use? If yes, please indicate.

Thanks

Hi,

Could you please check the returned value of memcopy/memset API? May be this API did not copy the memory completely. 

Rgds,

Brijesh

Hi,

1. I use memcpy, I checked its return value and found that the result is correct.

2. If I open up heap space on MCU2_0, should I use new or appMemAlloc? I am using new.

3. I now try the following, I divided the string into several small parts, after running, he can find the corresponding content! !! Why is that? Is it because the heap is limited?

Thanks

Hi,

ok, you are using new. this will allocate the buffer from the local heap, which is cached. So you need to write back the cache.

Just call Cache_wb API on the allocate buffer.

Regards,

Brijesh

Hi,

Where is the header file for this API, can you tell me?

Thanks

Hi,

You could include pdk\packages\ti\osal\CacheP.h and use CacheP_wb API to write back cache data. 

Please make sure to allocate 128byte aligned memory..

Regards,

Brijesh

Hi，

After using this function, I still can't find it in the string. This is how I use CacheP_wb (str, 1024 * 80); I have tried this function before and after memcpy, and it is not working.

Thanks

Can you please share your code?

Rgds,

Brijesh

Hi，

char * Copy2Str()

{

char *str=new char[80*1024];

char *src_str="";(The size is 70*1024);

//CacheP_wb(str,1024*80);

memcpy(str,,src_str,79*1024);

//CacheP_wb(str,1024*80);

return str;

}

The code looks fine.

How do you check whether memory is written or not? through CCS?

Any specific reason for using new, instead of malloc?

Rgds,

Brijesh  

Hi，

I currently cannot monitor whether it is written to memory! At present, I can only determine whether the program is written to memory by the correct result of the program? But I don't know if it is correct to write to memory?
I use new because I'm c ++ code, but the bottom of new is also using malloc. Shouldn't these two have a great impact on the code?

Thanks

Hi, 

ok, the code which checks for the correctness of the memory, is it running on the same core or different core?

Rgds,

Brijesh

Hi，

What do you mean? I don't quite understand what you said.

This program runs on MCU2_0, I should need to check the correctness of the memory on MCU2_0.

Also, the correctness of the program I said means that I can find out what I need in the string I applied for.

Thanks

Hi,

I meant both the programs are running on MCU2_0? the code which writes to this memory and code which checks this memory?

Rgds,

Brijesh

Hi,

Yes.

Can't it be on the same core? But my current requirement is to write this content to MCU2_0 and read the written content from MCU2_0 for operation.

Thanks

Hi，

I did a test today and found that on MCU2_0, the size of the string on the heap is about 16K-17K, and the stack is only 15-16K. Is this data correct? If not, has the official stated the size of this space?
In addition, I also want to ask a question, if I use malloc to open up memory, where is mallco.h, I did not find the MCU2_0 related header files.

Thanks

Hi,

No, Stack will not affect, as you are allocating memory.

Can you try using appMemAlloc?

Rgds,

Brijesh

Hi,

I have tried using appMemAllocc. The usage is as follows:

char * str = (char *) appMemAlloc (APP_MEM_HEAP_DDR, 80 * 1024,128);
// appMemCacheWb (str, 80 * 1024);
memcpy (str, content, 81084);
// appMemCacheWb (str, 80 * 1024);

These two methods have no effect. Due to limited time, I have to use other ways to avoid this big string problem, thank you very much for your help.

Thanks