STM32CubeMX 4.14.0/4.15.0 BUG: Target/IROM settings are NOT preserved

[Bogdan Golab]

Posted on January 20, 2016 at 10:16

Hi,

Whenever I regenerate the code using STM32CubeMX the new (re-generated) Keil project has Target/IROM1 Memory Areas overwritten  e.g. I usually use RAM area are for IROM1 for debug purposes and the IROM1 is set to: Start: 0x20000000, size:0x1000 After regenerating the code the IROM1 settings are overwritten and  now I see: Start: 0x8000000, size:0x10000 Is there any way to make STM32Cube preserve Keil Target/IROM settings? Please note Target/IRAM settings are preserved. It looks like a bug. Bogdan

[Bogdan Golab]

Posted on April 03, 2016 at 10:12

The bug is still present in 4.14.0

[Bogdan Golab]

Posted on April 03, 2016 at 10:13

Is there any way to make ST developers aware of this issue?

[Nesrine M_O · Accepted solution]

Posted on April 04, 2016 at 16:43

Hi golab.bogdan,

Thank you for your feedback. The issue has been reported internally.-Syrine-

[Bogdan Golab]

Posted on May 23, 2016 at 12:06

Hi Syrine,

Unfortunately the issue was NOT fixed in the CubeMX 4.15.0. The IROM setting are still altered after re-generating the project using CubeMX. Thanks, Bogdan

[Bogdan Golab]

Posted on November 07, 2016 at 17:47

Hi,

I wonder if there any plans to fix the issue. I see the problem also in 4.17.0, Bogdan

[Bogdan Golab]

Posted on February 03, 2017 at 13:50

It seems that the issue is fixed at least in 4.19.

Thank you

Bogdan

[Alex Ivanov]

Posted on June 03, 2017 at 07:23

The same error for STM32F745!!! ver. 4.21.0