BitGoblin/pico-clock
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Updated README with testing info

Browse Source
This commit is contained in:
Gregory Ballantine
2026-09-09 17:20:08 -04:00
parent af8a614480
commit 9a097b05c6
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+9 -3
View File
@@ -12,14 +12,20 @@ Made in Go with [TinyGo](https://tinygo.org/).
The following hardware is what I used for a deployment: The following hardware is what I used for a deployment:
* Raspberry Pi Pico 2 W: https://www.amazon.com/dp/B0DRJXPPWL * Raspberry Pi Pico 2 W: https://www.amazon.com/dp/B0DRJXPPWL
* The **W** is VERY important, as without networking it can't reach a time server! * The **W** is VERY important, as without networking it can't reach a time server!
* Also a Raspberry Pi Pico W *should* work too, but I haven't tested it yet
* Elegoo SSD1306 LCD: https://www.amazon.com/dp/B0FSRQG23K * Elegoo SSD1306 LCD: https://www.amazon.com/dp/B0FSRQG23K
Most (or all?) of these components can be swapped for equivalent components. You just need to make sure the code is compatible with whatever board you choose (not likely), and an SSD1306 display. Most (or all?) of these components can be swapped for equivalent components. You just need to make sure the code is compatible with whatever board you choose (not likely), and an SSD1306 display.
Support for other hardware types may come in the future, but if there's a specific board or display module you're interested in then submit an issue or pull request! Support for other hardware types may come in the future, but if there's a specific board or display module you're interested in then submit an issue or pull request!
### Tested On
This app has been tested to work on the following microcontrollers:
* Raspberry Pi Pico 2W
* Raspberry Pi Pico W
### Prototyping ### Prototyping
To help with debugging/testing deployments, I also used these components: To help with debugging/testing deployments, I also used these components:
@@ -42,7 +48,7 @@ To help with debugging/testing deployments, I also used these components:
4. Plug in your Pico to a USB port on your PC. 4. Plug in your Pico to a USB port on your PC.
5. Wait 2-3 seconds then release the **BOOTSEL** button. 5. Wait 2-3 seconds then release the **BOOTSEL** button.
6. Flash the program to the Pico: `tinygo flash -target=pico2-w .`. Or `tinygo flash -target=pico-w .` 6. Flash the program to the Pico: `tinygo flash -target=pico2-w .`. Or `tinygo flash -target=pico-w .`
a. **Note**: On Pop!_OS I needed to open the file browser and mount the RP2350 partition manually while tinygo was attempting the flash, otherwise it would fail. 1. **Note**: On Pop!_OS I needed to open the file browser and mount the RP2350 partition manually while tinygo was attempting the flash, otherwise it would fail.
7. Monitor the app: `tinygo monitor`. 7. Monitor the app: `tinygo monitor`.
At this point, you should be able to deploy this. Unplug the Pico, connect your SSD1306 display and power it back on - you should see some messages about it booting up and connecting to Wi-Fi, then it should display the time. At this point, you should be able to deploy this. Unplug the Pico, connect your SSD1306 display and power it back on - you should see some messages about it booting up and connecting to Wi-Fi, then it should display the time.