How to solve the problem that the Keil project can only run in debug mode but can't be executed normally when developing machine learning programs

How to solve the problem that the Keil project can only run in debug mode but can't be executed normally when developing machine learning programs in C++ with the Nuvoton evaluation board and Arm library?   Issue Date：2023-05-02

When the Keil project can run in debug mode but will get stuck if it is not connected to ICE in free-run mode, and it is found that the program continues to be stuck at a breakpoint from the debug mode, it may be a semihosting error.
If some error messages such as "stdout/stdin/stderr multiply defined..." appear when using the Arm library in the Nuvoton machine learning examples, it will cause semihosting errors by deleting the repeatedly defined items directly and lead to the continued breakpoint appearing in the Keil project.

Note: In order to avoid the semihosting errors, apart from deleting duplicate definitions, users need to add the following code in retarget.c:

extern void $Super$$_sys_open(void);

FILEHANDLE $Sub$$_sys_open(const char *name, int openmode)

{

 return 1; /* everything goes to the same output */

}

(If there are other L6200E errors (Symbol _sys_XXX multiply defined) during compilation, please also add the FILEHANDLE definition of sys_XXXX())