From: David Picard <david.picard@clermont.in2p3.fr>
To: ML_Barebox <barebox@lists.infradead.org>
Cc: s.trumtrar@pengutronix.de, abbotti@mev.co.uk
Subject: ARM: socfpga: enclustra-sa2: issue with I2C1
Date: Thu, 23 Apr 2026 14:00:12 +0200 [thread overview]
Message-ID: <aeaec45e-ef30-462b-a28f-53d2b82d6387@clermont.in2p3.fr> (raw)
Hello,
@Stephen and Ian: I Cc you since I spotted you authored commits related
to Intel SoC FPGA pin muxing.
I'm trying to enable the I2C1 bus on a Cyclone V-base module, mounted on
a base board. The I2C1 lines connect to a 2.54mm header, on which I
attached a I²C device with pull-up resistors at address 0x40.
https://www.enclustra.com/en/products/system-on-chip-modules/mercury-sa2/
I can't detect the I²C device, nor can I see any pulse on the SCL line,
which is constantly at +3.3V.
I changed the pin muxing in Quartus, updated the handoff files, changed
the devicetree. The I2C1 bus is visible in Barebox and Linux. More
detail here:
https://community.altera.com/discussions/fpga-device/cyclone-v-hps-i2c1-issue-no-activity-on-bus/352583
As documented on the Barebox website, I generated the BSP files with the
Quartus script bsp-create-settings and copied the handoff files to the
Barebox build directory. After that, I could see that
iocsr_config_cyclone5.c and pinmux_config.c had changed.
https://www.barebox.org/doc/2025.05.0/boards/socfpga.html#updating-handoff-files
https://www.intel.com/content/www/us/en/docs/programmable/683187/20-1/bsp-create-settings.html
If someone could give me some hint, that would be really great!
David
next reply other threads:[~2026-04-23 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 12:00 David Picard [this message]
2026-04-24 7:27 ` Steffen Trumtrar
2026-04-27 10:09 ` David Picard
2026-04-27 10:20 ` Steffen Trumtrar
2026-04-27 12:13 ` David Picard
2026-04-27 12:25 ` Steffen Trumtrar
2026-04-27 12:36 ` David Picard
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=aeaec45e-ef30-462b-a28f-53d2b82d6387@clermont.in2p3.fr \
--to=david.picard@clermont.in2p3.fr \
--cc=abbotti@mev.co.uk \
--cc=barebox@lists.infradead.org \
--cc=s.trumtrar@pengutronix.de \
/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