public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Zynq: Unable to boot from MMC
Date: Mon, 23 Nov 2015 11:27:31 +0100	[thread overview]
Message-ID: <5652EA13.2070406@xilinx.com> (raw)
In-Reply-To: <CAD6G_RQgguSrtSUwK=ZC71UaV0WbMW9VVoTd-sdDLUzjeWTGnA@mail.gmail.com>

Hi Jagan,

On 23.11.2015 10:20, Jagan Teki wrote:
> Hi Moritz,
> 
> On 23 November 2015 at 01:15, Moritz Fischer <moritz.fischer@ettus.com> wrote:
>> Hi Jagan,
>>
>>
>>
>> On Sun, Nov 22, 2015 at 6:25 AM, Jagan Teki <jteki@openedev.com> wrote:
>>> Hi Michal,
>>>
>>> I'm unable to boot the zynq board from MMC, here is my trails:
>>> 1. zynq-boot-bin.py -o boot.bin -u spl/u-boot-spl-dtb.bin
>>> copied boot.bin and u-boot-dtb.img on to sd card
>>>
>>
>> try reverting 9ac4fc82071ce346e3885118242ff45d22f69b82. I ran into
>> this friday and was pointed to that
>> by a colleague.
> 
> Still the same issue, here is the reverted commit
> 
>     Revert "board_init: Change the logic to setup malloc_base"
> 
>     This reverts commit 9ac4fc82071ce346e3885118242ff45d22f69b82.
> 
> 

I have reported problem with SPL in my pull request to Tom last week.
I have tested current HEAD. When you revert that sha1 reported above it
is just working directly in MMC bootmode on zc702.

On Friday Philip tried the same on zedboard and it was working fine for
him too.

I still don't know exactly where the problem is because I haven't spent
on it any time - just bisecting commit ID which was the first broken one.

Thanks,
Michal

  reply	other threads:[~2015-11-23 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 14:25 [U-Boot] Zynq: Unable to boot from MMC Jagan Teki
2015-11-22 19:45 ` Moritz Fischer
2015-11-23  9:20   ` Jagan Teki
2015-11-23 10:27     ` Michal Simek [this message]
2015-11-23 15:42       ` Michal Simek

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=5652EA13.2070406@xilinx.com \
    --to=michal.simek@xilinx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox