From: Jean Delvare <jdelvare@suse.de>
To: "Amutha Krishnasamy" <amutha.krishnasamy@montage-tech.com>
Cc: <linux-i2c@vger.kernel.org>
Subject: Re: How to build I2Ctools for OpenBMC
Date: Tue, 26 Sep 2023 14:37:59 +0200 [thread overview]
Message-ID: <20230926143759.66eeb323@endymion.delvare> (raw)
In-Reply-To: <009c01d9efe1$87f46080$97dd2180$@montage-tech.com>
Hi Amutha,
On Mon, 25 Sep 2023 14:53:10 -0400, Amutha Krishnasamy wrote:
> This is Amutha Krishnasamy <https://github.com/amuthakrishnasamy> from Montage technologies https://www.montage-tech.com/DDR5_SPD_PMIC_TS/M88SPD5118
>
> Currently, I am working on adding Device authentication feature for eSPD(enhanced Serial Presence Detect) device which is under development.
>
> For this testing, I would like to know how to rebuild the i2c-tools https://git.kernel.org/pub/scm/utils/i2c-tools/i2c-tools.git/ (used in the openBMC source) and what are the tools used for this build.
>
> I tried to build i2ctools with https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads - x86_64 Linux hosted cross toolchains - AArch64 GNU/Linux target (aarch64-none-linux-gnu) arm-gnu-toolchain-12.3.rel1-x86_64-aarch64-none-linux-gnu.tar.xz.
>
> This created a binary and when used the binary I could not execute and getting Execute format error.
>
> Please let me know if you have any info on how to build the i2ctools to run on EGS system.
I can't help you with that, sorry. I have no experience with
cross-building binaries for embedded systems. I don't think your
problem is related to i2c-tools anyway, the tool chain used to build
binaries would be the same for any project written in C.
--
Jean Delvare
SUSE L3 Support
parent reply other threads:[~2023-09-26 12:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <009c01d9efe1$87f46080$97dd2180$@montage-tech.com>]
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=20230926143759.66eeb323@endymion.delvare \
--to=jdelvare@suse.de \
--cc=amutha.krishnasamy@montage-tech.com \
--cc=linux-i2c@vger.kernel.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