yeah, it might be issue with pastebin service.
Posts by jernej
-
-
No, it's Armbian, so this should go to their forums and board Orange Pi Zero is not supported here (too little RAM).
-
Fortunately, I also have OrangePi 3
I tested with fresh installation and overlays work. Try to flash latest nightly image to spare card and see if it changes anything.For reference, my extlinux.conf:
CodeLABEL LibreELEC LINUX /KERNEL FDT /sun50i-h6-orangepi-3.dtb FDTOVERLAYS /overlays/sun50i-h6-i2c0.dtbo /overlays/sun50i-h6-i2c2.dtbo APPEND boot=UUID=2204-3027 disk=UUID=c1742531-5dac-434c-8390-f1decb06f821 quiet console=ttyS0,115200 console=tty1NOTE: Your UUIDs will be different.
If that doesn't work, then I have no idea.
-
Correct, nightly releases still follow LE10, which uses 5.10
-
Can you please specify in what sense isn't correct?
I have no clue, but it obviously doesn't work.
I wrote two overlays for I2C0 and I2C2 like so http://ix.io/2WSc (and same for I2C2). Then I included them to extlinux.conf like so FDTOVERLAYS /overlays/sun50i-h6-i2c0.dtbo /overlays/sun50i-h6-i2c2.dtbo. Now I have:
CodeLibreELEC:~ # i2cdetect -l i2c-3 i2c DesignWare HDMI I2C adapter i2c-1 i2c mv64xxx_i2c adapter I2C adapter i2c-2 i2c mv64xxx_i2c adapter I2C adapter i2c-0 i2c mv64xxx_i2c adapter I2C adapterNote - this is on PineH64 model B, but I don't see any reason why it wouldn't work on OPi3.
Binary version of overlays: Index of /overlays/
-
well, there you have it - overlay you're using isn't correct - it shouldn't freeze during boot and you should get additional i2c bus listed. What is wrong with it - I don't know. From what I can see, seems good.
-
There is no other i2c port on the GPIO header
All three are there, just pins are named differently. I2C1 is on SPI1-MOSI and SPI1-MISO, I2C2 is on UART3-RX and UART3-TX and they lack pull ups, so yeah, you most probably use I2C0.
BTW, 0x36 is PMIC address. You are probing wrong bus. Make sure you have now 3 buses and probe all except HDMI.
-
Is it right ?
It is (maybe just move FTDOVERLAYS one line higher, although it shouldn't matter).
What's next ?
Are you sure your device is connected to I2C0? H6 has 3 I2C buses, 4 if you count one for PMIC. If you sure, then I don't know...
-
You have to add line FDTOVERLAYS /overlays/sun50i-h6-i2c0.dtbo to extlinux.conf. I'm a bit lazy regarding documentation...
-
You have to enable I2C bus in DT. Easiest way is to add overlay. I believe Armbian enables I2Cs using patch during kernel build.
It doesn't look like we include the linux driver (CONFIG_HD44780)
That one supports only parallel interface.
-
Allwinner H6 has tonemapping functionality in display pipeline, but it's not implemented yet. There are other issues to be solved first.
-
Please explain wether I can continue to install nightly updates on that image you made with some output, or should I better format and do a clean install?
The only difference between my test image and nightly from that day are just two lines of debug output. You can treat them same. Clean install is recommended every now and then, when bootloader is updated.
Monoscopic mode not working? Although I select it, it has no effect.
I'm not even sure what it does. Something with 3D mode? If so, that's completely untested and unlikely it will get better anytime soon. I have no 3D display nor do I plan to obtain it.
-
I'll rebuild and test it at next beta.
-
In other words it's very like as the hardware is not capable to hold that stress load during such moments...
Nope, that's not it. In short, driver is fed by invalid data, which cause instability. Why invalid data is sent is another story, but anyway, driver should react properly on such frames. Fixing that is not straightforward due to some HW quirks. Be patient, it's my intention to solve it, but I can't give you any timeline.
-
Have I done something wrong?
Nope, exactly what I was looking for. Same issue as I have with my corrupted sample. Problem is that I'm not sure how to fix it. Today I tried few things with my sample but none worked.
-
levitsky86 test this update LibreELEC-H3.arm-10.0-devel-20210415204648-8f3d105-h264-diag.tar and provide dmesg output after issue is observed. I added some output which would explain what's wrong.
-
levitsky86 Can you confirm that streams use H264 codec (press "o" during playback)? If it possible, try seeking for few seconds back or forward. I have one H264 sample with broken frame which cause similar issue and picture is fixed only when seeking back or forward...
Timpanogos Slim No worries.
-
7.6.0.1 seems good.
