Hello,
Recently I have switched from Dunfell to Kirkstone for the image building for the BBB/ BBG. I have noticed multiple issues in the base demo image (using meta-ti). On of them is the problem regarding I2C 2. During the boot I can see:
2.816942] at24 2-0054: supply vcc not found, using dummy regulator
[ 3.829440] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 4.841437] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 4.850475] at24 2-0055: supply vcc not found, using dummy regulator
[ 5.865436] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 6.877435] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 6.886494] at24 2-0056: supply vcc not found, using dummy regulator
[ 7.901438] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 8.913436] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 8.922396] at24 2-0057: supply vcc not found, using dummy regulator
[ 9.937464] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 10.949435] omap_i2c 4819c000.i2c: timeout waiting for bus ready
[ 10.957951] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz
When I try to probe on this bus:
root@beaglebone:~# i2cdetect -y -r 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: [24342.373343] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24343.385337] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24344.397337] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24345.409340] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24346.421339] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24347.433338] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24348.445337] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24349.457338] omap_i2c 4819c000.i2c: timeout waiting for bus ready
--
10: [24350.469336] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24351.481337] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24352.493333] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24353.505336] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24354.517337] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24355.529335] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24356.541336] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24357.553335] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24358.565335] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24359.577333] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24360.589336] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24361.601337] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24362.613463] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24363.625337] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24364.637341] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24365.649338] omap_i2c 4819c000.i2c: timeout waiting for bus ready
--
20: [24366.661338] omap_i2c 4819c000.i2c: timeout waiting for bus ready
-- [24367.673338] omap_i2c 4819c000.i2c: timeout waiting for bus ready
What would be the best way to debug this behavior? I would appreciate all feedback!