ToShuk

have a problem with the same box how to boot from sdcard before boot from emmc ? as I know we need to run as update aml_autoscript file, but how to do that from armbian booted from sd card ?

Thank you! it's really work! wow, my eMMC is dead, os sees the real size of eMMC, but R\W operations are not available. One more question, I have MX10 with an sv6051p wifi chip, but the os is not see any wifi devices, is it possible to turn on sv6051p chip?

wow, good news! just a small clarification, Do you mean pins that turn on maskrom mode? in my side on the other side of the board under emmc. Also another question, what about speed? i guess eMMC is better than sdcard?

one second, if i short the clock ping of eMMC, what are the next steps ? how to boot Armbian from sd card? just flash img to sd card, put it to box and it will boot from sd card ?

it looks like the bootloader is in stock because the multitool is loaded successfully, but I cant burn Armbian to emmc, it is stuck. How can I run Armbian from sdcard ?

One question about my bricked MX10 4\64 GB, is it possible to update by maskrom image of armbian ? i suspect that my mmc is dead, I got Download IDB Failed, one more question, is it possible to boot Armbian from SD CARD if mmc is dead?

Thank you so much! everything is clear for me. another question, where I can find the latest Legacy img ? i guess it is only Debian buster?

So, the case with updating UUID like Hqnicolas say won`t work?

Understood, but how to determine correct UUID ?

and how to determine my UUID ? new UUID

But how can i do it via `multitool.img.xz` ? I flash NAND from multitool.img.xz

mx4 pro I tried to write to nand archive/Armbian_24.2.5_Rk322x-box_jammy_current_6.6.22.img via multitool, and get this message Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enougth?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=b9866ace-f260-437c-9794-8e1a363a3c71 does not exist. Dropping to a shell. I guess only legacy images is work now, how to fix this problem, who can help?

I compiled Armbian-unofficial_23.11.0-trunk_Olinux-som-a13_jammy_current_6.1.63_minimal.img Burn it to sd card, and tried to run it on my old Allwinner A13 laptop, and is got this Error message: U-Boot 2023.10-armbian (Oct 14 2023 - 01:13:59 +0000) Allwinner Technology CPU: Allwinner A13 (SUN5I) Model: Olimex A13-Olinuxino DRAM: 512 MiB Core: 59 devices, 21 uclasses, devicetree: separate WDT: Not starting watchdog@1c20c90 MMC: mmc@1c0f000: 0 Loading Environment from FAT... MMC: no card present ** Bad device specification mmc 0 ** Setting up a 1024x768 vga console (overscan 0x0) In: serial,usbkbd Out: serial,vidconsole Err: serial,vidconsole Allwinner mUSB OTG (Peripheral) Net: using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in MAC de:ad:be:ef:00:01 HOST MAC de:ad:be:ef:00:00 RNDIS ready eth0: usb_ether MMC: no card present ** Bad device specification mmc 0 ** Couldn't find partition mmc 0 MMC: no card present ** Bad device specification mmc 0 ** Couldn't find partition mmc 0 starting USB... Bus usb@1c14000: USB EHCI 1.00 Bus usb@1c14400: USB OHCI 1.0 scanning bus usb@1c14000 for devices... 2 USB Device(s) found scanning bus usb@1c14400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop MMC: no card present Device 0: unknown device The remote end did not respond in time.missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-de-ad-be-ef-00-01 The remote end did not respond in time.Retrieving file: pxelinux.cfg/00000000 The remote end did not respond in time.Retrieving file: pxelinux.cfg/0000000 The remote end did not respond in time.Retrieving file: pxelinux.cfg/000000 The remote end did not respond in time.Retrieving file: pxelinux.cfg/00000 The remote end did not respond in time.Retrieving file: pxelinux.cfg/0000 The remote end did not respond in time.Retrieving file: pxelinux.cfg/000 The remote end did not respond in time.Retrieving file: pxelinux.cfg/00 The remote end did not respond in time.Retrieving file: pxelinux.cfg/0 The remote end did not respond in time.Retrieving file: pxelinux.cfg/default-arm-sunxi-sunxi The remote end did not respond in time.Retrieving file: pxelinux.cfg/default-arm-sunxi The remote end did not respond in time.Retrieving file: pxelinux.cfg/default-arm The remote end did not respond in time.Retrieving file: pxelinux.cfg/default The remote end did not respond in time.Config file not found The remote end did not respond in time.The remote end did not respond in time.=> Please, help me to understand, what I need to do to fix it ? Please, I novice in u-boot and armbian, if possible, in more detail since I haven’t delved into the details of the launch very much, I’m still learning Thank you community

can it be an issue with dtb file?

Added this: setenv video-mode sunxi:1024x600-24@60,monitor=lcd setenv load_addr "0x45000000" setenv overlay_error "false" # default values setenv verbosity "7" setenv console "both" setenv disp_mem_reserves "off" setenv disp_mode "1024x600p60" setenv rootfstype "ext4" setenv docker_optimizations "on" setenv bootlogo "false" setenv devnum "0" setenv rootdev "/dev/mmcblk${devnum}p1" setenv earlycon "off" setenv video-mode sunxi:1024x600-24@60,monitor=lcd to boot.cmd , compiled boot.scr but nothing Any ideas? armbian-ramlog.log boot.log kern.log armbian-hardware-monitor.log syslog user.log