mirror of
https://github.com/brain-hackers/u-boot-brain
synced 2024-06-09 23:36:03 +09:00
f2980ece06
It doesn't make a lot of sense to hang on sandbox when hang() is called, since the only way out is Ctrl-C. In fact, Ctrl-C does not work if the terminal is in raw mode, which it will be if the command-line has not been reached yet. In that case, Ctrl-Z / kill -9 must be used, which is not very friendly. Avoid all of this by quiting when hang() is called. Signed-off-by: Simon Glass <sjg@chromium.org>
35 lines
884 B
C
35 lines
884 B
C
// SPDX-License-Identifier: GPL-2.0+
|
|
/*
|
|
* (C) Copyright 2013
|
|
* Andreas Bießmann <andreas@biessmann.org>
|
|
*
|
|
* This file consolidates all the different hang() functions implemented in
|
|
* u-boot.
|
|
*/
|
|
|
|
#include <common.h>
|
|
#include <bootstage.h>
|
|
#include <os.h>
|
|
|
|
/**
|
|
* hang - stop processing by staying in an endless loop
|
|
*
|
|
* The purpose of this function is to stop further execution of code cause
|
|
* something went completely wrong. To catch this and give some feedback to
|
|
* the user one needs to catch the bootstage_error (see show_boot_progress())
|
|
* in the board code.
|
|
*/
|
|
void hang(void)
|
|
{
|
|
#if !defined(CONFIG_SPL_BUILD) || \
|
|
(CONFIG_IS_ENABLED(LIBCOMMON_SUPPORT) && \
|
|
CONFIG_IS_ENABLED(SERIAL_SUPPORT))
|
|
puts("### ERROR ### Please RESET the board ###\n");
|
|
#endif
|
|
bootstage_error(BOOTSTAGE_ID_NEED_RESET);
|
|
if (IS_ENABLED(CONFIG_SANDBOX))
|
|
os_exit(1);
|
|
for (;;)
|
|
;
|
|
}
|