Click to view our Accessibility Statement or contact us with accessibility-related questions
particleMan
5
May 1, 2015
I use this firmware on my Ergodox. It works for the Infinity also: https://github.com/tmk/tmk_keyboard/tree/master/keyboard/infinity
Kaan
297
May 2, 2015
particleManI knew tmk firmware was compatible with infinity, but I didn't know it officially supported infinity, I've just checked the firmware, it looks very exciting, especially it's feature-set / mouse features
So thanks a lot for sharing this, I will use this firmware instead, particle man saves the day
I check this page every day, I hoped we would get an official update as tybenz's request for an update gets upvoted more and more, yet it's not happening :( As I observed from other drops, they don't seem to deliver bad news, so we can deduct that there aren't any good news
chrismetcalf
77
May 5, 2015
particleManAnybody have any luck getting the tmk firmware for the Infinity to compile on a Mac? I tried last night and couldn't find a arm-gcc for Homebrew with all the right libraries to build it.
Kaan
297
May 5, 2015
chrismetcalfI received the rev1 infinity I bought second-hand/unused, it was an initially nightmarish experience, partially destroyed the 60% case I bought to make room for diodes, mended the already broken/surface mounted USB socket etc.
I also noticed that the switches NEEDS to be PCB-mounts, unless you are ok with each of them being aligned to a random direction, I'm going to replace all of them soon, it's a pretty painful modding process overall, sadly, I don't think Massdrop is going to send PCB-mounts, so I strongly suggest buying PCB-mount switches externally
FMendoca: I bought icase's infinity, yet I'm sure you can find another seller in no time, just don't buy rev1's like I did :)
christmetcalf, going to attempt the same today on my secondary mac, If brew was sufficient I could have used my primary mac, but it seems this might be needed: http://www.obdev.at/products/crosspack/index.html - don't want to risk my primary mac with non-brew stuff, I will let you know If I get results
TL;DR: Strengthen the USB sockets, use PCB-mount switches, make sure diodes don't get destoyed by 60% cases
chrismetcalf
77
May 5, 2015
KaanI experimented with Crosspack a bit (it's available as a Brew Cask) but I don't think it'll work out of the box. I'll at least need to modify some Makefiles.
Kaan
297
May 5, 2015
chrismetcalfAfter digging in more, I have the hunch that infinity is ARM and not AVR, the tmk_keyboard is probably lacking steps for infinity, so I decided to concentrate on kiibohd/controller, make it work, then test tmk_keyboard with build tools in place, currently trying to find arm sources/tools/compiler to brew tap, the one kiibohd/controller links seems to lack the arm packages
At this stage, I just wanted to correct my possible mistake of suggesting the AVR/Crosspack package
Edit: Infinity is ARM-based, so the ARM instructions should be followed, it's easy to find the arm libraries with both brew/ports, many of them work with the "controller"project, I managed to switch "1" and "2" by editing it's default .kll, only "dfu-util libusb" is needed as extras as far as I can remember, yet I couldn't make tmk_keyboard work, the mbed framework that it uses is very picky, I'm guessing it requires a version of the arm libraries that doesn't exist through ports or brew
./infinity.bash created a "template" folder which has the "kiibohd.dfu.bin", "dfu-util -D kiibohd.dfu.bin" installs the framework, the ./infinity.bash uses the standard .kll files, the output also includes the directories - so it's easy to know which .kll's are loaded/used - to edit them manually
TL;DR: I'm locked at infinity's original framework, tmk_keyboard proved to be more challenging
I get now why almost no one can use their infinity keyboards, but on the bright side, the "controller" firmware is easier to work with, the structure is just a bit complicated, you have to jump from place to place to get what you want
chrismetcalf
77
May 6, 2015
KaanThat makes a lot more sense. The CPU difference should have been pretty obvious, don't know why I missed that...
What brew packages did you install? Following https://github.com/kiibohd/controller/wiki/Mac-Setup, I installed "dfu-util" and "gcc-arm-none-eabi", but I couldn't find an ARM "binutils" package in the "paxswill/homebrew-paxswill" tap.
It looks like I'm almost built but not quite, due to a missing packaging tool:
Create and sign dfu bin file: kiibohd.dfu.bin make[2]: /Users/metcalf/lib/pebble/arm-cs-tools/bin/arm-none-eabi-objcopy: No such file or directory make[2]: *** [kiibohd.elf] Error 1 make[1]: *** [CMakeFiles/kiibohd.elf.dir/all] Error 2 make: *** [all] Error 2 Firmware has been compiled into: 'template'
I suspect that "arm-none-eabi-objcopy" is in that missing binutils package.
Edit: Nevermind. I'm bad at reading my own error messages. I had a dead path referenced in ./templates, and I had to rerun "./Keyboards/template.bash" to rebuild them. All good now!
blais
88
May 15, 2015
Kaan> I get now why almost no one can use their infinity keyboards, but on the bright side, the "controller" firmware is easier to work with, the structure is just a bit complicated, you have to jump from place to place to get what you want
I don't know what you mean, I managed to get mine working great. Tips here: https://docs.google.com/document/d/13WwRq4NC4a9cUEwcMS7QcomnTu02k9kuBss7Ep5tDBU/
wes1099
183
May 15, 2015
blaisYou can also go way way back in this discussion page and read HaaTa's replies to the hundreds of questions I had about how to get the firmware to compile correctly. I believe I was the first one to successfully compile my own firmware and flash it successfully back in late February.
PRODUCTS YOU MAY LIKE
Trending Posts in Mechanical Keyboards