Posts by jernej

    Are tanix tx6 and tx6 mini most likely compatible?

    I did a bit of a research regarding H6 STB functionality. From what I can see, exactly the same image can be used on all of them, including TX6 mini. They have only few, small differences which are not important at this stage.

    If you can find detailed PCB image and Android image for that box (to extract DT), I can tell you more, but there shouldn't be any surprises.

    That would suggest improper HDMI PHY configuration. However, it shouldn't be all that different to Android. However, HDMI driver will certainly get improvements in future.

    Does anyone know why the other HDMI cable works with Amlogic and Rockchip boxes but not with Allwinner?

    It probably has to do something with HDMI PHY settings or electrical properties. Does it work with Android? How long is your non-working HDMI cable? Sometimes longer cables (for example, 5m) can be problematic since they need to be driven with higher power.

    The passport on the TX6 indicates that it 1000 (Gigabyte) network.

    If it is really gigabit ethernet, can you find ethernet phy chip? Usually it's realtek one. DT, which I extracted from Android image, says TX6 has RMII interface which would suggest 100 Mbit ethernet.

    For a wired network need fixes in DTS or even in the kernel ?

    Both, but needed kernel changes are currently part of OrangePi 3 patch set which you can find on one of various kernel mailing list. However, OrangePi 3 doesn't need those changes, because it has gigabit ethernet.

    balbes150 ethernet should be easy to fix once I get my box.

    BTW, this and other H6 STBs seem to be made as cheap as possible. They lack some of features present on H6 SBCs, like proper power management, gigabit ethernet and better RAM (I think DDR3 is the cheapest supported RAM type). However, you get enclosure, remote and AC adapter.

    SBCs also usually use WiFi modules which are better supported in Linux.

    One more thing I noticed was that the RAM in Kodi shows as 3gb. I remember you saying there was some limit on RAM, but there was a hack to get it to show/use 4gb RAM??

    H6 is only capable to address 3GiB of RAM. It has 32-bit address space and lower 1 GiB is reserved for memory mapped peripherals. Take another look at serial output. SPL DRAM driver will correctly report 4 GiB of RAM, because so much of RAM is physically present. However, U-Boot will report 3 GiB of RAM, because so much can be really used.

    No one really knows if there is a way to use that 1 GiB of RAM. It certainly can't be directly addressed.

    ukmark62 please test this image: libreelec-h6.arm-9.1-devel-20190615175620-0b86f08-tanix_tx6.img.gz

    It should have proper U-Boot already, so you just burn it on SD card and try right away. I also fixed resolution detection and HDMI audio. STB has additional pin which has to be enabled in order to correctly read EDID.

    USB3 also doesn't work yet. Anyway, if this works as intended so far, I'll stop right here until I receive my box.

    If you are curious, I uploaded LibreELEC changes here: Commits · jernejsk/LibreELEC.tv · GitHub

    1 Display resolution is limited to 1024x768 and below. Only 60hz frequencies available

    2 No sound (I notice on initial bootup that a "FAILED:Pulse Audio Driver not installed" message showed up. However it has not shown up since I've rebooted again. However, still no audio.

    I'll fix this with next image, which will also have proper U-Boot included.

    Image will have at least two issues - no wifi and no ethernet. I will fix ethernet after I receive my box, but wifi will be hard. Apparently, there are two variants of the box. One with Realtek SDIO wifi module with no open source drivers and another one with PCIE wifi module. PCIE on H6 is quirky and driver may never be properly included in mainline Linux.

    ukmark62 That seems fine.

    Are following lines continuously being repeated or they stop after some time?

    [  OK  ] Started Kodi Media Center.

    [  OK  ] Stopped Kodi Media Center.

    If not, are you sure you correctly identified TX pin?

    One thing you can try at this point is to recreate SD card. Burn image again, overwrite U-Boot and fix DT before first boot. It's possible that something was stored at first boot which doesn't match anymore, like board name.