1 #Planck Advanced (but not too advanced) `cygwin` Users Guide
2 If you are a user of the [cygwin environment](https://cygwin.com) in Windows and want the freedom to use the latest tools available, then this is the guide for you. If compiling your own copy of the latest and greatest Gnu C Compiler makes you super happy, then this is the guide for you. If the command line make you smile, then this is the guide for you.
4 This guide was written step by step as I went through the process on a `Windows 10` `x86_64` and a `Windows 7` `amd k10` based system. This should be generally applicable to to any `Windows` environment with `cygwin`.
6 #####Do not skip steps. Do not move past a step until the previous step finishes successfully.
8 Based on [avr-libc installation guide](http://www.nongnu.org/avr-libc/user-manual/install_tools.html)
10 ##Get the Required Packages
11 Download the `cygwin` setup ([x86_64](https://cygwin.com/setup-x86_64.exe)) and install the default system plus the following if they are not already selected:
29 The following sources will be required:
30 - [gmp](https://gmplib.org/) (6.1.0)
31 - [mpfr](http://www.mpfr.org/) (3.1.4)
32 - [mpc](http://www.multiprecision.org/) (1.0.3)
33 - [binutils](https://www.sourceware.org/binutils/) (2.26)
34 - [gcc](https://gcc.gnu.org/) (5.3.0)
35 - [avr-libc](http://www.nongnu.org/avr-libc/) (2.0.0)
37 The `dfu-programmer` will be required to flash the new firmware
38 - [dfu-programmer](https://dfu-programmer.github.io/) (0.7.2)
40 The set of commands below will create a directory (`~/local/avr`) for the sources you compile to be installed on the machine and a directory (`~/src`) for these source files to be stored. The commands then download the sources of the needed packages and unpack them. Note: the expand commands are different depending on if the packages are offered as a `bz2` or `gz` archive
46 $ wget https://gmplib.org/download/gmp/gmp-6.1.0.tar.bz2
47 $ wget http://www.mpfr.org/mpfr-3.1.4/mpfr-3.1.4.tar.bz2
48 $ wget ftp://ftp.gnu.org/gnu/mpc/mpc-1.0.3.tar.gz
49 $ wget http://ftp.gnu.org/gnu/binutils/binutils-2.26.tar.gz
50 $ wget http://mirror0.babylon.network/gcc/releases/gcc-5.3.0/gcc-5.3.0.tar.gz
51 $ wget http://download.savannah.gnu.org/releases/avr-libc/avr-libc-2.0.0.tar.bz2
52 $ tar -xjf gmp-6.1.0.tar.bz2
53 $ tar -xjf mpfr-3.1.4.tar.bz2
54 $ tar -zxf mpc-1.0.3.tar.gz
55 $ tar -zxf binutils-2.26.tar.gz
56 $ tar -zxf gcc-5.3.0.tar.gz
57 $ tar -xjf avr-libc-2.0.0.tar.bz2
60 ##Setup the Build Environment
61 These commands will set up the install directory and the `PATH` variable, which will allow you to access your installed packages. Note: if you close the `cygwin` terminal window, you will need to rerun these commands, they are not permanent.
63 $ PREFIX=$HOME/local/avr
65 $ PATH=/usr/local/bin:/usr/local/lib:/usr/local/include:/bin:/lib:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS
66 $ PATH=$PATH:$PREFIX/bin:$PREFIX/lib
70 ##The `gcc` Required Math Library Packages
71 The following packages are required to be complied and installed in order to compile `gcc`. They are not sufficiently available through the `cygwin` package system, so we have to make them ourselves. They must be complied in this order because each one depends on the previous. Verfiy that for each package, `make check` returns all passing and no fails.
73 ###Build and Install `gmp`
76 $ ./configure --enable-static --disable-shared
82 ###Build and Install `mpfr`
85 $ ./configure --with-gmp-build=../gmp-6.1.0 --enable-static --disable-shared
91 ###Build and Install `mpc`
94 $ ./configure --with-gmp=/usr/local --with-mpfr=/usr/local --enable-static --disable-shared
101 You can build and install a brand new `gcc` or you can use the one supplied by `cygwin`. This will take about 4-5 hours to compile (It is a "native build", so it does the entire build **3 times**. This takes a long while).
103 ###Build and Install `gcc` for Your Machine
108 $ ../configure --enable-languages=c,c++ --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local --enable-static --disable-shared
114 ###Build and Install `binutils` for Your Machine
116 $ cd ~/src/binutils-2.26
124 ##Buliding `binutils`, `gcc`, and `avr-libc` for the AVR system
125 Now we can make the critical stuff for compiling our firmware: `binutils`, `gcc`, and `avr-libc` for the AVR architecture. These allow us to build and manipulate the firmware for the keyboard.
127 ###Build `binutils` for AVR
128 If you plan to build and install `avr-gdb` also, use the `gdb` install at the end of this guide as it also builds the `binutils`
130 $ cd ~/src/binutils-2.26
133 $ ../configure --prefix=$PREFIX --target=avr --disable-nls
138 ###Build `gcc` for AVR
143 $ ../configure --prefix=$PREFIX --target=avr --enable-languages=c,c++ --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local --enable-static --disable-shared --disable-nls --disable-libssp --with-dwarf2
148 ###Build `avr-libc` for AVR
149 For building the `avr-libc`, we have to specify the host build system. In my case it is `x86_64-unknown-cygwin`. You can look for build system type in the `gcc` configure notes for the proper `--build` specification to pass when you configure `avr-libc`.
151 $ cd ~/src/avr-libc-2.0.0
152 $ ./configure --prefix=$PREFIX --build=x86_64-unknown-cygwin --host=avr
157 ##Building 'dfu-programmer' for flashing the firmware via USB and installing the drivers
158 We can either build our own, or use the precomplied binaries. The precompiled binaries don't play well with `cygwin` so it is better to build them ourselves. The procedure for the precompiled binaries is included at the end of this guide.
160 ### Build and Install the `libusb`
161 The `dfu-programmer` requires `libusb` so that it can interact with the USB system. These repos must be bootstrapped in order to create an appropriate `./configure` and `Makefile` for your system.
164 $ git clone https://github.com/libusb/libusb.git
172 ### Build and Install the `dfu-programmer`
175 $ git clone https://github.com/dfu-programmer/dfu-programmer.git
183 Verify the installation with:
185 $ which dfu-programmer
186 /usr/local/bin/dfu-programmer
190 https://github.com/dfu-programmer/dfu-programmer
191 Type 'dfu-programmer --help' for a list of commands
192 'dfu-programmer --targets' to list supported target devices
194 If you are not getting the above result, you will not be able to flash the firmware!
196 ###Install the USB drivers
197 The drivers are included in the windows binary version of [`dfu-programmer` 0.7.2](http://iweb.dl.sourceforge.net/project/dfu-programmer/dfu-programmer/0.7.2/dfu-programmer-win-0.7.2.zip).
200 $ wget http://iweb.dl.sourceforge.net/project/dfu-programmer/dfu-programmer/0.7.2/dfu-programmer-win-0.7.2.zip
201 $ unzip dfu-programmer-win-0.7.2.zip -d dfu-programmer-win-0.7.2
206 The official drivers are found in [Atmel's `FLIP` installer](http://www.atmel.com/images/Flip%20Installer%20-%203.4.7.112.exe). Download and then install `FLIP`. Upon installation, the drivers will be found in `C:\Program Files (x86)\Atmel\Flip 3.4.7\usb`.
208 Then, from an **administrator-privileged** `Windows` terminal, run the following command (adjust the path for username, etc. as necessary) and accept the prompt that pops up:
210 C:\> pnputil -i -a C:\cygwin64\home\Kevin\src\dfu-programmer-win-0.7.2\dfu-prog-usb-1.2.2\atmel_usb_dfu.inf
212 C:\> pnputil -i -a "C:\Program Files (x86)\Atmel\Flip 3.4.7\usb\atmel_usb_dfu.inf"
215 This should be the result:
217 Microsoft PnP Utility
219 Processing inf : atmel_usb_dfu.inf
220 Successfully installed the driver on a device on the system.
221 Driver package added successfully.
222 Published name : oem104.inf
226 Number successfully imported: 1
229 Alternatively, the `Windows` driver can be installed when prompted by `Windows` when the keyboard is attached. Do not let `Windows` search for a driver; specify the path to search for a driver and point it to the `atmel_usb_dfu.inf` file.
231 ##Building and Flashing the Planck firmware!
232 If you did everything else right. This part should be a snap! Grab the latest sources from `github`, make the Plank firmware, then flash it.
234 ###Build Planck and Load the Firmware
237 $ git clone https://github.com/qmk/qmk_firmware.git
238 $ cd qmk_firmware/keyboards/planck
242 Make sure there are no errors. You should end up with this or something similar:
244 Creating load file for Flash: planck.hex
245 avr-objcopy -O ihex -R .eeprom -R .fuse -R .lock -R .signature planck.elf planck.hex
247 Creating load file for EEPROM: planck.eep
248 avr-objcopy -j .eeprom --set-section-flags=.eeprom="alloc,load" \
249 --change-section-lma .eeprom=0 --no-change-warnings -O ihex planck.elf planck.eep || exit 0
251 Creating Extended Listing: planck.lss
252 avr-objdump -h -S -z planck.elf > planck.lss
254 Creating Symbol Table: planck.sym
255 avr-nm -n planck.elf > planck.sym
258 text data bss dec hex filename
259 18602 82 155 18839 4997 planck.elf
261 -------- end --------
264 If you do not get the above, you **did not** build the firmware, and you will have nothing to flash. If you have the fresh clone from `github`, it was probably something gone wrong in this install process, go check and see what didn't work and threw errors or what steps you might have missed.
266 But if everything went OK, you are ready to flash! Press the reset button on the bottom of the Planck, wait two seconds, then:
281 ###Installing Precompiled `dfu-programmer` Binaries (not recommended for `cygwin`)
282 To install the `dfu-programmer` from the binaries, we must get if from [the `dfu-programmer` website](https://dfu-programmer.github.io/) ([0.7.2](http://iweb.dl.sourceforge.net/project/dfu-programmer/dfu-programmer/0.7.2/dfu-programmer-win-0.7.2.zip)).
284 Copy this file into your `cygwin` home\src directory. (For me, it is `C:\cygwin64\home\Kevin\src`), extract the files, move `dfu-programmer.exe` to `~/local/avr/bin`. Most obnoxiously, the `libusb0_x86.dll` and `libusb0.sys` need to be moved from `./dfu-prog-usb-1.2.2/x86/` to a directory in the `Windows` `PATH` and the `cygwin` `PATH`. This is because the `dfu-programmer` binary is `mingw` based, not `cygwin` based, so the `dlls` do not cooperate. I achieved acceptable pathing by moving the files to `C:\cygwin64\home\Kevin\local\avr\bin` Then, in a `WINDOWS` command prompt running (Adjusting your path for username, etc. as needed):
286 C:\> set PATH=%PATH%;C:\cygwin64\home\Kevin\local\avr\bin
289 Then, rename `libusb0_x86.dll` to `libusb0.dll`.
291 You can tell that you were successful by trying to execute 'dfu-programmer' from the 'cygwin' prompt:
293 $ which dfu-programmer
294 /home/Kevin/local/avr/bin/dfu-programmer
298 https://github.com/dfu-programmer/dfu-programmer
299 Type 'dfu-programmer --help' for a list of commands
300 'dfu-programmer --targets' to list supported target devices
303 If you are not getting the above result, you will not be able to flash the firmware!
304 - Try making sure your `PATH` variables are set correctly for both `Windows` and `cygwin`.
305 - Make sure the `dll` is named correctly.
306 - Do not extract it with `cygwin`'s `unzip` as it does not set the executable permission. If you did it anyway, do `chmod +x dfu-programmer.exe`.
307 - Still have problems? Try building it instead.
312 These tools are for debugging your firmware, etc. before flashing. Theoretically, it can save your memory from wearing out. However, these tool do not work 100% for the Planck firmware.
315 `gdb` has a simulator for AVR but it does not support all instructions (like WDT), so it immediately crashes when running the Planck firmware (because `lufa.c` disables the WDT in the first few lines of execution). But it can still be useful in debugging example code and test cases, if you know how to use it.
319 $ git clone git://sourceware.org/git/binutils-gdb.git
323 $ ../configure --prefix=$PREFIX --target=avr --build=x86_64-unknown-cygwin --with-gmp=/usr/local --with-mpfr=/usr/local --with-mpc=/usr/local --disable-nls --enable-static
329 `simulavr` is an AVR simulator. It runs the complied AVR elfs. `simulavr` does not support the `atmega32u4` device... it does `atmega32` but that is not good enough for the firmware (no PORTE and other things), so you cannot run the Planck firmware. I use it to simulate ideas I have for features in separate test projects.
331 This one is a major pain in the butt because it has a lot of dependencies and it is buggy. I will do my best to explain it but... it was hard to figure out. A few things need to be changed in the 'Makefile' to make it work in `cygwin`.
336 $ git clone https://github.com/Traumflug/simulavr.git
339 $ ./configure --prefix=$PREFIX --enable-static --disable-tcl --disable-doxygen-doc
341 Edit `src/Makefile.am` now so that `-no-undefined` is included (I did this by removing the SYS_MINGW conditional surrounding `libsim_la_LDFLAGS += -no-undefined` and `libsimulavr_la_LDFLAGS += -no-undefined \ libsimulavr_la_LIBADD += $(TCL_LIB)`. Also, `$(EXEEXT)` is added after `kbdgentables` in two places.
350 - git repos for all sources
351 - command line magic for cygwin setup
352 - better options for `dfu-drivers`