RPI5 I2C1 Detects address but read/write fails
Hello,
I am trying to communicate with TDA8375 over I2C1 with 100khz speed. i2cdetect -y 1 detects all the addresses including TDA8375, it can read and write all addresses expect TDA8375. However when I try with I2C3 I am able to read and write to TDA8375.
I have bus pirate connected same I2C line and it can read and write to all addresses. R/W to TDA8375 fails because of the missing ACK from the slave device. Since I am using I2C3 for different purpose, I need to figure out why I2C1 is failing.
The I2C network that I am trying to hack has its own master and it is 5V logic. I am using bi-directional logic level shifters (BSS138) to connect RPI, bus pirate connected to 5V logic with pull up resistors enabled. What can be the reason for the read/write error? (I tried increasing and decreasing I2C clock frequency). Build in pull-up resistors of I2C1?
Many thanks
I am trying to communicate with TDA8375 over I2C1 with 100khz speed. i2cdetect -y 1 detects all the addresses including TDA8375, it can read and write all addresses expect TDA8375. However when I try with I2C3 I am able to read and write to TDA8375.
I have bus pirate connected same I2C line and it can read and write to all addresses. R/W to TDA8375 fails because of the missing ACK from the slave device. Since I am using I2C3 for different purpose, I need to figure out why I2C1 is failing.
The I2C network that I am trying to hack has its own master and it is 5V logic. I am using bi-directional logic level shifters (BSS138) to connect RPI, bus pirate connected to 5V logic with pull up resistors enabled. What can be the reason for the read/write error? (I tried increasing and decreasing I2C clock frequency). Build in pull-up resistors of I2C1?
Many thanks
- PhilE
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 6874
- Joined: Mon Sep 29, 2014 1:07 pm
Re: RPI5 I2C1 Detects address but read/write fails
Yes, I2C1 on GPIOs 2 & 3 has onboard pull-ups. If something else is also pulling-up the bus, your TDA8375 may be having difficulty overcoming the combined pull.
Return to "Interfacing (DSI, CSI, I2C, etc.)"
Jump to
- Community
- General discussion
- Announcements
- Other languages
- Deutsch
- Español
- Français
- Italiano
- Nederlands
- 日本語
- Polski
- Português
- Русский
- Türkçe
- User groups and events
- Raspberry Pi Official Magazine
- Using the Raspberry Pi
- Beginners
- Troubleshooting
- Advanced users
- Assistive technology and accessibility
- Education
- Picademy
- Teaching and learning resources
- Staffroom, classroom and projects
- Astro Pi
- Mathematica
- High Altitude Balloon
- Weather station
- Programming
- C/C++
- Java
- Python
- Scratch
- Other programming languages
- Windows 10 for IoT
- Wolfram Language
- Bare metal, Assembly language
- Graphics programming
- OpenGLES
- OpenVG
- OpenMAX
- General programming discussion
- Projects
- Networking and servers
- Automation, sensing and robotics
- Graphics, sound and multimedia
- Other projects
- Media centres
- Gaming
- AIY Projects
- Hardware and peripherals
- Camera board
- Compute Module
- Official Display
- HATs and other add-ons
- Device Tree
- Interfacing (DSI, CSI, I2C, etc.)
- Keyboard computers (400, 500, 500+)
- Raspberry Pi Pico
- General
- SDK
- MicroPython
- Other RP2040 boards
- Zephyr
- Rust
- AI Accelerator
- AI Camera - IMX500
- Hailo
- Software
- Raspberry Pi OS
- Raspberry Pi Connect
- Raspberry Pi Desktop for PC and Mac
- Beta testing
- Other
- Android
- Debian
- FreeBSD
- Gentoo
- Linux Kernel
- NetBSD
- openSUSE
- Plan 9
- Puppy
- Arch
- Pidora / Fedora
- RISCOS
- Ubuntu
- Ye Olde Pi Shoppe
- For sale
- Wanted
- Off topic
- Off topic discussion