- 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
- :
- 334042_en-US
334042_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
334042_en-US
334042_en-US
I try to use an MCU to communicate with MMA9553L by I2C. I'm sure that I2C and other command works fine.
As I've read the MMA955xLSWRM, I try to write command {0x12,0x20,0x06,0x01,0x04} to the cfg register, but it shows the same phenomenon with command {0x12,0x20,0x06,0x01,0x00} . The current is still very big.
So I want to know, how to make MMA9553L go into DOZE mode? Why I'm wrong? What should I do?
My E-Mail is biht@neusoft.com if necessary.
Thank you!
Thank you for notifying me. By the way, will MMA9555L update to a new FW at the same time?
Excellent,
FYI, we'll release soon a new FW revision for MMA9553L which reduces significantly the pedometer operating current.
I'll email you directly when it will be available.
Hi, Jacques Trichet
Thank you very much for your help. That PDF is useful. I have deceased the current successfully.
Hi,
Attached presentation describes how to optimize and reduce MMA9553L current consumption.
The most effective means are the following:
- autonomous suspend feature of the pedometer application,
- doze mode of the sleep/wake application.
I hope it will help to solve your issue. Don't hesitate to ask for further details if needed.
Regards, Jacques.