mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: gianluca <gianlucarenzi@eurekelettronica.it>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: New Board i.MX6 Dual Lite based
Date: Fri, 9 Jun 2017 09:31:05 +0200	[thread overview]
Message-ID: <b1dd6d19-7733-fe2c-1589-1421c1188ed5@eurekelettronica.it> (raw)
In-Reply-To: <8b1cafb3-8e87-8ce8-e4e1-42d28f82d1b0@eurekelettronica.it>

On 06/09/2017 09:25 AM, gianluca wrote:
>
>>>> i2c0: <i2c_fsl_bus_busy> timeout waiting for I2C bus busy
>>>> ek360_read_eeprom :Error on reading eeprom @ 0
>>>> ek360_read_eeprom :Error on reading bytes.
>>>> ek360_detect_hw :** ERROR on READ EEPROM BOARD ret: -1
>>>> Hit CTRL-C key to stop autoboot:  1
>>>
>>> Another issue is the i2c bus.
>>
>> You should measure the I2C data line with an oscilloscope. It could be
>> that the line is constantly low. This can happen if the pullup resistor
>> is missing (Pinmux?). Also in rare cases this can happen when a board is
>> resetted in the middle of a I2C transfer.
>>
>
> Now I am trying to extend the I2C Lines outside the board for a
> oscilloscope and/or a Saleae Logic Bus Analyzer. As soon as I find the
> solution or not I will keep you informed.
>
> Anyway in the config there is both GPIO BASED I2C DRIVER and Platform
> iMX Driver. I tried to disable the GPIO Based but it does not work.
>
> Now I am thinking about some pulled-low/high line by some chips in the
> board. I will see.
>

Due to an inversion on mounting the i2c eeprom all i2c chips are 
mulfunctioning, so I am trying to uses another board.

Now it works.

Good!

Thank you for everything.
-- 
Eurek s.r.l.                          |
Electronic Engineering                | http://www.eurek.it
via Celletta 8/B, 40026 Imola, Italy  | Phone: +39-(0)542-609120
p.iva 00690621206 - c.f. 04020030377  | Fax:   +39-(0)542-609212

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-06-09  7:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 15:06 gianluca
2017-06-09  6:15 ` Sascha Hauer
2017-06-09  7:25   ` gianluca
2017-06-09  7:31     ` gianluca [this message]
2017-06-09  7:32     ` 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=b1dd6d19-7733-fe2c-1589-1421c1188ed5@eurekelettronica.it \
    --to=gianlucarenzi@eurekelettronica.it \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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