In message <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
Signed-off-by: Yuri Tikhonov <[EMAIL PROTECTED]>
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: [EMAIL PROTECTED]
Documentation is the castor oil of programming.
Managers know it must be good because the programmers hate it so much.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
