Hello everyone I have a problem with I2C. I am trying to configure a user bus for another device that i need to run on my BBAI.
I followed these steps: congifured pin 17 and 18 as i2c pins and made so to enable them after each startup, follwing config-pin beaglebone start up · GitHub.
When i run “sudo show-pins | sort” I can see that the status of the pin is changed from default to I2C 4 .
But if i run i2cdetect -l I only have the default i2c 0 and 3 bus displaying, and indeed connecting the SDA and SCL to 18 and 17 pins, I see no device.
How can I solve this issue? Somebody has suggestion or a link with steps I can follow to activate the other I2c?
I was wandering if the same procedure i was using for CAN, coming from Deepak Katrhi in Google SoC might also work for it :
After having installed bb_overlays
- git clone https://github.com/lorforlinux/bb.org-overlays.git
- cd bb.org-overlays
- git checkout bone_can
- make
- sudo cp src/arm/BONE-CAN0.dtbo /lib/firmware/
- For the BBAI, use BONE-CAN0.dtbo and / or BONE-CAN1.dtbo
- sudo nano /boot/uEnv.txt
enable_uboot_overlays=1
uboot_overlay_addr4=/lib/firmware/BONE-CAN0.dtbo
uboot_overlay_addr5=/lib/firmware/BONE-CAN1.dtbo
Hi @ALEX_PARK thank you for the reply. I exactky followed the steps you linked me to:
debian@BeagleBone:~$ cd /opt/source/dtb-5.10-ti-arm64/
debian@BeagleBone:/opt/source/dtb-5.10-ti-arm64$ git pull
Already up to date.
debian@BeagleBone:/opt/source/dtb-5.10-ti-arm64$ make
debian@BeagleBone:/opt/source/dtb-5.10-ti-arm64$ sudo make install
Then add:
fdtoverlays /overlays/BONE-I2C1.dtbo