- 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
- 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
-
- 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
-
- 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
-
- Home
- :
- Wireless Connectivity
- :
- Wireless MCU
- :
- NTP53321G0JHK: I2C Strange behavior
NTP53321G0JHK: I2C Strange behavior
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
NTP53321G0JHK: I2C Strange behavior
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
I have a PCB which uses the NTP53321G0JHK NFC tag as a I2C bridge for communication and power supply to a sensor. I have only one master (tag) and one slave (sensor) at the I2C lanes. If I use an external power supply for the sensor and the pullup resistors (while the NFC tag feeds itself, VCC = VOUT = 3.0V) everything works fine, the signal gets tunnled and it is possible to read out values from the sensor through I2C.
If I feed everything from the tag (VOUT = 3.0V, Iload = 1.4mA, field to the coil more than strong enough), I get no working communication. The tag don't clocks the SCL or SDA lane, both are the whole time just high.
If I cut physically the sensor away (pullups feeded from energy harvesting from the tag) and start a communication with the sensor, I can see that the tag (master) starts the communication with a start condition and the slave address but receives no ACK, what make sense, there is no slave. But the communication starts correct.
The firmware code is in all three cases exactly the same. Also is the load current identical and I can't see any dips in the voltage supply or something like that. It seems to me like a stucked I2C bus (if I supply the whole circuit from energy harvesting) but with SDA and SCL constant high, that should not be the case...
My question is, how is it possible that the master send nothing to the bus (not even the SCL clocks)? Are there any known issues with the NTP53321G0JHK NFC tag which could explain this behavior?
Picture 1: The whole circuit
Picture 2: Communication if I cut away the sensor
Best regards
Raphael
