• State Resolved
  • Locked Locked
  • Replies 13 replies
  • Subscribers 84 subscribers
  • Views 342 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28374S: CS2619666 TMS320F28374S: Debug Error with TMS320F28374S and Request for Assistance

Cheng YuLong
Prodigy 20 points
Part Number: TMS320F28374S
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Dear Sir or Madam,

I am encountering an issue while debugging a project using the TMS320F28374S microcontroller. During debugging, I receive the following error message:

"No source available for '_system_post_cinit() at D:\LLCDebugProblem\EVDP-UA603W0001_LLC_S0.01T25\Debug\EVDP-UA603W0001_LLC_S0.01T25.out:{3} 0x3fe493{4}'"

The compiler version used is TIv20.2.5.LTS. We have taken the following actions to address this issue:

  1. Switching the compiler version to TIv22.6.1LTS (with optimization level set to 'off') also resolves the problem and enables normal debugging.

Additionally, debugging can proceed into the main function; however, after initializing the EEPROM, just before initializing the Flash, the debug process encounters an error and cannot continue further.

I need assistance with the following:

  1. The root cause of this issue.

Currently, we speculate that our company's encryption software might be causing file parsing errors, and the newer compiler version (TIv22.6.1LTS) may have implemented isolation measures for these files. However, we do not have concrete evidence to support this theory. We sincerely request assistance from TI engineers.

Additionally, I have attached relevant screenshots of the settings for your reference.

Best Regards,

Cheng Yulong

  • 0
    TI__Genius 13701 points

    Hi Cheng,

    Thank you for reaching out. I think your screenshots didn't get included in the original message, can you try reattaching them?

    What version of CCS are you using for your testing?

    There have been quite a number of compiler updates in between TIv20.2.5.LTS and TIv22.6.1LTS. To help narrow down the change that is causing the debugger to work correctly, are you able to test other compiler versions? It may be good to test 21.6.0 as that will help to narrow down the exact compiler change.

    Also in your linker command file, are you using the generic linker command files from the C2000WARE SDK or are you using a custom .cmd? If custom, can you review the linker file to make sure that you are correctly allocating the memory for the device? You may want to compare with the generic .cmd files from the SDK to make sure

    Regards,

    Peter

  • 0 in reply to Peter Luong1
    Prodigy 20 points

    Hi Peter,

    Here are the screenshots related to the debug configuration:

    the CCS version is:12.6.0.

    TIv21.6.0.LTS still has this issue, so the scope has been narrowed down to between versions TIv21.6.0.LTS and TIv22.6.1LTS.

    Here is the cmd configuration file:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    MEMORY
    {
    PAGE 0: /* Program Memory */
    PAGE 1: /* Data Memory */
    ACCESSPROTECTION : origin = 0x0005F4C0, length = 0x00000040
    ADCA : origin = 0x00007400, length = 0x00000080
    ADCB : origin = 0x00007480, length = 0x00000080
    ADCC : origin = 0x00007500, length = 0x00000080
    ADCD : origin = 0x00007580, length = 0x00000080
    ADCARESULT : origin = 0x00000B00, length = 0x00000018
    ADCBRESULT : origin = 0x00000B20, length = 0x00000018
    ADCCRESULT : origin = 0x00000B40, length = 0x00000018
    ADCDRESULT : origin = 0x00000B60, length = 0x00000018
    ANALOGSUBSYS : origin = 0x0005D180, length = 0x00000048
    CANA : origin = 0x00048000, length = 0x00000200
    CANB : origin = 0x0004A000, length = 0x00000200
    CLA1 : origin = 0x00001400, length = 0x00000080
    CLB1DATAEXCH : origin = 0x00003200, length = 0x00000200
    CLB2DATAEXCH : origin = 0x00003600, length = 0x00000200
    CLB3DATAEXCH : origin = 0x00003A00, length = 0x00000200
    CLB4DATAEXCH : origin = 0x00003E00, length = 0x00000200
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Regards,

    Cheng Yulong

  • 0 in reply to Peter Luong1
    Prodigy 20 points

    I have further narrowed down the scope of the compilation issue. There is a problem with TIv21.6.1.LTS, but TIv21.12.0.LTS works fine. Could you please help me identify the differences between these two compiler versions? Thank you very much.

  • 0 in reply to Cheng YuLong
    TI__Genius 13701 points

    Hi Cheng,

    Please see the following change log for the TIv21.12.0.LTS: https://software-dl.ti.com/codegen/esd/cgt_public_sw/C2000/21.12.0.STS/README.html

    I don't see anything that could possibly lead to the debug not working in previous revisions of the CGT so I'm thinking it's also likely to do with the CCS version you are using is a newer CCS and tested with the newer compiler versions.

    Regards,

    Peter

  • 0 in reply to Peter Luong1
    Prodigy 20 points

    Hi Peter,

    I have conducted the same experiment using Code Composer Studio 11.2.0 and Code Composer Studio 12.8.1, alongside Code Composer Studio 12.6.0, using the same codebase but in three different workspaces. The experimental results show that the debug issue occurs when using the TIv21.6.1.LTS compiler version, whereas no such debug issues are present when using the TIv21.12.0.LTS compiler version. Therefore, I believe that this issue is not related to the CCS version but is solely associated with the compiler version.

    Please continue to help me identify the cause. Thank you very much.

    Regards,

    Cheng

  • 0 in reply to Cheng YuLong
    TI__Genius 13701 points

    Hi Cheng,

    I reviewed the changelog for the compiler version and I don't see any specific reference to a compiler change that result in a different debug behavior. I will reach back out to the compiler team to provide insight once they have returned from the holiday break

    Regards,

    Peter

  • 0 in reply to Peter Luong1
    Prodigy 20 points

    Hi Peter,

    Thank you very much for your help！

    Regards,

    Cheng

  • 0 in reply to Cheng YuLong
    TI__Genius 13701 points

    Hi Cheng,

    Hope you have a happy new year. I am reaching out to our compiler to team to find out more information about the TIv21.12.0.LTS compiler version to get additional information

    Regards,

    Peter

  • 0 in reply to Peter Luong1
    TI__Guru**** 449111 points

    Hello,

    I have brought this thread to the attention of the compiler experts. Due to the current holiday time, it may be a few days before an update is available.

    Thank you

    ki

  • 0
    TI__Guru**** 449111 points
    Cheng YuLong said:
    "No source available for '_system_post_cinit() at D:\LLCDebugProblem\EVDP-UA603W0001_LLC_S0.01T25\Debug\EVDP-UA603W0001_LLC_S0.01T25.out:{3} 0x3fe493{4}'"

    For an explanation of the message, please see:

    https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers-group/c2000/f/c2000-microcontrollers-forum/1041655/tms320f28379d-no-source-available-for-_system_post_cinit-error-when-debugging-my-code/3852614#3852614

    The real issue is why you are getting stuck there. I don't have an answer for that one.

  • 0 in reply to Ki
    TI__Genius 13701 points

    Hi Cheng,

    I discussed with our compilers team. They mentioned that there is no change in the specific compiler version which necessarily addresses the issue you are facing. Different compiler versions put functions and data in memory in different places, so it cannot be deterministically understood the exact issue you are seeing just because of the compiler version

    Comment I received from the team is that there is likely some system issue/exception occurring in your code which needs to be resolved and can only be noticed in your code with older compiler version

    Regards,

    Peter

  • 0 in reply to Peter Luong1
    Prodigy 20 points

    Hi Peter and Ki:

    I have reviewed the link you sent me, and indeed, the issue was resolved after switching the compiler version. However, I have a concern that I need your help to confirm: since this problem only manifests during debugging, with compilation and linking proceeding normally, I am worried about whether there might be any issues with the generated binary files.

    Regards,

    Cheng

  • +1 in reply to Cheng YuLong
    TI__Genius 13701 points

    Hi Cheng,

    Understood, like mentioned previously, there may be some system-level issue in your code which is independent of the compiler and would require testing/evaluation of project files. This causes the source to not be found on different compiler versions. Since this is not necessarily a result of the compiler but of the codebase, then there is a chance that future changes in the compiler may reintroduce this error to your project depending on where compiler will be allocating parts of the code in memory. For the compiler versions you have tested successfully, if there is no error thrown during debugging, I don't consider there is a issue necessarily with the binary file but still there could be error with code

    Regards,

    Peter