balbes150

@balbes150
I did try your image linux1-rk3188-5.6.6-lubuntu.img on my Raxda Rock using sdcard. 
As I read from other members here I didnt thing it would boot, BUT it does  
 
I wonder about the differnt numbers when start_linux:
DDR Version 1.04 20130517 In DDR3 300MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=16 Size=2048MB Memory OK OUT BUILD=====2 SdmmcInit=0 0 FwPartOffset=2000 , 0 run on sd0 OK! 38492 unsigned! SecureBootEn = 0 0 Boot ver: 0000-00-00#0.00 start_linux=====56640 4661552 Starting kernel...@0x60408000 start_linux=====66979 start_linux=====56640 start_linux=====56653 start_linux=====54938 Not on every boot I do get boot-messages and reboot doenst seem to work.
But after a time I do get a LXDE(?) Desktop on my HDMI-Monitor  
Eth0 isnt working (also with a proper /etc/network/interfaces) so I connected a USB-Ethernet-Dongle and did get a eth2  
login as: root root@192.168.6.151's password: Welcome to Linaro 13.09 (GNU/Linux 5.6.6-arm-32 armv7l) * Documentation: https://wiki.radxa.com/ Last login: Thu Jan 1 00:02:12 1970 root@radxa:~# uname -a Linux radxa 5.6.6-arm-32 #20.06.0 SMP PREEMPT Mon Jun 29 22:11:12 MSK 2020 armv7l armv7l armv7l GNU/Linux At the next restart it didnt started with USB-Ethernet and serial TTL-Dongle attached.
So I removed both, started and reattached the USB-Ethernet-Dongle.
 
Now it booted again and I had to enable eth2 as root with
ifconfig eth2 up
 
As attachment here you get the dmesg-log  
 
Raxda_Rock_566_dmesg.txt

When starting u-boot and the main system, the kernel configures (switches) all hardware. If there is a UART, it can act as a backup power source that preserves the set parameters even when the power supply is disconnected. I regularly observe such" strange " HDMI behavior on many TV box. Therefore, when testing, I always disconnect all cables (power supply and UART) for a few minutes. This ensures that the hardware is activated correctly at startup. By the way, u-boot is the same Linux system as the main armbian system (with the Linux kernel and minisystem).

If anyone is interested: The UART bootlog from my RK3188 Raxda Rock with debian 8 in nand as attachment
[172723.041565] Restarting system. DDR Version 1.04 20130517 In SRX DDR3 300MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=16 Size=2048MB OUT BUILD=====2 SdmmcInit=0 20 No.1 FLASH ID:2c 64 44 4b a9 0 OK! 251802 unsigned! SecureBootEn = 0 0 Boot ver: 2013-12-02#2.08 start_linux=====256654 3252872 Starting kernel...@0x60408000  
Raxda_Rock_UART_Boot_debian_8_nand.txt

Hi ,  sorry for the delay ,but it took me more time then expected due to strange behaviour of my equipment.
When I double checked , some  results didn't make sense .I booted radxa lubuntu and couldn't get into the desktop anymore ,
nand android worked ok and I downloaded radxa lubuntu again but still no desktop.The weird thing is linuxium from sd and
android worked fine .So in the end I disconnected my android device and waited a long time  > 10 minutes and then
radxa booted ok again! Did something persist in memory for a while ?
Anyhow I'm checking the results again ,this will take some time ,but I can give some preliminary results :
-replacing u-boot etc. in the radxa img ,all combinations makes it complete unbootable.
-replacing u-boot taken from radxa and substituted in either linaro 3.0.36 or lubuntu 3.0.36 makes them partly bootable,
but the boot process stops before hdmi gets connected ,this doesn't work with the 5.6.6 img though so no extra
output with the 5.6.6 img .
- replacing u-boot taken from linuxium and substituted in the 3.0.36 images makes them also partly bootable.
 
I will test today again and post the results with uart output

Yes , I erased nand ( android was completely gone ,didn't boot anymore )and then I booted Armbian from sd and with this log as result

they only I know for sdcard are
https://dl.radxa.com/rock/images/ubuntu/sd/radxa_rock_lubuntu_desktop_140626_sdcard.zip
https://dl.radxa.com/rock/images/ubuntu/sd/radxa_rock_ubuntu_14.04_server_140820_sdcard.zip

Maybe also interesting:
https://dl.radxa.com/rock/images/android/Boot_android_from_sdcard/radxa_rock_kitkat_sdcard_boot_update_0621.zip

And the directorys:
https://dl.radxa.com/rock/images/loader/
https://dl.radxa.com/rock/images/parameter/
https://dl.radxa.com/users/dev/3188/

For all rk3188 owners, can you provide a link to any Linux image that you have start and running ? I want to see which version of u-boot and kernel is used there.

I plan to send the new version to network repositories after switching to version 20.08. Without this, the kernel package will have the same name as the existing package and the update does not work correctly.

ver 20200720 kernel 5.7.9

Added u-boot-2020.07 files for rk3399-rock-pi-4b

The issue has already been resolved and the Armbian build works on ARM devices.

Building a 6-hour kernel on an i7 is a new joke ?   
rk3399 builds a complete Armbian image (along with the core and other packages) in 50 minutes. 
Even the weak s905x2 collects the entire Armbian image in 200 minutes. 

It is theoretically possible.  But I haven't seen this successfully done.  To undertake a task like this you need access to source code and support from the underlying device manufacturers, which generally doesn't exist.  (This is part of the reason that balbes150 doesn't support the s905x3 cpus as Amlogic does not provide support for their products under mainline kernels).

Test image for rk3188
Download, unpack and burn the ArmbianTV image to your SD card.
Connect to the TV box and turn on the power. The system will start automatically.
 
https://yadi.sk/d/YXA09tNfyRhDIw

parametr.img
 
votparametr.img

Test image for rk3188
Download, unpack and burn the ArmbianTV image to your SD card.
Connect to the TV box and turn on the power. The system will start automatically.
 
https://yadi.sk/d/YXA09tNfyRhDIw

Good news. Using sources with patches from knaerzche,  it was possible to get the initial launch of the kernel 5 with an HDMI output for rk3188 (Ugoos UT2). Now I can see what messages the kernel gives out and I can move on, add the necessary options and Initrd for a full start of the system.
 

Good news. It turned out to fully launch Armbian with core 5 on Ugoos UT2 (rk3188) from an SD card. 
 
Question. Are there users with models running on the rk3188 platform ?

My images use u-boot-2020 (for rk3288), it only works if there is no u-boot in eMMC\NAND. Rk3188 needs its own version of u-boot-2020 (I don't have this option yet). But there is also good news, when performing a number of manual steps, it turned out to run the core 5 on rk3188 (but without HDMI output, network, etc.), there is only the inclusion of indicators and reaction to the combination CNTR+ALT+DEL (the system reboots). 
 
 
To all
New image 20200623-dev kernel 5.8-rc2

Ver 20200623-dev kernel 5.8-rc2

To make it more clear, can add the CPU type discussed here to the topic title.

Please contact the administration to move this topic to the TV box section. I would like to (as far as possible) continue this direction (native Armbian build directly on ARM devices). For skeptics. Recently, I completely moved the LivreELEC build to the ARM platform (i.e. the entire process of creating LE images and Addons now takes place on ARM rk3399\s922x devices). My dream is (perhaps) to try to transfer the ArmbianTV build completely to the ARM platform and get rid of the x86 dependency.

Please contact the administration to move this topic to the TV box section. I would like to (as far as possible) continue this direction (native Armbian build directly on ARM devices). For skeptics. Recently, I completely moved the LivreELEC build to the ARM platform (i.e. the entire process of creating LE images and Addons now takes place on ARM rk3399\s922x devices). My dream is (perhaps) to try to transfer the ArmbianTV build completely to the ARM platform and get rid of the x86 dependency.