Tool/software: TI-RTOS
Hello,
I can reproduce the issue described in (Target not run as the symbol "main" is not defined)
with CCS 8.2.0.00007 as well.
Is there any fix in the pipeline for the next update, or a workaround?
Best regards,
Thomas
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.
Tool/software: TI-RTOS
Hello,
I can reproduce the issue described in (Target not run as the symbol "main" is not defined)
with CCS 8.2.0.00007 as well.
Is there any fix in the pipeline for the next update, or a workaround?
Best regards,
Thomas
Thomas,
Yes, this is currently a known issue with A53 binaries built with GCC compiler that is being looked at. . Please confirm that you are also seeing this on the A53 core. For now, R5F related code built with TI ARM compiler should not be showing this behavior in CCS.
The bug ID for the same is PRSDK-4654. you can check for this in the Release notes to track resolution
Regards,
Rahul
Thomas,
I think we have it figured out. From what I understand, there's an issue in GCC where things get corrupted when generating a build-id but then later declaring it as NOLOAD.
The simplest workaround (in my opinion) is to just disable the build-id feature altogether.
Here's a screenshot:
I hope this hasn't been causing you too much grief. Sorry to keep you waiting so long for a fix. It wasn't easy to figure out!!!
FYI, the alternative fix is to remove the NOLOAD in linker.lds for the template app:
- .note.gnu.build-id (NOLOAD) : { *(.note.*) }
+ .note.gnu.build-id : { *(.note.*) }
My own preference is to fix this at the command line, though if you had any inputs on either of these as being preferable to the other, I'd be interested to get your perspective.
Best regards,
Brad