Learnincurve

Members
  • Content Count

    104
  • Joined

  • Last visited

Everything posted by Learnincurve

  1. Closer again. I'm now using the latest "Armbian Focal mainline based kernel 5.8.y" image, including the updated dtb .deb update. I have modified the dtb, changing the dsi section to "okay", and adding the vcc-dsi line and the feiyang panel subsection. This is what I'm getting: dmesg | grep dsi [ 2.263813] OF: /soc/dsi@1ca0000/panel@0: could not get #gpio-cells for /soc/hdmi@1ee0000/ports/port@0/endpoint [ 2.265832] OF: /soc/dsi@1ca0000/panel@0: could not get #gpio-cells for /soc/hdmi@1ee0000/ports/port@0/endpoint [ 2.266675] OF: /s
  2. Closer: dmesg | grep dsi [ 2.179940] OF: /soc/dsi@1ca0000: could not get #phy-cells for /soc/pinctrl@1c20800/rgmii-pins [ 2.179949] sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY Looking at the pinctrl@1c20800 section, there are quite a few differences between the original and @lex's file, so not sure how much to transpose. Transposing the whole section is giving far more duplicated phandle errors, so stopping here. dtc -f -O dtb -o sun50i-a64-pine64-plus.dtb sun50i-a64-pine64-plus_EDITED.dts sun50i-a64-pine64-plus_EDITED.
  3. Here's the original file with the dsi and feiyang section transposed from @lex's .dts I'm getting ERROR (explicit_phandles): /soc/dsi@1ca0000/port/endpoint: duplicated phandle 0x1c (seen before at /soc/lcd-controller@1c0c000/ports/port@0/endpoint@1) I forced output and have a dtb. .dts file attached sun50i-a64-pine64-plus_EDITED.dts
  4. Hmm... I do see quite a few differences in the two decompiled dts files. Will try to locate only the blocks affecting DSI /feiyang touch etc, as I don't dare just swap out the whole file. both .dts's attached sun50i-a64-pine64-plus_ORIG.dts sun50i-a64-pine64+_MIPI.dts
  5. Hi @lex and thank you for responding! I do have a 2GB Pine64+, so would be very interested to take a look at your .dtb If you could make it available on/to this thread that would be really great! My guess is that is should also work with the latest kernel. BR. --Marius--
  6. Anyone have this working yet? I see there are new images in "archive", but no dtbo overlay.
  7. So I finally tried installing the latest 5.4.43 build from Armbian. I applied your overlay, compiled and loaded from armbianEnv.txt and added the setenv video-mode sunxi:1024x600,monitor=lcd,hpd=0,edid=1 line. For me, the backlight works, but nothing else does. I decompiled the /boot/dtb/allwinner/sun50i-a64-pine64.dtb file, changed the dsi@1ca0000 { compatible = "allwinner,sun50i-a64-mipi-dsi"; reg = <0x1ca0000 0x1000>; interrupts = <0x00 0x59 0x04>;
  8. Just looking at Gavinb's latest commit. He is compiling the panel and dsi code into the kernel, instead of loading as modules. https://github.com/GavinBa/build/commit/73850d2db3814418d865304befd2afb370865f6c Perhaps that is a solution?
  9. Not really. I was just wondering whether it was an xorg issue, but if the message is from uboot, then you are right that something is wrong at a deeper level. Guess we'll just have to wait a little longer. Despite reading the Armbian Documentation many times, I'm still really hazy about applying the uboot video mode options: Cheers!
  10. Does the screen display anything when it intitialises, early in the uboot process, or is garbage the first thing you see? Also, do you see anything in the xorg logs that would give you more information?
  11. I'm suprised if the driver is buggy as it is in mainline. Did you just load the builtin driver or did you compile Jagan's from C? If you compiled, that could be the problem. BR.
  12. Gavinb has added DT patches (for sopine) at https://github.com/GavinBa/build/tree/Pine64-V5.4_MIPI_DSI/patch/kernel/sunxi-current You might want to look at the changes to see if anything is missing from your DT.
  13. Tried, and failed to send this yesterday: Well done! Sounds like you're making real progress now. Regarding the Feiyang, that driver is now included as a kernel module, so it should be enough to make sure it's loaded. The default resolution is a bit weird. 1024x600 if memory serves me right. I've no idea about the timings tho'. I'm guessing, that as this is now mainline, that the modeline, once we know what it is, can be set in xorg, or maybe needs to be specified as part of the kconfig video mode settings at https://docs.armbian.com/Hardware_Allwinner/ I'm a bit busy today, b
  14. Just a guess, but do you see any more in the device tree referencing vcc-dsi. Could it be that the voltages are not being set?? Regarding the panel, it's a Feiyang FY07024DI26A30-D DSI panel. Do you see any references to that?
  15. Could you send the content of the "/boot/dtb/allwinner/sun50i-a64-pine64.dtb" file? Could be that you need to do something from https://docs.armbian.com/User-Guide_Allwinner_overlays/ ? I don't think earlier versions of that file contained any reference to sun50i-a64-mipi-dsi". If there's no equivalent .dtbo file, that might indicate that the overlay is still a work in progress. Have you grepped dmesg for any mention of DSI? Cheers!
  16. Has anyone tries the new, 5.4.40 or 5.6.8 (dev branch) nightly builds and seen whether they contain the DT bindings for DSI? I have flashed my SD so many time's that I don't want to keep doing it (on the offchance). On the other hand, if the bindings are now there...
  17. So if you have the overlay from your previous sopine build , could you just attach it here so we could test? I'd be happy to do that, as I have a working 5.6 build (apart from the device tree).
  18. Fantastic news Gavinb! Thank you very much! I'm sorry I haven't been of any help regarding creating the overlay myself. Will the overlay be available for the pine64+ as well as the sopine64?
  19. Hi, If you want to compile, just follow the instructions at https://docs.armbian.com/Developer-Guide_Build-Preparation/ but it shouldn''t be necessary, as Armbian 20.05 will use it and the nightly builds already contain it. The problem is not the kernel, but the device tree bindings (DTB), which has been fixed for MIPI-DSI for the Pine64so (in this thread), but I still haven't figured out how to do it for the pine64+ and don't know if it is taken care of in the nightly builds or the sources. If it is, I still haven't figured out how to enable it at boot t
  20. Thanks Gavinb, That's a good Easter project. As I don't know my way around the sources very well, can you tell me which files(s) tool look for? Thanks very much!
  21. I'm going to have to go through Gavinb's changes and see what needs applying to the Pine64 base build.