All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] test/py main_signon
Date: Wed, 17 Feb 2016 09:42:26 +0100	[thread overview]
Message-ID: <56C43272.9020709@monstr.eu> (raw)
In-Reply-To: <56C396D1.1050704@wwwdotorg.org>

Hi Stephen,

On 16.2.2016 22:38, Stephen Warren wrote:
> On 02/16/2016 12:08 PM, Michal Simek wrote:
>> Hi Stephen,
>>
>> 2016-02-16 17:39 GMT+01:00 Stephen Warren <swarren@wwwdotorg.org
>> <mailto:swarren@wwwdotorg.org>>:
>>
>>     On 02/16/2016 09:04 AM, Michal Simek wrote:
>>
>>         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 assume this is resolved then?
>>
>>
>> Unfortunately both cases should work because SPL is not only one first
>> stage bootloader
>> which can be used. I didn't test zynqmp but there is no SPL and the same
>> problem is
>> probably there too. Or is there any dependency that if SPL is not build
>> than testing system
>> is not expecting it?
>>
>> I will look tmr at jtag boot mode with SPL if I can get it work.
> 
> The test scripts currently assume that if SPL is enabled in the U-Boot
> configuration file, then U-Boot SPL will run and print its signon
> message to the serial console. If you're starting U-Boot using a
> technique that invalidates this assumption, it won't work currently, as
> you found.
> 
> It's pretty easy to add a flag in the boardenv file to tell the system
> not to expect SPL signon. If you take a look at my second suggestion in:
> 
> http://lists.denx.de/pipermail/u-boot/2016-February/245759.html
> [U-Boot] [PATCH] test/py: only check for SPL signature if SPL uses
> serial output
> 
> ... then it's probably a simple as adding a third variable into the if
> condition, where that variable gets looks up from the "board
> environment", similar to:
> 
> spl_skipped = u_boot_console.config.env.get('env__spl_skipped', False)

ok. I see. Anyway I have done this change locally and it is working good.
Heiko: Are you able to add this one more checking to your patch? Or
should I wait till you add your patch to the tree?

Stephen: Do you have your u-boot-test-hooks for qemu?

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160217/e7c4d476/attachment.sig>

  reply	other threads:[~2016-02-17  8:42 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 [this message]
2016-02-17  9:05             ` Heiko Schocher
2016-02-17 18:38             ` Stephen Warren
2016-02-17  6:34     ` Heiko Schocher
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=56C43272.9020709@monstr.eu \
    --to=monstr@monstr.eu \
    --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.