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)
20 AVR Specific (Teensy 1.0/++,2.0/++) (try to use something recent, suggested versions below)
22 - avr-binutils (~2.23.2)
26 ARM Specific (Teensy 3.0/3.1) (Sourcery CodeBench Lite for ARM EABI
27 (http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/)
31 - arm-none-eaby-binutils
32 (I've actually had some issues with Sourcery CodeBench on Linux, so I often just use these)
36 ----------------------
38 ----------------------
40 Compiling on Windows does work, just it's a bunch more work.
42 First make sure Cygwin is installed - http://www.cygwin.com/ - 32bit or 64bit is fine. Make sure the following are installed:
44 - git (needed for some compilation info)
50 Also install the Windows version of CMake - http://cmake.org/cmake/resources/software.html
51 This is in addition to the Cygwin version. This is an easier alternative to installing another C compiler.
52 Add the following line to your .bashrc, making sure the CMake path is correct:
53 alias wincmake="PATH='/cygdrive/c/Program Files (x86)/CMake 2.8'/bin:\"${PATH}\" cmake"
55 Next, install the compiler(s) you want.
62 You just need the Atmel AVR 8-bit Toolchain. The latest should be fine, as of writing it was 3.4.3.
64 http://www.atmel.com/tools/atmelavrtoolchainforwindows.aspx
66 Extract the files to a directory, say C:\avr8-gnu-toolchain. Then copy all the folders in that directory to the Cygwin directory.
68 (You can also just setup the paths, but this is faster/simpler. Might screw up your Cygwin though).
75 Download the latest version of Mentor Graphics Sourcery CodeBench ARM EABI.
77 http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/
79 Use the installer and make sure you add the binaries to your path within the installer.
83 ----------------------
84 Selecting Architecture
85 ----------------------
87 This is where you choose which architecture you want to build for.
89 - Teensy 1.0 (Not tested)
90 - Teensy 1.0++ (Not tested)
96 Open up CMakeLists.txt in your favourite text editor.
103 #| Specify the compiler family to use
104 #| Currently only supports AVR and ARM
105 #| "avr" # Teensy 1.0
106 #| "avr" # Teensy 2.0
107 #| "avr" # Teensy++ 1.0
108 #| "avr" # Teensy++ 2.0
109 #| "arm" # Teensy 3.0
110 #| "arm" # Teensy 3.1
112 set( COMPILER_FAMILY "avr" )
115 Just change the COMPILER_FAMILY variable to whatever you are trying to build for.
117 NOTE: If you change this option, you will *may* to delete the build directory that is created in the Building sections below.
121 ----------------------
122 Selecting Microcontroller
123 ----------------------
125 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).
127 Open up avr.cmake (or arm.cmake) in your favourite text editor.
131 # Atmel Defines and Linker Options
135 #| You _MUST_ set this to match the board you are using
136 #| type "make clean" after changing this, so all files will be rebuilt
138 #| "at90usb162" # Teensy 1.0
139 #| "atmega32u4" # Teensy 2.0
140 #| "at90usb646" # Teensy++ 1.0
141 #| "at90usb1286" # Teensy++ 2.0
143 set( MCU "at90usb1286" )
148 # ARM Defines and Linker Options
151 #| Chip Name (Linker)
152 #| You _MUST_ set this to match the board you are using
153 #| type "make clean" after changing this, so all files will be rebuilt
155 #| "mk20dx128" # Teensy 3.0
156 #| "mk20dx256" # Teensy 3.1
158 set( CHIP "mk20dx128" )
161 Just change the CHIP variable to the microcontroller you are trying to build for.
163 NOTE: If you change this option, you will *need* to delete the build directory that is created in the Building sections below.
167 ----------------------
169 ----------------------
171 WARNING: Not all modules are compatible, and some modules may have dependencies on other modules.
173 This is where the options start getting interesting.
174 The Kiibohd Controller is designed around a set of 4 types of modules that correspond to different functionality:
181 The Scan Module is where the most interesting stuff happens. These modules take in "keypress data".
182 A converter Scan Module will interpret a protocol into key press/releases.
183 A matrix Scan Module may inherit from the matrix module to scan keypress from a matrix
184 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).
185 Each Scan Module has it's own default keymap/modifier map. (TODO recommend keymap changing in the Macro Module).
187 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!).
190 The Macro Module takes care of the mapping of the key press/release code into an Output (USB) scan code.
191 Any layering, macros, keypress intelligence/reaction is done here.
194 The Output Module is the module dealing with output from the microcontroller. Currently USB is the only output protocol.
195 Different USB output implementations are available, pjrc being the safest/least featureful one.
196 Debug capabilities may depend on the module selected.
199 The Debug Module enables various things like the Teensy LED on errors, debug terminal output.
200 (TODO get true UART working in avr, not just arm)
204 Open up setup.cmake in your favourite text editor.
211 #| Note: This is the only section you probably want to modify
212 #| Each module is defined by it's own folder (e.g. Scan/Matrix represents the "Matrix" module)
213 #| All of the modules must be specified, as they generate the sources list of files to compile
214 #| Any modifications to this file will cause a complete rebuild of the project
216 #| Please look at the {Scan,Macro,Output,Debug}/module.txt for information on the modules and how to create new ones
218 ##| Deals with acquiring the keypress information and turning it into a key index
219 set( ScanModule "avr-capsense" )
221 ##| Uses the key index and potentially applies special conditions to it, mapping it to a usb key code
222 set( MacroModule "buffer" )
224 ##| Sends the current list of usb key codes through USB HID
225 set( OutputModule "pjrc" )
227 ##| Debugging source to use, each module has it's own set of defines that it sets
228 set( DebugModule "full" )
231 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.
234 There are also CMake options for temporarily selecting modules. But it's easier to just edit the file.
235 e.g. cmake -DScanModuleOverride=<module name>
239 ----------------------
241 ----------------------
252 [master]: cmake .. [...sy/avr-capsense-haata/build](hyatt@901Mas:pts/4)
257 -- Detected Scan Module Source Files:
258 Scan/avr-capsense/scan_loop.c
259 -- Detected Macro Module Source Files:
261 -- Detected Output Module Source Files:
262 Output/pjrc/usb_com.c;Output/pjrc/avr/usb_keyboard_debug.c
263 -- Detected Debug Module Source Files:
264 Debug/full/../led/led.c;Debug/full/../print/print.c
267 -- Build files have been written to: /home/hyatt/Source/Teensy/avr-capsense-haata/build
268 [master]: make [...sy/avr-capsense-haata/build](hyatt@901Mas:pts/4)
269 Scanning dependencies of target kiibohd.elf
270 [ 12%] Building C object CMakeFiles/kiibohd.elf.dir/main.c.o
271 [ 25%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/avr-capsense/scan_loop.c.o
272 [ 37%] Building C object CMakeFiles/kiibohd.elf.dir/Macro/buffer/macro.c.o
273 [ 50%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrc/usb_com.c.o
274 [ 62%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrc/avr/usb_keyboard_debug.c.o
275 [ 75%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/led/led.c.o
276 [ 87%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/print/print.c.o
277 Linking C executable kiibohd.elf
278 Creating load file for Flash: kiibohd.hex
279 Creating Extended Listing: kiibohd.lss
280 Creating Symbol Table: kiibohd.sym
281 [ 87%] Built target kiibohd.elf
282 Scanning dependencies of target SizeAfter
283 [100%] Size after generation:
284 text data bss dec hex filename
285 0 6112 0 6112 17e0 kiibohd.hex
286 5792 320 852 6964 1b34 kiibohd.elf
287 [100%] Built target SizeAfter
291 ----------------------
292 Linux Loading Firmware
293 ----------------------
295 The 'load' script that is created during the build can load the firmware over USB.
296 It uses sudo, so make sure you have the priviledges.
302 ----------------------
304 ----------------------
309 wincmake -G "Unix Makefiles" ..
314 $ cmake -G "Unix Makefiles" ..
321 -- Detected Scan Module Source Files:
322 Scan/SKM67001/../matrix/matrix_scan.c;Scan/SKM67001/../matrix/scan_loop.c
323 -- Detected Macro Module Source Files:
324 Macro/PartialMap/macro.c
325 -- Detected Output Module Source Files:
326 Output/pjrcUSB/output_com.c;Output/pjrcUSB/avr/usb_keyboard_serial.c
327 -- Detected Debug Module Source Files:
328 Debug/full/../cli/cli.c;Debug/full/../led/led.c;Debug/full/../print/print.c
329 -- Found Git: C:/cygwin64/bin/git.exe (found version "1.7.9")
332 -- Build files have been written to: C:/cygwin64/home/jacob.alexander/src/capsense-beta/build
334 jacob.alexander@JALEXANDER2-LT ~/src/capsense-beta/build
336 Scanning dependencies of target kiibohd.elf
337 [ 10%] Building C object CMakeFiles/kiibohd.elf.dir/main.c.obj
338 [ 20%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/matrix/matrix_scan.c.obj
339 [ 30%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/matrix/scan_loop.c.obj
340 [ 40%] Building C object CMakeFiles/kiibohd.elf.dir/Macro/PartialMap/macro.c.obj
341 [ 50%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrcUSB/output_com.c.obj
342 [ 60%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrcUSB/avr/usb_keyboard_serial.c.obj
343 [ 70%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/cli/cli.c.obj
344 [ 80%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/led/led.c.obj
345 [ 90%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/print/print.c.obj
346 Linking C executable kiibohd.elf
347 Creating load file for Flash: kiibohd.hex
348 Creating Extended Listing: kiibohd.lss
349 Creating Symbol Table: kiibohd.sym
350 [ 90%] Built target kiibohd.elf
351 Scanning dependencies of target SizeAfter
352 [100%] Size after generation
353 Flash Usage: data (hex)
354 RAM Usage: data (elf)
355 text data bss dec hex filename
356 0 9738 0 9738 260a kiibohd.hex
357 7982 1756 264 10002 2712 kiibohd.elf
358 [100%] Built target SizeAfter
362 ----------------------
363 Windows Loading Firmware
364 ----------------------
368 ----------------------
370 ----------------------
374 ----------------------
375 Mac OS X Loading Firmware
376 ----------------------
381 ----------------------
382 Virtual Serial Port - CLI
383 ----------------------
385 Rather than use a special program that can interpret Raw HID, this controller exposes a USB Serial CDC endpoint.
386 This allows for you to use a generic serial terminal to debug/control the keyboard firmware (e.g. Tera Term, minicom, screen)
392 I generally use screen.
394 sudo screen /dev/ttyACM0
401 TODO Probably COM1, but not exactly sure. Tera Term.
408 TODO (What is the usual device name). screen if possible.