• State
  • Replies 11 replies
  • Subscribers 39 subscribers
  • Views 396 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CODECOMPOSER: CCS v12: Various Errors with New (empty) Projects and Likewise with Sample Projects

TI-CSC
Genius 15200 points

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: MSPM0C1104, SYSCONFIG

Hello E2E Experts,

I use CCS v12 (after unsuccessful installation attempts of Theia on my Win7) and I try to get started.

See below what I get when compiling a new project. The missing "driverlib.a" is in the location of the path stated in the error message.

Invoking: GNU Linker
"C:/Firmware/Tools/TI/CCS_v1281/gcc_arm_none_eabi_9_2_1/bin/arm-none-eabi-gcc-9.2.1.exe" -D__MSPM0C1104__ -Og -g -gdwarf-3 -gstrict-dwarf -Wall -specs="nosys.specs" -Wl,-Map,"Just2SortOut.map" -o"Just2SortOut.out" "./main.o" "./startup_mspm0c110x_gcc.o" -Wl,-T"../mspm0c1104.lds"  -Wl,--start-group "/source/ti/driverlib/lib/gcc/m0p/mspm0c110x/driverlib.a" -Wl,--end-group 
makefile:138: recipe for target 'Just2SortOut.out' failed
arm-none-eabi-gcc-9.2.1.exe: error: /source/ti/driverlib/lib/gcc/m0p/mspm0c110x/driverlib.a: No such file or directory

 

Similar result with a project I imported via the Project Wizard:

I"C:/Firmware/Tools/TI/CCS_v1281/mspm0_sdk_2_09_00_01/source" -I"C:/Firmware/Tools/TI/CCS_v1281/gcc_arm_none_eabi_9_2_1/arm-none-eabi/include/newlib-nano" -I"C:/Firmware/Tools/TI/CCS_v1281/gcc_arm_none_eabi_9_2_1/arm-none-eabi/include" -O2 -ffunction-sections -fdata-sections -g -gdwarf-3 -gstrict-dwarf -Wall -MMD -MP -MF"timx_timer_mode_capture_duty_and_period.d_raw" -MT"timx_timer_mode_capture_duty_and_period.o" -std=c99  -o"timx_timer_mode_capture_duty_and_period.o" "../timx_timer_mode_capture_duty_and_period.c"
subdir_rules.mk:9: recipe for target 'timx_timer_mode_capture_duty_and_period.o' failed
arm-none-eabi-gcc-9.2.1.exe: error: device.opt: No such file or directory

Where is the mistake?

  • 0
    TI__Expert 4680 points

    Hi TI-CSC,

    Is your system 64-bit? CSCv12 is not compatible with 32-bit windows systems. Additionally, can you make sure you have the latest versions of the SDK and GNU compiler? Did you have issues with the initial install of CCSv12? It may also be worth doing a fresh install of that as well.

    Best regards,
    Brian

  • 0 in reply to Brian Lee
    TI__Genius 15200 points

    Hello Brian,

    I tried a fresh installation on a different PC with Win7 64-bit. No errors during installation, no success, same result (in all aspects the same situation as before).

    I installed CCS v12 on a PC with Win10 64-bit ... surpise, it works. I can load and compile example projects.

    So, I copied both the successful installation AND the workspace (maintaining identical directory paths) to my Win7 64-bit.

    And here it gets spooky: same error as before !!!

    subdir_rules.mk:9: recipe for target 'gpio_toggle_output.o' failed
    tiarmclang: error: no such file or directory: '@device.opt'
    gmake: *** [gpio_toggle_output.o] Error 1

    It appears as if the "recipe" is taken from somewhere else: neither installation directories nor workspace directories ... ???

    I wonder if you have an idea.

    Regards,

    TICSC

  • 0 in reply to TI-CSC
    TI__Expert 4680 points

    Hi TICSC,

    I have consulted a member of our tools team for further assistance and will update you with their response.

    Best Regards,
    Brian

  • 0 in reply to TI-CSC
    TI__Guru**** 476461 points
    TI-CSC said:

    subdir_rules.mk:9: recipe for target 'gpio_toggle_output.o' failed
    tiarmclang: error: no such file or directory: '@device.opt'
    gmake: *** [gpio_toggle_output.o] Error 1

    device.opt should get generated from sysconfig during the build process and should get generated in the build configuration subfolder like "Debug". If the compiler is unable to find it then it sounds like it was not generated. Were there any build issues when the sysconfig file was build? Can you copy&paste to a text file all the messages in the build output window and attach it to this thread?

    Thanks

    ki

  • 0 in reply to Ki
    TI__Genius 15200 points

    Hello Ki,

    I enclose four text-files for your analysis (and I provide anything more that you need).
     
    The map-files are identical. 
    The build-ouput files show the difference in line 8:
     
        only the Win7 build-ouput has this entry (near the end of line 8):    @"./device.opt"
     
    I wonder how this entry gets here, since the installation of CCS v12 which I run on Win7 is the copied installation (including SDK) of the Win10 computer, copied while maintaining all paths identical on both computers. Likewise, also the two workspaces have identical paths.
    Regards,
    TICSC
  • 0 in reply to TI-CSC
    TI__Genius 15200 points

    Hello Ki,

    Any updates for us so far?

    Regards,

    TICSC

  • 0 in reply to TI-CSC
    TI__Expert 4680 points

    Hi TICSC,

    Our Software and Tools teams are investigating the issue further. Updates will continue to be posted here as they become available.

    Best Regards,
    Brian

  • 0 in reply to TI-CSC
    TI__Expert 4680 points

    Hi TICSC,

    Sorry for the delayed response. The teams are still looking into this internally but gave the following feedback in the meantime:

    1. Is the device.opt file being generated on the windows 7 version? it should be seen on the generated files list.
    2. If the file is generated but not picked up by the tool, can you try manually adding the symbols on the project properties->build->compiler->pre-defined symbols settings?

    Best Regards,
    Brian

  • 0 in reply to Brian Lee
    TI__Genius 15200 points

    Hello Brian,

    The file device.opt is NOT generated, and in general the debug folder on Win7 is rather depleted in comparison with Win10.
    The enclosed archive shows the file lists of both environments.
     
    I added two files manually from Win10 to Win7 to see if I get any further:
     
       device.opt
       gpio_toggle_output_LP_MSPM0C1104_nortos_ticlang.out
     
    The compilation result thereafter is included but does not get me anywhere.
    Regards,
    TICSC
  • 0 in reply to TI-CSC
    TI__Expert 4680 points

    Hi TICSC,

    Thank you for confirming the file is not being generated. Can you also do a clean build and attach the entirety of the build output to this thread? This will tell us if SysConfig is called, where it's told to generate to, and where the compiler is asked to look.

    Best Regards,
    Brian

  • 0 in reply to Brian Lee
    TI__Genius 15200 points

    Hello Brian,

    I enclose the results after doing a "clean" command. The build started thereafter automatically.

    gpio_toggle_output_LP_MSPM0C1104_nortos_ticlang (clean-build Win7).rar

    Fullscreen Clean-Build Win7.txt Download 
    **** Clean-only build of configuration Debug for project gpio_toggle_output_LP_MSPM0C1104_nortos_ticlang ****

"C:\\Firmware\\Tools\\TI\\CCS_v1281\\ccs\\utils\\bin\\gmake" -k -j 4 clean -O 
 
DEL /F  "gpio_toggle_output_LP_MSPM0C1104_nortos_ticlang.out" 
DEL /F "gpio_toggle_output.o" 
DEL /F "gpio_toggle_output.d" 
C:\Firmware\Work\CCSv12\gpio_toggle_output_LP_MSPM0C1104_nortos_ticlang\Debug\gpio_toggle_output_LP_MSPM0C1104_nortos_ticlang.out konnte nicht gefunden werden
Finished clean
 

**** Build Finished ****

    Regards,

    TICSC