Open grindhold opened 6 years ago
STLink is connected via SWD or JTAG?
I suggest try a real visual windowed step-by-step debugger. i could give you Keil MDK professional (no limits). Go to debugger and watch clocks etc.
I love those blue pills for 2 or 3 years now :)
//edit: That Keil offer is for Grindhold only, as we know each other in RL.
I have the same issue with j- and d- command.
Complete erase of the STM32 flash fixes the issue for now, but it readily occurs again when you reset it at the "wrong" time.
i think i found a way to destroy a pill duck.
way to reconstruct:
0) build pill_duck via make 1) start openocd
openocd -c "bindto 127.0.0.1" -f /usr/share/openocd/scripts/interface/stlink-v2.cfg -f /usr/share/openocd/scripts/target/stm32f1x.cfg
3) connect to openocdtelnet localhost 4444
4) halt the cpuhalt
5) flash pill_duckprogram /path/to/pill_duck.elf verify
6) reset the cpureset
7) disconnect bluepill from programmer, connect via usb to pc 8)lsusb
yields pill duck device descriptor 9)screen -L /dev/ttyACM0
enterj
for jiggler and press enter 10) reset device via RESET button 11) unplug the bluepill and plug it in again 12)lsusb
wont list pill duck device descriptor anymore 13) unplug from usb and connect to programmer again 13) repeat 3 - 7 15)lsusb
will not recognize the device anymore. for good.meanwhile in dmesg:
flashing stuff like miniblink still works, so the device does not seem utterly bricked. does anyhone have any ideas how to resolve that issue?