mattdibi / redox-keyboard

Ergonomic split mechanical keyboard
MIT License
1.81k stars 168 forks source link

Cant flash reciever #179

Closed SecretFinder closed 4 months ago

SecretFinder commented 4 months ago

I am trying to flash the receiver but keep getting the below error:

Starting redox-w-firmware-master_openocd_1 ... done
Starting redox-w-firmware-master_toolchain_1 ... done
Attaching to redox-w-firmware-master_openocd_1, redox-w-firmware-master_toolchain_1
openocd_1    | Open On-Chip Debugger 0.9.0 (2018-01-24-01:05)
openocd_1    | Licensed under GNU GPL v2
openocd_1    | For bug reports, read
openocd_1    | http://openocd.org/doc/doxygen/bugs.html
openocd_1    | WARNING: target/nrf51_stlink.cfg is deprecated, please switch to target/nrf51.cfg
openocd_1    | Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
openocd_1    | Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
openocd_1    | adapter speed: 1000 kHz
openocd_1    | Info : Unable to match requested speed 1000 kHz, using 950 kHz
openocd_1    | Info : Unable to match requested speed 1000 kHz, using 950 kHz
openocd_1    | Info : clock speed 950 kHz
openocd_1    | Info : STLINK v2 JTAG v34 API v2 SWIM v7 VID 0x0483 PID 0x3748
openocd_1    | Info : using stlink api v2
openocd_1    | Info : Target voltage: 3.245940
openocd_1    | Error: init mode failed (unable to connect to the target)
openocd_1    | in procedure 'init'
openocd_1    | in procedure 'ocd_bouncer'

I have successfully flashed both keyboard halves already, so I know the issue is not in my laptop or with the STLink V2. Fearing a bad MCU or error in my solder job I have made a new receiver with a fresh PCB and MCU but the error persists. Are there any common issues I could be missing to cause this problem?