CODECOMPOSER: Problem copying TIME and DATE macros

Mark Feller

Part Number: CODECOMPOSER

Tool/software:

I'm not sure if the is a "C" issue or something more specific to CCS.

I am trying to create a build string as follows:

char build_date[20] = __DATE__;
char build_time[20] = __TIME__;
char buildinfo[40];

void generate_builddate_string(){
    int i;

    for (i=0; i < 40; i++){
        gui_buildinfo[i] = '\0';
    }
    sprintf((char*)buildinfo,"%s %s", build_date, build_time);


}

If I check build_time in CCS expressions, it is correct, including the last 2 characters being the seconds for the build.

If I check buildinfo in CCS expressions, the seconds characters are not correct. The rest of buildinfo is correct.

Any suggestions why those last two characters of buildinfo are not correct?

(Target is 28379D)

Thanks!

6 months ago

0 Ki 6 months ago

TI__Guru**** 471881 points

Hi Mark,

What values did you specify for the stack and heap size? There are also additional considerations in the below article:

https://dev.ti.com/tirex/explore/node?node=A__AaFzMa1WBkGexmvHoJZodg__CCSTUDIO-ACADEMY__RdkYJ-M__LATEST

I'll also bring this thread to the attention of the compiler experts for further suggestions.

Thanks

0 Mark Feller 6 months ago in reply to Ki

Expert 1220 points

I had not changed the default heap and stack sizes. Stack was 0x200, Heap had no definition in the project settings, so I guess heap was some default setting. I changed both to 0x200, and then to 0x400, and the problem/behavior is unchanged.

0 George Mock 6 months ago in reply to Mark Feller

TI__Guru**** 251060 points

Be sure you have this line near the beginning ...

#include <stdio.h>

Thanks and regards,

-George

0 Mark Feller 6 months ago in reply to George Mock

Expert 1220 points

I did already have that (I just didn't paste the rest of the file).

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

0 George Mock 6 months ago in reply to Mark Feller

TI__Guru**** 251060 points

This is simple code. It has been a very long time since a problem was found in the family of printf functions. I have to continue to suspect some higher level detail is wrong. If you run straight through the function with no stops, then check the result, does that work? If you change the location of the character arrays to different memory, does that work?

Thanks and regards,

-George

+1 Mark Feller 6 months ago in reply to George Mock

Expert 1220 points

The strings are in the default .bss section. I moved .bss to its own RAM block (RAMLS4). No change in behavior. I have also run the project multiple times with and without breakpoints, and the behavior does not change.

I *did* copy the file to a different project, and it worked without modification. So I agree, it looks like something else is happening in my original project.

What's interesting, is that it is always the SAME garbage characters that end up in those final two characters of buildinfo.

0 Mark Feller 6 months ago in reply to Mark Feller

Expert 1220 points

I tried using Watchpoints to break on accesses to those characters of the string. I found a loop that ran beyond an array limits, where it was running over the buildinfo memory area. (Due to a hard-coded value that I had not changed yet).

So a note here for others...use Watchpoints!

Code Composer Studio™︎

Code Composer Studio forum

CODECOMPOSER: Problem copying TIME and DATE macros

Code Composer Studio™︎

Code Composer Studio forum

CODECOMPOSER: Problem copying __TIME__ and __DATE__ macros

CODECOMPOSER: Problem copying TIME and DATE macros