- 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
- :
- 282292_en-US
282292_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
282292_en-US
282292_en-US
Dear all,
Recenlty I have started using MMA6813BKW dual axis SPI sensor. I need to calculate the g-value out of this sensor and I am trying to configure it as below.
- Vcc supplied with 3.3v
- VREG and VREGA are connected to center plate with 1uf cap, VSS is given to ground
- MOSI, MISO, CLK and CS are connected to SPI tool.
I have configured the sensor according to the details given in the data sheet page num: 45, sec: 4.1. I requested the raw acceleration data out from x-axis, unsigned and with odd parity. based on the above configuration I send the SPI MOSIcommand as 0x3004 (I send only this command 4times, no other configuration made) as a response MISO I am getting only 0x0E00, even if I move the sensor in all directions. Can you please support me on the following topics,
- -Is the configuration I made correct? if not what I have to configure additionally.
- -Is the single MOSI command enough to get the acceleration data?
- -Do I additionally need anything other than the mentioned details to have acceleration data at least on one axis.
Thanks in advance.
Best Regards
Here is another thread which might give you some clues.
It talks about configuring the device.
community.freescale.com/thread/301952
Can you explain what the "center plate" you are refering to when you explain how you connected the reference pins?