Skip to main content
Javier1
Principal
March 8, 2021
Solved

Could ADC+DMA brick my mcu?

  • March 8, 2021
  • 1 reply
  • 1043 views

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)

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

0693W000008wIZHQA2.png 0693W000008wIlcQAE.png 

__________________________________________________________________________________

systick before hal_delay():

0693W000008wIWXQA2.pngsystick after werid jump to memory and debugger looses track of where the code is running

0693W000008wIWwQAM.png nvic_iser4 shows that value when everything goes south..0693W000008wIh1QAE.png 

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

This topic has been closed for replies.
Best answer by Javier1

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

Nothing to do with firmware or software

1 reply

Javier1
Javier1AuthorBest answer
Principal
March 9, 2021

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

Nothing to do with firmware or software

hit me up in https://www.linkedin.com/in/javiermuñoz/