Reverts #13179

this line in boards/common/stm32/dist/stm32f7.cfg
flash bank $_FLASHNAME.riot stm32f2x 0x08000000 0 0 0 $_TARGETNAME

leads to misinformation of openocd about the memory layout (there is an extra flash region at the same place) and since gdb gets its memory map information from openocd it will detect Overlapping regions in memory map and will not use it. this will hamper debugging.

gdb: warning: Overlapping regions in memory map: ignoring

For me it was:
gdb tells openocd to set soft break points, if it does not know about the memory map, which do not work (in flash regions?).

older versions of openocd (current ubuntu) ignore if gdb tells them to set soft breakpoints and decide on their own depending o the address. newer version respect what gdb tells them to do.

i am not sure how to fix the issue that #13179 tried to fix but i think i should be in openocd.sh

which states:

# Probing can fail when the board is in a non flashable state or
# maybe probing would need a different init procedure.
# At least, currently fallback to returning the configured value

i think the nucleo-f767zi is in a non flashable state with its reset being pulled there for the procedure should be pull the reset the release it then read the flash information

flash probe 0 allways fails for the nucleo-f767zi in that with the current procedure

the flash procedure does it like this

${OPENOCD_EXTRA_RESET_INIT} \
-c 'init' \
-c 'targets' \
-c 'reset halt' \

after this the flash is accessible and the flash probe 0 should not fail