arthur_bzh22
Member
Hello,
I am not a firmware generation expert, and I would like some help to understand a weird behaviour on my firmware size. I am not able to understand link between
variable size used in my code and firmware size.
We are using a lot of big const float arrays in our firmware. The firmware is too big to fetch the 8MB flash...
The problem is that the size of our array does not match the size in the firmware.
For example, if I am adding an array of 128 parameters of float (float 32 bits). I am expecting a new firmware size 512 bytes bigger (128 * 4 bytes).
But my new firmware is 1445 bytes bigger.
I tried to compare the two mapping file generated by the compilation, and I cannot understand this difference. Is it a normal result ? Why do I need 3 times
the space of variable in my final firmware?
Thanks,
Arthur.
I am not a firmware generation expert, and I would like some help to understand a weird behaviour on my firmware size. I am not able to understand link between
variable size used in my code and firmware size.
We are using a lot of big const float arrays in our firmware. The firmware is too big to fetch the 8MB flash...
The problem is that the size of our array does not match the size in the firmware.
For example, if I am adding an array of 128 parameters of float (float 32 bits). I am expecting a new firmware size 512 bytes bigger (128 * 4 bytes).
But my new firmware is 1445 bytes bigger.
I tried to compare the two mapping file generated by the compilation, and I cannot understand this difference. Is it a normal result ? Why do I need 3 times
the space of variable in my final firmware?
Thanks,
Arthur.