I didn’t face the problem you mentioned. I wasn’t expecting to write or read from the slave that is on the same device, but I expected to see it when I run the i2cdetect
command.
For example:
0x60: UU -- -- -- -- ...
However, I found the mistake: my kernel configuration was missing, so the kernel didn’t have CONFIG_I2C_SLAVE enabled. After configuring the kernel correctly and applying the patch I mentioned earlier, I was able to detect the slave.
After that, I tried writing to and reading from this slave using another BeagleBone Black connected to the i2c-2 bus, and it was successful.
Thank you for your answer. The issue has been resolved.