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.

unresolved symbol _TIMER_Isr, first referenced in...

My project is for a 5510.  I'm on CCSv4_1_3, using CGT 4.3.6 and BIOS 5.41.04.18

 

Randomly, when building my project, I'll get TONS of these errors... ex ://

 

 

Severity and Description Path Resource Location Creation Time Id

errors encountered during linking; "ff_app.out" not built ff_app line 0 1287748715461 5361

unresolved symbol _adc_open, first referenced in ./main.obj ff_app line 0 1287748715459 5357

unresolved symbol _aero_open, first referenced in ./main.obj ff_app line 0 1287748715459 5358

unresolved symbol _demod_open, first referenced in ./main.obj ff_app line 0 1287748715460 5359

unresolved symbol _FXN_F_read_samples, first referenced in ./ff_app.obj ff_appline 0 1287748715458 5350

unresolved symbol _hop_open, first referenced in ./main.obj ff_app line 0 1287748715460 5360

unresolved symbol _SWI_demodulator, first referenced in ./ff_app.obj ff_app line 0 1287748715459 5351

unresolved symbol _SWI_hpi_emif_comms, first referenced in ./ff_app.obj ff_app line 0 1287748715459 5352

unresolved symbol _TIMER_Isr, first referenced in ./ff_app.obj ff_app line 0 1287748715459 5353

unresolved symbol _TSK_FXN_F_demod, first referenced in ./ff_app.obj ff_app line 0 1287748715459 5354

unresolved symbol _TSK_FXN_F_hop, first referenced in ./ff_app.obj ff_app line 0 1287748715459 5355

Let me stress that these aren't real errors.  All I did was move one line of code and build.  This happens frequently, and it's impossible to get the app to build again until I reboot my machine!  After rebooting my machine, it builds normally, as it did before.  But restarting CCS doesn't fix it.  Changing workspaces doesn't fix it.  The only thing I've found to fix this issue is a reboot. (Annoying)

Some things cause it quite consistently.  I've found that if I change the optimization settings in my builds, it's virtually 100% guaranteed that this will happen.  (i.e. -o1 to -o3)  However, this time it happened when I commented out an "if" statement and hit build.

Does anyone know why this happens?  It's a huge time-waster for me.

 

  • Would it be possible to provide a reproducible test case?

    ki

  • Well, I don't think I can send my project off since our company doesn't like that type of thing.  But I can reproduce it pretty readily... like within a matter of an hour or so of building and rebuilding during my normal work flow.  If you'd be willing to tell me what you're looking for, I could try to watch for it when this happens again.

  • Would it be possible to strip down the project so that there is nothing confidential? It can be a dummy project... so long as the error can be reproduced.