public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: eija_flight <ajie.dirgantara@flightfocus.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot initialization test
Date: Thu, 2 Apr 2009 01:37:22 -0700 (PDT)	[thread overview]
Message-ID: <22843365.post@talk.nabble.com> (raw)
In-Reply-To: <20090402065709.588EA83797DC@gemini.denx.de>



>Dear eija_flight,

>In message <22840615.post@talk.nabble.com> you wrote:
> 
> During above initialization process of u-boot, 
> 
> 1. Does it conduct a test to all board hardware listed?

>No. In general, there is no testing performed. Minor exceptions from
>this rule exist, for example the RAM auto-sizing code also performas a
>minimal non-destructive memory test, but this is not strong enough to
>be called serious testing.

>If you need real Power-On Self Tests (POST), then you must enable
>POST in your board configuration and configure it according to your
>needs.

> 2. If above answer is yes, what method is used to do the test? 

>If you need such tests, then use the code in post/, see doc/README.POST

I've read through the README.post, and I can see that there's many
implemented test feature built in U-boot. I find it very useful. 

Using U-boot 1.3.1 version,  It is possible (as a user) to apply all of
these test feature into a standalone applications?
because I need to log the result using standalone app. 

Regards,
Eija_flight
 
-- 
View this message in context: http://www.nabble.com/U-boot-initialization-test-tp22840615p22843365.html
Sent from the Uboot - Users mailing list archive at Nabble.com.

  reply	other threads:[~2009-04-02  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02  4:20 [U-Boot] U-boot initialization test eija_flight
2009-04-02  6:57 ` Wolfgang Denk
2009-04-02  8:37   ` eija_flight [this message]
2009-04-02 11:32     ` Wolfgang Denk

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=22843365.post@talk.nabble.com \
    --to=ajie.dirgantara@flightfocus.net \
    --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