InfiniTimeOrg / InfiniTimeOrg/pinetime-mcuboot-bootloader

Higher consumption on nRF52832 when boot from mcuboot

Open
#8 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
80
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Moving this issue from https://github.com/lupyuen/pinetime-rust-mynewt/issues/36

Lup doesn't work on mcuboot anymore and his repo isn't the right place for this issue.

@vbelloir says:

I'm working with @JF002 on power consumption of Pinetime watch, using Infinitime from JF.

I noticed that consumption is higher when Infinitime is booted by mcuboot than when it is stand-alone. Difference is about 500µA.

As a example, I disabled watchdog in bootloader, and add a simple __WFE loop in main function of Infinitime.
Booting from mcuboot gives a consumption of 574µA, while booting in stand-alone configuration gives 170µA.

Resources may be used in mcuboot/mynewt and not de-initialized in mcuboot, nor in Infinitime.

Do you have any idea for me? How can I identify which resource is consuming power?

Thanks for your help.
Vincent

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the nRF52832 boot paths for mcuboot and standalone InfiniTime, using the reported 574µA versus 170µA measurements. Review the MyNEWT and mcuboot initialization involved in boot, then identify which resource remains active after handoff. Done means isolating the source of the roughly 500µA difference and documenting or correcting its cleanup.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.