Static memory allocation sets aside fixed memory before the program runs. It helps keep memory use simple and predictable.
When you know the exact size of data before running the program.
For storing configuration values that do not change.
When you want fast access to variables without overhead.
In embedded systems with limited memory and no dynamic allocation.
For global variables shared across functions.
Syntax
Embedded C
type variable_name[size];
// Example:
int numbers[10];
char message[20];
Static arrays have fixed size and memory is allocated at compile time.
Memory for static variables remains for the entire program run.
Examples
Declares an integer array of 5 elements with static memory.
Embedded C
int data[5];
Declares a character array with initial text stored in static memory.
Embedded C
char name[15] = "Embedded";
Declares a static integer variable that keeps its value between function calls.
Embedded C
static int counter = 0;
Sample Program
This program uses static memory for an array and a static variable. The array holds fixed numbers. The static variable counts how many times the function runs.
Embedded C
#include <stdio.h>
// Static array with fixed size
int numbers[5] = {10, 20, 30, 40, 50};
// Static variable to count calls
static int call_count = 0;
void print_numbers() {
call_count++;
printf("Call %d: ", call_count);
for (int i = 0; i < 5; i++) {
printf("%d ", numbers[i]);
}
printf("\n");
}
int main() {
print_numbers();
print_numbers();
return0;
}
OutputSuccess
Important Notes
Static memory is allocated once and stays until the program ends.
Static variables inside functions keep their value between calls.
Static arrays cannot change size during program execution.
Summary
Static memory allocation reserves fixed memory before running.
Use static arrays and variables when sizes and values are known and fixed.
Static memory is fast and simple but not flexible for changing data sizes.
Practice
(1/5)
1. What is the main characteristic of static memory allocation in embedded C?
easy
A. Memory size is fixed at compile time and cannot change during execution.
B. Memory is allocated dynamically during program execution.
C. Memory is allocated only when a function is called.
D. Memory size can grow or shrink based on input data.
Solution
Step 1: Understand static memory allocation
Static memory allocation means reserving memory before the program runs, with a fixed size.
Step 2: Compare with dynamic allocation
Dynamic allocation changes size during execution, but static does not.
Final Answer:
Memory size is fixed at compile time and cannot change during execution. -> Option A
Quick Check:
Static memory = fixed size [OK]
Hint: Static means fixed size known before running [OK]
Common Mistakes:
Confusing static with dynamic allocation
Thinking static memory can resize
Assuming static memory is allocated at runtime
2. Which of the following declarations uses static memory allocation correctly in embedded C?
easy
A. int *arr; arr = calloc(10, sizeof(int));
B. int *arr = malloc(10 * sizeof(int));
C. int arr[];
D. int arr[10];
Solution
Step 1: Identify static allocation syntax
Static arrays are declared with fixed size like int arr[10];
Step 2: Recognize dynamic allocation
malloc and calloc allocate memory dynamically at runtime, not static.
Final Answer:
int arr[10]; -> Option D
Quick Check:
Static array declaration = int arr[10]; [OK]
Hint: Static arrays use fixed size brackets [] [OK]
Common Mistakes:
Using malloc or calloc for static allocation
Not specifying array size for static arrays
Confusing pointer declarations with arrays
3. What will be the output of this code snippet in embedded C?
static int buffer[5] = {1, 2, 3, 4, 5};
void main() {
for(int i = 0; i < 5; i++) {
buffer[i] += 1;
printf("%d ", buffer[i]);
}
}
medium
A. Compilation error due to static keyword
B. 2 3 4 5 6
C. 0 1 2 3 4
D. 1 2 3 4 5
Solution
Step 1: Understand static array initialization
The static array buffer starts with values {1, 2, 3, 4, 5} fixed at compile time.
Step 2: Trace the loop increment and print
Each element is increased by 1, so values become {2, 3, 4, 5, 6} and printed.
Final Answer:
2 3 4 5 6 -> Option B
Quick Check:
Increment each element by 1 = 2 3 4 5 6 [OK]
Hint: Static arrays behave like normal arrays with fixed size [OK]
Common Mistakes:
Thinking static causes compile error
Forgetting to increment values before printing
Confusing static with uninitialized variables
4. Identify the error in this static memory allocation code snippet:
B. Static keyword cannot be used inside functions.
C. Array size is not specified for static array.
D. Missing return type for main function.
Solution
Step 1: Check static array declaration
Static arrays must have size or initializer; data[] without size or init is invalid.
Step 2: Verify other code parts
Static inside functions is allowed; assigning values and printing is valid; main return type is void (allowed in embedded C).
Final Answer:
Array size is not specified for static array. -> Option C
Quick Check:
Static array needs size or initializer [OK]
Hint: Static arrays need size or initializer [OK]
Common Mistakes:
Assuming static arrays can omit size without initializer
Thinking static is disallowed inside functions
Confusing main return type errors with static errors
5. You need to store sensor readings in a fixed-size buffer that must retain values between function calls in embedded C. Which static memory allocation pattern is best suited?
hard
A. Declare a static array inside the function to hold readings.
B. Use dynamic memory allocation with malloc inside the function.
C. Declare a local array inside the function without static keyword.
D. Use global variables without static keyword.
Solution
Step 1: Understand requirement for retaining values
Values must persist between calls, so memory must not be reinitialized each time.
Step 2: Choose static array inside function
Static array inside function keeps values between calls and has fixed size, perfect for sensor buffer.
Step 3: Exclude other options
Dynamic allocation is flexible but not static; local array resets each call; global without static may cause namespace issues.
Final Answer:
Declare a static array inside the function to hold readings. -> Option A
Quick Check:
Static inside function retains data between calls [OK]
Hint: Static inside function keeps data persistent [OK]
Common Mistakes:
Using local arrays that reset each call
Choosing dynamic allocation when fixed size needed
Ignoring static keyword for persistence
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.