- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2400327_en-US
2400327_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2400327_en-US
2400327_en-US
Hello NXP,
We are calculating battery life for RTC for which active & sleep current are required for SNVS power domain in RT1176.
However refer to datsheet IMXRT1170BIEC - Table13, page 35, only sleep current is given.
Please let us know the factors affecting the active current and various calculations related to active current for the SNVS power domain.
Hi @specneeraj ,
Thanks for your interest in NXP MIMXRT series!
VDD_SNVS_IN supplies power to the SNVS/RTC domain. This domain is an always-on, low-power domain that primarily maintains the 32 kHz RTC, SNVS logic, and related wake-up and safety functions. Its current consumption is only weakly correlated with the active/sleep states of CM7/CM4; therefore, the VDD_SNVS_IN values for the SNVS mode listed in Table 13 are not omitted “sleep-only” data, but rather baseline values that can be used in RTC backup scenarios.
- If the coin cell only provides power when the main power source fails → Use the SNVS mode current estimate directly;
- If the coin cell also supplies power to
VDD_SNVS_INwhile the system is active, calculate the average current based on the active/SNVS duty cycle.
The main factors affecting the SNVS current include temperature, VDD_SNVS_IN voltage, process variations, leakage from the 32 kHz RTC crystal/board, external leakage from SNVS-related pins, and whether the device has actually entered SNVS mode. Please refer to AN13104 for more details.
Best regards,
Gavin