Hey Stephen,
This is not a really an issue, but just description on my failed attempt.
I was wondering if you have tried loading vial/via on to your qmk code before? I'm currently attempting with your kinT41 code base. Only time I got it to successfully create the hex file is by bumping up the TRANSIENT_EEPROM_SIZE = 500 for DYNAMIC_KEYMAP_LAYER_COUNT= 2. However, once I programme it on to my teensy4.1, it errors out with 7 blinks. According to the documentation https://www.pjrc.com/store/ic_mkl02_t4.html
7 Blinks = ARM JTAG DAP Communication Error
A communication error was detected, but after correctly detecting (4 blinks) and initializing the ARM JTAG DAP (9 blinks). Programs which crash or have unusual startup behavior can cause a temporary 7 blink error at startup. With a known-good program or blank flash chip, this error may indicate a severe signal quality problem or any of the signal wires shorted to other lines which are initially high impedance but become output after a program is running. But these types of hardware issues are unusual, because hardware trouble for 7 blinks requires first successfully passing tests which would cause 4 or 9 blinks. 7 blinks can also be shown if the processor reboots, either by software write to SCB_AIRCR or due to fault or other error handling, while communication is in progress. If you see 7 blinks, program the flash memory with a simple known-good code before investigating hardware trouble.
Hey Stephen,
This is not a really an issue, but just description on my failed attempt.
I was wondering if you have tried loading vial/via on to your qmk code before? I'm currently attempting with your kinT41 code base. Only time I got it to successfully create the hex file is by bumping up the
TRANSIENT_EEPROM_SIZE = 500forDYNAMIC_KEYMAP_LAYER_COUNT= 2. However, once I programme it on to my teensy4.1, it errors out with 7 blinks. According to the documentation https://www.pjrc.com/store/ic_mkl02_t4.html