[U-Boot] POST related question

[Michael Zaidman]

On Wed, Feb 10, 2010 at 4:33 PM, Michael Zaidman
<michael.zaidman at gmail.com> wrote:
>
>
> On Wed, Feb 10, 2010 at 3:28 PM, Wolfgang Denk <wd at denx.de> wrote:
> > Dear Michael Zaidman,
> >
> > In message <660c0f821002100159i1a956edfx1c76945042f51954 at mail.gmail.com> you wrote:
> >> SGVsbG8sCgpXb3JraW5nIG9uIHRoZSBQT1NUIGZvciBvdXIgYm9hcmQgKHdoaWNoIEkgYW0gZ29p
> ...
> >
> > Please do not send base 64 encoded messages.
> >
> > Please do not send HTML messages.
> >
> > Please send plain text only.
> >
> > Message unreadable, ignored. Sorry.
> >
> >
>
Ok, sorry, I re-post my question again.

Hello,

Working on the POST for our board (which I am going to submit
to the u-boot in the near future) I was asked to output the POST tests
sequence progress to the dedicated LEDs (current test’s index and
test’s result – PASS or FAIL) in addition to the conventional console
output. Such indication can be helpful at the customer premises when
console is not available as well as at the production testing/diagnostics
to understand which POST test has failed while serial console does not
show signs of life.
In order to fulfill this requirement I see two possibilities:

1) Common infrastructure change - add pre-test and after test callbacks
to the post_test structure in the tests.c file. Call these callbacks
before and after each POST test in the post_run_single routine of post.c file.

2) Local, board specific change – duplicate all necessary POST tests into
specific board folder and add output to LEDs interface into every
xxxx_post_test routine.

Please advise.

Thanks,
Michael