Skip to content

Latest commit

 

History

History
96 lines (71 loc) · 4.15 KB

windows_build.md

File metadata and controls

96 lines (71 loc) · 4.15 KB
Raw

Building on Windows

So unfortunately there is no known way (yet), to fully work on Windows while working for Pebble. This document will guide you through the setup of a Ubuntu VM, the Pebble and Rebble development environment and finally look at some ways to move most of the development back to Windows.

Setting up a virtual machine

  • Install VirtualBox
  • Download the Ubuntu's ISO from their website
  • Inside virtualbox install Ubuntu
  • You propably want to install the guest additions from VirtualBox
  • Once inside the booted Ubuntu, open a terminal for further install steps

Install pebble SDK

For installing the pebble sdk and building on debian/ubuntu, please see the instructions in the debian build documentation

Setting up a development environment on Windows

If you are a more experienced, you can follow these steps to gradually move some of the development process back to Windows. Please notice that this is not an alternative to the solution above, but rather an extension which should make life easier. As such setting it up can be rather complicated.

First steps

  • Download MSYS from this website
  • Extract it to some directory
  • Download the arm-none-eabi Windows ZIP package from the ARM website
  • Extract it over MSYS (both archives have a bin folder with various *.exe files, these should be in the same folder after this step)

You can now compile the firmware by first cloning this repository and then running make (explicitly the one you downloaded) in the root folder, e.g.

C:\msys\bin\make.exe snowy_qemu

To prevent the copying of the compiled firmware, you can set up a shared folder in VirtualBox (in the menu tab "Devices"). However you can only have build files from either Windows or Linux present, which basically refrains you from using make. To start the emulator you have to run the command yourself (or put it in a bash script nearby):

cat Resources/snowy_boot.bin build/snowy/tintin_fw.bin > build/snowy/fw.qemu_flash.bin
qemu-pebble -rtc base=localtime -serial null -serial null -serial stdio -gdb tcp::63770,server -machine pebble-snowy-bb -cpu cortex-m4 -pflash build/snowy/fw.qemu_flash.bin -pflash Resources/snowy_spi.bin

and to attach gdb to it:

arm-none-eabi-gdb -ex "target remote localhost:63770" -ex "sym build/snowy/tintin_fw.elf"

Remote Debugging

For remote debugging to work you first have to enable the communication to your VM. The easiest way to do this (if you followed the steps above) is to open VirtualBox and select Your VM->Change->Networking->Advanced->Port Forwarding and add a new rule, which should like this:

Name Protocol Host-IP Host-Port Guest-IP Guest-Port
Rule 1 TCP 63770 63770

Then you can start the emulator on the virtual machine by running make snowy_qemu and then in windows:

C:\msys\bin\arm-none-eabi-gdb.exe -ex "target remote localhost:63770" -ex "sym build/snowy/tintin_fw.elf"

Integrating into VSCode

For building you can use this tasks.json:

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "Build all",
            "type": "shell",
            "command": "C:\\msys\\bin\\make.exe",
            "args": [ ],
            "options": {
                "env": {
                    "PATH": "C:\\msys\\bin"
                }
            },
            "group": {
                "kind": "build",
                "isDefault": true
            },
            "problemMatcher": "$gcc",
            "presentation": {
                "echo": true,
                "reveal": "always",
                "focus": true,
                "panel": "shared"
            }
        }
    ]
}

Unfortunately integrating remote debugging is still a problem, if you happen to solve it, please make a PR describing the solution!