1

I'm developing an embedded application on stm8s microcontroller using STVD IDE and COSMIC compiler.

I'm trying to define a static bool variable to use it to execute a snippet of code only once. Unexpectedly, the variable once is not initialized to FALSE or 0. Although I explicitly initialized it. Here is the snippet of my code:

uint32_t crc32_buffer(void)
{
    static bool once = FALSE;
    uint32_t crc = 0;

    if(!once)
    {
        calcTable();
        crc = 10;
        once = TRUE;
    }

    return crc;
}

When I tried to check the physical memory location, I found that every time after entering a new debugging session (even after hardware restarting the controller) and before running the application itself, the memory address 0x80 has the same value 0x14.

If I modified the code to assign FALSE to once after the variable's initialization:

once = FALSE;

The memory location is changed to contain 0x00. Then if I exit this debugging session and then re-modified the code to delete this line of code and start a new debugging session, I find the memory location 0x80 has again 0x14 before running the application.

I don't understand what can prevent the compiler to initialize the variable to 0. I don't understand what can write 0x14 to the memory location even before running the application.

I tried setting a breakpoint if the memory location 0x80 was accessed (read/write) but the application didn't stop until it reached the if statement in the code snippet.

UPDATE-2

As many pointed out the startup procedure, I don’t use the default startup code. However, I'm using a custom one. When I used the standard startup code instead of the custom one I was using, the memory locations were set to 0 before main() function start execution. This is not the case with the custom startup code. So, when I define a new static variable and explicitly initialize it to FALSE, this initialization will only take place in the startup code before main(), right?

Improve this question
7
  • 2
    Put the breakpoint at the first line of main and check then. It should be initialized by the startup code before main is entered. stackoverflow.com/questions/17783210/… Commented Jul 16, 2019 at 15:34
  • 2
    Most of the compilers add __main() at the beginning or before actual main() to initialize statics, so you have to let appliaction to start Commented Jul 16, 2019 at 16:05
  • Please check that in your map file contains entries for the .bss and/or .data sections. Commented Jul 16, 2019 at 17:06
  • 2
    If you're using some custom or non-standard startup code then most likely you're missing a loop which zeroes out the .bss segment. Commented Jul 16, 2019 at 23:50
  • @brhans It looks like you are right. Please check UPDATE-2 Commented Jul 17, 2019 at 8:33

2 Answers 2

Reset to default
3

If you read this storage duration reference you will see that for static storage duration

the value stored in the object is initialized only once, prior to main function

So you have to let the startup code running before main run first. Once the main function is called the value should have been initialized.

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

@Clifford The OP says "before running the application itself" (emphasis mine), with together of some other wording make me think that the OP is using a hardware debugger or similar, and doesn't enter the C startup code which does the initialization.
Indeed - now I read more carefully. The important clue comes way down the question. It does say that but it does not say that crc32_buffer() is being invoked them, merely that the value observed in is memory while at the reset vector - i.e.. the CRT is not performing initialisation. However later he says that it does break on a data access break-point, indicating initialisation on first use so you are right, except this is not a CRT initialisation, but a local static initialise on first use.
0

I find the memory location 0x80 has again 0x14 before running the application.

Initialisation requires code; the state of the memory after reset, before any code has executed is non-deterministic.

I tried setting a breakpoint if the memory location 0x80 was accessed (read/write) but the application didn't stop until it reached the if statement in the code snippet.

That sounds like the initialisation right there. What value did the variable acquire at that point? Local statics can be initialised on first use, rather than in the run-time start-up. It looks to me that in fact you do not have a problem at all other than understanding the semantics of static.

If for example you place a break-point on the static declaration itself, and run it, I expect you will observe that the break point is hit once on first use initialisation, and thereafter will not break on subsequent calls to the function.

Improve this answer

2 Comments

I think that when I define a new static variable and initialize it to FALSE, when I first check its value in the if statement, it should have the initial value of FALSE, right? This is not the case for me. When I check its value, I find once has the value of 0x14 instead of 0
@Salahuddin OK, but that is not clear in your question. Also if you have hit a data access breakpoint, something accessed it. You need to set it to a write access rather than read/write to be more selective re initialisation. Also inspect the code disassembly and register values. Some debuggers do not handle static variables well and may give misleading indications.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.