From: Marcel Behlau <marcel.behlau@elfin.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Usage of i2c_-Tools in Barebox
Date: Thu, 07 May 2015 13:24:19 +0200 [thread overview]
Message-ID: <554B4B63.7020301@elfin.de> (raw)
In-Reply-To: <20150506071228.GQ25193@pengutronix.de>
Hi,
many thanks for your help. I activated the i2c devices in the device
tree, the pinctrl is already done in the imx6q.dtsi, which is included.
The used pins are identically with the used pins on the SBC. devinfo
told me, that the driver "i2c-fsl" is loaded. After rebuild barebox,
it's possible to probe the bus, but the command only answered with an
timeout:
barebox@Phytec phyFLEX-i.MX6 Quad Carrier-Board:/ i2c_probe 1 83 83
probing i2c range 0x53 - 0x53 :
i2c2: <i2c_fsl_bus_busy> timeout waiting for I2C bus busy
I'm using barebox-2013.08.0, which is provided by the phytec-bsp.
Thanks in advance,
Marcel
On 06.05.2015 09:12, Uwe Kleine-König wrote:
> Hello,
>
> On Tue, May 05, 2015 at 05:54:50PM +0200, Sascha Hauer wrote:
>> On Tue, May 05, 2015 at 04:56:10PM +0200, Marcel Behlau wrote:
>>> i'm using a phyFLEX-i.MX6 SBC and want to communicate with an
>>> external µC over I2C. I only want to read/set 1 register, so i tried
>>> to use the builtin i2c_read and i2c_write-Commands. The µC is
>>> connected to i2c-bus 1 of the device, so i tried to probe the hole
>>> bus with "i2c_bus 1 3 30". The command only answered with
>>> "i2c_probe: No such device". I tried also the busses 0-3, with the
>>> same result. I searched in the board.c sourcecode of the phyflex,
>>> but couldn't find i2c related stuff, so i think, i have to add the
>>> initalisation for the i2c.
>>>
>>> Do i have to add the i2c-init in the boards/phytec-pfla02/board.c
>>> -file? Is there some documenation about this stuff?
>> The phyFLEX board is device tree based. You have to enable the i2c
>> controller in the dts file (same as you would do in the kernel).
>> Usually a:
>>
>> &i2c0 {
>> status = "okay";
>> };
>>
>> Should be enough. You probably also have to add the proper pinctrl node.
> and enable the i2c driver. You might want to check the output of
> devinfo.
>
> Best regards
> Uwe
>
--
Dipl. Ing (FH) Marcel Behlau
(Software Developer)
ELFIN GmbH
Siegburger Straße 215
50679 Köln
Germany
Tel: +49 (221) 6778932-0
Fax: +49 (221) 6778932-2
marcel.behlau@elfin.de
www.elfin.de
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-05-07 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 14:56 Marcel Behlau
2015-05-05 15:54 ` Sascha Hauer
2015-05-06 7:12 ` Uwe Kleine-König
2015-05-07 11:24 ` Marcel Behlau [this message]
2015-05-08 5:12 ` Sascha Hauer
2015-05-20 6:34 ` Marcel Behlau
2015-05-22 6:41 ` Sascha Hauer
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=554B4B63.7020301@elfin.de \
--to=marcel.behlau@elfin.de \
--cc=barebox@lists.infradead.org \
--cc=u.kleine-koenig@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