Part Number: AM3358
Hello,
u-boot version: 2018.07
Code Build: Manual Command line build on a Ubuntu-16.04 Host machine.
Usage of Device Tree Model: DTS files are not used.
Code Build : No issues
u-boot configuration : default
I2C h/w modules (viz. bmp280, tiny rtc module etc) are wire-connected (one at a time over breadboard ) with i2c1 controller interface of
beaglebone black Also, i2C1 controller was configured to one of the below pins set in i2c1_pin_mux() in boards/ti/am335x/mux.c .
+ spi0_d1 ( I2C1_DATA ) and spi0_cs0 ( I2C1_SCLK ) pins
+ uart1_rxd ( I2C1_DATA ) and uart1_txd ( I2C1_SCLK ) pins
i2c1_pin_mux() function is called from enable_board_pin_mux() under "board_is_bone_lt " option.
The board is booting fine. On trying to probe the devices on i2c1 controller, we are getting mixed response.
At certain times, the probe
+ is successful , with all the device addresses displayed
+ does'nt display any device addresses
+ throws a time-out error.
The probe command on i2c0 gives a consistent output of all i2c devices on it.
The Device modules are working fine (they have been verified with other H/W ).
What could be the reason for this uncertainity in "i2c probe" on i2c1??
Any advise on getting this scenario fixed will be of great help.
Thank You,
Adarsh
