C6678 JPEG Encoder problem

Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages (for processor issues). Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics (e2e.ti.com). Please read all the links below my signature.

Please do not duplicate threads. I have deleted your other post. We will get back to you on the above query shortly. Thank you for your patience.

Hi Paula,

Thank you for your quick reply. I'd like to make my problem more clear to you.

1. We didn't use the CCS TestApplication project. We are using the JPEG Baseline Profile Encoder (v02.02.03) on C66x in our own project. But basically, we didn't change the main process -- Parameter Setup, Algorithm Instance Creation and Initialization, Process Call, Algorithm Instance Deletion. And we wrote our codes based on the TestApplication project. And besides the problem I mention below, it worked well.

2. Yes, we'are using Shannon EVM + emulator,

Tools versions are all the same. And we followed exactly the same 7 steps you offered.

The problem is that when we did the 7 steps for the first time after power up, we got stuck in step 6 (Demo stops in main()). It didn't stop in main(). Then we restarted from step 3 (Do system reset for Core 0). It worked well and gave the right results.

May I get some suggestions about how to fix it, like what might be the reason to such situation? I'm aware that it is not easy to solve the problem without actually reading our project. If you need, I could offer our codes.

I really appreciate your help.

Thanks,

Zhengyang Wang

jpeg_multi_core_v1.rar

Thanks, Paula. I've attached our project in this reply. Hope that we could figure it out.

The purpose of our project is: Divide an image into 7 pieces and ask each core (0-6) to encode one piece (using OpenMP). Then we combine the pieces into the full image. We've checked that it works well. There might be some Chinese comments which you could ignore. They won't influence your understanding.

For your question, I checked that after the first time I do "system reset", core0 address is 0x20B00000.

And I tried to simply add what you pasted here to the .cfg file in our project, It didn't build successfully because undefined symbol setLocalId and startup_reset.

Hi Zhengyang, about XDC startup code I copied, it was just an example, the main idea is that you can add functions to init your board and call them before anything else runs. I found a page with a good explanation for your reference http://rtsc.eclipse.org/docs-tip/Using_xdc.runtime_Startup/TI 

You can also select from were to run _c_int00, and example code below

CCS command file example

MEMORY
{

    L2SRAM_BOOTCFG    (RWX) : org = 0x800000, len = 0x100
    MSMCSRAM1 (RWX) : org = 0xc000000, len = 0x100
    DDR3_MAILBOX_RESERVED (RW)   : org = 0x9FC00000, len = 0x8000

}

 
SECTIONS
{
    .text_start > MSMCSRAM1
  {
    *(.text:_c_int00)
  }
    .boot_config > L2SRAM_BOOTCFG , type NOINIT
    .host2dspmailbox   >       DDR3_MAILBOX_RESERVED
    .dsp2hostmailbox   >       DDR3_MAILBOX_RESERVED
}

About your project, our codec experts are taking a look, they mentioned to me there were facing building errors. I was wondering if you could check that your project builds/runs on fresh setup, and if no, if you can help us to clean build errors. This sanity check in your side could help us to speed up debugging process..

Thank you,

Paula

Hi Paula. Sorry for the long delay and hope you had had a nice weekend.

We've tried to solve the issue through xdc.runtime Startup but unfortunately made little progress.

About our project, I'm sorry that I didn't provide all the information last time. I attach a new .rar file in this thread which includes all that you need to build the project.

There're five pictures in it to help you check all the settings:

Proj_info_1 & Proj_info_2 show the libraries with their versions we use, which are same as what TestAppEncoder uses. (Also note that we use the platform whose settings are shown in Proj_info_5) ;

Proj_info_3 shows the device information, compiler version and output format;

Proj_info_4 shows "#include search path";

Proj_info_5 shows the platform settings. We use red rectangular to emphasize what we think important.

With the updated project dir and platform dir, I believe the project would build/run well. 

We really appreciate your help and patience!

Sincerely,

Zhengyang Wang

7230.project.rar

Hi Zhengyang Wang,

I am looking into this issue. Thanks for sharing the updated project.

I have one quick question. As shown in the Proj_info_1 shared, I could not able to locate platform "omp_lwip_platform_master" at our end. Can please point us to that path? Also in Proj_info_5, Edit platform page2 of 2 was shared. Can you please share page 1of 2 ?

Thanks,

Praveen 

Hi Praveen,

Thank you for your help. Here is the page1.

I provided the platform directory in the .rar file. You could put it in the directory shown in page1.

Thanks,

Zhengyang Wang

Hi Zhengyang Wang,

Thanks for sharing the requested information.

We could not able to replicate the reported issue at our end.

When we try to build the shared project as is we got couple build errors and after resolving those errors we could able to get the .out file.

When we try to load the generated .out file on the C6678 EVM, it is going to infinite loop in IPC_attach() function and same is observed when we try to load multiple times.

The below are the build errors we got while building the project as is,
1) Buildfile generation error occurred..
This project was created for a device-variant that is not currently recognized: TMS320C66XX.TMS320C6678. Please install the device-variant descriptor, or migrate the project to one of the supported device-variants by adjusting project properties.
Build stopped..
To remove this error: We have changed the Device variant type to - Generic C66x Device

2)"../system/resourcemgr.c", line 797: error: argument of type "Cppi_GlobalConfigParams (*)[3]" is incompatible with parameter of type "Cppi_GlobalConfigParams *"
To remove this error:
result = Cppi_init (&cppiGblCfgParams);
is changed to
result = Cppi_init (&cppiGblCfgParams[0]);

Can you please comment on our observations and help us to replicate the issue

Thanks,
Praveen