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)
47 And make sure CMake is *NOT* installed through Cygwin. This is extremely important.
48 If this is not possible, you'll have to play with your paths in Cygwin to prioritize the Windows version of CMake.
50 Install the latest version of CMake - http://cmake.org/cmake/resources/software.html
51 Make sure to have CMake add itself to at least your PATH in the installer.
52 (If this errors out, you'll have to add CMake to your .bashrc path).
54 Next, install the compiler(s) you want.
60 You just need the Atmel AVR 8-bit Toolchain. The latest should be fine, as of writing it was 3.4.3.
62 http://www.atmel.com/tools/atmelavrtoolchainforwindows.aspx
64 Extract the files to a directory, say C:\avr8-gnu-toolchain. Then copy all the folders in that directory to the Cygwin directory.
66 (You can also just setup the paths, but this is faster/simpler. Might screw up your Cygwin though).
73 Download the latest version of Mentor Graphics Sourcery CodeBench ARM EABI.
75 http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/
77 Use the installer and make sure you add the binaries to your path within the installer.
81 ----------------------
82 Selecting Architecture
83 ----------------------
85 This is where you choose which architecture you want to build for.
87 - Teensy 1.0 (Not tested)
88 - Teensy 1.0++ (Not tested)
94 Open up CMakeLists.txt in your favourite text editor.
101 #| Specify the compiler family to use
102 #| Currently only supports AVR and ARM
103 #| "avr" # Teensy 1.0
104 #| "avr" # Teensy 2.0
105 #| "avr" # Teensy++ 1.0
106 #| "avr" # Teensy++ 2.0
107 #| "arm" # Teensy 3.0
108 #| "arm" # Teensy 3.1
110 set( COMPILER_FAMILY "avr" )
113 Just change the COMPILER_FAMILY variable to whatever you are trying to build for.
115 NOTE: If you change this option, you will *may* to delete the build directory that is created in the Building sections below.
119 ----------------------
120 Selecting Microcontroller
121 ----------------------
123 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).
125 Open up avr.cmake (or arm.cmake) in your favourite text editor.
129 # Atmel Defines and Linker Options
133 #| You _MUST_ set this to match the board you are using
134 #| type "make clean" after changing this, so all files will be rebuilt
136 #| "at90usb162" # Teensy 1.0
137 #| "atmega32u4" # Teensy 2.0
138 #| "at90usb646" # Teensy++ 1.0
139 #| "at90usb1286" # Teensy++ 2.0
141 set( MCU "at90usb1286" )
146 # ARM Defines and Linker Options
149 #| Chip Name (Linker)
150 #| You _MUST_ set this to match the board you are using
151 #| type "make clean" after changing this, so all files will be rebuilt
153 #| "mk20dx128" # Teensy 3.0
154 #| "mk20dx256" # Teensy 3.1
156 set( CHIP "mk20dx128" )
159 Just change the CHIP variable to the microcontroller you are trying to build for.
161 NOTE: If you change this option, you will *need* to delete the build directory that is created in the Building sections below.
165 ----------------------
167 ----------------------
169 WARNING: Not all modules are compatible, and some modules may have dependencies on other modules.
171 This is where the options start getting interesting.
172 The Kiibohd Controller is designed around a set of 4 types of modules that correspond to different functionality:
179 The Scan Module is where the most interesting stuff happens. These modules take in "keypress data".
180 A converter Scan Module will interpret a protocol into key press/releases.
181 A matrix Scan Module may inherit from the matrix module to scan keypress from a matrix
182 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).
183 Each Scan Module has it's own default keymap/modifier map. (TODO recommend keymap changing in the Macro Module).
185 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!).
188 The Macro Module takes care of the mapping of the key press/release code into an Output (USB) scan code.
189 Any layering, macros, keypress intelligence/reaction is done here.
192 The Output Module is the module dealing with output from the microcontroller. Currently USB is the only output protocol.
193 Different USB output implementations are available, pjrc being the safest/least featureful one.
194 Debug capabilities may depend on the module selected.
197 The Debug Module enables various things like the Teensy LED on errors, debug terminal output.
198 (TODO get true UART working in avr, not just arm)
202 Open up setup.cmake in your favourite text editor.
209 #| Note: This is the only section you probably want to modify
210 #| Each module is defined by it's own folder (e.g. Scan/Matrix represents the "Matrix" module)
211 #| All of the modules must be specified, as they generate the sources list of files to compile
212 #| Any modifications to this file will cause a complete rebuild of the project
214 #| Please look at the {Scan,Macro,Output,Debug}/module.txt for information on the modules and how to create new ones
216 ##| Deals with acquiring the keypress information and turning it into a key index
217 set( ScanModule "avr-capsense" )
219 ##| Uses the key index and potentially applies special conditions to it, mapping it to a usb key code
220 set( MacroModule "buffer" )
222 ##| Sends the current list of usb key codes through USB HID
223 set( OutputModule "pjrc" )
225 ##| Debugging source to use, each module has it's own set of defines that it sets
226 set( DebugModule "full" )
229 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.
232 There are also CMake options for temporarily selecting modules. But it's easier to just edit the file.
233 e.g. cmake -DScanModuleOverride=<module name>
237 ----------------------
239 ----------------------
250 [master]: cmake .. [...sy/avr-capsense-haata/build](hyatt@901Mas:pts/4)
255 -- Detected Scan Module Source Files:
256 Scan/avr-capsense/scan_loop.c
257 -- Detected Macro Module Source Files:
259 -- Detected Output Module Source Files:
260 Output/pjrc/usb_com.c;Output/pjrc/avr/usb_keyboard_debug.c
261 -- Detected Debug Module Source Files:
262 Debug/full/../led/led.c;Debug/full/../print/print.c
265 -- Build files have been written to: /home/hyatt/Source/Teensy/avr-capsense-haata/build
266 [master]: make [...sy/avr-capsense-haata/build](hyatt@901Mas:pts/4)
267 Scanning dependencies of target kiibohd.elf
268 [ 12%] Building C object CMakeFiles/kiibohd.elf.dir/main.c.o
269 [ 25%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/avr-capsense/scan_loop.c.o
270 [ 37%] Building C object CMakeFiles/kiibohd.elf.dir/Macro/buffer/macro.c.o
271 [ 50%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrc/usb_com.c.o
272 [ 62%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrc/avr/usb_keyboard_debug.c.o
273 [ 75%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/led/led.c.o
274 [ 87%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/print/print.c.o
275 Linking C executable kiibohd.elf
276 Creating load file for Flash: kiibohd.hex
277 Creating Extended Listing: kiibohd.lss
278 Creating Symbol Table: kiibohd.sym
279 [ 87%] Built target kiibohd.elf
280 Scanning dependencies of target SizeAfter
281 [100%] Size after generation:
282 text data bss dec hex filename
283 0 6112 0 6112 17e0 kiibohd.hex
284 5792 320 852 6964 1b34 kiibohd.elf
285 [100%] Built target SizeAfter
289 ----------------------
290 Linux Loading Firmware
291 ----------------------
293 The 'load' script that is created during the build can load the firmware over USB.
294 It uses sudo, so make sure you have the priviledges.
300 ----------------------
302 ----------------------
307 cmake -G "Unix Makefiles" ..
312 $ cmake -G "Unix Makefiles" ..
319 -- Detected Scan Module Source Files:
320 Scan/SKM67001/../matrix/matrix_scan.c;Scan/SKM67001/../matrix/scan_loop.c
321 -- Detected Macro Module Source Files:
322 Macro/PartialMap/macro.c
323 -- Detected Output Module Source Files:
324 Output/pjrcUSB/output_com.c;Output/pjrcUSB/avr/usb_keyboard_serial.c
325 -- Detected Debug Module Source Files:
326 Debug/full/../cli/cli.c;Debug/full/../led/led.c;Debug/full/../print/print.c
327 -- Found Git: C:/cygwin64/bin/git.exe (found version "1.7.9")
330 -- Build files have been written to: C:/cygwin64/home/jacob.alexander/src/capsense-beta/build
332 jacob.alexander@JALEXANDER2-LT ~/src/capsense-beta/build
334 Scanning dependencies of target kiibohd.elf
335 [ 10%] Building C object CMakeFiles/kiibohd.elf.dir/main.c.obj
336 [ 20%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/matrix/matrix_scan.c.obj
337 [ 30%] Building C object CMakeFiles/kiibohd.elf.dir/Scan/matrix/scan_loop.c.obj
338 [ 40%] Building C object CMakeFiles/kiibohd.elf.dir/Macro/PartialMap/macro.c.obj
339 [ 50%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrcUSB/output_com.c.obj
340 [ 60%] Building C object CMakeFiles/kiibohd.elf.dir/Output/pjrcUSB/avr/usb_keyboard_serial.c.obj
341 [ 70%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/cli/cli.c.obj
342 [ 80%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/led/led.c.obj
343 [ 90%] Building C object CMakeFiles/kiibohd.elf.dir/Debug/print/print.c.obj
344 Linking C executable kiibohd.elf
345 Creating load file for Flash: kiibohd.hex
346 Creating Extended Listing: kiibohd.lss
347 Creating Symbol Table: kiibohd.sym
348 [ 90%] Built target kiibohd.elf
349 Scanning dependencies of target SizeAfter
350 [100%] Size after generation
351 Flash Usage: data (hex)
352 RAM Usage: data (elf)
353 text data bss dec hex filename
354 0 9738 0 9738 260a kiibohd.hex
355 7982 1756 264 10002 2712 kiibohd.elf
356 [100%] Built target SizeAfter
360 ----------------------
361 Windows Loading Firmware
362 ----------------------
366 ----------------------
368 ----------------------
372 ----------------------
373 Mac OS X Loading Firmware
374 ----------------------
379 ----------------------
380 Virtual Serial Port - CLI
381 ----------------------
383 Rather than use a special program that can interpret Raw HID, this controller exposes a USB Serial CDC endpoint.
384 This allows for you to use a generic serial terminal to debug/control the keyboard firmware (e.g. Tera Term, minicom, screen)
390 I generally use screen.
392 sudo screen /dev/ttyACM0
399 TODO Probably COM1, but not exactly sure. Tera Term.
406 TODO (What is the usual device name). screen if possible.