Search the Community

Uart port works fine in the latest image `Armbian_community_24.5.0-trunk.93_Orangepi3b_jammy_legacy_5.10.160_gnome_desktop.img.xz`

Nope, they are not useful. To identify the issue I need the serial logs from the board UART when you boot multitool to understand the reason why it does not proceed. Did you try to burn a second multitool on a USB stick, plug both the sdcard with multitool and USB stick with multitool and see if it boots?

Thanks for the tips Nick. I'll look at the Miniarch. Soooo many slightly different boards. Ahh, maybe I was hung up on the 1.5M baud uart - I've been playing with several Rockchip boards recently that need 1.5M. My goto serial is tio on Linux.

Hi all, I have an Armbian installed on Orange PI 4B. I am trying to connect a flight controller to Orange PI 4B by using UART port. This board has a 40 pin header. I went to armbian-config, and enabled the UART1 and UART 4 which are available from armbian-config. I plug the UART port (to Pin 8 and pin 10) on the 40 pin header. Is that port UART 4? I am not sure. It does not work. I tried the debug port, but the Orange PI does not start up if something is plugged in to the debug UART port. The PIN layout https://wiki.adopisoft.com/doku.php?id=4.0.0:gpio_numbering The layout of the board is similiar to Orange PI One. I know the 5 V location by using the case fan. Thanks,

@nitrolackI soldered the UART pins onto the board. I thought I saw the holes in your board too.

@heiko910 ty also for posting pictures, so it's easier to clarify stuff. What seems interesting by your board is, that you have uart connectors. Could not determine them on my board yet. I was also thinking about saving the firmware of it first before doing anything. Read that you could do it directly from armbian.

@audio kees the eMMC when the board is turned on is 400 KHz (no typo), then when it gets initialized (immediately, in practice) runs at 50 MHz. The best thing you can do right now is find the TX/RX pins of the debug uart, attach an USB to TTL serial adapter and see what the board is saying during boot and understand why the board is bricked posting here the logs. Bitrate is 115000bps. About 1T or 2T, it is the DDR Command Rate parameter. If you don't change that, current images have it set to 2T which is more compatible, but some board still don't like it and want 1T. That's exactly the reason I strongly suggest (in the first page tutorials) to first try and boot armbian from sdcard before installing it in eMCP/eMMC.

Hi all, I need to enable rts/cts on my OrangePi Zero with Armbian buster with Linux 5.4.26-sunxi installed. I added the "param_uart2_rtscts=1" (I'm using /dev/ttyS2) to the /boot/armbianEnv.txt file On mi code I use this initialization of the port. xxxxx.c_cflag |= port_parity | port_bits | port_stop | CLOCAL | CRTSCTS | CREAD; Not only rts/cts but also the tx and rx pin aren't working now. Has anyone managed to enable the port on this board? Am I doing something wrong?

@audio kees I definetly agree with @RaptorSDS on the right side you have pins for a nand that isn't soldered .you can spot ecmp clock even there. usually pin 6 or 7 starting from the dot, but check with oscilloscope or try to boot pressing the little switch just at the end of eraphones hole at while still pressing it plug power. also try to find uart

Good day to you))) I have a TV BOX TX9Pro. Chassis (Main Board): H616/H313mini84 V2.0 kernel 4.9.170 I would like to run one of the armbian builds on it. But I can’t figure out how to do this, here are the logs when starting the console... Is there support for this device? tell me what to do and how... Thanks in advance. U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) DRAM:This DRAM setup is currently not supported. resetting ... [70]HELLO! BOOT0 is starting! [73]BOOT0 commit : 803d783 [75]set pll start [78]periph0 has been enabled [81]set pll end [83]unknow PMU [84]unknow PMU [86]PMU: AXP1530 [88]dram return write ok [90]board init ok [92]DRAM BOOT DRIVE INFO: V0.645 [96]the chip id is 0x5d00 [98]chip id check OK [103]DRAM_VCC set to 1500 mv [106]DRAM CLK =600 MHZ [108]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [116]Actual DRAM SIZE =1024 M [118]DRAM SIZE =1024 MBytes, para1 = 30eb, para2 = 4000000, dram_tpr13 = 6041 [132]DRAM simple test OK. [134]rtc standby flag is 0x0, super standby flag is 0x0 [140]dram size =1024 [143]card no is 2 [145]sdcard 2 line count 8 [147][mmc]: mmc driver ver 2020-09-10 15:32 [157][mmc]: Wrong media type 0x0, but host sdc2, try mmc first [163][mmc]: ***Try MMC card 2*** [202][mmc]: RMCA OK! [204][mmc]: bias 4 [207][mmc]: MMC 5.0 [209][mmc]: HSSDR52/SDR25 8 bit [212][mmc]: 50000000 Hz [214][mmc]: 7456 MB [216][mmc]: ***SD/MMC 2 init OK!!!*** [291]Loading boot-pkg Succeed(index=0). [294]Entry_name = u-boot [304]Entry_name = monitor [307]Entry_name = dtbo [310]Entry_name = dtb [314]tunning data addr:0x4a0003e8 [317]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):a0d3abd NOTICE: BL3-1: Built : 17:32:02, 2020-10-20 NOTICE: BL3-1 commit: 8 ERROR: Error initializing runtime service tspd_fast NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 U-Boot 2018.05 (Feb 15 2023 - 17:22:04 +0800) Allwinner Technology [00.391]CPU: Allwinner Family [00.394]Model: sun50iw9 I2C: ready [00.398]DRAM: 1 GiB [00.401]Relocation Offset is: 35ebf000 [00.442]secure enable bit: 0 [00.444]pmu_axp152_probe pmic_bus_read fail [00.448]PMU: AXP1530 [00.454]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz [00.462]drv_disp_init [00.492]__clk_enable: clk is null. [00.497]drv_disp_init finish [00.500]gic: sec monitor mode [00.522]flash init start [00.524]workmode = 0,storage type = 2 [00.528]MMC: 2 [00.529][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00 [00.535][mmc]: get sdc_type fail and use default host:tm4. [00.546][mmc]: SUNXI SDMMC Controller Version:0x40502 [00.590][mmc]: Best spd md: 4-HS400, freq: 3-100000000, Bus width: 8 [00.596]sunxi flash init ok [00.600]Loading Environment from SUNXI_FLASH... OK [00.609]usb burn from boot delay time 0 weak:otg_phy_config [00.623]usb prepare ok [01.426]overtime [01.430]do_burn_from_boot usb : no usb exist [01.434]boot_gui_init:start FAT: Misaligned buffer address (7be7be58) 32 bytes read in 4 ms (7.8 KiB/s) tcon_de_attach:de=0,tcon=2[01.567]boot_gui_init:finish [01.570]bmp_name=bootlogo.bmp 2764854 bytes read in 40 ms (65.9 MiB/s) [01.633]update dts ** Unrecognized filesystem type ** [01.642]load file(ULI/factory/rootwait init.txt) error. ** Unrecognized filesystem type ** [01.655]load file(ULI/factory/snum.txt) error. [01.659]name in map mac ** Unrecognized filesystem type ** [01.668]load file(ULI/factory/wifi_mac.txt) error. ** Unrecognized filesystem type ** [01.680]load file(ULI/factory/bt_mac.txt) error. ** Unrecognized filesystem type ** [01.692]load file(ULI/factory/selinux.txt) error. ** Unrecognized filesystem type ** [01.704]load file(ULI/factory/specialstr.txt) error. [01.713]update part info [01.738]update bootcmd [01.740]No ethernet found. Hit any key to stop autoboot: 0 [02.050]Starting kernel ... [02.053][mmc]: mmc exit start [02.101][mmc]: mmc 2 exit ok [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.170 (akrd6@R740XD) (gcc version 5.3.1 20160412(Linaro GCC 5.3-2016.05) ) #80 SMP PREEMPT Wed Feb 15 17:22:30 CST 2023 [ 0.000000] Boot CPU: AArch64 Processor [410fd034] [ 0.000000] bootconsole [earlycon0] enabled [ 0.027874] BOOTEVENT: 27.858249: ON [ 0.242175] sunxi_i2c_probe()2209 - [i2c3] warning: failed to get regulator d [ 0.243164] sunxi_i2c_probe()2209 - [i2c5] warning: failed to get regulator d [ 0.244517] axp2101-regulator axp2101-regulator.0: Setting DCDC frequency fo unsupported AXP variant [ 0.244601] axp2101-regulator axp2101-regulator.0: Error setting dcdc frequecy: -22 [ 0.279245] [ac200] get ave_regulator_name failed! [ 0.279751] [ac200] pwm enable [ 0.363211] gpio_pin_4(229) gpio_request fail [ ▒[ 0.369727] uart uart1: get regulator failed [ 0.402346] [NAND][NE] Not found valid nand node on dts [ 0.411005] sunxi-wlan soc@03000000:wlan: get gpio chip_en failed [ 0.417894] sunxi-wlan soc@03000000:wlan: get gpio power_en failed [ 0.550010] hci: request ohci1-controller gpio:232 [ 0.742282] axp2101_pek: axp2101-pek can not register without irq [ 0.752785] sunxi_ir_startup: get ir protocol failed [ 0.761135] VE: get debugfs_mpp_root is NULL, please check mpp [ 0.761135] [ 0.769395] VE: sunxi ve debug register driver failed! [ 0.769395] [ 0.784659] mmc:failed to get gpios [ 0.865627] mmc:failed to get gpios [ 0.901895] FD655: ==fd655_driver_probe==================== [ 0.908284] FD655: : (null) [ 0.909038] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 0.912260] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 0.926757] FD655: : (null) [ 0.929915] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.935814] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.941713] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.947606] sunxi-mmc sdc1: smc 2 p1 err, cmd 5, RTO !! [ 0.953859] FD655: register_fd655_driver: Successed to add fd655 module [ 0.973520] failed get gpio-spdif gpio from dts,spdif_gpio:-2 [ 0.983217] [audio-codec]dachpf_cfg configurations missing or invalid. [ 0.990865] lineout_vol:26, linein_gain:3, fmin_gain:3, digital_vol:0, adcdr_cfg:0, adchpf_cfg:0, dacdrc_cfg:0, dachpf_cfg:0, ramp_func_used:1, pa_msleep_tme:160, pa_ctl_level:0, gpio-spk:0 [ 1.014903] sndhdmi sndhdmi: ASoC: CPU DAI (null) not registered [ 1.021698] sndhdmi sndhdmi: snd_soc_register_card() failed: -517 [ 1.035293] sunxi-ahub-cpudai 5097000.cpudai3-controller: ahub cpudai id invlid [ 1.068733] ERROR: pinctrl_get for HDMI2.0 DDC fail [ 1.078344] tv_probe()1435 - of_property_read_string tv_power failed! [ 1.174637] cpu cpu1: opp_list_debug_create_link: Failed to create link [ 1.182156] cpu cpu1: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.189771] cpu cpu2: opp_list_debug_create_link: Failed to create link [ 1.197234] cpu cpu2: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.204828] cpu cpu3: opp_list_debug_create_link: Failed to create link [ 1.212279] cpu cpu3: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.684491] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 context=u:object_r:default_prop:s0 tclass=property_service permissive=1 [ 1.684491] [ 1.702686] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 context=u:object_r:dalvik_prop:s0 tclass=property_service permissive=1 [ 1.702686] [ 2.576915] FAT-fs (mmcblk0p15): bogus number of reserved sectors console:/ $ [ 8.720978] apexd: Failed to walk /product/apex : Can't open /prduct/apex for reading : No such file or directory ^C 130|console:/ $ [ 22.711942] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RTO !! [ 22.913822] SSV6XXX_SDIO mmc2:0001:1: vendor = 0x3030 device = 0x3030 [ 22.947618] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 22.958352] sunxi-mmc sdc1: smc 2 p1 err, cmd 52, RE RCE !! [ 23.030814] SSV6XXX_SDIO mmc2:0001:1: dataIOPort 0x10000 regIOPort 0x10020 [ 23.057388] SSV6XXX HCI TX Task started. [ 23.135876] Enable HCI TX aggregation [ 24.042450] SSV WLAN driver SSV6006C: Set new macaddr [ 24.060821] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e4 of type 2 is added. [ 25.361805] SSV WLAN driver SSV6006C: Set new macaddr [ 25.386662] SSV WLAN driver SSV6006C: VIF 08:1a:1e:fd:85:e5 of type 2 is added. [ 27.173711] selinux: avc: denied { set } for property=sys.config.rootservice pid=2978 uid=0 gid=0 scontext=u:r:rootservice:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=1 [ 27.173711] [ 27.207603] audit: rate limit exceeded [ 30.214797] apexd: Can't open /product/apex for reading : No such file or directory U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) /system/bin/sh: syntax error: unexpected '(' 1|console:/ $ DRAM:This DRAM setup is currently not supported. /system/bin/sh: DRAM:This: inaccessible or not found 127|console:/ $ [ 34.750480] selinux: avc: denied { set } for property=supolicy.loaded pid=3902 uid=0 gid=0 scontext=u:r:toolbox:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=1 [ 34.750480] U-Boot SPL 2021.04 (May 25 2023 - 13:03:46 +0200) /system/bin/sh: syntax error: unexpected '(' 1|console:/ $ DRAM:This DRAM setup is currently not supported. /system/bin/sh: DRAM:This: inaccessible or not found 127|console:/ $

Hi Gents, I would like to ask for your help or tips and tricks in the following problem... Basically to keep the long story short, I have a custom board with RK3566 and 2 GB of RAM, 32 GB Samsung emmc on it ... basically if you are familliar it is a Linxdot Helium miner which has some problems with the onboard Lora module. I had tried to flash using RKDevTool a few Debian version that I found for Rk3566 but not all of them worked properly. All the time I was able to reflash it by using RKDevTool by pressing the button while I powered up the board but after flashing the Armbian minnimal for Orange Pi3B I can't use the RKDevTool anymore, it is simply not seeing the board anymore (No device found). I have an UART 3.5mm Jack type port, I had a homemade cable so I was able to create the user at the first boot, I am able to log in, but there is no HDMI, the ethernet port is no recognized, WiFi also not recognized, I am plug in a USB Flash stick and I am not seeing it in the lsblk command output, so basically I have now a very basic board. (I know, I am stupid, but I was thinking that I can't damage it because the RKDevTool was working fine under all previous circumstances). My question would be, if there is any possibility somehow to restore the functionality to be able to boot it in MaskMode for the RKDevTool or any other solution to make at least the Ethernet and USB ports to work? There are no other button, just 2, one reset and one user button on it. All the time I had to keep pressed the user button in order to be detected by the RK tool. There are no jumpers on the board (at least I can't find them) which I can short to stop the emmc from booting or similar things Many thanks in advance ! The booting process: ▒▒▒DDR V1.18 f366f69a7d typ 23/07/17-15:48:58 ln LP4/4x derate en, other dram:1x trefi ddrconfig:15 DDR4, 324MHz BW=32 Col=10 Bk=4 BG=2 CS0 Row=16 CS=1 Die BW=16 Size=2048MB tdqss: cs0 dqs0: 192ps, dqs1: 144ps, dqs2: 96ps, dqs3: 96ps, change to: 324MHz clk skew:0x8d change to: 528MHz clk skew:0x8d change to: 780MHz clk skew:0x8d change to: 1056MHz(final freq) clk skew:0x8d PHY drv:clk:37,ca:37,DQ:37,odt:139 vrefinner:50%, vrefout:61% dram drv:34,odt:120 cs 0: the read training result: DQS0:0x3c, DQS1:0x39, DQS2:0x36, DQS3:0x3b, min : 0x7 0xa 0xb 0x8 0x2 0x4 0x4 0x2 , 0x3 0x7 0x1 0x4 0x4 0x6 0x8 0x2 , 0x5 0x6 0x3 0x6 0x2 0x1 0x2 0x4 , 0x8 0x6 0x6 0x0 0x5 0x8 0x9 0x6 , mid :0x24 0x27 0x28 0x25 0x1f 0x21 0x21 0x1f ,0x21 0x23 0x1e 0x22 0x22 0x23 0x24 0x1f , 0x21 0x23 0x20 0x22 0x1f 0x1d 0x1f 0x21 ,0x26 0x23 0x23 0x1d 0x22 0x26 0x26 0x23 , max :0x42 0x45 0x46 0x43 0x3c 0x3e 0x3f 0x3c ,0x3f 0x40 0x3b 0x40 0x40 0x40 0x41 0x3d , 0x3e 0x40 0x3e 0x3f 0x3c 0x3a 0x3d 0x3e ,0x44 0x40 0x41 0x3a 0x40 0x44 0x44 0x41 , range:0x3b 0x3b 0x3b 0x3b 0x3a 0x3a 0x3b 0x3a ,0x3c 0x39 0x3a 0x3c 0x3c 0x3a 0x39 0x3b , 0x39 0x3a 0x3b 0x39 0x3a 0x39 0x3b 0x3a ,0x3c 0x3a 0x3b 0x3a 0x3b 0x3c 0x3b 0x3b , the write training result: DQS0:0xa6, DQS1:0xa0, DQS2:0x99, DQS3:0x99, min :0x8c 0x92 0x90 0x8f 0x88 0x89 0x8a 0x89 0x8f ,0x85 0x89 0x84 0x89 0x89 0x8b 0x8b 0x85 0x85 , 0x84 0x85 0x84 0x85 0x83 0x81 0x83 0x85 0x82 ,0x7f 0x7d 0x7c 0x7a 0x81 0x81 0x82 0x7e 0x7e , mid :0xa8 0xab 0xab 0xa9 0xa1 0xa4 0xa3 0xa2 0xa9 ,0x9f 0xa2 0x9e 0xa3 0xa2 0xa3 0xa4 0x9f 0x9f , 0x9e 0x9e 0x9f 0xa0 0x9c 0x9b 0x9a 0x9c 0x9d ,0x9b 0x97 0x97 0x95 0x9a 0x9c 0x9c 0x9a 0x99 , max :0xc5 0xc5 0xc7 0xc3 0xbb 0xc0 0xbc 0xbb 0xc4 ,0xba 0xbb 0xb8 0xbd 0xbb 0xbc 0xbe 0xba 0xb9 , 0xb9 0xb8 0xba 0xbb 0xb6 0xb5 0xb2 0xb4 0xb8 ,0xb7 0xb2 0xb3 0xb0 0xb3 0xb7 0xb6 0xb6 0xb5 , range:0x39 0x33 0x37 0x34 0x33 0x37 0x32 0x32 0x35 ,0x35 0x32 0x34 0x34 0x32 0x31 0x33 0x35 0x34 , 0x35 0x33 0x36 0x36 0x33 0x34 0x2f 0x2f 0x36 ,0x38 0x35 0x37 0x36 0x32 0x36 0x34 0x38 0x37 , out U-Boot SPL 2023.10-rc4-armbian (Feb 10 2024 - 01:24:45 +0000) Trying to boot from MMC1 ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK ## Checking hash(es) for Image atf-4 ... sha256+ OK ## Checking hash(es) for Image atf-5 ... sha256+ OK ## Checking hash(es) for Image atf-6 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-607-gbf602aff1:cl NOTICE: BL31: Built : 10:16:03, Jun 5 2023 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: pmu v1 is valid 220114 INFO: dfs DDR fsp_param[0].freq_mhz= 1056MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 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 = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2023.10-rc4-armbian (Feb 10 2024 - 01:24:45 +0000) Model: Rockchip RK3566 OPi 3B DRAM: 2 GiB PMIC: RK8090 (on=0x40, off=0x00) Core: 338 devices, 32 uclasses, devicetree: separate MMC: mmc@fe2b0000: 1, mmc@fe2c0000: 2, mmc@fe310000: 0 Loading Environment from nowhere... OK In: serial@fe660000 Out: serial@fe660000 Err: serial@fe660000 Model: Rockchip RK3566 OPi 3B Net: eth0: ethernet@fe010000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 ** Booting bootflow 'mmc@fe310000.bootdev.part_1' with script Boot script loaded from mmc 0:1 204 bytes read in 12 ms (16.6 KiB/s) 8023386 bytes read in 204 ms (37.5 MiB/s) 35062272 bytes read in 767 ms (43.6 MiB/s) 166117 bytes read in 54 ms (2.9 MiB/s) Working FDT set to a100000 Failed to load '/boot/dtb/rockchip/overlay/rk35xx-fixup.scr' Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=4420000 ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8023322 Bytes = 7.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0a100000 Booting using the fdt blob at 0xa100000 Working FDT set to a100000 Loading Ramdisk to 7c71d000, end 7cec3d1a ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000007c68c000, end 000000007c71cfff ... OK Working FDT set to 7c68c000 Starting kernel ... Armbian_community 24.5.0-trunk.6 Bookworm ttyFIQ0 orangepi3b login:

Hi, all I have tested all the bookworm images and they all have the same error. HDMI debugging not working... This is the log uart Armbian_23.5.1_Nanopik2-s905_bookworm_current_6.1.30 Regards npik2-armbian

Hey @Nick A, I tried your newest Image. Things have changed a bit but It is still not booting all the way into the desktop but with my UART we are getting somewhere now. Here is the output! BTW I have ethernet connected when this happens U-Boot SPL 2024.01-armbian (Feb 08 2024 - 23:32:11 -0500) DRAM: 4096 MiB Trying to boot from MMC2 H616: init mmc 2 clock(8000000) and io NOTICE: BL31: v2.10.0 (debug):armbian NOTICE: BL31: Built : 23:30:40, Feb 8 2024 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a09c188, model: Transpeed 8K618-T INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.01-armbian (Feb 08 2024 - 23:32:11 -0500) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: Transpeed 8K618-T DRAM: 4 GiB Core: 58 devices, 21 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: H616: init mmc 2 clock(8000000) and io mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... Bus usb@5101000: sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 Bus usb@5101400: USB OHCI 1.0 Bus usb@5200000: USB EHCI 1.00 Bus usb@5200400: USB OHCI 1.0 scanning bus usb@5101000 for devices... 1 USB Device(s) found scanning bus usb@5101400 for devices... 2 USB Device(s) found scanning bus usb@5200000 for devices... 1 USB Device(s) found scanning bus usb@5200400 for devices... 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr ** fs_devread read error - block Failed to load '/boot/boot.scr' ## Executing script at 4fc00000 Bad data crc SCRIPT FAILED: continuing... MMC: no card present No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image MMC: no card present Device 0: unknown device No ethernet found. missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/00000000 No ethernet found. Retrieving file: pxelinux.cfg/0000000 No ethernet found. Retrieving file: pxelinux.cfg/000000 No ethernet found. Retrieving file: pxelinux.cfg/00000 No ethernet found. Retrieving file: pxelinux.cfg/0000 No ethernet found. Retrieving file: pxelinux.cfg/000 No ethernet found. Retrieving file: pxelinux.cfg/00 No ethernet found. Retrieving file: pxelinux.cfg/0 No ethernet found. Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi No ethernet found. Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. Retrieving file: pxelinux.cfg/default-arm No ethernet found. Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. No ethernet found. Thanks @Nick A

Hi, I broke my /boot on eMMC and my Beelink GT1 is in boot loop. I can't configure u-boot to boot from the SD card to reinstall it. Can you help me reconfigure u-boot to boot from the SD card? Thx printenv bootargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.mem_address=0x20000000 ramoops.mem_size=0x100000 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive logo=osd1,loaded,0x3f800000,576cvbs hdmimode=720p60hz cvbsmode=576cvbs hdmitx= androidboot.firstboot=0 mac=86:48:d8:49:99:56 androidboot.mac=86:48:d8:49:99:56 bootcmd=run start_autoscript; run storeboot bootdelay=1 bootmode_check=get_rebootmode; echo reboot_mode=${reboot_mode};if test ${reboot_mode} = factory_reset; then defenv_reserv aml_dt;setenv upgrade_step 2; save;fi; bootup_offset=0x10ac270 bootup_size=0x5eec36 cmdline_keys=if keyman init 0x1234; then if keyman read usid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac} androidboot.mac=${mac};fi;if keyman read deviceid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.deviceid=${deviceid};fi;fi; cvbsmode=576cvbs display_bpp=24 display_color_bg=0 display_color_fg=0xffff display_color_index=24 display_height=576 display_layer=osd1 display_width=720 dtb_mem_addr=0x1000000 edid.crcvalue=0x9f290000 ethact=Meson_Ethernet ethaddr=00:15:18:01:81:31 factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; fb_addr=0x3f800000 fb_height=1080 fb_width=1920 fdt_high=0x20000000 filesize=320 firstboot=0 gatewayip=10.18.9.1 hdmimode=720p60hz hostname=arm_gxbb identifyWaitTime=750 init_display=hdmitx hpd;osd open;osd clear;vout output ${outputmode};imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale initargs=rootfstype=ramfs init=/init console=ttyS0,115200 no_console_suspend earlyprintk=aml-uart,0xc81004c0 ramoops.mem_address=0x20000000 ramoops.mem_size=0x100000 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive ipaddr=10.18.9.97 irremote_update=if irkey 0xe31cfb04 0xb748fb04 2500000; then echo read irkey ok!; if itest ${irkey_value} == 0xe31cfb04; then run update;else if itest ${irkey_value} == 0xb748fb04; then run update;\ fi;fi;fi; loadaddr=1080000 mac=86:48:d8:49:99:56 netmask=255.255.255.0 outputmode=576cvbs preboot=run factory_reset_poweroff_protect;run upgrade_check;run bootmode_check;run init_display;run storeargs;run upgrade_key;run switch_bootmode; reboot_mode=cold_boot recovery_from_flash=if imgread kernel recovery ${loadaddr}; then wipeisb; bootm ${loadaddr}; fi recovery_from_sdcard=if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload mmc 0 ${loadaddr} recovery.img; then if fatload mmc 0 ${dtb_mem_addr} dtb.img; then echo sd dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi; recovery_from_udisk=if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; bootm ${loadaddr};fi; saradc_val=0x1 sdc_burning=sdc_burn ${sdcburncfg} sdcburncfg=aml_sdc_burn.ini serverip=10.18.9.113 start_autoscript=if mmcinfo; then run start_mmc_autoscript; fi; if usb start; then run start_usb_autoscript; fi; run start_emmc_autoscript start_emmc_autoscript=if fatload mmc 1 1020000 emmc_autoscript; then autoscr 1020000; fi; start_mmc_autoscript=if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi; start_usb_autoscript=for usbdev in 0 1 2 3; do if fatload usb ${usbdev} 1020000 s905_autoscript; then autoscr 1020000; fi; done stderr=serial stdin=serial stdout=serial storeargs=setenv bootargs ${initargs} logo=${display_layer},loaded,${fb_addr},${outputmode} hdmimode=${hdmimode} cvbsmode=${cvbsmode} hdmitx=${cecconfig} androidboot.firstboot=${firstboot}; run cmdline_keys; storeboot=if imgread kernel boot ${loadaddr}; then store dtb read $dtb_mem_addr; bootm ${loadaddr}; fi;run update; switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then run recovery_from_flash;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = cold_boot; then run try_auto_burn; fi;fi;fi; try_auto_burn=update 700 750; update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash; upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else if itest ${upgrade_step} == 1; then defenv_reserv; setenv upgrade_step 2; saveenv;fi;fi; upgrade_key=saradc open 0; if saradc get_in_range 0x0 0x50; then echo detect upgrade key; run update;fi; upgrade_step=2 usb_burning=update 1000 wipe_cache=successful wipe_data=successful

I am using the latest Armbian Noble image (version 6.6.8) on my Banana Pi CM4. For my application, I am utilizing the Linux UART (/dev/ttyAML0), which is currently printing dmesg logs on this port. Is there a way I can disable dmesg debug logging and exclusively use /dev/ttyAML0 for my application? Thanks.

Here is the UART output when trying to boot from EMMC: U-Boot SPL 2024.01-rc5-armbian (Jan 31 2024 - 05:51:55 +0000) DRAM: 4096 MiB Trying to boot from MMC2 mmc_load_image_raw_sector: mmc block read error SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###

rpi4b/bcm2711: introduce RPI_DEBUG_CONSOLE=yes which at once disables bt, enables uart, and adds ttyAMA0 Enabling uart debug on rpi4b requires a bunch of seemingly unrelated changes. The UART stuff on bcm is a bit cuckoo. View the full article

@Gunjan Gupta I only used the Armbian-Config to see what the Boot Environment was set to and to see if the correct boot device was set by Armbina-Install. It turned out that Armbian-Install had set the UUID of the SD-Card as the boot device. I will try to add a UART Serial port to the board and see what I can come up with.

@robertoj I started reading up a few things but that I'm more confused as ever: There is this thing about pincontrol https://www.kernel.org/doc/html/v4.13/driver-api/pinctl.html https://elinux.org/images/b/b6/Pin_Control_Subsystem_Overview.pdf https://wiki.st.com/stm32mpu/wiki/Pinctrl_overview ^ I liked this one from ST, but that I've not read well enough to understand how pin-control relates to gpio. on a superficial level, I understand it like such, as there are various configurations related to gpio pins e.g. that gpio pins can be configured in varous setups, e.g. input, output, pull up, pull down and other gpio properties etc (possibly soc related), then that for the pins in addition to gpio, there is pin mux, which 'behind' it can be configured for various 'alternate functions' e.g. spi, i2c, uart, pwm etc, then add interrupts etc. and accordingly earlier 'gpio' implementations eventually digressed and requires 'hacks' to get around 'missing' capabilities that is mapped in the more complex pin-control. But that I don't understand deeper than this that if pin control after all configures the pins as above, then where do gpio in the 'simple' sense e.g. reading the pins high or low, or writing to the pins work? Accordingly, there are API interfaces for that if you read the documentation, but I got stuck understanding further about this, i.e. I still don't know how gpio works in this context. on further 'google searches', I stumbled into more recent documentation https://www.kernel.org/doc/html/v6.7/driver-api/pin-control.html https://www.kernel.org/doc/html/v6.7/driver-api/gpio/index.html so it'd seem pin-control and gpio are after all 2 sets of API

Well, I don't see how a translator could have messed that as it's simple sentence construction, but I sleep the same at night 😂 Coming back to the reason I need that UART adapter... same thing happens on a debian OPi official image. This does not happen on a server (no desktop) version. So i guess if I want to use DWservice on a desktop I would a virtual monitor dongle..

I've got Orange Pi 5 Plus board with 16 Gb of RAM, 256 Gb of eMMC, Realtek RTL8852BE-CG wireless module. SD card is Samsung EVO Plus 32Gb. I tried to run Armbian images on this board (from the SD-card I've mentioned before) but it was absolutely failed. I tried 5 images: Armbian_23.11.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz Armbian_23.11.1_Orangepi5-plus_bookworm_legacy_5.10.160.img.xz Armbian_23.11.1_Orangepi5_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz Armbian_23.11.1_Orangepi5-plus_bookworm_edge_6.7.0-rc1.img.xz Armbian_23.11.1_Orangepi5-plus_jammy_edge_6.7.0-rc1.img.xz which I downloaded from your website but the result the same: tons of errors, a lot of dumps, no even chance to see a desktop. Also I should say the official images of Ubuntu and Debian works fine so I guess it's not a hardware issue. There is UART log when I tried to start Armbian_23.11.1_Orangepi5-plus_jammy_legacy_5.10.160_gnome-amazingfated_desktop.img.xz image putty.log Could anyone tell me what the problem is?

Yeah speaking from personal experience, he didn't meant to offend you. He uses an online translator so I guess if message appeared rude, that is not his fault. He was only trying to help FTDI232 and FT232 is actually the same thing. its just printed differently on different chips. But as I said before, anyone of the adapters will be fine. Some boards require to communicate at very high speed and thats when generally we have to be careful in choosing the uart adapter. But this board uses standard 115200 bps rate. So any adapter can handle it.

Hi, After running armbian-install on S905x device it stopped booting. USB Burning Tool doesn't recognize the device, nothing. After connecting to UART it looks like install script has overwritten the original u-boot. That's the boot log from UART connection without sd card: GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 104174 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vcck to 1120 mv set vddee to 1000 mv Board ID = 1 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - PASS Rank0: 1024MB(auto)-2T-13 Rank1: 1024MB(auto)-2T-13 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 [BL31]: GXL CPU setup! mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.359461 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast <debug_uart> U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc Model: Libre Computer AML-S905X-CC SoC: Amlogic Meson GXL (S905X) Revision 21:b (82:2) DRAM: 2 GiB Core: 169 devices, 27 uclasses, devicetree: separate MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial [BL31]: tee size: 0 [BL31]: tee size: 0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 1: Armbian Retrieving file: /uInitrd ** File not found /uInitrd ** Skipping Armbian for failure retrieving initrd SCRIPT FAILED: continuing... Found U-Boot script /boot/boot.scr 8147 bytes read in 1 ms (7.8 MiB/s) ## Executing script at 08000000 U-boot default fdtfile: amlogic/meson-gxl-s905x-libretech-cc.dtb Current variant: Current fdtfile after armbianEnv: amlogic/meson-gxl-s905x-libretech-cc.dtb Mainline bootargs: root=/dev/mmcblk1p1 rootwait rootfstype=ext4 splash=verbose c onsole=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ub ootpart=d27dbd06-01 libata.force=noncq usb-storage.quirks= cgroup_enable=memo ry swapaccount=1 22783841 bytes read in 500 ms (43.5 MiB/s) 27433472 bytes read in 601 ms (43.5 MiB/s) 40228 bytes read in 4 ms (9.6 MiB/s) Failed to load '/boot/dtb/amlogic/overlay/-fixup.scr' ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22783777 Bytes = 21.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7a982000, end 7bf3c721 ... OK Loading Device Tree to 000000007a90f000, end 000000007a981fff ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 00000000010656ec lr : 0000000001055038 (reloc) elr: 000000007dfb46ec lr : 000000007dfa4038 x0 : e14b4287a666c25d x1 : 000000007dfbc290 x2 : 0000000000000010 x3 : 000000007bf54e10 x4 : 0000000000000000 x5 : e14b4287a666c25d x6 : 0000000001000000 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 0000000000000178 x11: 000000007bf40eec x12: 00000000000000a4 x13: 000000007bf40ea8 x14: 000000007a90f000 x15: 0000000000000020 x16: 000000007df5946c x17: 0000000000000000 x18: 000000007bf4cdb0 x19: 000000007af41040 x20: 000000007df4fb18 x21: 000000007dfbc290 x22: 0000000000001000 x23: 000000007bf54d60 x24: 000000007dfdacb8 x25: 0000000001000000 x26: 0000000000000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf40ea0 Code: eb04005f 54000061 52800000 14000006 (386468a3) Resetting CPU ... resetting ... bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. And with sd card GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 103545 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vcck to 1120 mv set vddee to 1000 mv Board ID = 1 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - PASS Rank0: 1024MB(auto)-2T-13 Rank1: 1024MB(auto)-2T-13 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x000af000 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 [BL31]: GXL CPU setup! mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 8f bb f0 da ba 22 d2 cf 1 b0 31 f4 [0.358822 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast <debug_uart> U-Boot 2022.07-armbian (Nov 25 2023 - 12:50:42 +0000) libretech-cc Model: Libre Computer AML-S905X-CC SoC: Amlogic Meson GXL (S905X) Revision 21:b (82:2) DRAM: 2 GiB Core: 169 devices, 27 uclasses, devicetree: separate MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from nowhere... OK In: serial Out: serial Err: serial [BL31]: tee size: 0 [BL31]: tee size: 0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Armbian Retrieving file: /uInitrd Retrieving file: /Image append: root=UUID=a6cf29bd-49ae-4d3b-bf22-800408ae1fba rootflags=data=writeback console=ttyAML0,115200n8 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles Retrieving file: /dtb/amlogic/meson-gxl-s905x-p212.dtb Moving Image from 0x8080000 to 0x8200000, end=9cd0000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 22783777 Bytes = 21.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 08008000 Booting using the fdt blob at 0x8008000 Loading Ramdisk to 7a982000, end 7bf3c721 ... OK Loading Device Tree to 000000007a975000, end 000000007a98169c ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 00000000010656ec lr : 0000000001055038 (reloc) elr: 000000007dfb46ec lr : 000000007dfa4038 x0 : e14b4287a666c25d x1 : 000000007dfbc290 x2 : 0000000000000010 x3 : 000000007bf54e10 x4 : 0000000000000000 x5 : e14b4287a666c25d x6 : 0000000001000000 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 0000000000000188 x11: 000000007bf409ec x12: 00000000000000b4 x13: 000000007bf409a8 x14: 000000007a975000 x15: 0000000000000020 x16: 000000007df7a768 x17: 0000000000000000 x18: 000000007bf4cdb0 x19: 000000007af41040 x20: 000000007df4fb18 x21: 000000007dfbc290 x22: 0000000000001000 x23: 000000007bf54d60 x24: 000000007dfdacb8 x25: 0000000001000000 x26: 0000000000000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf409a0 Code: eb04005f 54000061 52800000 14000006 (386468a3) Resetting CPU ... resetting ... bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. Is there any way to restore original firmware?

I managed to fix the device I downloaded u-boot.bin from that thread Then I ran it from uart using 2 commands: fatload mmc 0 0x01000000 u-boot.bin go 0x01000000 With this u-boot version, the system booted up fine. After that, I tried to overwrite the corrupted u-boot using dd command. I failed but actually, that broke uboot on emmc which allowed the device to enter usb download mode. From that, I was able to write original ROM using amlogic burning tool

Hello, I am trying to communicate using UART PORT. I have connected to 8, 10 and GND pin. Also I enabled UART3, but it doesn't work. Any solution? Thanks !! Enviado desde mi iPhone utilizando Tapatalk