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 15:34:59 +0200	[thread overview]
Message-ID: <CADnUhn39NjZkRFv8E9SLpb2yU4vhsjLwS7Dm5T3RnU94xe2gsg@mail.gmail.com> (raw)
In-Reply-To: <CADnUhn0c4ktLT-YFnyHU+BHm_ngEVj6KYKTNbFjzvcAZzLe0zQ@mail.gmail.com>

2017-01-03 14:33 GMT+02:00 matti kaasinen <matti.kaasinen@gmail.com>:

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



Now I did this I2C0 configuration separately prior to running i2c_probe().
Nand boot went further now. However, main u-boot did not start properly. I
got following messages
Trying to boot from NAND
The Expected Linux image was not found. Please check your NAND
configuration.
Trying to start u-boot now...

........ more messages ....
Press SPACE to abort autoboot in 2 seconds
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
data abort
pc : [<8ff70f94>]          lr : [<8ff701dd>]
reloc pc : [<8081df94>]    lr : [<8081d1dd>]
sp : 8ef28678  ip : 8ff5891d     fp : 00000003
r10: 8ffb3af8  r9 : 8ef32ed8     r8 : 8ef41e40
r7 : 8ff584bd  r6 : 8ef39478     r5 : 8ef39500  r4 : 47810000
r3 : 8ff70f85  r2 : 00000d8d     r1 : 00000000  r0 : 8ef39500
Flags: nZCv  IRQs off  FIQs on  Mode SVC_32
Resetting CPU ...

resetting ...

And game over....
So, it's not quite sure that voltage adjustments went through even though
I2C did not complain anymore.
There could be something wrong with nand settings, too. I need to check
where these complaints are coming.

Thanks anyway for your comments,
Matti

  reply	other threads:[~2017-01-03 13:34 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
2017-01-03 13:34     ` matti kaasinen [this message]
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=CADnUhn39NjZkRFv8E9SLpb2yU4vhsjLwS7Dm5T3RnU94xe2gsg@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.