CCS/MSP430FR6989: More on the Load file error (.out file)

Brendan Richart

Tool/software: Code Composer Studio

What happens is that I'll build the project and then press debug and the moment I press debug, it deletes the binary file AND the .out file. I've observed this severe bug on several occasions. How do I get around it?

over 6 years ago

0 Ki over 6 years ago

TI__Guru**** 483601 points

Hello,

Ok, looks like this thread is related to your other thread.

Brendan Richart said:
What happens is that I'll build the project and then press debug and the moment I press debug, it deletes the binary file AND the .out file.

Are you manually doing a build and it is successful (out and binary file is successfully generated) and then when you press debug, it triggers are rebuild where it deletes the out and binary file but the files are not regenerated? If this is the case, please provide all your build output, starting with the successful initial build and the attempted second build.

Thanks

0 Brendan Richart over 6 years ago in reply to Ki

Prodigy 70 points

What happens is I build the project successfully without any errors or warnings and then when I press
debug, the .out file and "Binaries" file gets deleted.

Here's what I noticed tonight, I created a project called 'dummy' which included a main.c with it, built
and ran it before adding any code and it builds successfully. When I take the main.c code from the old project
parse it into the body of the main I get the same error as on the previous project. It doesn't seem to care whether
I format the main.c as either forms seen below as both those forms of main have compiled for me in previous projects
without the loading error we are talking about. It doesn't seem to be the formatting of the main().

int main(void)
{
//Body
return 0;
}

-------OR----------

main()
{
//Body

}

I'm going to try and attach the text file of the code along with the before and after pressing debug of the dummy
project tree. The site seems to be having issues with attaching things at the moment, these weren't issues I had
the first time I reached out.

Thanks again for your help on this bug

0 Ki over 6 years ago in reply to Brendan Richart

TI__Guru**** 483601 points

There are two related threads going on at the same time. Please reply just to the other thread.

Thanks

0 Brendan Richart over 6 years ago in reply to Ki

Prodigy 70 points

Hey Ki, I'll stay on this thread. When you say "provide build" do you mean that I should copy and paste the code or send a screenshot of what is in the folder with each successive mentioned step. I wasn't sure what was meant.

Thanks,

Brendan

0 Ki over 6 years ago in reply to Brendan Richart

TI__Guru**** 483601 points

Brendan Richart said:
When you say "provide build" do you mean that I should copy and paste the code or send a screenshot of what is in the folder with each successive mentioned step.

I was looking for all the build messages in the build console. Copy and paste all the messages in there to a text file and attach the text file. Do it for both the successful and non-successful build.

Also provide the project+source as requested in: https://e2e.ti.com/support/tools/ccs/f/81/p/896277/3316715#3316715

Thanks

0 Brendan Richart over 6 years ago in reply to Ki

Prodigy 70 points

Here's the build - it mentions some kind of error but doesn't flag it in the errors table

**** Build of configuration Debug for project LCD_DisplayWord ****

"D:\\Texas Instruments\\ccsv6\\utils\\bin\\gmake" -k all
'Building file: ../main.c'
'Invoking: MSP430 Compiler'
"D:/Texas Instruments/ccsv6/tools/compiler/ti-cgt-msp430_4.4.3/bin/cl430" -vmspx --abi=eabi --data_model=restricted --use_hw_mpy=F5 --include_path="D:/Texas Instruments/ccsv6/ccs_base/msp430/include" --include_path="D:/TI Projects/LCD_DisplayWord/driverlib/MSP430FR5xx_6xx" --include_path="D:/Texas Instruments/ccsv6/tools/compiler/ti-cgt-msp430_4.4.3/include" --advice:power=all --advice:hw_config=all -g --define=__MSP430FR6989__ --diag_warning=225 --display_error_number --diag_wrap=off --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU40 --printf_support=minimal --preproc_with_compile --preproc_dependency="main.pp" "../main.c"
At end of source: error #68: expected a "}"
"../main.c", line 33: remark #1544-D: (ULP 13.1) Detected loop counting up. Recommend loops count down as detecting zeros is easier
"../main.c", line 33: remark #1527-D: (ULP 2.1) Detected SW delay loop using empty loop. Recommend using a timer module instead
1 error detected in the compilation of "../main.c".

>> Compilation failure
gmake: *** [main.obj] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

0 Ki over 6 years ago in reply to Brendan Richart

TI__Guru**** 483601 points

Brendan Richart said:
At end of source: error #68: expected a "}"

This is definitely a compile error that would prevent the *.out file from getting generated.

Code Composer Studio™︎

Code Composer Studio forum

CCS/MSP430FR6989: More on the Load file error (.out file)