# I2c devices list of wp768 **URL:** \ **Category:** mangOH Red\ **Created:** [September 21, 2018, 1:57pm UTC](https://mangoh.discourse.group/t/i2c-devices-list-of-wp768/1939 "2018-09-21T13:57:39Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![stirulaka](https://avatars.discourse-cdn.com/v4/letter/s/a587f6/32.png) [@stirulaka](https://mangoh.discourse.group/u/stirulaka)\ **Post date:** [September 21, 2018, 1:57pm UTC](https://mangoh.discourse.group/t/i2c-devices-list-of-wp768/1939/1 "2018-09-21T13:57:40Z")
Hi Team, This question is in relation to the below topic > **[I2cdetect shows no devices on the bus](https://forum.legato.io/t/i2cdetect-shows-no-devices-on-the-bus/3502/5)** > > From the schematic, Its mentioned the following are the I2C devices . But from software its different i2c address. root@swi-mdm9x28:~# i2cdetect -r -y 4 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: – 04 05 06 07 – -- – -- – -- –... In brief, in linux below are the list of i2c devices root@swi-mdm9x28:~# i2cdetect -r -y 4 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: – 04 05 06 07 – – – – – – – – 10: – – – – – – – – – – UU – – – – – 20: – – – – – – – – – – – – – – – – 30: – – – – – – – – – – UU – – – – – 40: – – – – – – – – – – – – – – – – 50: – 51 – – – – – – – – – – – – – – 60: – – – – – – – – 68 – – – – – – – 70: – 71 – – – – 76 – How ever, From the schematic has the below snapshot [https://discourse-cdn-sjc1.com/business5/uploads/legato1/original/1X/489ba7812b8f8e498866a3444790ecdc42b15e21.png](https://discourse-cdn-sjc1.com/business5/uploads/legato1/original/1X/489ba7812b8f8e498866a3444790ecdc42b15e21.png) I am not able to correlate both the devices. Why there is a difference in the i2c devices ? Is there any document to outline what are the available I2C devices with address ? Thanks ---
**Author:** ![asyal](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/asyal/32/78_2.png) [@asyal](https://mangoh.discourse.group/u/asyal)\ **Post date:** [September 21, 2018, 4:09pm UTC](https://mangoh.discourse.group/t/i2c-devices-list-of-wp768/1939/2 "2018-09-21T16:09:26Z")
> [@stirulaka](#): > > i2cdetect -r -y Some of the devices are behind the i2c hub. You need to enable all the ports on the hub: root@swi-mdm9x28:/dev# i2cset -y 4 0x71 0x0f root@swi-mdm9x28:/dev# i2cdetect -y -r 4 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: – 04 05 06 07 – – – – – – – – 10: – – – – – – – – – – UU – – – – – 20: – – – – – – – – – – – – – – – – 30: – – – – – – – – – – UU – – – 3e – 40: – – – – – – – – – – – – – – – – 50: – 51 – – – – – – – – – – – – – – 60: – – – – – – – – 68 – – 6b – – – – 70: – 71 – – – – 76 – ---
**Author:** ![dfrey](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/dfrey/32/303_2.png) [@dfrey](https://mangoh.discourse.group/u/dfrey)\ **Post date:** [September 24, 2018, 4:30pm UTC](https://mangoh.discourse.group/t/i2c-devices-list-of-wp768/1939/3 "2018-09-24T16:30:01Z")
What Ashish said about enabling all ports on the I2C switch is true, but it’s generally not a good idea to do this because there’s already a Linux kernel driver that is controlling the device and things could go wrong if the driver’s understanding of the hardware configuration and the actual hardware configuration get out of sync. It’s better to just run `i2cdetect` against each of the switch ports by using `i2cdetect -y -r N` where `N` is 5, 6, 7, 8 for segments 0, 1, 2, 3 respectively.