NickFoley

Update: I flashed on Sunvell-r69 with legacy kernel 3.4.113 and it has booted up and seems to be running nicely (No change to fex files). I tried using the mainline kernel and it had the same issue. Will try building for Orange pi with the legacy kernel also to see if that could be the cause of the issue. EDIT: just saw your reply. Thanks for your help. I will have a play and let you know how i go. Thanks, Nick

Bummer that it either has crappy components or uses incorrect values. Thanks for the reference to the Sunvel R69, i am building an image for it now and doing some reading. Regardless of picking an image for an Orange Pi or something like the Sunvell R69 the steps i need to do is as follows Compare their fex file with the sys_config.fex file from my board and copy over the differences. Meaning making the R69.fex match my sys_config.fex. Build the image for the R69 (with my changes). Flash it to the emmc. Hopefully then i will be able to actually boot past the kernel into Armbian. Correct me if i am missing some steps or over simplifying things. I appreciate the help

Hi tkaiser. I am reading what i can find and am learning more by the day. I checked my board's clock speed. It is 576 MHz, so quite a bit slower. I figured because it runs an H3 it should be capable of the same clock-speeds as any other H3. Thanks for the commit history link. So what i gather you are suggesting is that I get the orangepi.fex and compare it to my sys_config.fex (included below), much like what they did in the link. Then try and compile a new image with the altered fex and see how it goes. Hopefully i am not too far off the mark.

The kernel running on the mainline linux is 3.4.39. In the source of mainline linux i have found about 50 fex files. I have included a photo of the fex files below. In regards to the devicetree blob, I have found a bunch of dts files and two dtd files but no btd files. Not too sure what files to investigate.

Hi Xalius, I have started comparing the boards the best i can. I am looking at editing the OrangePiPcPlus.fex file found at https://github.com/armbian/build/blob/master/config/fex/orangepipcplus.fex. Just checking that this is the file containing the devicetree and the correct place to start editing? Thanks, Nick

Hi Xalius, thanks for the quick reply. I have started comparing both boards. However i do not have a particularly clear schematic of this custom board, so it is proving difficult. I have the base linux-image (and android image) that the manufacturer provided. Would i be able to use the uboot/kernel provided with it or be able to pull the devicetree information from it?

Hi Guys i searched the forums but could not find anything too similar. Any advice would be welcomed. Summarised version I am currently trying to install the OrangePiPC Debian Server image of Armbian on a custom H3 board emmc and getting a kernel error (Gave up waiting for root file system device. Common problems . Please see serial log at bottom for full information. TLDR VERSION Objective To install armbian directly onto the emmc. Board Information Board acquired from a manufactorir. It has USB_OTG, eth, Uarts, emmc and some other ports but NO SD card slot. Using OrangePiPC as it seems the most similar. How I am Installing 1) I mount the emmc directly to a Debian computer via using zador-blood-stained/fel-mass-storage. 2) I use etcher to burn the image to the emmc. 3) I plug in an external power supply and read the serial output (see log). 4) after the issue occurs it boot loops showing the same error. Suspected cause of Failure I suspect that because my hardware has differences to the OrangePiPc it is causing this issue and that i will probably need to build a custom image of armbian specifically for my board. If this is the case any information on how to proceed would be appreciated. Other information I have booted the OrangePiPc image using FEL boot. It boots up into Armbian and works correctly for around 10 minutes before experiencing a kernel panic. I have set up the development environment for compilation and am a developer so hopefully compiling a custom board/kernel/uboot should be doable for me. Thanks and sorry for the wall of text, Nick Serial Log