• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1145 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.

CCS v 5.2.1.00018 cannot load full debug code in simulator mode

Robert W
Mastermind 7100 points

Hi,

Today CCS 5.2.1.00018 makes me frustrating. It is first in debug mode. Then, I change it to release mode after I change the Debugging  model to skeletal. Now, I cannot change back to full debug mode, no matter to Debug or Release options. At the Debugging configuration option, the Program menu/Project, Program options cleared, reselected, no change to the problem. I also delete Debug and Release folders, recompile, relaunch, it also fails.

What is wrong with the project?

Thanks,

  • 0
    Mastermind 7100 points

    Hi,

    The PC is Windows 7, 64 bit. The CCS is bundled with C6678. The simulator is cycle accurate C6678 simulator.

  • 0
    TI__Guru**** 475621 points

    Hi Robert,

    Robert W said:
    It is first in debug mode. Then, I change it to release mode after I change the Debugging  model to skeletal.

    What exactly did you do here? Did you explicitly change the active build configuration? Or did you change the compiler options? Or both?

    Please provide exact step-by-step details on what you did. The more details, the better. If you can attach a small test case project, even better.

    Thanks

    ki

  • 0 in reply to Ki
    Mastermind 7100 points

    Hi,

    The debug option is set as:

    When I launch debugger, the "Debug" (not  release mode) has the "_auto_init_elf() at autoinit.c:110 0x0000D910 (_auto_init_elf has only skeletal debug info). It is not the general main() function for full symbol debug simulator (not yet EVM board download).

    The Console window has the info as:

    What do you find on the debug symbol info from the Console?

    I do not know why the debug only sticks to skeletal mode although it compiles with Full symbol info settings.

    Thanks,

    What is the meaning of /F in 

    DEL /F  "C64P_viterbi_C.out"?

    The project is in Drive C, not F.

    ...........

    **** Clean-only build of configuration Debug for project C64P_viterbi_C ****

    "C:\\ti\\ccsv5\\utils\\bin\\gmake" -j4 -k clean
    DEL /F "C64P_viterbi_C.out"
    Could Not Find C:\Users\Jeff\workspace_v5_1_Viterbi\C64P_viterbi_C\Debug\C64P_viterbi_C.out
    DEL /F "C64p_Viterbi_t.pp"
    Could Not Find C:\Users\Jeff\workspace_v5_1_Viterbi\C64P_viterbi_C\Debug\C64p_Viterbi_t.pp
    DEL /F "C64p_Viterbi_t.obj" "vit_C64p.obj"
    Could Not Find C:\Users\Jeff\workspace_v5_1_Viterbi\C64P_viterbi_C\Debug\C64p_Viterbi_t.obj
    DEL /F "vit_C64p.pp"
    Could Not Find C:\Users\Jeff\workspace_v5_1_Viterbi\C64P_viterbi_C\Debug\vit_C64p.pp
    'Finished clean'
    ' '

    **** Build Finished ****

    **** Build of configuration Debug for project C64P_viterbi_C ****

    "C:\\ti\\ccsv5\\utils\\bin\\gmake" -j4 -k all
    'Building file: ../C64p_Viterbi_t.c'
    'Building file: ../vit_C64p.sa'
    'Invoking: C6000 Compiler'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6600 --abi=eabi -g --include_path="C:/ti/ccsv5/tools/compiler/c6000_7.4.1/include" --display_error_number --diag_warning=225 --diag_wrap=off --preproc_with_compile --preproc_dependency="C64p_Viterbi_t.pp" "../C64p_Viterbi_t.c"
    'Invoking: C6000 Compiler'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6600 --abi=eabi -g --include_path="C:/ti/ccsv5/tools/compiler/c6000_7.4.1/include" --display_error_number --diag_warning=225 --diag_wrap=off --preproc_with_compile --preproc_dependency="vit_C64p.pp" "../vit_C64p.sa"
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "x" was declared but never referenced
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "h" was declared but never referenced
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "Nh" was declared but never referenced
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "Ny" was declared but never referenced
    "../C64p_Viterbi_t.c", line 43: warning #179-D: variable "y" was declared but never referenced
    "../C64p_Viterbi_t.c", line 51: warning #179-D: label "for_0" was declared but never referenced
    'Finished building: ../vit_C64p.sa'
    'Finished building: ../C64p_Viterbi_t.c'
    ' '
    ' '
    'Building target: C64P_viterbi_C.out'
    'Invoking: C6000 Linker'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6600 --abi=eabi -g --display_error_number --diag_warning=225 --diag_wrap=off -z -m"C64P_viterbi_C.map" -i"C:/ti/ccsv5/tools/compiler/c6000_7.4.1/lib" -i"C:/ti/ccsv5/tools/compiler/c6000_7.4.1/include" --reread_libs --warn_sections --display_error_number --diag_wrap=off --rom_model -o "C64P_viterbi_C.out" "./vit_C64p.obj" "./C64p_Viterbi_t.obj" -l"libc.a"
    <Linking>
    warning #10247-D: creating output section ".metrics" without a SECTIONS specification
    warning #10210-D: creating ".stack" section with default size of 0x400; use the -stack option to change the default size
    'Finished building target: C64P_viterbi_C.out'
    ' '

    **** Build Finished ****

  • 0 in reply to Robert W
    TI__Guru**** 475621 points

    Your second screenshot is showing that autoinit.c was compiled with skeletal debug. Where is that file coming from? A library? because I don't see as one of the two files compiler below:

    Robert W said:

    **** Build of configuration Debug for project C64P_viterbi_C ****

    "C:\\ti\\ccsv5\\utils\\bin\\gmake" -j4 -k all
    'Building file: ../C64p_Viterbi_t.c'
    'Building file: ../vit_C64p.sa'
    'Invoking: C6000 Compiler'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6600 --abi=eabi -g --include_path="C:/ti/ccsv5/tools/compiler/c6000_7.4.1/include" --display_error_number --diag_warning=225 --diag_wrap=off --preproc_with_compile --preproc_dependency="C64p_Viterbi_t.pp" "../C64p_Viterbi_t.c"
    'Invoking: C6000 Compiler'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6600 --abi=eabi -g --include_path="C:/ti/ccsv5/tools/compiler/c6000_7.4.1/include" --display_error_number --diag_warning=225 --diag_wrap=off --preproc_with_compile --preproc_dependency="vit_C64p.pp" "../vit_C64p.sa"
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "x" was declared but never referenced
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "h" was declared but never referenced
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "Nh" was declared but never referenced
    "../C64p_Viterbi_t.c", line 42: warning #179-D: variable "Ny" was declared but never referenced
    "../C64p_Viterbi_t.c", line 43: warning #179-D: variable "y" was declared but never referenced
    "../C64p_Viterbi_t.c", line 51: warning #179-D: label "for_0" was declared but never referenced
    'Finished building: ../vit_C64p.sa'
    'Finished building: ../C64p_Viterbi_t.c'
    ' '
    ' '
    'Building target: C64P_viterbi_C.out'
    'Invoking: C6000 Linker'
    "C:/ti/ccsv5/tools/compiler/c6000_7.4.1/bin/cl6x" -mv6600 --abi=eabi -g --display_error_number --diag_warning=225 --diag_wrap=off -z -m"C64P_viterbi_C.map" -i"C:/ti/ccsv5/tools/compiler/c6000_7.4.1/lib" -i"C:/ti/ccsv5/tools/compiler/c6000_7.4.1/include" --reread_libs --warn_sections --display_error_number --diag_wrap=off --rom_model -o "C64P_viterbi_C.out" "./vit_C64p.obj" "./C64p_Viterbi_t.obj" -l"libc.a"
    <Linking>
    warning #10247-D: creating output section ".metrics" without a SECTIONS specification
    warning #10210-D: creating ".stack" section with default size of 0x400; use the -stack option to change the default size
    'Finished building target: C64P_viterbi_C.out'
    ' '

    **** Build Finished ****

    It that source file is not part of your project, it explains why your changing of the build options for C64P_viterbi_C is not having any effect.

    ki

  • 0 in reply to Ki
    TI__Guru**** 475621 points

    I'm guessing it is coming from the runtime library since you are not linking in any other libraries. If you halt when the program is in the actual source file of your project, do you have full debug visibility?