On Fri, Feb 22, 2008 at 10:53 AM, Wolfgang Denk <wd@denx.de> wrote:

In message <8ff29df80802220653u7af49b35sf2d437baa4afa461@mail.gmail.com> you wrote:
>
> How would i go about halting u-boot, one on my requirement is to stop the
> board from booting if one of the POST test fails or anthor test fails.

That's what we call a "critical POST failure".

> The only thing that i could think of was setting ....
>
> setenv("bootcmd", "");
>
> But i think there is a better way. Any suggestions,

What you want is this commit:

8a484d2b87067bfbf83583606600486ff4b4f0a2

The patch introduces the CRITICAL feature of POST tests. If the test
marked as POST_CRITICAL fails then the alternative, post_critical,
boot-command is used. If this command is not defined then U-Boot
enters into interactive mode.

Signed-off-by: Dmitry Rakhchev <rda@emcraft.com>
Signed-off-by: Yuri Tikhonov <yur@emcraft.com>

You can find this in the lwmon5 branch of the U-Boot git repository
where it is queued up ready for merge into mainline as soon as the
next merge window opens again.

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Documentation is the castor oil of programming.
Managers know it must be good because the programmers hate it so much.