Hello! My model 01 arrived yesterday, and being a dvorak user and already having some preferences on what goes where on thumb keys I decided to dive right in to reflashing the keyboard with a better layout for me. I’ll go through my steps following the guides on the wiki for posterity & information, and end with where I hit my snag. I didn’t dig too deep yet, but whatever problem I’m having should (is?) probably commented somewhere.
Arduino 1:1.8.5-1 was already installed on my system, which should be up to date enough according to the guide.
As the article hesitantly says, I don’t have the dialout group, but I do have the uucp group (which I’m already a part of).
Arduino was not installed in /usr/local/bin/arduino , but in /usr/bin/arduino. I therefore had to set the $ARDUINO_PATH flag
$ echo 'export ARDUINO_PATH=/usr/bin/' >> ~/.bashrc $ source ~/.bashrc $ echo $ARDUINO_PATH /usr/bin/
mkdir and git cloning worked as expected.
this is where I hit a snag though
$ make flash ls: cannot access '/home/hatten/.arduino15/packages/keyboardio/hardware/avr/*': No such file or directory BOARD_HARDWARE_PATH="/home/hatten/Arduino/hardware" /home/hatten/Arduino/hardware/keyboardio/avr/libraries/Kaleidoscope/bin//kaleidoscope-builder flash Building output/Model01-Firmware/Model01-Firmware (0.0.0-gv1.13-55-g8ab1) ... stat /usr/bin/hardware: no such file or directory make: *** [/home/hatten/Arduino/hardware/keyboardio/avr/build-tools/makefiles//rules.mk:75: flash] Error 1
Some tentative poking around that might help:
$ ls ~/.arduino15 staging library_index.json package_index.json package_index.json.sig preferences.txt $ which hardware which: no hardware in (<long list of custom stuff as well as default system paths>) $ find / -name hardware 2>/dev/null /home/hatten/Code/AndroidStudioProjects/MyApplication/app/build/tmp/expandedArchives/classes.jar_a0efcwrns6wtef8zezsroqw5l/android/support/v4/hardware /home/hatten/Arduino/hardware /usr/lib/modules/4.13.5-1-ARCH/kernel/drivers/isdn/hardware /usr/share/arduino/hardware /opt/android-sdk/sources/android-25/com/android/internal/hardware /opt/android-sdk/sources/android-25/android/support/v4/hardware /opt/android-sdk/sources/android-25/android/hardware
My hunch is that the initial
ls is for finding previous builds, and not findinig anything isn’t an error? If so, should probably write a more descriptive warning/info message instead of a scary
ls error message.
I have no clue what
hardware you’re trying to find in
/usr/bin. I could go digging in the source to see what it might be, but it’s easier to ask for help (and will make the question show up for others)