From: "Srinivasan, Usha" <usha.srinivasan@cornelisnetworks.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: entity-manager FruDevice & eeprom questions
Date: Wed, 14 Apr 2021 21:03:22 +0000 [thread overview]
Message-ID: <BYAPR01MB47582E93CAFD772A1EF5E5649E4E9@BYAPR01MB4758.prod.exchangelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]
Hello.
This is my first-time using entity-manager for inventory & the ability to create one binary image with different json files for different platform configurations.
But, first, I am trying to initialize the eeprom on my development board and have it picked up by FruDevice.
1. I defined the eeprom in my dts file but as 24lc128 so at24 driver didn't pick it up but that allowed me to use i2ctransfer to initialize the eeprom contents.
2. I initialized the eeprom contents following the layout in this doc:
https://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/platform-management-fru-document-rev-1-2-feb-2013.pdf
3. I fixed the dts file to define the eeprom using generic "24c128" and now at24 is picking it up and I see:
ls /sys/bus/i2c/devices/8-0051/
8-00510 eeprom name subsystem
driver modalias of_node uevent
cat /sys/bus/i2c/devices/8-0051/name
24c128
1. But I also see this:
ls /sys/bus/i2c/devices/8-0051/8-00510/
nvmem of_node subsystem type uevent
2. In the json file for entity manager I have:
{
"Address": "0x51",
"Bus": 8,
"Name": "CN FRU EEPROM",
"Type": "EEPROM"
},
1. But, FruDevice fails looking for "/etc/fru/baseboard.fru.bin".
Questions:
1. Can someone who has used entity-manager & FruDevice explain the reading/processing of the contents of the eeprom & the of "/etc/fru/baseboard.fru.bin" or in other words, what am I doing wrong that FruDevice won't get off the ground?
2. Is there a recommended method for how to initialize the eeprom in manufacturing?
3. Has someone developed a script or an application which given the important pieces of info(see pdf above) formats the contents of the eeprom?
4. In general, does one define the eeprom in the dts as well as in the entity-manager json?
Thanks,
Usha
__________________________
Usha Srinivasan
Embedded Software Engineer
Cornelis Networks
1500 Liberty Ridge Dr
Chesterbrook, PA, 19087
484-498-8425
610-703-8475 (cell)
[-- Attachment #2: Type: text/html, Size: 9882 bytes --]
next reply other threads:[~2021-04-14 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 21:03 Srinivasan, Usha [this message]
2021-04-21 19:18 ` entity-manager FruDevice & eeprom questions Ed Tanous
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=BYAPR01MB47582E93CAFD772A1EF5E5649E4E9@BYAPR01MB4758.prod.exchangelabs.com \
--to=usha.srinivasan@cornelisnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).