• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 377 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.

CCSV4 issue with binary output folder

dive
Prodigy 190 points

Other Parts Discussed in Thread: MSP430F2370

Hi,

I often see the problem below which is a little annoying.

Please let me know if you need more information.

Thanks.

 

Problem: the code generation output folder sometimes cannot be accessed any more (This folder has the same name as the project configuration being built)

FYI, I've put a . in front of my configuration names so that the output folder does not appear in the project explorer view of CCSv4 IDE (e.g. one of my configurations is named ".Bootloader")

Symtoms are:

1) The project refuses to build. I often see that kind of compiler error:

C:\Program Files\Texas Instruments 2\ccsv4\utils\gmake\gmake: *** No rule to make target `_bootloader/BootLoader.obj'.  Stop. MSP-Dev Unknown 1242805916428 69386

2) In Windows explorer, trying to delete the output folder results in the following error:
"Destination Folder Access Denied - You need permission to perform this action."

Workaround:

Rename the project configuration and rebuild the project. This works, but the old output folder still persists and is still undeletable until machine reboot.

 

Environment:

Code Composer Studio  Version: 4.0.0.14000

Code Generation Tools 3.1.0

Windows VISTA SP1

Target : MSP430F2370, using MSP-FET430UIF debug interface

Compiler options:

$(GEN_OPTS_QUOTED) --define=BOOTLOADER --fp_reassoc=off --include_path="C:/Program Files/Texas Instruments 2/ccsv4/msp430/include" --include_path="C:\Users\sdivito\Documents\__DEV\code_composer_studio_workspace\MSP-Dev" --include_path="C:\Users\sdivito\Documents\__DEV\code_composer_studio_workspace\MSP-Dev/_bootloader" --include_path="C:\Users\sdivito\Documents\__DEV\code_composer_studio_workspace\MSP-Dev/include" --include_path="C:/Program Files/Texas Instruments/CC Essentials v3.1/tools/compiler/MSP430/include" --keep_asm --sat_reassoc=off --symdebug:dwarf --gen_acp_raw --gen_acp_xref --no_inlining --diag_error=225 --diag_warning=238 --issue_remarks --plain_char=unsigned --silicon_version=msp --auto_inline=0 --opt_for_speed=0 --opt_level=3 --optimize_with_debug --optimizer_interlist --remove_hooks_when_inlining --single_inline --printf_support=minimal

Linker options:

--absolute_exe --reread_libs --use_hw_mpy=16 --warn_sections --search_path="C:/Program Files/Texas Instruments/CC Essentials v3.1/tools/compiler/MSP430/lib" --search_path="C:/Program Files/Texas Instruments/CC Essentials v3.1/tools/compiler/MSP430/include" --generate_dead_funcs_list=deads.txt --map_file="map.txt" --undef_sym=RestoreBoot --rom_model --heap_size=0 --stack_size=256

 

  • 0
    TI__Guru**** 163035 points

    Sorry for the late answer on this one but we have some more info on this now.

    We are changing the installer to warn Win 7 and Vista users that if installing in program files that UAC needs to be off and you need admin privs.  These OSs really don't think things writing to program files which CCS does.

    People seem to have problems with removing folders with "." in front of them.  We advise not creating config names like this.  As far as how to remove them afterwards you will need to make sure that CCS is full closed (take a peak in task manager as well for javaw) and that you have the necessary privs to delete in that folder.

     

    John