Bug 9841 - i2cset not working as expected
Summary: i2cset not working as expected
Status: NEW
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-27 11:57 UTC by jose1711
Modified: 2017-04-27 11:57 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jose1711 2017-04-27 11:57:58 UTC
i2cset applet is unable to properly communicate to AT24C256 EEPROM chip, reading works, write does not.

here's a testcase with busybox 1.26.2 on a raspberry pi 1:

# writing 3 bytes (0x05) to the first 3 memory registers

# i2c address of eeprom chip
address="0x50"
# memory register
memory_address1="0x00"
memory_address2="0x00"
value="0x05"
i2cset -y 0 ${address} ${memory_address1} ${memory_address2} ${value} ${value} ${value} i

# reading back to verify write was successful
i2cset -y 0 ${address}
i2cget -y 0 ${address}; i2cget -y 0 ${address}; i2cget -y 0 ${address}

using busybox applet no error is reported, but the data is not written to chip. i2cset from i2c-tools works as expected.