From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16120] New: Unable to get I2C working on Raspberry-pi-5
Date: Fri, 28 Jun 2024 12:13:43 +0000 [thread overview]
Message-ID: <bug-16120-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=16120
Bug ID: 16120
Summary: Unable to get I2C working on Raspberry-pi-5
Product: buildroot
Version: 2024.05
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: albert.david@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
excuse me for filing this as a bug, but i am not really sure where the issue
is.
here is the problem description:
1) created sdcard.img using make raspberrypi5_defconfig
2) sdcard.img was written to micro-sdcard and able to boot the pi5 board
3) on pi5 console, ls /dev/i2c* did not show anything
4) on a running system, mounted /dev/mmcblk0p1 to /tmp/boot and added following
lines to /tmp/boot/config.txt
dtoverlay=i2c1,pins_2_3,baudrate=1000000
dtparam=i2c_arm=on
5) rebooted the board but /dev/i2c* didnt show anything
6) modified config.txt again with following changes but /dev/i2c* didnt show
up.
dtoverlay=i2c1-pi5
dtparam=i2c_arm=on
7) when booting pi-5 with RaspberryPi-OS and enabling the i2c using sudo
raspi-config shows up three nodes under /dev/i2c*
Any idea what am I missing here? has anyone managed to get i2c working on a
buildroot generated image for pi-5? what changes did u do in your config.txt?
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2024-06-28 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-16120-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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