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@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
