Hi Heinrich, On 11/14/2025 5:28 PM, Heinrich Schuchardt wrote: > Without pre-boot command usb start it is not possible to stop the boot > process via the USB keyboard. > > CMD_ERASEENV allows to easily reset the environment to the initial state. > > Signed-off-by: Heinrich Schuchardt <[email protected]> > --- > configs/rock-pi-4-rk3399_defconfig | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/configs/rock-pi-4-rk3399_defconfig > b/configs/rock-pi-4-rk3399_defconfig > index 219f42bc7d4..6cf80e7fa5e 100644 > --- a/configs/rock-pi-4-rk3399_defconfig > +++ b/configs/rock-pi-4-rk3399_defconfig > @@ -22,6 +22,7 @@ CONFIG_AHCI=y > CONFIG_EFI_CAPSULE_ON_DISK=y > CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y > # CONFIG_ANDROID_BOOT_IMAGE is not set > +CONFIG_USE_PREBOOT=y
Please do not enable PREBOOT in defconfig, this will create an unnecessary boot delay of a few seconds for normal use. Instead please make it more clear in the documentation on how users can enable use of USB keyboard e.g. using environment variables or in their custom build. USB is also auto-probed when nothing can be booted so if I am not mistaken USB keyboard should work at end of a failed autoboot. Regards, Jonas > CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rock-pi-4a.dtb" > CONFIG_DISPLAY_BOARDINFO_LATE=y > CONFIG_SPL_MAX_SIZE=0x40000 > @@ -31,6 +32,7 @@ CONFIG_SYS_SPI_U_BOOT_OFFS=0xE0000 > CONFIG_SPL_ATF_NO_PLATFORM_PARAM=y > CONFIG_TPL=y > CONFIG_CMD_BOOTZ=y > +CONFIG_CMD_ERASEENV=y > CONFIG_CMD_NVEDIT_EFI=y > CONFIG_CMD_DFU=y > CONFIG_CMD_GPT=y
