anchor.diff:  
   . Name the project, set the project location, and change the Toolchain/IDE to SW4STM32. 
   *If this isn't done, CubeMX2Makefile won't work!* 
  -CubeMX2Makefile looks for an SW4STM32 project which correlates to CubeMX.
  +CubeMX2Makefile looks for an SW4STM32 project which was created by CubeMX.
   If the Toolchain/IDE is not set to SW4STM32, it will be in the format of a different IDE, not CubeMX.
   For example, EWARM is for the IAR Embedded Workbench IDE and CubeMX2Makefile will not know what to do with that format.
   
  
positive.code: 
  . Click OK and download any dependencies that are needed, then click OK again.
  
  . Do configurations and go to Project > Generate Code, then save project.
  
  
  == Generating a Makefile and Compiling
  . Create the makefile  `CubeMX2Makefile /path/to/project/folder`.
  
  . Go to the directory that the Makefile was made then compile the Makefile `make`.
  
  . Navigate to the build directory and there should be a `<project>.bin` file. Where `<project>` is the project name. 
  
  == Flashing
  Flashing is how the `.bin` that was made is put onto the board. This is how the processor on the board is able to carry out the instructions that were generated from the code.
  
  To flash the board use `st-flash write /path/to/project/build/<project>.bin 0x8000000`.
  
  If a board isn't connected, and it ran successfully, you should get an output that looks like: 
  ----
  st-flash 1.3.0-dev
  DATE/TIME WARN /opt/stlink/src/usb.c: Couldn't find any ST-Link/V2 devices
  
negative.code: 
  . Go to UCSolarCarTeam repo > Recruit Resources, and clone.
  
  . Navigate to STM32F4Discovery-Resources and run the auto installer using `sudo ./install.sh`. 
  This should download the necessary tools needed (gcc4mbed, STlink, and CubeMX2Makefile)
  
  . http://www.st.com/en/development-tools/stm32cubemx.html[Go to the download page of the official ST website by clicking this link^].
  
  