gpread

U-boot defaults to "In: serial" and also listens for packets (its assumed that its a keyboard/terminal) so that a keypress can stop autoboot. I am successfully using /dev/ttyS2 after modifying /boot/armbianEnv.txt (Console=Display) and masking the gettyS2 service. The device/system I have connected to UART2 (/dev/ttyS2) periodically sends bytes. Thus, if a remote restart or a cold boot is performed (power glitch or power reset) while that system is connected to UART2, it triggers the abort of Autoboot. Requiring the other system/device to be disconnected from UART2, a cold boot of the RockPi4 and then reconnection of the system/device to UART2. I don't see any standard way to reconfigure things to avoid use of UART2 during U-boot and of course its useful for dealing with real issues to be able to interrupt autoboot and then interactively control what happens. Hence the best solution I can see would be for there to be a change to the armbian u-boot to look for a specific key or key sequence rather than just any old key/byte that hits the UART2 RX. Perhaps there could even be a parameter added for use in armbianEnv.txt that allows the abort Autoboot key or key sequence to be defined/redefined ? Thanks for any/all assistance

Hi, I am trying to install Armbian_20.07_Arm-64_buster_current_5.7.9.img onto the emmc (internal storage) of my TVBOX. Its a T95N S905X device with 1g RAM and 8g emmc. I followed the process at the start of this thread and I can get it running fine off of the micro sd card, using either/both of the meson-gxl-s905x-p212.dtb or meson-gxl-s905x-nexbox-a95x.dtb and I have successfully used the Amlogic USB burning tool to install and run stock firmware images for MXQPro, T95N, T95X and A95X-nexbox. I have tried without success once running ambian from the external microsd to install it to the intermal emmc using the /root/install-aml.sh or /root/install-aml-S905.sh. I have tried to debug why it does not work and it appears to come down to how the storage is seen by the kernel/OS. fdisk -l shows the emmc in the form of /dev/mmcblkX with /dev/mmcblkXp1 and /dev/mmcblkXp1 but the devices tree has them as /dev/mmcblkXboot0 and /dev/mmcblkXboot1. The X varies according to which dtb I use, its either 0 or 1. I tried renaming the /dev/xxxxxboot0 and 1 entries to match what fdisk and the script wants but it does not resolve the issue. Any pointers or solutions will be gratefully received, thanks