Timeline for STM32 & ST-LINK - Cannot connect to MCU after successful programming
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Aug 7, 2021 at 20:16 | history | rollback | zupazt3 | Rollback to Revision 1 - Edit approval overridden by post owner or moderator | |
| Aug 2, 2021 at 9:28 | history | suggested | CommunityBot | CC BY-SA 4.0 | "Connect to the target" button shall be clicked unless it does not work |
| Aug 1, 2021 at 18:02 | review | Suggested edits | |||
| S Aug 7, 2021 at 20:16 | |||||
| Aug 22, 2019 at 5:39 | comment | added | andrew | The Erase chip didn't work for me. I went to Target -> Erase Sectors -> Select all -> apply. After this I regained access of my board. I'm not sure why the chip erase didn't word | |
| Mar 31, 2018 at 18:32 | comment | added | nathan | In linux, I used this bash command to erase the chip: st-flash erase | |
| Dec 11, 2015 at 2:04 | comment | added | Chris Stratton | Yes, that is pretty much to be expected if you use the SWD pins for a different purpose. Experience shows that even STM32 designs which don't intentionally do so can occasionally get "stuck" in a mode where the SWD pins are unresponsive (corrupted program?) and require such treatment for recovery. | |
| Dec 11, 2015 at 0:24 | vote | accept | zupazt3 | ||
| Dec 11, 2015 at 0:24 | history | answered | zupazt3 | CC BY-SA 3.0 |