adeck/platform-raspberrypi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update readmes

Browse Source
This commit is contained in:
unknown 2022-08-22 01:05:09 +02:00
parent 4c0d7ea35c
commit 47726da601
2 changed files with 22 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
examples/arduino-ota/README.md
View File

@ -8,7 +8,7 @@ How to build PlatformIO based project
```shell ```shell
# Change directory to example # Change directory to example
$ cd platform-raspberrypi/examples/arduino-blink $ cd platform-raspberrypi/examples/arduino-ota
# Build project # Build project
$ pio run $ pio run
@ -22,8 +22,12 @@ $ pio run --target clean
## Notes ## Notes
For Raspberry Pi Pico devices, two Arduino cores exist: This examples showcases the usage of Over-The-Air (OTA) updates with the Raspberry Pi Pico W.
* https://github.com/arduino/ArduinoCore-mbed
* https://github.com/earlephilhower/arduino-pico
This examples showcases how to use both of these cores in the `platformio.ini`. For more details, see the [documentation](https://arduino-pico.readthedocs.io/en/latest/ota.html).
For the initial firmware update, use the `rpipicow_via_usb` environment.
Then, open the serial monitor and note down the IP of the Pico that it outputs.
Use this IP as the `upload_port` in the `rpipicow_via_ota` environment and use the "Upload" project task there.

18
examples/arduino-signed-ota/README.md
View File

@ -8,7 +8,7 @@ How to build PlatformIO based project
```shell ```shell
# Change directory to example # Change directory to example
$ cd platform-raspberrypi/examples/arduino-blink $ cd platform-raspberrypi/examples/arduino-signed-ota
# Build project # Build project
$ pio run $ pio run
@ -22,8 +22,16 @@ $ pio run --target clean
## Notes ## Notes
For Raspberry Pi Pico devices, two Arduino cores exist: This examples showcases the usage of **signed** Over-The-Air (OTA) updates with the Raspberry Pi Pico W.
* https://github.com/arduino/ArduinoCore-mbed
* https://github.com/earlephilhower/arduino-pico
This examples showcases how to use both of these cores in the `platformio.ini`. The difference to regular OTA updates is that update binaries are signed using the `private.key` to produce a `firmware.bin.signed` file.
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.
For more details, see the [documentation](https://arduino-pico.readthedocs.io/en/latest/ota.html).
For the initial firmware update, use the `rpipicow_via_usb` environment.
Then, open the serial monitor and note down the IP of the Pico that it outputs.
Use this IP as the `upload_port` in the `rpipicow_via_ota` environment and use the "Upload" project task there.