Skip to content

Commit 97b9edb

Browse files
Update README.md
1 parent 5932b1f commit 97b9edb

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,7 @@ So we need a Debug serial port (currently which is different than flashing port)
3838
7. Select your Serial Debug port from it's respective dropdown list.
3939
8. Click on the <img src="https://raw.githubusercontent.com/FortAwesome/Font-Awesome/5.x/svgs/solid/file.svg" width="20" height="20"> to select the test firmware binary i.e. [watch_firmware.hex](https://watchfirmware.s3.ap-northeast-1.amazonaws.com/watch_firmware.hex) (from the location where you downloaded it)
4040
9. When ready, click on the <img src="https://raw.githubusercontent.com/FortAwesome/Font-Awesome/5.x/svgs/solid/arrow-right.svg" width="20" height="20"> to flash the test firmware.
41+
10. After the flashing is done, in 10 seconds, the board will start spitting out test results and data over serial. So pay attention and follow the on-screen prompts.
4142

4243
### To Flash production firmware:
4344
Depending on the usecase, the firmware typically should not have any serial debug logs coming from it, unless that's intended. If it is so intended as the later use-case, Then to flash and test even the production firmware, you can use the methods from last step.

0 commit comments

Comments
 (0)