This all succeeded, and I wasn’t able to reproduce the issue. I installed Arduino with all bells and whistles, not sure if that matters.
I then uninstalled Arduino, and downoladed the zip file instead, extracted it to a random directory, and tried all the other steps - still succeeded in the end.
@algernon - I followed your steps exactly, and now it seems to compile, though it throws this error/warning:
Invalid library found in C:\Users\ejinks4\Documents\Arduino\hardware\keyboardio\avr\libraries\Kaleidoscope-Plugin: C:\Users\ejinks4\Documents\Arduino\hardware\keyboardio\avr\libraries\Kaleidoscope-Plugin
Perhaps I was not putting the files in the right locations previously…
Was discussing this with my husband, whose background is EE, and he thought that the installer might be doing something different based on what else is on the system - which would explain why it works for @jesse & @algernon but not for the rest of us.
Above, Jesse showed checking out the Arduino-Boards repo to hardware/avr/keyboardio, but in his follow up, algernon shows hardware/keyboardio/avr (Note the different nesting order of the avr and the keyboardio directories.)
After…
doing a fresh clone of theArduino-Boards repo with the hardware/keyboardio/avr directory structure
restarting the Arudino IDE
selecting the “Keyboardio Model 01” board in Tools > Board… (It had reverted to an generic arduino board)
…I no longer get the missing ‘arduino:arduino’ core error and was to able successfully run Verify/Compile. Simply renaming the directories so they are in the correct nesting order would likely work. I just did a fresh clone to have as “clean” a redo as possible when trying it.
I checked and the Model01-Firmware README does have the correct path. While I did RTFM, I did not pickup on the variance between it and what was posted above
I’m sorry! I’m writing the docs, but was in a car crash last week and have several months of rehab to look forward to. I hope to have docs up by the end of the weekend, but everything is slowed down for me right now.
I know a bunch of people have been successful with this, and I’m sure some folks will hop in with suggestions. Please keep asking questions and let us know what happens so we can help you and make the path a little smoother for the next folks.
Does anyone have a timeline on updating the wiki to include Windows specific instructions? I’m so out of my depth with this stuff I could use a guide. When I saw the code for the first time last night my reaction was to just go to bed and leave it for another time.
Edit: the title is “Windows Instructions to build firmware” but the discussion is all about this Win7 bug. The FAQ mentions: “Rather than taking an existing topic in a radically different direction, use Reply as a Linked Topic.” but for the life of me I can’t find this “Reply as a Link Topic” button. Can someone point me in the right direction?
I’m really sorry about that. I think that ‘sometime this week’ is a reasonable guess at when I can write up a Windows install guide or re-edit my cross-platform install guide to include the Windows names for things.
