Hi,
I've bought a P60s pcb. If I flash the corresponding xtips_p60s_v2_vial.bin in your repository, it works fine: layers are working, rgb animations are shown and leds react to layer changes.
However, when I build the project from the code in https://github.com/X-Tips/QMK-Keyboard/tree/main/p60s on the latest vial-qmk I have several issues:
- I need to put the files in /v2 (info and rules) in the root directory
- I need to rename the info.json to keyboard.json
- Once I done, it compiles fine but, when I uploaded the resulting .bin file the leds stay on and white and are unresponsive to layer changes. Keys and layers still work fine.
It seems your code is using a different/outdated vial-qmk version (which one?)
I really need to be able to compile the code and get a fully funtional keyboard so that I can add other funtions on top (RAW HID, among other things I cannot configure with VIAL direactly).
More specifically, I need the exact build environment (QMK/Vial fork URL and commit hash) used to compile the xtips_p60s_v2_vial.bin, and whether WS2812_DRIVER is set to pwm, spi, or bitbang for the P60S v2.
Hi,
I've bought a P60s pcb. If I flash the corresponding xtips_p60s_v2_vial.bin in your repository, it works fine: layers are working, rgb animations are shown and leds react to layer changes.
However, when I build the project from the code in https://github.com/X-Tips/QMK-Keyboard/tree/main/p60s on the latest vial-qmk I have several issues:
It seems your code is using a different/outdated vial-qmk version (which one?)
I really need to be able to compile the code and get a fully funtional keyboard so that I can add other funtions on top (RAW HID, among other things I cannot configure with VIAL direactly).
More specifically, I need the exact build environment (QMK/Vial fork URL and commit hash) used to compile the xtips_p60s_v2_vial.bin, and whether WS2812_DRIVER is set to pwm, spi, or bitbang for the P60S v2.