4 TODO, write some insightful/informative :P
6 Please give authors credit for modules used if you use in a distributed product :D
10 ----------------------
12 ----------------------
14 Below listed are the Arch Linux pacman names, AUR packages may be required.
16 These depend a bit on which targets you are trying to build, but the general one:
17 - cmake (2.8 and higher)
18 - Teensy Loader (http://pjrc.com/teensy/loader.html)
21 AVR Specific (Teensy 1.0/++,2.0/++) (try to use something recent, suggested versions below)
23 - avr-binutils (2.23.2)
27 ARM Specific (Teensy 3.0/3.1) (Sourcery CodeBench Lite for ARM EABI
28 (http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/)
32 - arm-none-eaby-binutils
33 (I've actually had some issues with Sourcery CodeBench on Linux, so I often just use these)
37 ----------------------
39 ----------------------
41 Compiling on Windows does work, just it's a bunch more work.
43 First make sure Cygwin is installed - http://www.cygwin.com/ - 32bit or 64bit is fine. Make sure the following are installed:
45 - git (needed for some compilation info)
50 And make sure CMake is *NOT* installed through Cygwin. This is extremely important.
51 If this is not possible, you'll have to play with your paths in Cygwin to prioritize the Windows version of CMake.
53 Also install the Windows version of CMake - http://cmake.org/cmake/resources/software.html
54 This is in addition to the Cygwin version. This is an easier alternative to installing another C compiler.
55 Add the following line to your .bashrc, making sure the CMake path is correct:
56 alias wincmake="PATH='/cygdrive/c/Program Files (x86)/CMake 2.8'/bin:\"${PATH}\" cmake"
58 Next, install the compiler(s) you want.
64 You just need the Atmel AVR 8-bit Toolchain. The latest should be fine, as of writing it was 3.4.3.
66 http://www.atmel.com/tools/atmelavrtoolchainforwindows.aspx
68 Extract the files to a directory, say C:\avr8-gnu-toolchain. Then copy all the folders in that directory to the Cygwin directory.
70 (You can also just setup the paths, but this is faster/simpler. Might screw up your Cygwin though).
77 Download the latest version of Mentor Graphics Sourcery CodeBench ARM EABI.
79 http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/
81 Use the installer and make sure you add the binaries to your path within the installer.
85 ----------------------
86 Selecting Architecture
87 ----------------------
89 This is where you choose which architecture you want to build for.
91 - Teensy 1.0 (Not tested)
92 - Teensy 1.0++ (Not tested)
98 Open up CMakeLists.txt in your favourite text editor.
105 #| Specify the compiler family to use
106 #| Currently only supports AVR and ARM
107 #| "avr" # Teensy 1.0
108 #| "avr" # Teensy 2.0
109 #| "avr" # Teensy++ 1.0
110 #| "avr" # Teensy++ 2.0
111 #| "arm" # Teensy 3.0
112 #| "arm" # Teensy 3.1
114 set( COMPILER_FAMILY "avr" )
117 Just change the COMPILER_FAMILY variable to whatever you are trying to build for.
119 NOTE: If you change this option, you will *may* to delete the build directory that is created in the Building sections below.
123 ----------------------
124 Selecting Microcontroller
125 ----------------------
127 Even if you selected the "avr" family of microcontroller architectures, you will still need to specify a target microcontroller (or once more ARM microcontrollers are supported).
129 Open up avr.cmake (or arm.cmake) in your favourite text editor.
133 # Atmel Defines and Linker Options
137 #| You _MUST_ set this to match the board you are using
138 #| type "make clean" after changing this, so all files will be rebuilt
140 #| "at90usb162" # Teensy 1.0
141 #| "atmega32u4" # Teensy 2.0
142 #| "at90usb646" # Teensy++ 1.0
143 #| "at90usb1286" # Teensy++ 2.0
145 set( MCU "at90usb1286" )
150 # ARM Defines and Linker Options
153 #| Chip Name (Linker)
154 #| You _MUST_ set this to match the board you are using
155 #| type "make clean" after changing this, so all files will be rebuilt
157 #| "mk20dx128" # Teensy 3.0
158 #| "mk20dx256" # Teensy 3.1
160 set( CHIP "mk20dx128" )
163 Just change the CHIP variable to the microcontroller you are trying to build for.
165 NOTE: If you change this option, you will *need* to delete the build directory that is created in the Building sections below.
169 ----------------------
171 ----------------------
173 WARNING: Not all modules are compatible, and some modules may have dependencies on other modules.
175 This is where the options start getting interesting.
176 The Kiibohd Controller is designed around a set of 4 types of modules that correspond to different functionality:
183 The Scan Module is where the most interesting stuff happens. These modules take in "keypress data".
184 A converter Scan Module will interpret a protocol into key press/releases.
185 A matrix Scan Module may inherit from the matrix module to scan keypress from a matrix
186 This module just has to give press/release codes, but does have some callback control to other modules depending on the lifecycle for press/release codes (this can be very complicated depending on the protocol).
187 Each Scan Module has it's own default keymap/modifier map. (TODO recommend keymap changing in the Macro Module).
189 Some scan modules have very specialized hardware requirements, each module directory should have at least a link to the needed parts and/or schematics (TODO!).
192 The Macro Module takes care of the mapping of the key press/release code into an Output (USB) scan code.
193 Any layering, macros, keypress intelligence/reaction is done here.
196 The Output Module is the module dealing with output from the microcontroller. Currently USB is the only output protocol.
197 Different USB output implementations are available, pjrc being the safest/least featureful one.
198 Debug capabilities may depend on the module selected.
201 The Debug Module enables various things like the Teensy LED on errors, debug terminal output.
202 (TODO get true UART working in avr, not just arm)
206 Open up setup.cmake in your favourite text editor.
213 #| Note: This is the only section you probably want to modify
214 #| Each module is defined by it's own folder (e.g. Scan/Matrix represents the "Matrix" module)
215 #| All of the modules must be specified, as they generate the sources list of files to compile
216 #| Any modifications to this file will cause a complete rebuild of the project
218 #| Please look at the {Scan,Macro,Output,Debug}/module.txt for information on the modules and how to create new ones
220 ##| Deals with acquiring the keypress information and turning it into a key index
221 set( ScanModule "avr-capsense" )
223 ##| Uses the key index and potentially applies special conditions to it, mapping it to a usb key code
224 set( MacroModule "buffer" )
226 ##| Sends the current list of usb key codes through USB HID
227 set( OutputModule "pjrc" )
229 ##| Debugging source to use, each module has it's own set of defines that it sets
230 set( DebugModule "full" )
233 Look at each module individually for it's requirements. There is chip/architecture dependency checking but some permutations of modules may not be tested/compile.
236 There are also CMake options for temporarily selecting modules. But it's easier to just edit the file.
237 e.g. cmake -DScanModuleOverride=<module name>
241 ----------------------
243 ----------------------
254 [master]: cmake .. [...sy/avr-capsense-haata/build](hyatt@901Mas:pts/4)
259 -- Detected Scan Module Source Files:
260 Scan/avr-capsense/scan_loop.c
261 -- Detected Macro Module Source Files:
263 -- Detected Output Module Source Files:
264 Output/pjrc/usb_com.c;Output/pjrc/avr/usb_keyboard_debug.c
265 -- Detected Debug Module Source Files:
266 Debug/full/../led/led.c;Debug/full/../print/print.c
269 -- Build files have been written to: /home/hyatt/Source/Teensy/avr-capsense-haata/build
270 [master]: make [...sy/avr-capsense-haata/build](hyatt@901Mas:pts/4)
271 Scanning dependencies of target kiibohd.elf
272 [ 12%] Building C object CMakeFiles/kiibohd.elf.dir/main.c.o
273 [ 25%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/avr-capsense/scan_loop.c.o
274 [ 37%] Building C object CMakeFiles/kiibohd.elf.dir/Macro/buffer/macro.c.o
275 [ 50%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrc/usb_com.c.o
276 [ 62%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrc/avr/usb_keyboard_debug.c.o
277 [ 75%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/led/led.c.o
278 [ 87%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/print/print.c.o
279 Linking C executable kiibohd.elf
280 Creating load file for Flash: kiibohd.hex
281 Creating Extended Listing: kiibohd.lss
282 Creating Symbol Table: kiibohd.sym
283 [ 87%] Built target kiibohd.elf
284 Scanning dependencies of target SizeAfter
285 [100%] Size after generation:
286 text data bss dec hex filename
287 0 6112 0 6112 17e0 kiibohd.hex
288 5792 320 852 6964 1b34 kiibohd.elf
289 [100%] Built target SizeAfter
293 ----------------------
294 Linux Loading Firmware
295 ----------------------
297 The 'load' script that is created during the build can load the firmware over USB.
298 It uses sudo, so make sure you have the priviledges.
304 ----------------------
306 ----------------------
311 wincmake -G "Unix Makefiles" ..
316 $ cmake -G "Unix Makefiles" ..
323 -- Detected Scan Module Source Files:
324 Scan/SKM67001/../matrix/matrix_scan.c;Scan/SKM67001/../matrix/scan_loop.c
325 -- Detected Macro Module Source Files:
326 Macro/PartialMap/macro.c
327 -- Detected Output Module Source Files:
328 Output/pjrcUSB/output_com.c;Output/pjrcUSB/avr/usb_keyboard_serial.c
329 -- Detected Debug Module Source Files:
330 Debug/full/../cli/cli.c;Debug/full/../led/led.c;Debug/full/../print/print.c
331 -- Found Git: C:/cygwin64/bin/git.exe (found version "1.7.9")
334 -- Build files have been written to: C:/cygwin64/home/jacob.alexander/src/capsense-beta/build
336 jacob.alexander@JALEXANDER2-LT ~/src/capsense-beta/build
338 Scanning dependencies of target kiibohd.elf
339 [ 10%] Building C object CMakeFiles/kiibohd.elf.dir/main.c.obj
340 [ 20%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/matrix/matrix_scan.c.obj
341 [ 30%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/matrix/scan_loop.c.obj
342 [ 40%] Building C object CMakeFiles/kiibohd.elf.dir/Macro/PartialMap/macro.c.obj
343 [ 50%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrcUSB/output_com.c.obj
344 [ 60%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrcUSB/avr/usb_keyboard_serial.c.obj
345 [ 70%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/cli/cli.c.obj
346 [ 80%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/led/led.c.obj
347 [ 90%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/print/print.c.obj
348 Linking C executable kiibohd.elf
349 Creating load file for Flash: kiibohd.hex
350 Creating Extended Listing: kiibohd.lss
351 Creating Symbol Table: kiibohd.sym
352 [ 90%] Built target kiibohd.elf
353 Scanning dependencies of target SizeAfter
354 [100%] Size after generation
355 Flash Usage: data (hex)
356 RAM Usage: data (elf)
357 text data bss dec hex filename
358 0 9738 0 9738 260a kiibohd.hex
359 7982 1756 264 10002 2712 kiibohd.elf
360 [100%] Built target SizeAfter
364 ----------------------
365 Windows Loading Firmware
366 ----------------------
370 ----------------------
372 ----------------------
376 ----------------------
377 Mac OS X Loading Firmware
378 ----------------------
383 ----------------------
384 Virtual Serial Port - CLI
385 ----------------------
387 Rather than use a special program that can interpret Raw HID, this controller exposes a USB Serial CDC endpoint.
388 This allows for you to use a generic serial terminal to debug/control the keyboard firmware (e.g. Tera Term, minicom, screen)
394 I generally use screen.
396 sudo screen /dev/ttyACM0
403 TODO Probably COM1, but not exactly sure. Tera Term.
410 TODO (What is the usual device name). screen if possible.