stm32f030c8tx bricked?

[AHolm.1]

I have finally managed to access these chips using a SEGGER.... I have no idea why but STLINKv2 and CUBE programmer won't access the same chips.

Anyway, as I've finally gained access I have flashed my chips to test that they were properly functioning. The idea was to get a new STLINKv2 to reprogram them with lockbits before using them for real.

I used the standard segger 0x00000 bin address.... my developer says I should have used 0x800000 ..... have I bricked my chips? My experience with ST kit has been wretched so far so I expect all the chips are wrecked :(

[Uwe Bonnes]

F;ash is physical located at 0x08000000, and depending on Boot pins/boot option bits/syscfg settings mapped at 0 or not. By connecting under reset, you should always regain access on the chip, if it is not Read Protected Type 2, wrong connected or broken.