You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/arduino-signed-ota/README.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ How to build PlatformIO based project
8
8
9
9
```shell
10
10
# Change directory to example
11
-
$ cd platform-raspberrypi/examples/arduino-blink
11
+
$ cd platform-raspberrypi/examples/arduino-signed-ota
12
12
13
13
# Build project
14
14
$ pio run
@@ -22,8 +22,16 @@ $ pio run --target clean
22
22
23
23
## Notes
24
24
25
-
For Raspberry Pi Pico devices, two Arduino cores exist:
26
-
*https://github.com/arduino/ArduinoCore-mbed
27
-
*https://github.com/earlephilhower/arduino-pico
25
+
This examples showcases the usage of **signed** Over-The-Air (OTA) updates with the Raspberry Pi Pico W.
28
26
29
-
This examples showcases how to use both of these cores in the `platformio.ini`.
27
+
The difference to regular OTA updates is that update binaries are signed using the `private.key` to produce a `firmware.bin.signed` file.
28
+
29
+
The firmware then uses the `public.key` file to verify the signature on the binary it receives in an OTA update. It will reject OTA update binaries that were not properly signed.
30
+
31
+
For more details, see the [documentation](https://arduino-pico.readthedocs.io/en/latest/ota.html).
32
+
33
+
For the initial firmware update, use the `rpipicow_via_usb` environment.
34
+
35
+
Then, open the serial monitor and note down the IP of the Pico that it outputs.
36
+
37
+
Use this IP as the `upload_port` in the `rpipicow_via_ota` environment and use the "Upload" project task there.
0 commit comments