• TI Thinks Resolved

Compiler/TDA2: When will the visionSDK3 's cgtc6000 compiler upgrade to v8.x.x ?

Part Number: TDA2

Tool/software: TI C/C++ Compiler

The cgtc6000 comiler v7.4.2 is used in the latest visionSDK3.05. The v7.4.2 comiler is not enough for our project, the v8.x.x is OK.

In below thread,

e2e.ti.com/.../715156

Rishabh Garg  told me that the visionSDK3.05 will upgrade cgtc6000 comiler to v8.x.x two month ago.

But visionSDK 3.05 still use v7.4.2 when it was released.

So when will visionSDK upgrade cgtc6000 compiler to v8.x.x?

  • Hi Bao,

    CGT change was planned for the 03.05 release.
    I will get back to you with details.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    Hi Bao,

    There were some issues due to which we could not change the compiler to 8.x.
    You can compile your algorithm with 8.x compiler and link the library with Vision SDK which is built using 7.4.2.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    Dear Rishabh,
    Thanks for your reply.
    We tried use v8.1.3 comiler compile our algorithm and link the library with vision SDK which is built using v7.4.2. We got the binary file.
    But the DSP2 program was crashed when the system is startup before main() function was called.
    The detail of this issue was descriped in the orignal thread.
  • In reply to Bao Shang:

    Hi Bao,

    The original question mentions that you have build SDK also with v8.1.3 compiler.
    Also we are trying to upgrade to 8.2.4 compiler.
    With this version we have not seen any crash.
    As an experiment can you try this version.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    OK, I will try it later。
  • In reply to Bao Shang:

    Hi Bao,

    Do let me know in case you face any issues.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    Hi Rishabh,
    As your suggestion,
    I comile our algorithm by v8.2.4 comiler and link the library with Vision SDK which is built using 7.4.2.
    The issue still exist. The system can't startup properly.
    Our algorithm refer comlex c++ .
    I debug it , the dsp program crashed in __c_init00, which do some initialization for the program.
    If I comment off the c++ related function calls from our algorithm, the system startup properly.
  • In reply to Bao Shang:

    Hi Bao,

    Can you please debug it further and see what are the exact instructions that are causing DSP to crash.
    It might be an issue with some compiler options.

    Regards,
    Rishabh
  • In reply to Rishabh Garg:

    Hi Rishabh,

       When I debug it:

       (1) I set a break point at "_c_int00" for DSP2.

       (2)  I load the DSP2 exectable file "vision_sdk_c66xdsp_2_release.xe66".

              The CCS show :    Can't find a source file at "/db/ztree/library/trees/xdctargets/xdctargets-l07/src/ti/targets/rts6000/boot.c"

              I locate the path as "PROCESSOR_SDK_VISION_03_05_00_00\ti_components\os_tools\bios_6_46_04_53\packages\ti\targets\rts6000"

       (3) Then debug step by step to fuction "_auto_init_elf",  I just see the program crashed at below code seciotns, and crashed at function "memcpy" :

       if (!(&__TI_Handler_Table_Base >= &__TI_Handler_Table_Limit))

      {

         table_ptr   = (unsigned char**) &__TI_CINIT_Base;

         table_limit = (unsigned char**) &__TI_CINIT_Limit;

         while (table_ptr < table_limit)

         {

           unsigned char* load_addr  = *table_ptr++;

           unsigned char* run_addr   = *table_ptr++;

           unsigned char handler_idx = *load_addr++;

           handler_fptr handler      = (handler_fptr)(&HANDLER_TABLE)[handler_idx];

           (*handler)((const unsigned char*)load_addr, run_addr);

         }

      }

    Exception at 0x857ad40c

    857ad380    000000a0     rts6600_elf.lib : memcpy64.obj (.text:memcpy)
    857ad420    000000a0                     : modf.obj (.text:modf) 

       (4) Once time , I see the program crashed after execute " table_limit = (unsigned char**) &__TI_CINIT_Limit;", maybe due to the symbol not match.

       (5) I attach the AppImage and vision_sdk_c66xdsp_2_release.xe66.  You could try on your board, the DDR size is 1G.

    executable file.rar

  • In reply to Bao Shang:

    Hi Bao,

    Unfortunately the person who is working on CGT migration is out of office this week.
    Kindly expect a slight delay in response.

    Regards,
    Rishabh