Hi all,
I'm hoping for some troubleshooting tips. I have a self-build split keyboard using Blackpills.
If I flash either side with 'SPLIT_KEYBOARD = no' in my rules.mk, then both sides work fine (but both working as the left side). If however I set 'SPLIT_KEYBOARD = yes', then both sides stop working.
It's driving me insane!
These are the relevant details of rules.mk:
MCU = STM32F401
BOOTLOADER = stm32-dfu
SPLIT_KEYBOARD = yes
SERIAL_DRIVER = usart
And config.h:
#pragma once
#define HAL_USE_SERIAL TRUE
#define SOFT_SERIAL_PIN A12
#define MASTER_LEFT
#define MATRIX_ROWS 6
#define MATRIX_COLS 6
#define SERIAL_USART_DRIVER SD1
#define SERIAL_USART_TX_PAL_MODE 7
And halconf.h:
#pragma once
#define SERIAL_USB_BUFFERS_SIZE 256
#include_next
And mcuconf.h:
#pragma once
#include_next
#undef STM32_SERIAL_USE_USART1
#define STM32_SERIAL_USE_USART1 TRUE
Please help! I've been at this for two days.
Never worked with keyboard firmware but done my share of editing config files before maybe you should remove the # In front of define left / right.
Are you referring to the #define MASTER_LEFT?
This is just defining whether the USB is plugged into the left board or right board.
All defines start with a hash as standard. It’s not commenting the line out. For that, you’d use //.
Wasted your time there, didn't mean to. Noticed this in the QMK docs Some controllers (e.g. Blackpill with DFU compatible bootloader) will need to be flashed with handedness bootloader parameter every time because it is not retained between flashes. I understand that you define it by MASTER_LEFT because you have connected the USB on the left half, and that "notice" text is relevant to another way of defining the handedness. But maybe it's a specific Blackpill thing.
Ah, thank you. I’ll have a go at that then.