|
@@ -10,6 +10,18 @@ application which you want to be able to update over WiFi.
|
10
|
10
|
|
11
|
11
|
There's an example project using picowota at https://github.com/usedbytes/picowota_blink
|
12
|
12
|
|
|
13
|
+The simplest way to build `picowota` by itself is:
|
|
14
|
+
|
|
15
|
+```
|
|
16
|
+mkdir build
|
|
17
|
+cd build
|
|
18
|
+export PICOWOTA_WIFI_SSID=picowota
|
|
19
|
+export PICOWOTA_WIFI_PASS=password
|
|
20
|
+export PICOWOTA_WIFI_AP=1
|
|
21
|
+cmake -DPICO_BOARD=pico_w -DPICO_SDK_PATH=/your/path/to/pico-sdk ../
|
|
22
|
+make
|
|
23
|
+```
|
|
24
|
+
|
13
|
25
|
## Using in your project
|
14
|
26
|
|
15
|
27
|
First add `picowota` as a submodule to your project:
|
|
@@ -40,7 +52,7 @@ PICOWOTA_WIFI_AP # Optional; 0 = connect to the network, 1 = create it
|
40
|
52
|
Then, you can either build just your standalone app binary (suitable for
|
41
|
53
|
updating via `picowota` when it's already on the Pico), or a combined binary
|
42
|
54
|
which contains the bootloader and the app (suitable for flashing the first
|
43
|
|
-time):
|
|
55
|
+time):
|
44
|
56
|
|
45
|
57
|
```
|
46
|
58
|
picowota_build_standalone(my_executable_name)
|