• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by Learnincurve

  1. 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>; clocks = <0x02 0x1c>; resets = <0x02 0x05>; phys = <0x41>; phy-names = "dphy"; status = "disabled"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x84>; port { endpoint { remote-endpoint = <0x42>; phandle = <0x1e>; }; }; }; section to dsi@1ca0000 { compatible = "allwinner,sun50i-a64-mipi-dsi"; reg = <0x1ca0000 0x1000>; interrupts = <0x00 0x59 0x04>; clocks = <0x02 0x1c>; resets = <0x02 0x05>; phys = <0x41>; phy-names = "dphy"; status = "enabled"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x84>; port { endpoint { remote-endpoint = <0x42>; phandle = <0x1e>; }; }; }; I couldn't find any other references in that file and recompiled it. dmesg | grep dsi lists nothing, while dmesg | grep mipi [ 3.505719] vcc-mipi: Bringing 2900000uV into 3300000-3300000uV [ 6.603912] Modules linked in: cpufreq_dt zram sch_fq_codel g_serial libcomposite ip_tables x_tables autofs4 realtek axp20x_usb_power pinctrl_axp209 axp20x_regulator phy_sun6i_mipi_dphy dwmac_sun8i mdio_mux i2c_mv64xxx pwm_bl and dmesg | grep display root@pine64:~# dmesg | grep drm [ 5.394228] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. I also tried adding feiyang_fy07024di26a30 and sun6i_mipi_dsi to /etc/modules. with same result.
  2. 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?
  3. 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!
  4. 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?
  5. 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.
  6. 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.
  7. 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, but will try to take a look when I can.
  8. 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?
  9. 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!
  10. 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...
  11. 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).
  12. 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?
  13. 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 time. I hope that someone can explain that in this thread, as pretty much everything we need is now in the mainline kernel.
  14. 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!
  15. I'm going to have to go through Gavinb's changes and see what needs applying to the Pine64 base build.
  16. So I do see one mistake, I've been compiling for Pine64, but I see that the patched build is for Pine64SO. I updated the configs with pine64_lcd=on and am trying again.
  17. This didn't work either. I must be missing something really simple as Gavinb said this should just work out of the box. One possibility is that Windwoes is still getting in my way, as even with the vagrantfile tweak, the config-default.conf symlink is not being created and I have to manually copy the example file. Another is that after reading the developer guide I am still simply missing something that si so obvious that it is expected that all armbian builders should simply know it, and not be so stupid as to leave it out?? I find the generic documentation for getting the LCD monitor working from mainline allwinner builds quite confusing: First "U-Boot supports HDMI and LCD output on Allwinner sunxi SoCs, LCD output requires the CONFIG_VIDEO_LCD_MODE Kconfig value to be set." - Does this need to be done in the build environment config file and in addition to changes to uboot which can be made in the running system from the armbian-config utility?/boot.cmd file? - from the running 3.10 (legacy) system, I see that the mode is FBDEV(0): Virtual size is 1024x600 (pitch 1024) [ 9.811] (**) FBDEV(0): Built-in mode "current": 55.0 MHz, 35.7 kHz, 56.2 Hz [ 9.811] (II) FBDEV(0): Modeline "current"x0.0 55.00 1024 1420 1440 1540 600 612 614 635 -hsync -vsync -csync (35.7 kHz b) Should I set this in boot.cmd like so: setenv video-mode sunxi:1024x600@56.2,monitor=lcd ? saveenv or at compile time in config-default.conf, like: CONFIG_VIDEO_LCD_MODE="x:1024,y:600 ... ??? (not sure how to set the rest of these parameters. there's also a file in the config/bootenv directory called pine64-fdefault.txt , containing verbosity=1 console=both disp_mode=720p60 camera_type=none pine64_lcd=off surely that last line needs to be changed to pine64_lcd=on BR.
  18. I'm trying to follow exactly karlitos' steps now. Downloaded whole gavinb repo and building against the build-9-a64-dsi branch. Possible that the build was wrong first time round.
  19. Built full desktop environment from Gavinb's build-9-a64-dsi branch (only downloaded that specific branch). Board boots, I added the user and rebooted, but nothing. Added monitor=lcd to end of uboot environment file using armbian-config and added saveenv to boot.cmd -> recompiled boot.scr. Still black screen and # dmesg | grep sun4i [ 2.273463] sun4i-usb-phy 1c19400.phy: failed to get clock usb0_phy [ 2.505354] sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff800010bde840) [ 2.506971] sun4i-drm display-engine: bound 1200000.mixer (ops 0xffff800010bde840) [ 2.507338] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 2.507349] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xffff800010bdad40) [ 2.507555] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xffff800010bdad40) [ 2.507628] sun4i-drm display-engine: failed to bind 1ee0000.hdmi (ops 0xffff800010bddbe8): -517 [ 2.507939] sun4i-drm display-engine: Couldn't bind all pipelines components [ 2.508055] sun4i-drm display-engine: master bind failed: -517 [ 2.701844] sun4i-drm display-engine: bound 1100000.mixer (ops 0xffff800010bde840) [ 2.703439] sun4i-drm display-engine: bound 1200000.mixer (ops 0xffff800010bde840) [ 2.703825] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 2.703836] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xffff800010bdad40) [ 2.704033] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xffff800010bdad40) [ 2.705824] sun4i-drm display-engine: bound 1ee0000.hdmi (ops 0xffff800010bddbe8) [ 2.706137] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 0 no mention of DSI. Can anyone say what I've missed? BR.
  20. I'm still trying to get it working using the mainline images and images (mainline) built from trunk. The Teki patches seem to be applied, so I'm guessing all that is needed is a configuration of the boot environment. Trying to follow the generic allwinner instructions, adding monitor=lcd in armbian-config, adding saveenv to boot.cmd and recompiling, but sun6i_mipi_dsi is not loading and lcd monitor is black. Wondering whether to start with Gavinb's build, then update to latest and greatest kernel.
  21. It looks like the mipi-dsi patch is now in the default build script at https://github.com/armbian/build I'm now building a standard image based on that script and will try it with the LCD screen when I get a chance. @ any other windows sufferers out there, you might need to add the following block to your Vagrantfile to allow symlinks to work: config.vm.provider "virtualbox" do |v| v.customize ["setextradata", :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate/v-root", "1"] end
  22. Cool! No tweaking to armbianEnv.txt then?
  23. That's good news! Probably the instructions at https://www.armbian.com/pine64/ aren't valid for the mainline mipi-dsi kernel module and you'll either have to tweak the script that reads armbianEnv.txt or load the modules and configure x manually. I'm guessing that that should be much more straightforward now that the standard mechanisms are in place and you can disable the allwinner-specific way of doing it with the 3.11 kernel., but someone else will need to advise you on that. I'm going to hang on now, as 5.6-rc1 is already out and it can't be long until we have a mainline image including the dsi stuff.... although it is hard to wait!