• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 53 subscribers
  • Views 4028 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.

Compiler/LAUNCHXL-F28377S: Compiler/LAUNCHXL-F28377S

Wayne Hunter
Intellectual 340 points

Part Number: LAUNCHXL-F28377S

Tool/software: TI C/C++ Compiler

I get the following error message.  I checked for updates in the app center and it said that the compiler was up to date.  I have made no changes to the software.

**** Build of configuration F2837x_RAM for project MonoMtrServo_377s ****

"C:\\ti\\ccsv7\\utils\\bin\\gmake" -k all
'Building file: ../MonoMtrServo.c'
'Invoking: C2000 Compiler'
"C:/ti/ccsv7/tools/compiler/ti-cgt-c2000_16.9.1.LTS/bin/cl2000" -v28 -ml -mt --float_support=fpu32 --tmu_support=tmu0 --cla_support=cla0 --vcu_support=vcu2 -O1 --opt_for_speed=5 --fp_mode=relaxed --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-c2000_16.9.1.LTS/include" --include_path="C:/Users/hunte/workspace_v7/MonoMtrServo_377s/utility Src Files" --include_path="C:/ti/controlSUITE/device_support/F2837xS/v170/F2837xS_headers/include" --include_path="C:/ti/controlSUITE/device_support/F2837xS/v170/F2837xS_common/include" --include_path="C:/ti/controlSUITE/libs/app_libs/motor_control/math_blocks/v4.3" --include_path="C:/ti/controlSUITE/libs/math/IQmath/v160/include" --advice:performance=all -g --define="_DEBUG" --define="CPU1" --define="LARGE_MODEL" --quiet --diag_warning=225 -k --asm_listing --preproc_with_compile --preproc_dependency="MonoMtrServo.d" --tmu_support=tmu0  "../MonoMtrServo.c"

>> Compilation failure
subdir_rules.mk:86: recipe for target 'MonoMtrServo.obj' failed

INTERNAL ERROR: C:\ti\ccsv7\tools\compiler\ti-cgt-c2000_16.9.1.LTS\bin\cg2000.exe experienced a segmentation fault
                  while processing function _MotorControlISR

This is caused by a defect in the compiler itself. TI Customer
Support may be able to suggest a workaround to avoid this.

Upgrading to the newest version of the compiler may fix this problem.

Contact TI in the E2E support forums at http://e2e.ti.com under
"Development Tools", "TI C/C++ Compiler". See the link titled
"Submitting an issue". Include this ENTIRE error message and a
copy of the .pp file created when option --preproc_with_comment
(-ppc) is used.

gmake: *** [MonoMtrServo.obj] Error 1
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

  • 0
    TI__Guru**** 232900 points

    Thank you for notifying us of this problem.  I can reproduce it.  I filed CODEGEN-2069 in the SDOWP system to have this addressed.  You are welcome to follow it with the SDOWP link below in my signature.

    Thanks and regards,

    -George

  • 0
    TI__Intellectual 2560 points

    Hi Wayne,

    Are you compiling on Windows and if so, which version?  I can't reproduce this error and I'm on a different version of Windows than George, so I'm trying to figure out if the OS version makes the difference.

    Thanks,

    Anna

  • 0 in reply to Anna Youssefi
    Intellectual 340 points

    It was compiled with Windows 10.   It is intermittent.  It works about 1/3 of the time and it makes a difference whether executed  by right clicking the project name > rebuild, clicking the debug icon or other approaches. 

    I keep getting a "This project was created using a version of compiler that is not currently installed 6.4.6 [c2000].  Another version of the compiler will be used."  It is using v6.4.6 [ti v16.9.1.LTS].  Are there compatibility issues?

    Wayne Hunter

  • 0 in reply to Wayne Hunter
    Intellectual 340 points
    I forgot to ask. Is this related?

    Memory Map Initialization Complete
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320
    IcePick_C_0: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x320

    Wayne Hunter
  • 0 in reply to Wayne Hunter
    TI__Guru**** 232900 points

    Wayne Hunter said:
    Is this related?

    No.

    Thanks and regards,

    -George

  • 0 in reply to Wayne Hunter
    TI__Intellectual 2560 points

    Wayne, please try the new patch release (16.9.2.LTS) and see if the problem goes away.  We are still investigating this issue but the only person running Windows 10 here doesn't get the problem on 16.9.2.LTS or releases prior to 16.9.1.LTS.  

    Please let me know if you still experience the problem with 16.9.2.LTS.

    Thanks,

    Anna

  • 0 in reply to Anna Youssefi
    TI__Intellectual 2560 points
    This bug appears to be a duplicate of CODEGEN-1709 which was fixed in 16.9.2.LTS. Please let us know if updating to 16.9.2.LTS does not fix the problem.
    Thanks,
    Anna
  • 0 in reply to Anna Youssefi
    Intellectual 340 points
    No, it did not help but what else is new.
  • 0 in reply to Wayne Hunter
    TI__Guru**** 232900 points

    Then it seems likely you are experiencing a different bug that we have not seen.  

    When I use version 16.9.2.LTS to build the test case I filed in CODEGEN-2069 (the entry I filed in response to your first post), it always works.  So the way I collected that test case could be wrong.  I didn't directly get it from you.  I noticed you were building a source file in a controlSUITE project.  So I built that same project and experienced the problem.  Then I extracted the test case from that.  

    That being the case, to be certain we are building the same code exactly the same way, please directly submit a test case, using these steps.

    1. Preprocess the problem source file
    2. Attach that file to your next post
    3. By copy-n-paste from the CCS console view, show all the build options exactly as the compiler sees them

    Thanks and regards,

    -George

  • 0 in reply to Wayne Hunter
    Intellectual 340 points
    I moved on to another project. I can not wait for weeks until you final decide to respond.

    Wayne Hunter
  • 0 in reply to Wayne Hunter
    TI__Intellectual 2560 points

    Wayne,

    I posted on March 7 that we believed the issue was resolved and asked you to try 16.9.2.LTS to confirm.  We didn't hear back from you until April 25. Therefore, I fail to understand the criticism here.  

    For bugs that are hard to reproduce, we must rely on cooperation from customers experiencing the issue.  I am sorry if the issue has not been resolved to your satisfaction, but we did believe this issue to be resolved within two weeks of your initial post and we had no evidence to the contrary as you did not reply for well over a month and a half.

    Thank you.

    Anna

  • 0 in reply to Anna Youssefi
    Intellectual 340 points
    I am not goiing to waste time trying to reconstruct the details here. If I did not respond it is because I have given up getting timiely response from TI on technical issues. If your group is trying to do better then you deserve to be complimented. IN short I find Ti's technical support polisces disgusting. So I just moved on to a different project. To take a product out of the box and using the software you provide and it doesn't compile makes one wonder about the testing procdedures. I had done nothing to change the software at that point.

    I have noticed one thing that could be part of your problem. The libraries in control suite are used in many projects. I am sure that changes are made to benefit one project while creating problems for previous projects. I understand the to reuse code as much as possible but perhaps the libraries used in a project should be kept together at release to avoid this problem.

    Wayne Hunter