All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henbin Chang <henbinchang@gmail.com>
To: james.feist@linux.intel.com, OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Some problems about FruDevice in the entity-manager
Date: Fri, 22 Mar 2019 13:41:30 +0800	[thread overview]
Message-ID: <CAG9c7cDQc=o_=vEFRAjRRq9bV2Fz6ZD7Osp+vkd2QRgxmGcXGg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

Hi James,

There is EEPROM (AT24C64) with the valid FRU data on my board.

But the FruDevice would fail to format it.

I added some debug information to determine what's wrong with it.

Then I found the flag variable returned by isDevice16Bit() was equal 0.
That's, the FruDevice could think it's 8-bit EEPROM.
/* Check for Device type if it is 8 bit or 16 bit */
int flag = isDevice16Bit(file);

There is the below comment in the isDevice16Bit().

/* Read 7 more bytes, it will read same first byte in case of
 * 8 bit but it will read next byte in case of 16 bit
*/
But the rule isn't applicable to my EEPROM (AT24C64) .
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile# i2ctransfer -f -y 6 w1@0x50 0 r1
0x00
root@henbin:/var/volatile#

Could you give some suggestion?

Thanks.

[-- Attachment #2: Type: text/html, Size: 1835 bytes --]

             reply	other threads:[~2019-03-22  5:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  5:41 Henbin Chang [this message]
2019-03-22 15:54 ` Some problems about FruDevice in the entity-manager James Feist
2019-03-22 18:10   ` Vijay Khemka
2019-03-25  1:39     ` Henbin Chang
2019-03-25 23:05       ` Vijay Khemka
2019-03-26  1:01         ` Henbin Chang
2019-03-26 18:44           ` Vijay Khemka
2019-03-27  6:33             ` Henbin Chang
2019-03-27 18:49               ` Vijay Khemka
2019-03-29 18:14                 ` Vijay Khemka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG9c7cDQc=o_=vEFRAjRRq9bV2Fz6ZD7Osp+vkd2QRgxmGcXGg@mail.gmail.com' \
    --to=henbinchang@gmail.com \
    --cc=james.feist@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.