c046b23ea2
Helps prevent the filesystem from getting formatted by mistake, among other things. For example, on a Pico board, entering Ctrl+D and Ctrl+C fast many times will eventually wipe the filesystem (without warning or notice). Further rationale: Ctrl+C is used a lot by automation scripts (eg mpremote) and UI's (eg Mu, Thonny) to get the board into a known state. If the board is not responding for a short time then it's not possible to know if it's just a slow start up (eg in _boot.py), or an infinite loop in the main application. The former should not be interrupted, but the latter should. The only way to distinguish these two cases would be to wait "long enough", and if there's nothing on the serial after "long enough" then assume it's running the application and Ctrl+C should break out of it. But defining "long enough" is impossible for all the different boards and their possible behaviour. The solution in this commit is to make it so that frozen start-up code cannot be interrupted by Ctrl+C. That code then effectively acts like normal C start-up code, which also cannot be interrupted. Note: on the stm32 port this was never seen as an issue because all start-up code is in C. But now other ports start to put more things in _boot.py and so this problem crops up. Signed-off-by: David Grayson <davidegrayson@gmail.com>
60 lines
2.2 KiB
C
60 lines
2.2 KiB
C
/*
|
|
* This file is part of the MicroPython project, http://micropython.org/
|
|
*
|
|
* The MIT License (MIT)
|
|
*
|
|
* Copyright (c) 2013, 2014 Damien P. George
|
|
*
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
* in the Software without restriction, including without limitation the rights
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
* furnished to do so, subject to the following conditions:
|
|
*
|
|
* The above copyright notice and this permission notice shall be included in
|
|
* all copies or substantial portions of the Software.
|
|
*
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
* THE SOFTWARE.
|
|
*/
|
|
#ifndef MICROPY_INCLUDED_LIB_UTILS_PYEXEC_H
|
|
#define MICROPY_INCLUDED_LIB_UTILS_PYEXEC_H
|
|
|
|
#include "py/obj.h"
|
|
|
|
typedef enum {
|
|
PYEXEC_MODE_FRIENDLY_REPL,
|
|
PYEXEC_MODE_RAW_REPL,
|
|
} pyexec_mode_kind_t;
|
|
|
|
extern pyexec_mode_kind_t pyexec_mode_kind;
|
|
|
|
// Set this to the value (eg PYEXEC_FORCED_EXIT) that will be propagated through
|
|
// the pyexec functions if a SystemExit exception is raised by the running code.
|
|
// It will reset to 0 at the start of each execution (eg each REPL entry).
|
|
extern int pyexec_system_exit;
|
|
|
|
#define PYEXEC_FORCED_EXIT (0x100)
|
|
|
|
int pyexec_raw_repl(void);
|
|
int pyexec_friendly_repl(void);
|
|
int pyexec_file(const char *filename);
|
|
int pyexec_file_if_exists(const char *filename);
|
|
int pyexec_frozen_module(const char *name, bool allow_keyboard_interrupt);
|
|
void pyexec_event_repl_init(void);
|
|
int pyexec_event_repl_process_char(int c);
|
|
extern uint8_t pyexec_repl_active;
|
|
|
|
#if MICROPY_REPL_INFO
|
|
mp_obj_t pyb_set_repl_info(mp_obj_t o_value);
|
|
MP_DECLARE_CONST_FUN_OBJ_1(pyb_set_repl_info_obj);
|
|
#endif
|
|
|
|
#endif // MICROPY_INCLUDED_LIB_UTILS_PYEXEC_H
|