# Reading I2C device with address 0x00 **URL:** \ **Category:** mangOH Red\ **Created:** [December 26, 2017, 8:37pm UTC](https://mangoh.discourse.group/t/reading-i2c-device-with-address-0x00/1028 "2017-12-26T20:37:11Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Kas.Lewis](https://avatars.discourse-cdn.com/v4/letter/k/e9a140/32.png) [@Kas.Lewis](https://mangoh.discourse.group/u/Kas.Lewis)\ **Post date:** [December 26, 2017, 8:37pm UTC](https://mangoh.discourse.group/t/reading-i2c-device-with-address-0x00/1028/1 "2017-12-26T20:37:11Z")
Hello, I’m looking to read data from a i2c device (TSD30D - Thermopile) which has an i2c address of 0x00. While this device is made specifically for the Raspberry Pi I have not found away to access anything at address 0x00. When I attempt to run “i2cdetect -y -r 0” the addresses 0x00 - 0x03 are out of range. Even if I check all 4 I2C busses there is still seemingly no way to check I2C address 0x00. If there is away I would be very interested in entertaining it. Thankfully Kas ---
**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:** [December 27, 2017, 2:05pm UTC](https://mangoh.discourse.group/t/reading-i2c-device-with-address-0x00/1028/2 "2017-12-27T14:05:37Z")
Address 0x00 is reserved by spec, so you have to specify the force flag to i2cdetect. I think it is either `-a` or `-f`. ---
**Author:** ![Kas.Lewis](https://avatars.discourse-cdn.com/v4/letter/k/e9a140/32.png) [@Kas.Lewis](https://mangoh.discourse.group/u/Kas.Lewis)\ **Post date:** [December 28, 2017, 10:08pm UTC](https://mangoh.discourse.group/t/reading-i2c-device-with-address-0x00/1028/3 "2017-12-28T22:08:18Z")
Thank you, found out the part datasheet was incorrect the I2C address is 0x76 or 0x77 and not as stated in the documentation 0x00. Thanks Kas