chocho I updated U-Boot, please test it. Instructions in #143 still apply.
Posts by jernej
-
-
chocho Please wait, I figured few other things. I'll prepare another U-Boot.
-
gamma-271 Can you also upload Kodi log (/storage/.kodi/temp/kodi.log)? Dmesg and console log seem to be fine. Unfortunately I don't have this specific board.
-
chocho Here is new U-Boot: u-boot-sunxi-with-spl.bin
Burn it with sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8 where /dev/sdX is your SD card device.
-
chocho Test this: libreelec-h6.arm-9.80-devel-20190628231511-fea1a3d-tanix_tx6.img.gz
If it doesn't work, some more text should be printed. I'm interested what it says. If it works, I'm interested if appropriate amount of RAM is detected.
-
chocho box uses "Half DQ" DRAM configuration which is not implemented yet. Are you willing to test images in order to fix this? Hopefully only a few tries should be enough.
-
-
I noticed that DRAM parameters are very different. I will have to go over them and check what might cause the issue.
-
yes it is. I'm comparing it to Tanix TX6 now, but till now I didn't find any important difference.
-
chocho While that helps, it would be even better if you can upload /sys/firmware/fdt file somewhere.
-
chocho I'm not able to find DT file. Can you check if /sys/firmware/devicetree/base exists? If so, it's binary version of device tree, which can be easily decompiled.
-
Actually, I found an issue with latest nightlies on H6. For some reason, kernel crashes in all cases except if it is connected on 4K TV and enhanced colors are enabled - exactly the opposite I thought it would help. If enhanced colors are disabled or 1080p PC monitor is used, Kodi won't start due to kernel crash.
I think that latest GPU driver has caused this issue, but I'm not sure how to fix it. Reverting driver change isn't an option. It will take some time...
-
gamma-271 Adjames089 Can both of you provide output of edid-decode /sys/class/drm/card0-HDMI-A-1/edid, when TV with issue is connected?
BTW, that system log file looks fine.
-
chocho can you somehow extract DTB file? I usually do that from box image, but I can't find any for TX6 mini on the net. As last resort, you can make clone of eMMC to some external media like USB using dd, compress it and upload somewhere.
-
chocho Test this image: libreelec-h6.arm-9.80-devel-20190627172418-9866786-tanix_tx6.img.gz
I lowered RAM clock to 648 MHz (taken from Android boot log). It's only 12 MHz difference, but may be important.
If this still doesn't work, boot Android, execute busybox devmem 0x3006100 over serial console and tell me what value you get.
-
Apparently there is difference between TX6 and TX6 mini, because can't boot.
Which image did you use? This board has exactly the same RAM chips as Tanix TX6, so I don't see any reason why it shouldn't work. Unless some voltage regulator has to be enabled to power RAM, which is unlikely.
-
How do I install the image in EMMC memory?
Just dd it on eMMC over ssh. Currently this is the only way (except for OrangePi 3, where a U-Boot update is needed).
Is this of any relevance: Can't get HDMI out on OrangePi One on sunxi-next · Issue #290 · linux-sunxi/linux-sunxi · GitHub? I know that the issue is about Orange-Pi One, and I have the One-Plus, but the symptom is the same.
Actually, it's not the same. In that issue report you can see reported -517 two times, but in your report it's only once, because second time driver loads properly. If driver mentioned in the issue wouldn't be enabled, then image wouldn't work on any combination of TV and board.
Do you have by any chance 4K TV with enhanced colors enabled? If so, try disabling enhanced colors.
-
Amlogic hardware - sun50iw6p1
Yeah, I don't think anyone at Tanix bothered to check. This will bring a lot of confusion.
