[Bug 9841] New: i2cset not working as expected

bugzilla at busybox.net bugzilla at busybox.net
Thu Apr 27 11:57:58 UTC 2017


https://bugs.busybox.net/show_bug.cgi?id=9841

            Bug ID: 9841
           Summary: i2cset not working as expected
           Product: Busybox
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at busybox.net
          Reporter: jose1711 at gmail.com
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the busybox-cvs mailing list