public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] test/py main_signon
Date: Wed, 17 Feb 2016 07:34:53 +0100	[thread overview]
Message-ID: <56C4148D.4070608@denx.de> (raw)
In-Reply-To: <56C3487B.5070802@xilinx.com>

Hello Michal,

Am 16.02.2016 um 17:04 schrieb Michal Simek:
> Hi Heiko,
>
> On 16.2.2016 14:32, Heiko Schocher wrote:
>> Hello Michal,
>>
>> Am 16.02.2016 um 13:12 schrieb Michal Simek:
>>> Hi Stephen,
>>>
>>> trying to run the latest testing on zynq board and getting this
>>> main_signon error.
>>>
>>> This is what I am running
>>> ./test/py/test.py --bd zynq_zc702  --build --board-identity zc702
>>> and getting below.
>>
>> Does this board has SPL support without SPL serial output?
>
> I do load u-boot via jtag that's why SPL logs are not visible.
>
>> If so, can you try my patch:
>> http://patchwork.ozlabs.org/patch/583348/
>
> I have applied your patch but it is still not working.
>
> If I run full flow with SPL then I can't see any issue.

I am not an expert of test/py (I still try to dig into it), but as
I understand it, it looks if CONFIG_SPL is defined, if so, the
framework expects a SPL output first, if not found, it raises
the error you see ...

My patch fixes this, for boards which use SPL, but without serial
SPL output ...

Now you test only u-boot with SPL configured with SPL serial output ...

I think Stephen can say here more, how to solve this ...

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

  parent reply	other threads:[~2016-02-17  6:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 12:12 [U-Boot] test/py main_signon Michal Simek
2016-02-16 13:32 ` Heiko Schocher
2016-02-16 16:04   ` Michal Simek
2016-02-16 16:39     ` Stephen Warren
2016-02-16 19:08       ` Michal Simek
2016-02-16 21:38         ` Stephen Warren
2016-02-17  8:42           ` Michal Simek
2016-02-17  9:05             ` Heiko Schocher
2016-02-17 18:38             ` Stephen Warren
2016-02-17  6:34     ` Heiko Schocher [this message]
2016-02-17  7:24       ` 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=56C4148D.4070608@denx.de \
    --to=hs@denx.de \
    --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