InfiniTimeOrg / InfiniTimeOrg/InfiniTime
Power analysis
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
In commit f7e40b1b5879242b4ce59854dbbadb44fe5f75e4, I re-implemented sleep/wakeup for all devices (touchpanel, display, NOR Flash, SPI and TWI).
I checked (using the logs) that all Sleep() and Wakeup() method are called in the correct order.
I also checked that the MCU is put in deep sleep with a logic analyzer (the MCU is in deepsleep during the call to __WFE() in port_cmsis_systick.c).
Now, I think it would be very interesting to actually measure the power consumption of InfiniTime while running different use-cases:
- Display the Clock Screen
- BLE disconnected/connected
- BLE advertising (BLE advertising is enabled for 3 minutes after a wakeup) and continue even if the soft is in sleep mode -> measure power for more than 3 minutes after switch off the screen).
- ...
But... I do not have the necessary instruments and knowledge to do the measurement by myself.
If anyone has the setup and instruments necessary to measure the power consumed by InfiniTime, just write a comment to this issue !
Also, if you can, just leave your Pinetime running this commit (f7e40b1b5879242b4ce59854dbbadb44fe5f75e4) or a next one just to see how long it runs on battery!
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing commit f7e40b1b5879242b4ce59854dbbadb44fe5f75e4 and port_cmsis_systick.c, then reproduce the listed Clock Screen, BLE, advertising, and sleep scenarios on a Pinetime. Done means collecting power measurements for the scenarios and, if possible, recording battery runtime; the issue does not specify a measurement setup or test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100