Hi,
@msfujino I have the same issue on my device.
I was playing around with the clock manager configuration in Simplicity studio, trying to optimize the power consumption of the device and… looks like I broke something. After flashing, the device does not respond anymore and OpenOCD now returns errors when I try to erase the device or any thing else:
Open On-Chip Debugger 0.12.0+dev-01514-g21fa2de70 (2024-02-07-19:19)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
efm32s2_dci_read_se_status
Info : Using CMSIS-DAPv2 interface with VID:PID=0x2886:0x0062, serial=D75A6F9E
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Serial# = D75A6F9E
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 0
Info : CMSIS-DAP: Interface ready
Info : clock speed 1000 kHz
Info : SWD DPIDR 0x6ba02477
Info : SWD DPIDR 0x6ba02477
Warn : Connecting DP: stalled AP operation, issuing ABORT
Info : SWD DPIDR 0x6ba02477
Error: Failed to read memory at 0xe000ed00
Error: [efm32s2.cpu] Examination failed
Successfully connected to DCI
DCI WPENDING bit set, retrying
DCI WPENDING bit set, retrying
...
DCI WPENDING bit set, retrying
Error executing event examine-fail on target efm32s2.cpu:
Warn : target efm32s2.cpu examination failed
Info : starting gdb server for efm32s2.cpu on 3333
Info : Listening on port 3333 for gdb connections
Error: Error connecting DP: cannot read IDR
Nothing solved the issue up to now. Putting PC0 to ground before reset/power up nor running the recovery script provided by SEEED neither a combination of both.