# Clearfog base cn9130 : read tlv eeprom info into Linux

**URL:** <https://community.solid-run.com/t/clearfog-base-cn9130-read-tlv-eeprom-info-into-linux/632>\
**Category:** OCTEON CN9130\
**Created:** [April 22, 2023, 5:47pm UTC](https://community.solid-run.com/t/clearfog-base-cn9130-read-tlv-eeprom-info-into-linux/632 "2023-04-22T17:47:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![doudootiana](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@doudootiana](https://community.solid-run.com/u/doudootiana)\
**Post date:** [April 22, 2023, 5:47pm UTC](https://community.solid-run.com/t/clearfog-base-cn9130-read-tlv-eeprom-info-into-linux/632/1 "2023-04-22T17:47:59Z")

</div>

Hy,

I need to get some informations stored into the eeprom tlv

If i well understand the dts, the eeprom is on the I2C bus 0 address 0x53

When i tried to access with i2c command, it returns the device is busy.

```auto
# i2cdetect -y 0
     0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --
50: -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- 64 -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
#
# i2cdump -y 0 0x53
No size specified (using byte-data access)
Error: Could not set address to 0x53: Device or resource busy
# i2cget -y 0 0x53 0x0
Error: Could not set address to 0x53: Device or resource busy

```

is it normal?

Thanks by advance 🙂

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [April 23, 2023, 6:35am UTC](https://community.solid-run.com/t/clearfog-base-cn9130-read-tlv-eeprom-info-into-linux/632/2 "2023-04-23T06:35:00Z")

</div>

Yes this is normal. It is because the device is bound to the kernel eeprom driver. You can access the eeprom through the standard sysfs interface exposed by the kernel.
