sunwellQplus
Which RAM type has it? DDR3? If so, you'll have to wait a bit. Currently there is an effort to add H6 DDR3 support in U-Boot.
sunwellQplus
Which RAM type has it? DDR3? If so, you'll have to wait a bit. Currently there is an effort to add H6 DDR3 support in U-Boot.
supportvem Can you provide detailed logs? Currently I don't have much time to work on that.
boatfreak Currently there is no support for DT overlays to enable additional functionality like hats you linked. Hopefully I'll have time to add support for them soon. I'm also not sure if there is appropriate driver for stereo audio DAC board. Regarding bluetooth/wifi module, I suggest you use something else, Realtek drivers are pain to maintain and we will probably stop supporting them in near future. Use non-Realtek USB dongles instead.
Gatuno I merged your PR, thanks! Nightly builds for OrangePi 3 should be available soon. I think build machine was fixed today.
How do you find those differences? I mean compared to what?
To decompiled libdram, which we know it correctly initializes DDR3, but it's not acceptable solution for many reasons.
Just to be sure - I am reverting the previously applied patch before applying the new one. Is that correct?
That's correct. I include all changes in new patch.
In latest one I found out that 2T bit was enabled only in controller and not in PHY. I hoped this is solution, but obviously not.
If anyone wonder, this is the closest documentation we have: Zynq UltraScale+ MPSoC Register Reference (DDRC and DDR_PHY modules) It's not 100% same, but close enough.
ukmark62 I found few differences. Can you please test http://sprunge.us/pcxdsq ? I promise I'll wait for my own box for next test.
I referred balbes150 to post #31 in this thread. AFAIK that branch does not use libdram.
Yes, that's fine.
Now I'm thinking of buying one of those DDR3 boxes just for sake of working with DRAM driver (and later LE support).
What do you hope to see?
DRAM size should be printed and execution should continue.
ukmark62 Can you please test this patch? http://sprunge.us/f0y8yf
I rebased a20 at branch GitHub - jernejsk/LibreELEC.tv: Just enough OS for KODI on top on master and adjusted config.
Are the nightlies still not working properly?
Yes, troubles with build machine.
Note, I moved Tanix TX6 talk to Tanix TX6
ukmark62 Can you try this patch if it helps? http://sprunge.us/7jcinx
Simply_Kot Can you narrow the problem a bit? Is this issue present on all H264 1280x720 videos or only on some or only on one you have?
I'm testing the Orange PI 3 image and still has the "ethernet reboot issue". I understand that this is a 'known bug'.
Which image? the one I linked? if yes, then yeah, that image still has that issue. However, if you build your image from source, it should work.
In other things, I would be very useful for orange pi 3 if you could add "mmc2" definition in the device tree for u-boot loader. This could allow the image to be "dumped" directly to the integrated emmc. I understand that there is not official support for "dumping" the image yet, but, useful.
In the current testing image, the emmc is not listed at /dev (usually named mmcblk2).
It would be best to add them to U-Boot and Linux kernel (not the same DT files are used for now). You can make pull request against Libreelec master with necessary updates to opi3 patches.
Thanks - I've done a basic test, and the image seems to work at least as well as the early build.
Ok, thanks for testing, I'll ask for nightly builds. I'll ask for OrangePi 3 too (I know you are not interested in that board, but just for public note).
IR driver is already enabled. What is missing is patch set which enables IR on H6 and A64 and will be merged soon. I'm just waiting for that to happen. That way I'm sure I don't need to update patches later.
What would be the next step for me to do? Thx.t
Now the fun begins. First of all, make a backup of those binaries, they will be useful to check out register values at later time. Better yet, make another clone of that git repository in another folder, like this:
git clone https://github.com/apritzel/u-boot.git u-boot-dram-wip
go into that folder and execute:
Important, you need 64-bit ARM GCC for that, including correct CROSS_COMPILE value.
Now you will have U-Boot with work in progress H6 DDR3 driver. Building instructions still applies here, except that libdram is no longer used. This code is just few commits back from libdram one.
We will have to fix arch/arm/mach-sunxi/dram_sun50i_h6.c and arch/arm/mach-sunxi/dram_timings/h6_ddr3_1600.c .
This is also perfect time to get familiar with our primary sources of information for this job. File arch/arm/include/asm/arch-sunxi/dram_sun50i_h6.h has a lot of useful references to similar DRAM controllers with documentation available. It would be useful to obtain a copy of pdf or find a web page with docs.
So from now on it's modify above files, build new U-Boot, flash it on SD card and test if it helps anything. Standard debug practice is to add printf(), so you can see final register values and compare to the working ones from libdram version.
I will help you with ideas what to change based on reverse engineering libdram and looking what it does for DDR3.
BTW, I'll ask moderators to split this conversation to a new thread.
Problem: Image freezes on rewind. Sometimes sound after it still playing sound.
Only solution is stoping video and play it again.
Can you please tell me what is the resolution of your video and which codec is used? Press "o" during playback to get that info. Is this happening also with other videos with same resolution and codecs?
It mentions RAM of 2gb in the log, should that not be 4gb? The box is 4gb ram and 64gb rom (or supposed to be).
H6 only supports 3 GiB of memory, so if you have it 4 GiB on board, you should see 3 GiB reported in U-Boot.
There are two possible reasons why you see 2 GiB reported:
1. libdram supports only power of two sizes
2. Eachlink board has only 2 GiB of RAM and there is a hack for that.
In any way, when DDR3 support will be fixed, you should see 3 GiB reported.