- 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
- 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
-
- NXP Tech Blogs
- Home
- :
- General Purpose Microcontrollers
- :
- LPC Microcontrollers
- :
- I3C communication of LPC860, received data are duplicated in read operation
I3C communication of LPC860, received data are duplicated in read operation
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When use I3C module of LPCXpresso860-MAX BOARD, and I3C configured as a controller, received data are duplicated in read operation. In I2C mode, it repeats two times, in I3C SDR mode, it repeats three times. For example, when "0xAA 0xBB 0xCC 0xDD" are sent, "0xAA 0xAA 0xBB 0xBB" are received.
But when measure SCL signal with an oscilloscope, the received data are correct. We found that the count register of rxfifo didn't decrease immediately whithout an oscilloscope, but decrease immediately whith an oscilloscope probe in SCL signal.
what causes received data to be duplicated in read operation?
Solved! Go to Solution.
Harry_Zhang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Travel
The duplication of received data in read operations when using the I3C module of the LPCXpresso860-MAX board could be due to several potential issues. Since you've observed that the received data are correct when measuring the SCL signal with an oscilloscope, but the count register of rxfifo doesn't decrease immediately without the oscilloscope, it suggests that the issue might be related to the electrical characteristics of the bus or the timing of the read operation.
Here are some possible causes for the duplication of data:
1. Electrical Noise or Interference: Without the oscilloscope probe, there might be more electrical noise on the bus, which could cause the I3C controller to erroneously detect additional start or stop conditions, leading to duplicated data. The capacitive load introduced by the oscilloscope probe might help to stabilize the signal and reduce noise.
2. Bus Timing Issues: The I3C protocol has specific timing requirements for start, address, and data phases. If the bus timing is not properly configured or if there are delays due to software overhead, it could cause the controller to mistakenly interpret a single data packet as multiple packets.
3. Incorrect Configuration: If the I3C module is not correctly configured as a controller, or if there are settings that are not properly adjusted for the specific mode of operation (I2C or I3C SDR), it could lead to unexpected behavior during data transfer.
Hope this will help you.
BR
Hang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
when I use STM32H5，it doesn't have the same issue. It is strange.
Harry_Zhang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Travel
The duplication of received data in read operations when using the I3C module of the LPCXpresso860-MAX board could be due to several potential issues. Since you've observed that the received data are correct when measuring the SCL signal with an oscilloscope, but the count register of rxfifo doesn't decrease immediately without the oscilloscope, it suggests that the issue might be related to the electrical characteristics of the bus or the timing of the read operation.
Here are some possible causes for the duplication of data:
1. Electrical Noise or Interference: Without the oscilloscope probe, there might be more electrical noise on the bus, which could cause the I3C controller to erroneously detect additional start or stop conditions, leading to duplicated data. The capacitive load introduced by the oscilloscope probe might help to stabilize the signal and reduce noise.
2. Bus Timing Issues: The I3C protocol has specific timing requirements for start, address, and data phases. If the bus timing is not properly configured or if there are delays due to software overhead, it could cause the controller to mistakenly interpret a single data packet as multiple packets.
3. Incorrect Configuration: If the I3C module is not correctly configured as a controller, or if there are settings that are not properly adjusted for the specific mode of operation (I2C or I3C SDR), it could lead to unexpected behavior during data transfer.
Hope this will help you.
BR
Hang
