CCS/TMS320F28379D: Post Build Errors Not Reported to Console

Ed Sanders

Part Number: TMS320F28379D

Tool/software: Code Composer Studio

Greetings,

I have created a new project with a Post build step which runs a program. To test it, I have deliberately created an error which the program attempts to report. This error manifests itself, in part, by outputting to the Console, the string “Error:”, along with text describing the issue. This should turn the line red, and the text should appear in the Problems tab, a behavior which occurs in our other projects.

But the line which contains the string “Error:” is not appearing. Other lines of text which are also part of the description of the issue do appear which shows that the error was successfully generated. But the lack of the "Error" line results in the text not showing up in red in the Console, and also not showing up in the Problems tab. I have created the same error in a project which does work, and I get the expected result. So I’ve compared the project properties of the new project which those in the project which does work, and cannot find anything which would cause this. Where should I be looking?

Thank you,

over 5 years ago

0 Ed Sanders over 5 years ago

Genius 4035 points

OK. This was my issue. But it exposed an unexpected behavior. When I created the project, in the Properties->Resource->Linked Resources->Path Variables tab, I created a new Path Variable to our tools folder. This was designed to be relative to another Path Variable to the root folder for the codeset. However, I hadn’t created the Path Variable for the root. So they should have looked something like this:

TOOLS ${ROOT}\<Path to Tools>

ROOT <Path to Root>

But ROOT was missing. Rather than fail the instruction, the Post build step appears to have used a NULL value for ROOT which resulted in a path which, coincidentally, was valid, and contained an older version of the tool which did not have the “Error:” strings in it. Is the NULL string substitution the expected behavior?

Thanks,

0 JohnS over 5 years ago in reply to Ed Sanders

TI__Guru**** 162305 points

Ed,

Yes that is the expected behavior from Eclipse. If a variable is not defined its value is NULL.

Depending on where the variable is used there is some validation. The most common place these variables are used is in the include paths. Here I have added a path that uses ${JOHN}. However that variable is not defined so it gets replaced by NULL. In this case the resulting path is then /hello

For include paths the system does check if the include paths exist and you get a warning:

For pre and post build steps there is no validation that the command is valid.

Regards,

John

Code Composer Studio™︎

Code Composer Studio forum

CCS/TMS320F28379D: Post Build Errors Not Reported to Console