All of lore.kernel.org
 help / color / mirror / Atom feed
From: matti kaasinen <matti.kaasinen@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] am335x board i2c_probe fails from nand boot
Date: Tue, 3 Jan 2017 14:33:43 +0200	[thread overview]
Message-ID: <CADnUhn0c4ktLT-YFnyHU+BHm_ngEVj6KYKTNbFjzvcAZzLe0zQ@mail.gmail.com> (raw)
In-Reply-To: <672491fd-cf35-dedf-bc8a-975f16d43dca@ti.com>

2017-01-03 13:16 GMT+02:00 Lokesh Vutla <lokeshvutla@ti.com>:

> > Would anyone have idea why spl boot fails in i2c_probe when running from
> > nand but not when running from mmc card or anything at all to check?
>
> Do you have different mux configurations for different boot modes?(Just
> wondering if mux is properly configured for i2c in nand boot)
>
> No, not that I know and can detect from the board file. In fact it looks
like mmc boot has the correct configuration.

> >
> > My card is am335x based board with u-boot coming from u-boot-it v2016.05.
>
> Can you specify the tree? Also which config are you using and what board
> it it?
>
I have been using youcto/poky build system with meta-ti layer that brings
up u-boot-ti-staging.
I have patched board/ti/am335x/board.c and mux.c. I have used am335x_evm
config that I have had to patch somewhat to suit my board.
Board resembles somewhat am335x_evm but it does not have configuration
eeprom, has different ddr3 chips. Also, it has different PMIC (same as
beaglebone). Therefore I need to patch guite a lot. One reason why I2C
configuration is wrong in nand mode could be the fact that I have
CONFIG_TI_I2C_BOARD_DETECT variable is undefined (because I do not have
that eeprom). But it looks that do_board_detect runs enable_i2c0_pin_mux()
that I do not run separately. On the other hand, that does not explain why
mmc boot works.

>
> Thanks and regards,
> Lokesh
>

  reply	other threads:[~2017-01-03 12:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03  9:26 [U-Boot] am335x board i2c_probe fails from nand boot matti kaasinen
2017-01-03 10:56 ` Yegor Yefremov
2017-01-03 11:02   ` matti kaasinen
2017-01-03 11:05     ` Yegor Yefremov
2017-01-03 11:10       ` matti kaasinen
2017-01-03 11:16 ` Lokesh Vutla
2017-01-03 12:33   ` matti kaasinen [this message]
2017-01-03 13:34     ` matti kaasinen
2017-01-03 14:37       ` matti kaasinen
2017-01-04  4:46         ` Lokesh Vutla
2017-01-04  7:33           ` matti kaasinen
2017-01-05 10:09             ` matti kaasinen
2017-01-05 13:01               ` matti kaasinen
2017-01-04 10:23           ` matti kaasinen

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=CADnUhn0c4ktLT-YFnyHU+BHm_ngEVj6KYKTNbFjzvcAZzLe0zQ@mail.gmail.com \
    --to=matti.kaasinen@gmail.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.