Cube IDE v2.0.0 - Hard Fault error

[silelis]

Hello,

I had developed my firmare in STM Cube ide 1.5.1 (stm32h7/)

Project repo is here: https://github.com/silelis/MustangRadio_develepementVersion/tree/main/02_Firmware/02_STM32/Radio_main

And after I have updated IDE to 2.0.0 I have noticed that STM32h7 falls into hard error interrupt.

It also appears when I uninstall IDE and installed pure 2.0.0.

When I moved back to 1.5.1 hard errot dissapired.

Please check this error in IDE.

[Andrew Neil]

---

@silelis wrote:

How is it possible that on previous versions firmware works and on newes not??

---

Also, remember that the C programming language, by design,  has a number of things which are Implementation-Defined, and a number of things which are Undefined.

It's fairly rare that am implementation (eg, GCC) would change an Implementation-Defined behaviour - but it can happen.

Code which relies upon Undefined behaviour is always risky ...

[AScha.3]

You didnt get ..or i explained wrong : update IDE is/was always also update for Cube and the associated HAL settings and functions - so update was always like rolling the dice : will still work, what was working before and /or get new features. Most times both not sure.

The GCC is different - i never had a problem with it, update or not.

Just my experience.

[silelis]

To be detailed I have made update from Cube IDE Help menu.

Very strange thing because I wrote code in HAL not registers.

Earlier I did not have such behaviour when I change/ update STM Cube IDE version to newer 

[AScha.3]

>

Hi,

Try with IDE 1.19. , and tell...

[Andrew Neil]

---

@silelis wrote:

I wrote code in HAL not registers.

---

Did you update the Firmware Pack version?

Again, you're going to need to do some debugging to find out what's going on.

[TDK]

Consider the possibility that this has nothing to do with the IDE but rather with a bug in your code. I suggest approaching the problem from that point of view. See where it is hard faulting. See if you can pare down the code to something smaller and reproduce the issue. Your code is complex, unlikely anyone here has the desire to parse through everything searching for the needle in a haystack.