openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Zev Weiss <zweiss@equinix.com>
To: damon3000 <damon3000@163.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Re: FRU access configuration
Date: Fri, 18 Feb 2022 03:48:14 +0000	[thread overview]
Message-ID: <20220218034814.GS5754@packtop> (raw)
In-Reply-To: <3cbbabf.9be4.17f07606bbc.Coremail.damon3000@163.com>

On Thu, Feb 17, 2022 at 03:10:33AM PST, damon3000 wrote:
>Hi Patrick,
>
>
>  1.  According to your suggestion, I can scan my FRU information via busctl command, but entity-manager did not start and can not be accessed.
>The log is as below:
>
>"
>busctl tree --no-pager xyz.openbmc_project.FruDevice
>`-/xyz
>  `-/xyz/openbmc_project
>    `-/xyz/openbmc_project/FruDevice
>      |-/xyz/openbmc_project/FruDevice/10_64
>      |-/xyz/openbmc_project/FruDevice/10_65
>      |-/xyz/openbmc_project/FruDevice/10_67
>      |-/xyz/openbmc_project/FruDevice/3_80
>      |-/xyz/openbmc_project/FruDevice/6_72
>      |-/xyz/openbmc_project/FruDevice/6_74
>      |-/xyz/openbmc_project/FruDevice/6_76
>      |-/xyz/openbmc_project/FruDevice/7_81
>      |-/xyz/openbmc_project/FruDevice/7_89
>      `-/xyz/openbmc_project/FruDevice/test
>
>
>busctl introspect --no-pager xyz.openbmc_project.FruDevice \
>>  /xyz/openbmc_project/FruDevice/Brahma______________
>NAME                                TYPE      SIGNATURE RESULT/VALUE                       FLAGS
>org.freedesktop.DBus.Introspectable interface -         -                                  -
>.Introspect                         method    -         s                                  -
>org.freedesktop.DBus.Peer           interface -         -                                  -
>.GetMachineId                       method    -         s                                  -
>.Ping                               method    -         -                                  -
>org.freedesktop.DBus.Properties     interface -         -                                  -
>.Get                                method    ss        v                                  -
>.GetAll                             method    s         a{sv}                              -
>.Set                                method    ssv       -                                  -
>.PropertiesChanged                  signal    sa{sv}as  -                                  -
>xyz.openbmc_project.FruDevice       interface -         -                                  -
>.ADDRESS                            property  u         80                                 emits-change
>.BOARD_FRU_VERSION_ID               property  s         "UVD050"                           emits-change
>.BOARD_INFO_AM1                     property  s         "V1  "                             emits-change
>.BOARD_INFO_AM2                     property  s         "0123456789ABCDE001TAG0000002  " emits-change
>.BOARD_INFO_AM3                     property  s         "R1B "                             emits-change
>.BOARD_INFO_AM4                     property  s         "XX1 "                             emits-change
>.BOARD_INFO_AM5                     property  s         "0E11223344E0"                     emits-change
>.BOARD_INFO_AM6                     property  s         "02"                               emits-change
>.BOARD_LANGUAGE_CODE                property  s         "0"                                emits-change
>.BOARD_MANUFACTURER                 property  s         "Huaqin Telecom  "                 emits-change
>.BOARD_MANUFACTURE_DATE             property  s         "1996-07-07 - 10:57:00"            emits-change
>.BOARD_PART_NUMBER                  property  s         "NA                  "             emits-change
>.BOARD_PRODUCT_NAME                 property  s         "test              "             emits-change
>.BOARD_SERIAL_NUMBER                property  s         "3120E33900011X0010            " emits-change
>
>
>
>root@sky:/etc/default/obmc/eeproms/system/chassis# echo "24c64 0x50 > /sys/bus/i2c/devices/i2c-3/new_device"
>24c64 0x50 > /sys/bus/i2c/devices/i2c-3/new_device

I haven't closely followed what else you're doing here, but this
definitely looks wrong -- I think you meant to do

  $ echo "24c64 0x50" > /sys/bus/i2c/devices/i2c-3/new_device

Note the position of the close quote -- as you had it above it's just
writing a long string to stdout instead of sending the device name and
i2c address to the sysfs 'new_device' file.


Zev

  reply	other threads:[~2022-02-18  3:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  3:13 FRU access configuration damon3000
2022-02-15 19:34 ` Patrick Williams
2022-02-17 11:10   ` damon3000
2022-02-18  3:48     ` Zev Weiss [this message]
2022-02-18  6:08     ` damon3000

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=20220218034814.GS5754@packtop \
    --to=zweiss@equinix.com \
    --cc=damon3000@163.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).