-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define reqs for power mgmt v4.x boards #72
Comments
3 - NICE TO HAVE |
Nice to have fast charging, still needs to be done.. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Define the requirements and follow-up design goals for the power management on v4.x boards: powering the device, charging the battery, power-on/power-off, protection.
DEFINITIONS (loosely based on AXP2101 terminology).
VBUS = 5V from USB charger
VSYS = System voltage for AXP2101
VBAT = Battery voltage
Other voltages mentioned are for internal use in CORE2 V1.1
GIVENS:
M5Stack CORE2 v1.1. The original CORE2 no longer available because the AXP192 PMIC was obsoleted by the manufacturer.
Single cell Li-Ion battery 18650 3.7V 18mm x 65 mm cylindrical form factor, capacities range up to 3400mAh
1- MUST HAVE
Reverse battery protection: against inserting battery in wrong polarity.
Over-voltage protection on VBAT.
Over-discharge protection
Over-charge protection for the battery
Charging without connecting USB cable: avoid connector point of failure.
2 - IMPORTANT TO HAVE
Low component count: cost, build complexity and, well, Zen.
No SMT soldering: easy for inexperienced kit builders (power device like DPAK or D2PAK would be OK).
Extended operating time between recharges; what is the target?
Remove power switch that was on v3.x boards
Charging without opening case, i.e. Qi charger
3 - NICE TO HAVE
Battery fast charge I(CH) > 300mA (AXP2101 default).
Control over power off: firmware read of CORE2 power button and control of power on/off through AXP2101 control register.
The text was updated successfully, but these errors were encountered: