A new CRCs Area is created and overlapped with other when post-build is called.

[EmbeddedPepe]

Hi,

We have a working ( if we can say so ) firmware.

The issue is that everytime he calls the build option (IAR EWARM) he calls, at the end, the cubeprogrammer utility that adds the CRC area to the firmware in post-build. The from-to memory region he selects is correct.

The issue here is that everytime the build option is called a new CRCs Area with the same VMA (Virtual Memory Address) is created, so obviously CubeProgrammers reads the file as corrupted/not valid.

Is this a bug or something else? 

18 CRCs area     000001f8  0801f608  0801f608  0034ee5d  2**2
                  CONTENTS, ALLOC, LOAD, DATA
19 CRCs area     000001f8  0801f608  0801f608  0034f055  2**2
                  CONTENTS, ALLOC, LOAD, DATA
20 CRCs area     000001f8  0801f608  0801f608  0034f24d  2**2
                  CONTENTS, ALLOC, LOAD, DATA
21 CRCs area     000001f8  0801f608  0801f608  0034f445  2**2
                  CONTENTS, ALLOC, LOAD, DATA