- 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
-
- Home
- :
- i.MX Forums
- :
- i.MX Processors
- :
- Re: mxs-i2c driver failure.
mxs-i2c driver failure.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
mxs-i2c driver failure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm trying to communicate with some i2c device, with slave address 0x20. There is principal driver fault, where driver sends out only slave address, and after that reports "adapter timeout" on any subsequent master_xfers to any other addresses. Confirmed by scope.
the kernel version is 2.6.31, built with latest ltib.
Did anyone experience any issues with mxs-i2c driver?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for the driver, i've temporarily fixed that myself, but wasn't satisfied with results, and rewrite was on my todo list before release. The driver works perfectly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The I2c driver is not properly implemented for the imx233. Reads are completely broken and the address is also mangled and there is poor error recovery.
Attached is a replacment for the driver on this CPU (it only works with the imx233 and overwrites it for the time being!). I have been working with Freescale's FAE and I am hoping to improve this further and make it work along side the driver for the other CPUs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The slave may not ACK it's slave address until it's ready, but that should not cause the driver to get to "locked" state.
the protocol to read register from the chip is -- start, send slave addr+ write cmd, send reg addr, start send slave addr+read cmd, read 1 byte, stop.
What i see on the scope is following :
start condition, proper address, nak. (there's no stop!)
then 10 ms later i see another 9 clocks with register address... it's like driver didn't stopped/reset the dma.
any other attempts to access the driver, even with different addresses doesn't produce single clock -- the driver is locked until reset.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Check if your slave is connected and is sending an ACK once it receives the command from master. Also check if your I2C lines are pulled up with appropriate resistor values (as per I2C Specifications).
Regards,
Balaji
