Search the Community

I still have the UART connected to monitor what is going on. The usb cable is 100% working as I tried to run ums 0 mmc 0 command and computer detects the SD card.

So when UART works you can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -U to print debug output to serial and then use a pastebin service of your choice to share the whole output.

I tried rebooting the router. Nothing changed in the end. The router does not respond to ping, but the board works properly via uart. Please help

@shellless USB as GND source sound legit. Just to double check that you are correctly wired UART - have you tried to swap RX/TX? I have a board that looks exactly the same as yours: GND is a last drill hole on a board corner (probably there is nothing to afraid of soldering), then board's TX, board's RX, and VCC (next to the IR receiver). Baudrate 1500000. Also, be aware that sometimes board does not fully reset with board's RX pin connected to PC (it seems some components still powered up by RX pin). So I have to temporary disconnect RX pin. AFAIK Armbian does not need bootloader on emmc. So emmc could be cleared, masked or unsoldered.

Anyone have Armbian image for Amlogic S805? Android Box Infomation FDT: m8b_m201_1GB UART Log: QA5:B;SVN:B72;POC:1DF;STS:0;BOOT:0;INIT:0;READ:0; U-boot-00000-ge0c1103-dirty(m8b_m201_v1@) (Feb 02 2018 - 15:47:12) clr h-ram DRAM: 1 GiB relocation Offset is: 2fec4000 aml_card_type=0x200 MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6 [mmc_register] add mmc dev_num=1, port=2, if_type=6 SDIO Port B: 0, SDIO Port C: 1 power init out reg=c110804c,value=dfffffff IR init done! register usb cfg[0][1] = 3ff67d4c register usb cfg[2][0] = 3ff6ac98 NAND: EMMC BOOT: not init nand do not init nand : cause boot_device_flag without nand get_boot_device_flag: init_ret -1 get_boot_device_flag EMMC BOOT: Emmckey: Access range is illegal! [mmc_init] SDIO Port C:1, if_type=7, initialized OK! [mmc_get_partition_table] skip cache partition. Partition table get from SPL is : name offset size flag =================================================================================== 0: bootloader 0 400000 0 1: reserved 2400000 4000000 0 2: cache 6c00000 20000000 2 3: env 27400000 800000 0 4: logo 28400000 2000000 1 5: recovery 2ac00000 2000000 1 6: misc 2d400000 2000000 1 7: boot 2fc00000 2000000 1 8: system 32400000 40000000 1 9: data 72c00000 15f400000 4 mmc read lba=0x12000, blocks=0x1 mmc read lba=0x12001, blocks=0x1 mmc_read_partition_tbl: mmc read partition OK! eMMC/TSD partition table have been checked OK! i=0,register --- emmc_key mmc_storage_probe 493 mmc storage node0 addr = 2600000 and node1 addr = 2640000 MMC BOOT, emmc_env_relocate_spec : env_relocate_spec 59 set_storage_device_flag: store 2 [imgread]Secure kernel sz 0x7c4730 Multi dtb tool version: v2 . Multi dtb detected, support 2 dtbs. aml_dt soc: m8b platform: m201 variant: 1G dtb 0 soc: m8b plat: m201 vari: 1G dtb 1 soc: m8b plat: m201 vari: 2G Find match dtb: 0 vpu clk_level in dts: 3 set vpu clk: 182150000Hz, readback: 182150000Hz(0x701) Net: Meson_Ethernet main_loop... cvbs trimming.1.v5: 0xa0, 0x1 preboot... hdmi tx power init TV mode 576cvbs selected. vdac open.1 = 0x1, 0x1 mode is: 4 viu chan = 1 config HPLL config HPLL done reboot_mode=charging ### main_loop entered: bootdelay=1 ### main_loop: bootcmd="run mytvboot; if test ${bootfromnand} = 1; then setenv bootfromnand 0; saveenv; else run bootfromsd; run bootfromusb; run bootfromemmc; fi; run storeboot" Hit Enter key to stop autoboot -- : 0 exit abortboot: 0 (Re)start USB(0)... USB0: dwc_usb driver version: 2.94 6-June-2012 USB (1) peri reg base: c1108820 USB (1) use clock source: XTAL input USB (1) base addr: 0xc90c0000 Force id mode: Host dwc_otg: No USB device found ! lowlevel init failed USB error: all controllers failed lowlevel init ** Invalid boot device ** ** Invalid boot device ** ** Invalid boot device ** ** Invalid boot device ** [mmc_init] SDIO Port B:0, if_type=7, initialized OK! reading s805_autoscript 1991 bytes read ## Executing script at 01000000 reading uInitrd 4373257 bytes read reading uImage 6608764 bytes read reading dtb.img ** Unable to read "dtb.img" from mmc 0:1 ** [imgread]Secure kernel sz 0x7c4730 Multi dtb tool version: v2 . Multi dtb detected, support 2 dtbs. aml_dt soc: m8b platform: m201 variant: 1G dtb 0 soc: m8b plat: m201 vari: 1G dtb 1 soc: m8b plat: m201 vari: 2G Find match dtb: 0 ## Booting kernel from Legacy Image at 14000000 ... Image Name: Linux-3.10.108 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 6608700 Bytes = 6.3 MiB Load Address: 00208000 Entry Point: 00208000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 15000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4373193 Bytes = 4.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 11800000 Booting using the fdt blob at 0x11800000 Uncompressing Kernel Image ... OK uboot time: 12750841 us. EFUSE machid is not set. Using machid 0xf81 from environment From device tree /memory/ node aml_reserved_end property, for relocate ramdisk and fdt, relocate_addr: 0x4435001 Loading Ramdisk to 04009000, end 04434ac9 ... OK Loading Device Tree to 04000000, end 04008845 ... OK Starting kernel ... It stuck at "Starting kernel ..." I've used image from https://projects.milankragujevic.com/amlogic/s805/2018-10-28/ (https://forum.armbian.com/topic/1919-armbian-for-amlogic-s805/page/10/)

I doubt that our last images are broken as this is one of popular devices and this is the only report I can remember. Also we are running test automation, which shows not problems. However, non working images can exists, ... we keep previous versions for you to verify quickly: "Current images doesn't work ..." ... if its something on your side (powering, SD card) or image is broken. Official images are few years old version of Armbian with different boot loader and kernel. Can you attach UART to the serial console and see where it stops?

Okay, but the box is now dead, I need to somehow either enable SD boot again or revert the firmware. Is there a way to do it via UART? As that's the only thing that still works on the box

The power supply has been upgraded to an Argon 40 rated at 5.25V and 3.5A, but still connected by the standard micro USB. I had a A3 SD Card and downgraded to A1. Installation is identical to that originally reported. These USB to serial devices are recognized and have persistence in /dev/tty* and /dev/serial: Bus 001 Device 010: ID 1a86:5523 QinHeng Electronics CH341 in serial mode, usb to serial port converter Bus 001 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Phone Data Cable These devices are recognized and transiently build devices in /dev/tty* which persist for seconds, then disappear: Bus 001 Device 011: ID 1a86:7523 QinHeng Electronics CH340 serial converter Bus 001 Device 014: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC Bus 001 Device 013: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Other than the built in Tinker Board USB devices, I use a Logitech receiver: Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver The devices above were plugged in and subsequently removed one at at a time with Logitech Unifying Receiver also in place. I'm happy to test removing the Braille device. Do I remove a kernel module, or is there an app that can be used to manage assistive technologies?

Description Added DMA support for H616/H618 devices. Added overlays for interfaces available on 26-pin header of orangepi zero2 and zero3. The 26 pin headers can provide upto 3 i2c interfaces, 2 pwm, 2 uarts and 1 spi with 2 chip selects. I have added overlays for the 3 i2c and 2 uart interfaces. I didn't saw the pwm suppport yet in the kernel and hence have skipped the same. For spi, the existing spidev1_0 and spidev1_1 seems to apply fine. As part of this PR, I am also stepping down as the maintainer. As a wip device needs a maintainer, I have moved the device to be csc instead. Any further development for this device should be handled by the community. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested patch applies and both kernel builds fine. [X] Tested all the overlays applies correctly on 6.7 kernel and their corresponding device nodes appear in /dev. I don't have any peripherals to attach and hence detail testing is not performed. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

everything is working. i've plugged an uart to have boot logs. as i want a debian flavor to use it as a lowcost homeassistant, i'll try to create a script to "create" an image from scratch (with just your armbi_boot + any other armbi_root like an official one) did you create a git repo with Image + uInitrd + dtb + armbianEnv.txt + boot.scr ? what modifications did you do to armbi_root ? also, the automatic partition extender seems to corrupt everything after a first reboot

@bahtiyar57 _________________ FTDI232 BPI | _________________ | | 3.3v |_____ ____ UART GND o|---------------|o GND o| | || | | Linux TX o|---------------|o RX o| | USB|| |====USB cable===| console RX o|---------------|o TX o |____||____| | "minicom" _________________| |________5v______| o| 3.3v o| This is the jumper on the device. I use this scheme. Everyone uses this scheme. It's safe.

I bought a Uart cable but Im afraid of plug it to my sbc Is there an other option? Or can you help me to use it without destroying anything?

Hello. For some reason, UART1 does not work for transmission, only for reception. The transmitter pin itself is definitely working, I checked by switching this pin to output mode, and then switching it to a high/low logical level, everything works properly, the level on the Pin changes. How I check the UART itself: I installed picocom, shorted the TX and RX pins, and I’m trying to see what I’m sending. For UART2 this method works as it should, but UART1 only works for reception. I realized this when I opened the TX and RX, and was able to receive incoming data sent through the USB-UART converter.

@Tu Hu @AaronNGray I tested this image on my board: Armbian_23.10_Bananapim3_bookworm_edge_6.4.16_minimal.img Please confirm that the OS is loaded and working properly. If you have problems downloading, please the output in the UART console and post it here.

@Werner sudo screen -LU /dev/ttyUSB0 1500000 is the command used using a diff USB-UART(CH341) and debug pins, im getting output to terminal, the only thing is im noticing not all is printing, and its changing every time i re-run the command. the logfile screenlog.0 shows different output to whats on the screen, unsure if this is due to character encoding, or missing data. Example somtimes it may show missing text such as Boo nux on physi... CPU instead of Booting Linux on physical CPU

1. Not using CP2102 as it cannot handle 1.5mbaud. CP2104 for example does. 2. not using random UART you find on the GPIO but using the actual debug UART connectors: https://wiki.friendlyelec.com/wiki/images/7/7c/NanoPi_NEO3-layout.jpg 3. @lpirl can be right too. I used to own a Neo3 just like yours but it died on me.

I do run a Neo3 for years 24/7 without problems. Please avoid the rage. Of course, you may have a faulty unit. At the same time, if you want to run a relatively bare board, you should be ready to learn how to do it. This looks like a connection issue before even being able to connect to the board. Can you connect to any network using the USB Ethernet adapter? Your home router, for example? Could you maybe also connect the board to your home router using Ethernet? Are you sure your UART chip supports baud 1500000? CP2102 does not, CH340G and FT232RQ do IIRC (please re-check before buying). Best Lukas

@Werner Connected to UART and running sudo dmesg returns [ 5936.103740] usb 1-1: new full-speed USB device number 12 using xhci_hcd [ 5936.283946] usb 1-1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 5936.283951] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 5936.283954] usb 1-1: Product: CP2102 USB to UART Bridge Controller [ 5936.283956] usb 1-1: Manufacturer: Silicon Labs [ 5936.283958] usb 1-1: SerialNumber: 0001 [ 5936.293074] cp210x 1-1:1.0: cp210x converter detected [ 5936.296064] usb 1-1: cp210x converter now attached to ttyUSB0 connecting usb to uart cables to pin 6 for GND, 8 for TX, 10 for RX - https://wiki.friendlyelec.com/wiki/index.php/NanoPi_NEO3 now running sudo screen /dev/ttyUSB0 115200 Also tried with baud rate 1500000 no output in screen, just a flashing cursor also tried powering down the SBC, reconnecting, etc. the img im using is https://www.armbian.com/nanopineo3/ - Armbian Bookworm - Armbian_community_24.2.0-trunk.449_Nanopineo3_bookworm_current_6.6.13 What do you recommend? These friendlyElec boards are a great stress, I never had this much problems with other boards such as raspberry Pi. 3 days wasted trying to connect... not a single bit of progress made, numerous distros copied to sd card, nothing works.

@pixdrift rather than to say that 'enable all' isn't well received, i think we (at least myself) may be misguided, as I've not explored a lot of things, especially access to the io header pins. there are also a lot of things that we'd need @pixdrift, @Gunjan Gupta, @Stephen Graf and others who happened to use those functionality (e.g. the header pins / spi / gpio etc) to share if after all enabling them actually lead to conflicts? and if after all pinmux 'works the way as expected', e.g. my notion that pin mux selects the function is *pure speculation*, e.g. that after all we can simply 'enable everything' and just use pin mux to choose between them. e.g. pin mux determines if gpio or alternate function ( spi / uart/ i2c / pwm etc is seen at the pin. There are also *unproven* things that I simply speculate if simply 'okay' the device in DTS actually cause a higher power consumption / higher temperature, there is no actual report / comment to indicate that it really works that way ! i'm simply being *lazy* to comment that maybe leaving it 'disabled' is just 'safe', that may not even be true.

Hello everyone. Please help me with the following problem. I have a Rock Pi 4b 1.4 (with SPI flash). I did the boot from the NVMe SSD using the image rkspi_loader-v20.11.2-trunk-v2.img according to the instructions. I installed Armbian 23.11 Jammy XFCE on NVMe SSD KingSpec NX 1TB. I’m using a power supply Baseus 65W GaN Pro (with PD). The system loads and works well. However, the system cannot reboot. When i click on reboot, the system starts to reboot and after the reset goes into a cyclic reboot. I need to turn off the power to reboot. What could be the problem and how to solve it? UART (Serial console) log: " " $&0 f@`B@@NF0f@`B@@NF 0f@`B@@NF@@@LN`b`N" " 0 "$`@@NN`0@b`@``@LFbpb`@H U-Boot TPL 2020.07-armbian (Dec 04 2020 - 22:10:39) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB 256B stride 256B stride lpddr4_set_rate: change freq to 400000000 mhz 0, 1 lpddr4_set_rate: change freq to 800000000 mhz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.07-armbian (Dec 04 2020 - 22:10:39 +0100) Trying to boot from SPI NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: If lpddr4 need support multi frequency, INFO: please update loader! INFO: Current ctl index[0] freq=400MHz INFO: Current ctl index[1] freq=800MHz INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Dec 04 2020 - 22:10:39 +0100) SoC: Rockchip rk3399 Reset cause: RST Model: Radxa ROCK Pi 4B DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from SPI Flash... SF: Detected XT25F32B with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Model: Radxa ROCK Pi 4B Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! Card did not respond to voltage select! "Synchronous Abort" handler, esr 0x96000210 elr: 000000000022d918 lr : 000000000022d8b4 (reloc) elr: 00000000f3f5a918 lr : 00000000f3f5a8b4 x0 : 00000000f8000000 x1 : 0000000000000001 x2 : 0000000000000000 x3 : 0000000000100000 x4 : 00000000f1f36b30 x5 : 0000000000100000 x6 : 0000000000000001 x7 : 00000000f3fcd888 x8 : 0000000000000000 x9 : 0000000000000008 x10: 00000000ffffffe8 x11: 0000000000000010 x12: 000000000000149c x13: 00000000f1f149fc x14: 00000000f1f15b20 x15: 0000000000000020 x16: 00000000f3f5a878 x17: 0000000000060001 x18: 00000000f1f26dc0 x19: 00000000f1f14970 x20: 0000000000000001 x21: 0000000000000000 x22: 0000000000010000 x23: 00000000f3fd37f8 x24: 0000000000010000 x25: 00000000f3fba3f2 x26: 0000000000000000 x27: 0000000000000000 x28: 00000000f1f36a40 x29: 00000000f1f148d0 Code: 540000c1 350000a5 93407c05 f9400080 (b86068a0) Resetting CPU ... resetting ... U-Boot TPL 2020.07-armbian (Dec 04 2020 - 22:10:39) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB 256B stride 256B stride lpddr4_set_rate: change freq to 400000000 mhz 0, 1 lpddr4_set_rate: change freq to 800000000 mhz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.07-armbian (Dec 04 2020 - 22:10:39 +0100) Trying to boot from SPI NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: If lpddr4 need support multi frequency, INFO: please update loader! INFO: Current ctl index[0] freq=400MHz INFO: Current ctl index[1] freq=800MHz INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Dec 04 2020 - 22:10:39 +0100) SoC: Rockchip rk3399 Reset cause: RST Model: Radxa ROCK Pi 4B DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from SPI Flash... SF: Detected XT25F32B with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Model: Radxa ROCK Pi 4B Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! Card did not respond to voltage select! "Synchronous Abort" handler, esr 0x96000210 elr: 000000000022d918 lr : 000000000022d8b4 (reloc) elr: 00000000f3f5a918 lr : 00000000f3f5a8b4 x0 : 00000000f8000000 x1 : 0000000000000001 x2 : 0000000000000000 x3 : 0000000000100000 x4 : 00000000f1f36b30 x5 : 0000000000100000 x6 : 0000000000000001 x7 : 00000000f3fcd888 x8 : 0000000000000000 x9 : 0000000000000008 x10: 00000000ffffffe8 x11: 0000000000000010 x12: 000000000000149c x13: 00000000f1f149fc x14: 00000000f1f15b20 x15: 0000000000000020 x16: 00000000f3f5a878 x17: 0000000000060001 x18: 00000000f1f26dc0 x19: 00000000f1f14970 x20: 0000000000000001 x21: 0000000000000000 x22: 0000000000010000 x23: 00000000f3fd37f8 x24: 0000000000010000 x25: 00000000f3fba3f2 x26: 0000000000000000 x27: 0000000000000000 x28: 00000000f1f36a40 x29: 00000000f1f148d0 Code: 540000c1 350000a5 93407c05 f9400080 (b86068a0) Resetting CPU ... resetting ... U-Boot TPL 2020.07-armbian (Dec 04 2020 - 22:10:39) Channel 0: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB Channel 1: LPDDR4, 50MHz BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB 256B stride 256B stride lpddr4_set_rate: change freq to 400000000 mhz 0, 1 lpddr4_set_rate: change freq to 800000000 mhz 1, 0 Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.07-armbian (Dec 04 2020 - 22:10:39 +0100) Trying to boot from SPI NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: If lpddr4 need support multi frequency, INFO: please update loader! INFO: Current ctl index[0] freq=400MHz INFO: Current ctl index[1] freq=800MHz INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2020.07-armbian (Dec 04 2020 - 22:10:39 +0100) SoC: Rockchip rk3399 Reset cause: RST Model: Radxa ROCK Pi 4B DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from SPI Flash... SF: Detected XT25F32B with page size 256 Bytes, erase size 4 KiB, total 4 MiB *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Model: Radxa ROCK Pi 4B Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! Card did not respond to voltage select! "Synchronous Abort" handler, esr 0x96000210 elr: 000000000022d918 lr : 000000000022d8b4 (reloc) elr: 00000000f3f5a918 lr : 00000000f3f5a8b4 x0 : 00000000f8000000 x1 : 0000000000000001 x2 : 0000000000000000 x3 : 0000000000100000 x4 : 00000000f1f36b30 x5 : 0000000000100000 x6 : 0000000000000001 x7 : 00000000f3fcd888 x8 : 0000000000000000 x9 : 0000000000000008 x10: 00000000ffffffe8 x11: 0000000000000010 x12: 000000000000149c x13: 00000000f1f149fc x14: 00000000f1f15b20 x15: 0000000000000020 x16: 00000000f3f5a878 x17: 0000000000060001 x18: 00000000f1f26dc0 x19: 00000000f1f14970 x20: 0000000000000001 x21: 0000000000000000 x22: 0000000000010000 x23: 00000000f3fd37f8 x24: 0000000000010000 x25: 00000000f3fba3f2 x26: 0000000000000000 x27: 0000000000000000 x28: 00000000f1f36a40 x29: 00000000f1f148d0 Code: 540000c1 350000a5 93407c05 f9400080 (b86068a0) Resetting CPU ... resetting ...

from the photos it seem you didn't connect GND uart pin

I checked my image. In the minicom console (BPI-M3 -UART -> FTD232 -> USB - Host Linux), in the SSH session, and on the monitor screen connected via HDMI, I see the same greeting pictures: ____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ Welcome to Armbian 23.10 Bookworm with Linux 6.4.10 No end-user support: built from trunk & unsupported (bookworm) userspace! System load: 1% Up time: 4 min Memory usage: 6% of 1.96G IP: 192.168.100.101 CPU temp: 46�°C Usage of /: 6% of 15G leo@bananapim3:~$ dmesg | grep -i hdmi [ 0.000000] Kernel command line: root=UUID=41970142-87ec-4b91-8231-1b55ee68d69f rootwait rootfstype=ext4 splash=verbose console=ttyS0,115200 console=1 [ 0.084376] platform 1ee0000.hdmi: Fixed dependency cycle(s) with /soc/lcd-controller@1c0d000/ports/port@1/endpoint@1 [ 0.086788] platform connector: Fixed dependency cycle(s) with /soc/hdmi@1ee0000/ports/port@1/endpoint [ 2.327031] sun8i-dw-hdmi 1ee0000.hdmi: supply hvcc not found, using dummy regulator [ 2.327713] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy) [ 2.328344] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin [ 2.328730] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.329389] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xc0baecbc) [ 2.330594] sun8i-dw-hdmi 1ee0000.hdmi: read_hpd result: 1 [ 43.228319] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin [ 44.121951] sun8i-dw-hdmi 1ee0000.hdmi: EVENT=plugin Observation: My monitor is very smart. He thinks he has correctly identified the entrance from the three possible ones. But he was wrong. I had to press the button with my hand to switch the mode and see the command prompt for entering the password.

@goingyes, i used HDMI. Sorry, i don't know, how can i get uart output🥺. via UART-->TTL and special programm? during the booting, i saw, error at console-setup.service

On my board: After the reboot: All these output texts are received in the minicom console and a physical connection to the board via a USB-UART adapter. SSH connection: > ssh leo@192.168.100.101 leo@192.168.100.101's password: ____ ____ _ __ __ _____ | __ )| _ \(_) | \/ |___ / | _ \| |_) | | | |\/| | |_ \ | |_) | __/| | | | | |___) | |____/|_| |_| |_| |_|____/ Welcome to Armbian 23.10 Bookworm with Linux 6.4.10 No end-user support: built from trunk & unsupported (bookworm) userspace! System load: 1% Up time: 8 min Memory usage: 5% of 1.96G IP: 192.168.100.101 CPU temp: 43°C Usage of /: 6% of 15G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] Last login: Sat Jan 27 12:07:12 2024 leo@bananapim3:~$ sudo apt update [sudo] пароль для leo: Пол:1 http://security.debian.org bookworm-security InRelease [48,0 kB] Пол:2 http://deb.debian.org/debian bookworm InRelease [151 kB] ...... I have not tested HDMI and other connected devices. I communicate with the device only via UART or SSH. You will have to install the graphical environment yourself.

Can you share the uart output? That will tell the reason why it keeps on rebooting.