balbes150

Currently, the site has the latest version 20200517 (used branch 20200515).

I'm sorry, I didn't understand your question ? Which (boot.ini) is currently used to run (its full contents) ?

You haven't studied what models are supported and how they work. You immediately bought shit for a meager price, the profit from this purchase was received exclusively by the seller and manufacturer. And now you want everyone around you, for free, to rush to solve your problems ? Personally, I don't care if you use Armbian or not.

If you pay $300, I will write a detailed changlog (this is the cost of the time that I will have to spend on a detailed description). This is an absolutely correct (work) file. Read carefully the information in this topic, especially the first message and highlighted in red.

Options. 1. contact the manufacturer (seller) of your TV box to send support for this model to the main core (driver, settings, firmware , etc.). 2. you will write the necessary driver for the core 5. 3. you will find or hire specialists who will do this work.

ver 20200516 kernel 5.7-rc5

On s805 TV boxes, launch is only possible from an SD card. Important. The screen resolution must be 1080p. Perhaps u-boot on C1 does not correctly switch the video resolution (you may need to play with the parameters in boot.ini). Unfortunately , I don't have a C1, I can't help with diagnostics and fixes.

How is the TV\monitor connected ? What resolution does it support ? I have 2 TV boxes with s805 and s812 running HDMI. log to s805 http://ix.io/2mec There is a bug, the TV colors are not quite correct, instead of red purple. Screenshot from running Armbian on the s805 TV box.

you did not configure DTB to USB. The system starts normally. If HDMI doesn't work , check the cable and your TV\monitor. To work with eMMC, you need the correct DTB.Either you select the appropriate one from the available ones, or you need to create your own one for your hardware. But maybe you don't have eMMC, it's NAND memory, it won't work.

No, this is not the correct order. This won't work.

No. These files are intended for other purposes and do not need to be changed.

This is the key string used by u-boot to determine whether to execute this file or not. It must be strict ODROIDC2-UBOOT-CONFIG

By the way, I noticed a difference and correctly, as it should be

Yes, you need to replace the contents of the file (boot.ini) with eMMC (in android). It should only contain the lines I gave above. Second check, check the launch from USB. Write an image USB and configure it (uEnv.txt) and replace this line in (boot.ini) with eMMC setenv devtype "mmc" setenv devnum "1" to usb start setenv devtype "usb" setenv devnum "0"

Perhaps this command is the reason. usbmulticam=${usbmulticam} gpiopower=${gpiopower}" save showlogo ${hdmimode} Try temporarily replacing the entire file (boot.ini) with eMMC with this version. Write Armbian and configure (uEnv.txt) to the SD card. Connect the SD card and check the launch. ODROIDN2-UBOOT-CONFIG # set load addresses setenv env_addr 0x10400000 setenv kernel_addr 0x11000000 setenv initrd_addr 0x13000000 setenv dtb_addr 0x1000000 #if test "${devtype}" = ""; then setenv devtype "mmc"; fi setenv devtype "mmc" setenv devnum "1" # load uEnv.txt load ${devtype} ${devnum} ${env_addr} uEnv.txt && env import -t ${env_addr} ${filesize} setenv bootargs ${APPEND} # Load kernel, dtb load ${devtype} ${devnum} ${kernel_addr} ${LINUX} load ${devtype} ${devnum} ${initrd_addr} ${INITRD} load ${devtype} ${devnum} ${dtb_addr} ${FDT} fdt addr ${dtb_addr} # boot booti ${kernel_addr} ${initrd_addr} ${dtb_addr}

What is your current configuration of eMMC + SD , eMMC + USB, SD + USB media etc (which media do you want to run Armbian from) ?

Yes, it is possible, which system option do you want to get ?

I haven't checked (I don't have this model), but I think it should work, provided you use the appropriate LE and Armbian images (which use the appropriate partitioning). Specify which addresses you are referring to. No, this u-boot is intended for new versions of Armbian and LE (which have different partition placement).

ver 20200514 kernel 5.7-rc5

I uploaded u-boot files and scripts (boot.ini) to the site for testing with LE and Armbian images. After writing the image to the SD card, you need to write the u-boot file with two commands. dd if=u-boot-s805-odroid-c1.img of=/dev/<you_sd_card> conv=fsync bs=1 count=442 dd if=u-boot-s805-odroid-c1.img of=/dev/<you_sd_card> conv=fsync bs=512 skip=1 seek=1 Add one of the options (boot.ini) for the desired system to the SD card. Download the desired boot.ini-* file and rename it to (boot.ini). https://yadi.sk/d/RHCR-HwE886n_A

Unfortunately, this is for the old core 4. as far as I understand, these parameters are already used on the new core. https://github.com/150balbes/Amlogic_s905-kernel/blob/master/arch/arm64/boot/dts/rockchip/rk3399.dtsi#L1601 https://github.com/150balbes/Amlogic_s905-kernel/blob/master/arch/arm64/boot/dts/rockchip/rk3399.dtsi#L1765 https://github.com/150balbes/Amlogic_s905-kernel/blob/master/arch/arm64/boot/dts/rockchip/rk3399-nanopi4.dtsi#L889 By the way, the latest version of Libreelec (20200512) has support for 4K decoding. I checked it on T4 - it works.

Update ver LE 20200512 (branch 20200510)

Thank you for checking. It looks like u-boot is not working correctly (or is missing) for c1. I will check and write when another test image for c1 is ready.

Agree. The name rockchip64 - for rk3399 is unfortunate and creates confusion. It is better to use rk3399.