Could ADC+DMA brick my mcu?

[Javier1]

I was happily developing some ADC+DMA routines for my stm32f205 and suddenly my MCU started to freeze.

I am able to connect, erase, and flash binaries with stm32CubeProgrammer trough an ST-link.

After erasing multiple times my STM32F205 with stlink and STM32cubeprogrammer, i am using as debugging code a simple blink programm autogenerated with cubeMX with:

internal clock

SW debugging

and my led pin.

This program is also failing to execute.(it does execute no problem in my nucleo-f207 board)

When launching the debugging session i realised the HAL_Delay() function is leading the code to a weird flash non mapped in .elf memory location.

  

__________________________________________________________________________________

systick before hal_delay():

systick after werid jump to memory and debugger looses track of where the code is running

 nvic_iser4 shows that value when everything goes south.. 

if i comment out the hal_delay function the blink works....

[Javier1 · Accepted solution]

So the problem ended up being damaged MCUs due to too high temperature reflow soldering.

Nothing to do with firmware or software