• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 536 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

fatal error for h263 decoder with CCS v5.2.1

Xin Li2
Prodigy 30 points


Hi,

I am developing the h.263 decoder with the CCS v5.2.1. When I imported and built the TI's example project "c66x_m4h3dec_02_03_00_01_ELF", I got the following errors:

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

warning: relocation to symbol "ECPY_directStartEdma" overflowed; the 22-bit relocated address 0x10f49e is too large to encode in the 21-bit signed PC-Relative field (type = 'R_C6000_PCR_S21' (4), file = "...\Lib\m4h3dec_ti_le66", offset = 0x000209b8, section = ".text: M4H3DEC_TI_cSect1")

warning: relocation to symbol "ECPY_directConfigure" overflowed; the 22-bit relocated address 0x10f49e is too large to encode in the 21-bit signed PC-Relative field (type = 'R_C6000_PCR_S21' (4), file = "...\Lib\m4h3dec_ti_le66", offset = 0x0002f4ec, section = ".text: M4H3DEC_TI_cSect1")

DIAG/user_msg_api.c: 211: internal fatal error #99926: (ofile_error_handler(): TestAppDecoder.out: illegal operation: writing 0x1ffff384 bytes to offset 0x0 in section ".text" exceeds its formatted size (0xa6360))
Internal ERROR: C:\ti\ccsv5\tools\compiler\c6000_7.3.4\bin\lnk6x.exe aborted.

This is a serious problem.  Please contact Customer Support with this message and a copy of the input file and help us to continue to make the tools more robust.

However, the example project runs successfully with CCS v4.

Please help me.

Thanks and Best regards!



  • 0
    TI__Guru* 84285 points

    You may be suffering from SDSCM00045612, which causes the mesage "exceeds its formatted size."  There is no known workaround for this problem.

    You should try to correct the relocation overflows first; perhaps that will change the program enough to make the error go away.  Relocation R_C6000_PCR_21 is only used for branches and calls.  Are trampolines enabled in your project?

  • 0 in reply to Archaeologist
    Prodigy 30 points

    How to correct the relocation overflows? 

    I am wondering why the decoder is correct with CCS v5.0.1 but failed with CCS v5.2.1.  I think there may be some incompatible problems.

    So, can you simulate the h263 decoder with CCS v5.2.1? 

  • 0 in reply to Xin Li2
    TI__Guru* 84285 points

    In order to fix the relocation overflows, we need figure out why they are occurring.

    There could be many things that changed between your project on CCS 5.0.1 and CCS 5.2.1, most importantly the compiler version.  In the case of 5.2.1, you are using C6000 compiler version 7.3.4 (it is shown in the error message above.)  What version of the C6000 compiler are you using inside CCS 5.0.1?

  • 0 in reply to Archaeologist
    Prodigy 30 points

    Thanks for your reply.

    The compiler version is 7.2.1 inside CCS 5.0.1. I have compiled the project using the compiler version 7.2.1 on CCS 5.2.1, then it became successful. Does this means that the h263 decoder is not compatible with the newer compiler?

    Next, I build a new project using the original head files, source files and library files on CCS 5.2.1 with compiler version 7.2.1. There are several other errors as follows:

    ERROR: Cannot open command file './configPkg/compiler.opt': No such file or directory

    "C:/ti/framework_components_3_20_02_29/fctools/packages/xdc/std.h", line 76: fatal error: #error xdc_target_types_ must be defined to name a target-specific head containing definitions of xdc_Int8, xdc_Int16,...

    1 fatal error detected in the compilation of "../Repository/Packages/ti/platforms/custom66x/package/package_ti.platforms.custom66x.c"
    compilation terminated.

    I find that the file "compiler.opt'" is generated during the process of project building. Then what is the problem?