tERBO

Boot from SD card -> chroot in to emmc partition -> install known working kernel. Detailed instructions are in 3318 main thread.

When it's "flashing armbian" is it going instantly? Like 0-100% in 1 second or is it taking a significant amount of time? I had an issue with a faulty or incompatible SD card when it was booting multitool but refusing to flash any images. The other card worked just fine. Also try this image with factorytool: https://drive.google.com/file/d/1EoQJMtfkvgYQE0WOa4qSpH-SDNjwxyct/view

Ah, yeah, there is something hs200 related, voltages speeds and stuff. But it's for rk3308 which is the same deal as 3318 but with no GPU - should be compatible... in theory...

Uboot package is getting upgraded (along with dtb and some others) too from trunk 314 but it does not break the system. I did upgraded all the packages one by one manually and the only one that breaks the system is linux-image-current-rockchip64 Anyways if you can't reproduce the issue and want me to do more tests on my board - let me know.

Well, I just did that - the two hs200-related error lines went away but everything else is the same and it still cant init MMC card.

Ok so here is what I have managed to gather so far 1. Dmesg from trunk 314 booting from emmc: armbian-hardware-monitor-trunk314.log 2. Dmesg from trunk 355 booting from SD: armbian-hardware-monitor-trunk355.log 3. A snippet of dmesg from trunk 355 not booting from Emmc: There are some visible error messages but they all means nothing to me.

I don't think it is defective. I have verified many times - installing an image from multitool = works. Doing apt upgrade, linux-image-current-rockchip64 package specifically breaks the system. The shell appears after a few seconds indeed and I can't see any /dev/mmcblkxxx devices so no wonder it doesn't boot. I'm not really familiar with these systems so I'm not sure how to debug the issue. For now I just put linux-image-current-rockchip64 package on hold. But I think it should be fairly easy for someone who know how it works to look at the changes made in said package between trunk 314 and 322 to determine what could affect emmc drivers or what not...

Correct. After the update the system cant see emmc anymore and refuse to boot. Emmc verbosity=1 bootlogo=false console=both overlay_prefix=rockchip fdtfile=rockchip/rk3318-box.dtb rootdev=UUID=58276691-7264-424f-9624-0279e1a3f1db rootfstype=ext4 overlays=rk3318-box-cpu-hs rk3318-box-emmc-hs200 rk3318-box-led-conf1 rk3318-box-wlan-ap6334 extraargs=systemd.unified_cgroup_hierarchy=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u It's a green PCB from 2019. 4/64 memory.

Try "Upgrade" instead of "Restore" in the factory tool. If it wont work - your emmc is probably dead.

This is a current build. I also tried Armbian_community_24.8.0-trunk.314_Rk3318-box_noble_current_6.6.36_gnome_desktop.img.xz - ubuntu-based one and it acts exactly the same. The system breaks after updating linux-image-current-rockchip64 package

Installing Armbian_community_24.8.0-trunk.314_Rk3318-box_bookworm_current_6.6.36_minimal.img.xz from the github works fine. Doing apt upgrade renders system unbootable. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Pls fix

Do SD cards work at all in android? Maybe the SD cards slot is damaged or something...

Anyone running gnome on this chip? I have 3318 paired with 4Gb of RAM and the GUI is very slow. Choppy mouse movements, loading youtube front page with chromium takes forever, cant play videos without stutters even at 480p. Is it supposed to be like that or do I have to enable 3D accel somewhere/somehow? I know stock android fw renders at 720p (even tho you can select 4k resolution for your display) so it wont surprise me this chip just have a bad graphics core...