Skip to content

Conversation

@phaseloop
Copy link

Draft - PR during testing

This PR fixes memory corruption issues on ProMicro/NiceNano2 boards (and possibly other NRF52 boards) where battery voltage hovers around 2.5-2.7V.

Depending on components used - some LDO regulators shut down around 3V but with some regulators or different board designs (like LDO bypass into VDDH) it's perfectly fine to work down to 2.5V and utilize most of the battery capacity (auto shutdown feature at 3.1V aside right now).

Bug being fixed:

NRF52840 uses power fail comparator that prevents flash memory write if voltage is below safety threshold. While this comparator is enabled in meshtastic firmware - it was set to 2.4V threshold which is below power failure mode of VDDH REG0 regulator (specified min voltage is 2.5V) and li-ion battery protectors (also around 2.5V) which means power will be randomly cut to the device before this protection can trigger.

Due to other bugs and issues: #8789 in some cases device will not go into deep sleep when voltage drops below 3V.

This results in memory corruption (device boots with clear config) when voltage is at 2.5-2.7V and heavier operation is being executed (BLE setting changed, meshtastic frame received, etc).

@phaseloop phaseloop marked this pull request as draft November 28, 2025 23:28
@CLAassistant
Copy link

CLAassistant commented Nov 28, 2025

CLA assistant check
All committers have signed the CLA.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@thebentern thebentern added the bugfix Pull request that fixes bugs label Nov 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Pull request that fixes bugs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants