Re: Usage of i2c_-Tools in Barebox

[Marcel Behlau <marcel.behlau@elfin.de>]

Hi,

i found the problem. The Pad Mux Register (0x20E008C and 0x20E0090) are 
not initialised. In both registers is a 0x00000005 (reset value), 
instead of 0x00000016. I think, i must specify the value of the mux 
register in the device tree, too. How can i do this?

Thank in advance,

Marcel

md 0x20E008C-0x20E0093

On 08.05.2015 07:12, Sascha Hauer wrote:
> On Thu, May 07, 2015 at 01:24:19PM +0200, Marcel Behlau wrote:
>> 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 *think* this means that the levels on the bus do not properly follow
> what the controller wants to do. Maybe pullup missing? An oscilloscope
> might help here.
>
> Sascha
>

-- 
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