You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And as a newbie in the setup process I added A # to the 3rd line removed the # in front of #MCU = at90usb1287 and after some hours of keymapping I tried to compile and it gave me weird errors in the quantum_keycodes.h file. After spending 2 hours trial and error I found that the teensy 2.0++ used 'MCU = at90usb1286' and then it worked perfectly again, but there is still something wrong with MCU = at90usb1287
Would be really nice if there was an easier way to retrace such an error, and something should probably be fixed somewhere.
The text was updated successfully, but these errors were encountered:
Yeah, while the 1287 is an MCU, I'm not sure why it's being used there instead of the 1286, which is much more popular from what I've seen. I think this error (if it is one) came from TMK, but I'd be happy to switch everything over the 1286!
Probably for the best, seeing as 1287 doesn't seem to be (fully) supported. It gave a lot of errors when compiling for me, but turning the 7 into a 6 made everything work perfectly so I suppose it was never meant to be 1287, otherwise the 1286 should have also been an option in the comments.
For me it created:
And as a newbie in the setup process I added A # to the 3rd line removed the # in front of
#MCU = at90usb1287
and after some hours of keymapping I tried to compile and it gave me weird errors in the quantum_keycodes.h file. After spending 2 hours trial and error I found that the teensy 2.0++ used 'MCU = at90usb1286' and then it worked perfectly again, but there is still something wrong withMCU = at90usb1287
Would be really nice if there was an easier way to retrace such an error, and something should probably be fixed somewhere.
The text was updated successfully, but these errors were encountered: