WZ9V Posted December 21, 2018 Posted December 21, 2018 If I do i2cdetect -y 0 I don't see the device id I expect to 0x10 but I do see 0x30 and 0x50 which I shouldn't because there should only be one device at 0x10. I only see one i2c bus at /dev/i2c-0. Is that the i2c bus using header pins 3 and 5 which is where my device is attached? If not how would I enable the bus on pins 3 and 5?
WZ9V Posted December 21, 2018 Author Posted December 21, 2018 http://ix.io/1wtZ BTW i2cdetect -l says i2c-0 i2c DesignWare HDMI I2C adapter My best guess is that /dev/i2c-0 is picking up an i2c channel on the hdmi interface and not the one on header pins 3 and 5. The docs say you can enable onboard i2c/spi via the armbian_config System->Hardware menu but I don't have the menu option when I run it from the Applications menu.
TonyMac32 Posted December 21, 2018 Posted December 21, 2018 OK, I'm adding the I2C for that to the device tree. For 4.19 I'll toss a set of overlays out so the various hardware can be configured at will. Install the deb attached into your 4.14 install and let me know if it works for you. Not complete, I need to add proper processor pin names for a few of these yet: linux-dtb-meson64_5.67_arm64.deb
WZ9V Posted December 21, 2018 Author Posted December 21, 2018 Thanks, worked great. I now see bus /dev/i2c-0 and /dev/i2c-1 and my device id shows up on /dev/i2c-0 i2cdetect -l i2c-1 i2c DesignWare HDMI I2C adapter i2c-0 i2c Meson I2C adapter I2C adapter Looking forward to the future update with the overlays and eMMC, I have what I need to try and port the Pi-Top device support over now. 1
vt19 Posted April 12, 2020 Posted April 12, 2020 Hi, I'm having same issue. i2cdetect -l shows me only: i2c-0 i2c DesignWare HDMI I2C adapter And no device detected at bus /dev/i2c-1. It should be typically detected at 0x60. I've connected the sensor at pin 3 and 5. And I'm running 4.19.55+ kernel. Any idea how to solve this? Thanks!
Igor Posted April 12, 2020 Posted April 12, 2020 5 hours ago, vt19 said: And I'm running 4.19.55+ kernel. Providing logs with armbianmonitor -u significantly raises chances that issue is getting addressed.
TonyMac32 Posted April 23, 2020 Posted April 23, 2020 @vt19 let me know what the output of On 4/12/2020 at 12:57 PM, Igor said: armbianmonitor -u gives you, and I can take a look.
mihaipop10 Posted May 20, 2020 Posted May 20, 2020 Hi, Im having same problem, I'm not able to get i2c detect to find my device. I tried to install the deb file but I stilul see only Designware Hdmi input. Im running 4.19++ Can you help me? Thanks
Igor Posted May 20, 2020 Posted May 20, 2020 58 minutes ago, mihaipop10 said: Im running 4.19++ Use latest kernel and provide logs with armbianmonitor -u
mihaipop10 Posted May 21, 2020 Posted May 21, 2020 Hi, I managed to get it running using the tutorial from here https://github.com/libre-computer-project/libretech-overlays But my problem now is that after restart the overlay is gone. Do you know how to configure it at boot? And also how to set the baudrate. Any ideas? Thanks
Recommended Posts