fss-hacks

That part of the instructions is clear. It's the steps involving the "wipe_part" file that supposedly erases partitions on the eMMC and the flashing of the second loader file that I can't make out. It looks like the instructions were edited to make them unusable. Nicolas has had the same issue in the H96 subforum with bad instructions and people asking for help due to the lack of clarity. I was able to make the board boot from SD card after flashing it with the YYT provided Debian 11 image, but only to Armbian Noble. No Debian distros work. When a Debian SD is inserted, the board boots then enters a systemd-devd shell with error messages about a UUID not being found. All Debian images do the same, I think it has to do with the eMMC memory not being seen because it is still formatted and not cleared. I have never seen a shell like this. Armbian Noble still boots properly, but only Noble. I need a Debian minimal distro in order to install OpenMediaVault and save my friend's files.

This is a sidebar/urgent request for help. I was previously able to install Armbian noble on my YY3568 board thanks to instructions from these forums (https://forum.armbian.com/topic/49775-board-bring-up-youyeetoo-yy3568-rockchip-rk3568/). I now need to use the board for a Debian project to help a friend that lost their backup, and am unable to reproduce the instructions in that post to empty the eMMC and enable SD boot. The poorly written/flawed instructions in this post involve loading a config file into RKDevTool, writing loader, parameters and uboot, then there is a line about "destroying partitions by writing wipe_part" (a file you can download in the post), with no clarity or description of how to do this. The steps then move onto flashing another loader to the board. I have done all of these steps in MANY different adaptions and versions and it is always unsuccessful because whatever portion involving the "wipe_part" is missing from the original steps. I am hoping that someone else whose board uses similar procedure sees this and can correct the instructions and make SD boot possible again. It's really aggravating that my board is being held hostage to this - the person who wrote the instructions has worked on other projects with similar steps and others have had the same issue with their incomplete/incorrect instructions in those posts, and so far will not reply regarding this. I've tried 4 different versions of RKDevTool and worked for around 7 hours on this so far with no success. I'm hoping someone else can come save me!

Reply from the company that makes Cubox: the SOC of the MiiPC is the same family as the Dove based SOC that was in the original Cubox device. We're getting closer.

My apologies. I started working on this board again and just spent 3 wasted hours getting angry at the previous wipe eMMC instructions only to realize *I* had the wrong version of RKDevTool. Protip - do not do any hardware development angry, hungry, in a rage, or pressed for time. Wow. Here is the issues with your "erase eMMC" instructions (apparently partly taken from the guide to getting Linux on the T95 Plus): -Config file was loaded, loader, parameters and uboot were written. Board usually does not restart when this is done, restarted once out of my many attempts. -There are no instructions about "wipe_part", what partitions to destroy, or how to do this. Using your version of RKDevTool, no partitions are loaded which then appear in the Download Image window (as I assume they are supposed to). -Flashing the other Miniloader file is met with a Waiting for Device Success prompt, which never completes. These instructions obviously worked the first time I did this several months ago. I don't know what at all could have changed, and I'm pretty frustrated as I'm trying to recover from another OMV system crashing and trying to recover data, so the use was/is pretty urgent, and given this forum, it could be a few days before a replay so my system is now sitting hostage to these instructions.

They did. Or at least the kernel is built, and this was reported (https://linux-arm-kernel.infradead.narkive.com/WmgM10BC/rfc-v1-0-5-arm-initial-support-for-marvell-armada-1500) . This family of chipset includes the original Google TV and some others.

I'm not sure what you're asking. I'm requesting information because I am seeing information stating that there is a working linux kernel that exists, but I don't know how to bridge that into a form where that kernel could be built or compiled into an image. Can what is on that github page be input into the build process? I've looked at what it takes to build Armbian from source and I understand the instructions when the board being built fits the categories in the instructions, but I'm not sure if that github kernel is useable or can be applied in that buidl process.

So I have made some progress. A linux kernel for this device (based on the Berlin chipset family) exists at https://github.com/MarvellEmbeddedProcessors. I',m not sure how this piece adds towards creating a functional armbian install tho.

Turns out the Armbian option on H3Droid is dependent on extremely old outdated URLs. I’m trying to get into the board structure when h3resc is booted in order to see if I can find the sources list that provides these URLs rn

Is it just modifying the dtb? I was reading and I understand that means decompiling to dts and then recompiling but what edits would I have to do to enable eMMC?

Hello, I have a T95 Super with H2+/H3 processor. I've been successful running Armbian in the past on it and even writing to eMMC but am looking for the most updated build I can to burn to the eMMC. I have H3droid running on it after a VERY long install process and many board reburns to fix it. I noticed H3droid has an "Armbian" option in it's rescue menu but there don't seem to be any instructions on how to install with the menu/use it. What is the best new build for this setup? Thank you!

Hello, My pet labubu and I got the most recent onecloud/odroid c1 versions fully working on my horrid former Oriental TV box, the TVPad 4 (previously brought up by user @daniyo). Everything works perfectly, except I want to finish my building by installing to eMMC. None of the recent builds I can find come with an install.sh script, and I cannot see the eMMC (or NAND if it's NAND) in lsblk or any of the installers. Does anyone have any clues or suggestions that can help the poor long suffering Labubu fix this issue? He just wants to watch IPTV and play little games

I was extremely excited to read this. My issue currently is that I'm dealing with S805 and H3 builds which had builds dominated by the megalomaniacal user whose name starts with "B" (really not a fan of their behavior but extremely impressive work). For some reason, these builds never come with the install.sh scripts that Amlogic builds normally come with, and I can only write S805 builds to eMMC using builds with the 5.7/3.10 kernel to eMMC because they come with an install.sh. I really want to "finish" the builds by writing them. I'm hoping to use dd to write to the eMMC but it doesn't come up with lsblk at all (except with the 3.10 kernel). Does anyone have any suggestions about how to get around this?

I agree, it would be a small adjustment that is hopefully easy. I don't know how to do it myself but the inbuilt eMMC is definitely not big enough for the kind of files I want to serve from the board. And I apologize, I didn't realize that random people can upload builds like that; I meant that it appeared to be a listed frequently updated board.

This SSD thing has been broken for several months. YY3568 is now one of the Armbian recognized boards. Can someone please provide a fix?

So my experience with Armbian is pretty broad, starting with Raspberry PI, then taking a hard left turn at Albuquerque with me successfully running a docker server on an Allwinner H3 based T95 super TV box. I’ve also run it on SBCs like the yeayeetoo Rockchip series. I’ve just never compiled a build and it is so hard to find any info from anywhere about the Armada 1500 running anything. What is the virtual system option?