<![CDATA[PINE64 - LCD and Touch Panel]]> https://forum.pine64.org/ Sat, 18 Apr 2026 11:59:44 +0000 MyBB <![CDATA[LCD 7" Pine64 own not working with pine64 A64 board]]> https://forum.pine64.org/showthread.php?tid=19648 Mon, 27 Jan 2025 16:51:21 +0000 HL3D]]> https://forum.pine64.org/showthread.php?tid=19648
my first expirience with Pine64 I buy 3 boards and 3 LCD but nothing work the kernel dmesg |grep mipi tell: vcc-mipi: disabling. I don't know to solve this.

Please help me.

Thanks for all reply

Andrea Manca]]>
my first expirience with Pine64 I buy 3 boards and 3 LCD but nothing work the kernel dmesg |grep mipi tell: vcc-mipi: disabling. I don't know to solve this.

Please help me.

Thanks for all reply

Andrea Manca]]> <![CDATA[Is there a screen for the Rockchip RK3399 that works with FreeBSD out of the box ?]]> https://forum.pine64.org/showthread.php?tid=19504 Sun, 10 Nov 2024 08:06:09 +0000 ziomario]]> https://forum.pine64.org/showthread.php?tid=19504
I want to assemble some kind of tablet powered by FreeBSD. The main electronic components of this tablet that I've bought or that I want to buy in the next future are the following :

1) soc = RockPro64 (Rockchip RK3399 hexa-core SoC) : already bought

2) this enclosure : (already bought)

https://ameridroid.com/products/pine64-p...eq=uniform

3) these batteries : https://www.ebay.com/itm/315203768497 ---> not yet bought

Since I want to create a "tablet" that will be powered by FreeBSD,I need an USB display that does NOT requires any driver to work and the size should fit with the enclosure at point 2 that I like ; because I'm not a programmer, I will be not able to make the porting of a driver from Linux to FreeBSD. I also would like to reuse the screen for different projects,so it is great if it can be powered and work only connecting the HDMI cable from the screen to the soc.

Can someone suggest to me one ? thanks.]]>
I want to assemble some kind of tablet powered by FreeBSD. The main electronic components of this tablet that I've bought or that I want to buy in the next future are the following :

1) soc = RockPro64 (Rockchip RK3399 hexa-core SoC) : already bought

2) this enclosure : (already bought)

https://ameridroid.com/products/pine64-p...eq=uniform

3) these batteries : https://www.ebay.com/itm/315203768497 ---> not yet bought

Since I want to create a "tablet" that will be powered by FreeBSD,I need an USB display that does NOT requires any driver to work and the size should fit with the enclosure at point 2 that I like ; because I'm not a programmer, I will be not able to make the porting of a driver from Linux to FreeBSD. I also would like to reuse the screen for different projects,so it is great if it can be powered and work only connecting the HDMI cable from the screen to the soc.

Can someone suggest to me one ? thanks.]]> <![CDATA[7 inch LCD touch panel is upside down?]]> https://forum.pine64.org/showthread.php?tid=16060 Fri, 11 Feb 2022 21:47:35 +0000 joshpl]]> https://forum.pine64.org/showthread.php?tid=16060
I've purchased few years ago (actually, 5 years ago!) PineA64+ with 2GB RAM.
Tried to use it with one project, but didn't work as I wanted so I've dumped it.

Recently I was looking for some touchscreen device for few tasks (running an IVMS android app to see CCTV cameras), and just found this old board. After connecting - everything worked fine.
I've decided to buy a LCD touchscreen (since I've tried with some USB-based monitors with touchscreen and they were not supported), but it seemed it's out of stock. However... it occured, that a local company had this exact item - last one, just waiting for me Wink I was thrilled and ordered it.

At first - I was warried: ribbons were so fragile, and I had completely no idea if I'm connecting them correctly. Especially, that when I turned power on - nothing happened at all. Then I discovered that you need to have one of dedicated LCD disk images. Downloaded, ran - yeah, screen works!

But then... a BIG disappointment: touch screen does not work! I tried connecting TP ribbon again, but suddenly the touch input seemed to SOMEHOW react.

After a short investigation - I saw what's going on: the touch input is completely flipped upside down!
When I touch screen in top left corner - system reacts, as if I have touched it in bottom right! Swiping my finger from top left to top right corner is read as swiping from bottom right to bottom left!  Confused

What is going on? I was looking for some settings in screen, display, input section... but couldn't find anything that would help me Sad
Is it some problem with the disk image I've downloaded (3.2.2 Stock Android 6.0.1 (LCD Panel Video Output) [20170209] from official pine64 wiki)? Or is it something physical, like something went wrong during the assembly of the screen? I even thought that I might try taking the screen out from its case and flipping it 180 degrees, but the ribbons are glued to the back of the screen and I'm afraid I would damage them. Nevertheless, the back of the screen looks correct - I mean, the ribbons seem to be placed correctly when I compare it to the PDF manuals that show how to connect the screen.

May it be, that I have connected something wrong? How come? The ribbon cable seems to have contact points only on one side, so connecting it upside down would rather result in having completely no output, right? And, even if - probably forcing other connection would mess up the signal and DC pins, with baked LCD as effect.

Any help? Maybe there's some other option? I was searching for anyone having such problem, but seems like I'm the only one...

Greetings,
-- 
Jacek]]>
I've purchased few years ago (actually, 5 years ago!) PineA64+ with 2GB RAM.
Tried to use it with one project, but didn't work as I wanted so I've dumped it.

Recently I was looking for some touchscreen device for few tasks (running an IVMS android app to see CCTV cameras), and just found this old board. After connecting - everything worked fine.
I've decided to buy a LCD touchscreen (since I've tried with some USB-based monitors with touchscreen and they were not supported), but it seemed it's out of stock. However... it occured, that a local company had this exact item - last one, just waiting for me Wink I was thrilled and ordered it.

At first - I was warried: ribbons were so fragile, and I had completely no idea if I'm connecting them correctly. Especially, that when I turned power on - nothing happened at all. Then I discovered that you need to have one of dedicated LCD disk images. Downloaded, ran - yeah, screen works!

But then... a BIG disappointment: touch screen does not work! I tried connecting TP ribbon again, but suddenly the touch input seemed to SOMEHOW react.

After a short investigation - I saw what's going on: the touch input is completely flipped upside down!
When I touch screen in top left corner - system reacts, as if I have touched it in bottom right! Swiping my finger from top left to top right corner is read as swiping from bottom right to bottom left!  Confused

What is going on? I was looking for some settings in screen, display, input section... but couldn't find anything that would help me Sad
Is it some problem with the disk image I've downloaded (3.2.2 Stock Android 6.0.1 (LCD Panel Video Output) [20170209] from official pine64 wiki)? Or is it something physical, like something went wrong during the assembly of the screen? I even thought that I might try taking the screen out from its case and flipping it 180 degrees, but the ribbons are glued to the back of the screen and I'm afraid I would damage them. Nevertheless, the back of the screen looks correct - I mean, the ribbons seem to be placed correctly when I compare it to the PDF manuals that show how to connect the screen.

May it be, that I have connected something wrong? How come? The ribbon cable seems to have contact points only on one side, so connecting it upside down would rather result in having completely no output, right? And, even if - probably forcing other connection would mess up the signal and DC pins, with baked LCD as effect.

Any help? Maybe there's some other option? I was searching for anyone having such problem, but seems like I'm the only one...

Greetings,
-- 
Jacek]]> <![CDATA[What other devices can the LCD screen work on?]]> https://forum.pine64.org/showthread.php?tid=8339 Fri, 15 Nov 2019 22:35:06 +0000 kodachrome]]> https://forum.pine64.org/showthread.php?tid=8339
What else is it compatible with (and/or touch support too)?]]>
What else is it compatible with (and/or touch support too)?]]> <![CDATA[LCD on Pine 64+: my experience (or DO NOT BUY)]]> https://forum.pine64.org/showthread.php?tid=8079 Mon, 14 Oct 2019 07:34:11 +0000 NexusDude]]> https://forum.pine64.org/showthread.php?tid=8079
My Pine64+ is the kickstarter version with 2gb ram. Due to lack of spare cash when I first got the Pine64, I've tried to do this on-the-cheap, by buying unofficial accessories and (trying to) get them to work with the Pine64. Due to challenges with getting non-Pine64-sold WiFi to work, I ended up getting the official WiFi from Pine64.org, and assumed that would go a lot easier (it did), and assumed the same of the LCD touchscreen panel (it very much did not). I also got the 5MP camera. (Jury is still out on that.)

My Pine64 has gathered dust, mostly, and run BOINC some, and I've tried various OS's. My dream, however, is to get a working "Kitchen Computer" that will track various household things, fairly distribute chores to household members, show & edit Google calendar items for the family, edit our individual to-do's, birthdays, track taking meds, feeding the pets, if it's a recycle/bulky-trash/trash day, how long it's been since something got changed (A/C filter, oil filters), and so on. Google and Amazon have since developed similar ideas, but my dream idea (which has similarly gathered dust) is something that I can program myself, and can excel in ways that the lame, pathetic, limited-imagination programmers of Google & Amazon & their users would never dream or at least bother to do (well).

For years (?), I've known that the official (Pine64-sold) LCD touchscreen panel is a steal, compared to RasPi, etc. What I didn't know was why it was so inexpensive (or who was doing the stealing). 

The LCD arrived along with the WiFi and camera. I noticed that the 7" LCD touchscreen has a slot for a camera to go in, but the Pine64 5MP camera is much too big to fit. (Could you make it fit, somehow?) I decided to get them working one at a time, the WiFi first. It was pretty much a no-brainer. Then the LCD. Nothing. Black screen.

I vaguely remembered there being separate Pine64 images for HDMI and LCD output. So I researched into that, and was greatly disappointed in the support of the community for something I thought that (surely, by now) would be supported: the original Pine64+ running some form of Linux with the LCD touchscreen.

(Could you get a non-standard touchscreen, with matching ribbon connections?)

The research came up with:
  • modsbyus.com has a working Armbian image that used the LCD screen and touch interface
  • earlier (standard Pine64) versions of Armbian worked with the LCD with tweaks to a text file (/boot/armbianEnv.txt), at least for some
  • Some buyers of the 7" LCD have accidentally rendered it trash, by tearing a ribbon connection on it. I vowed that this would not occur to me and my precious LCD.
An official image is naturally preferable, since it is more likely to be kept going in the future, and less likely to have little errors, important omissions or even intentional trickery hidden in it.

The problem is that the current, standard images of Pine64 Armbian desktop do not work with the LCD. You have to find an earlier version, up to _______.___. And good luck finding that. You could ask the community. I know I've occasionally downloaded an image for my Pine64 over the years, and never used it.

So I took the risk, and tried modsbyus.com Armbian. It worked. The LCD screen was working! The touchscreen interface was fine. Joy!

That is, it worked after a sort. When I tried to connect to my WiFi, up popped a password request that wasn't asking for my WiFi password, nor asking for the credentials that modsbyus.com had already supplied.

During the next little delay, while I went back to seeing if any of the images of Armbian I had would work with the LCD, I discovered that the fragile ribbon connector had somehow torn, despite my efforts to treat it all very gingerly.

You can scoff all you want at my lack of research into the LCD before I purchased it. Perhaps I deserve that.

If you want to use the LCD with Android, it will. But I would disconnect the LCD from the Pine after each use, until you're ready to put it in an enclosure. That main ribbon cable may seem sturdy enough at first, but it can tear VERY easily.

My LCD is now in the trash, and you all have my dream idea to do with, as you will. But I know that my ideas for programming it would have been ideal, at least for me and my household.]]>
My Pine64+ is the kickstarter version with 2gb ram. Due to lack of spare cash when I first got the Pine64, I've tried to do this on-the-cheap, by buying unofficial accessories and (trying to) get them to work with the Pine64. Due to challenges with getting non-Pine64-sold WiFi to work, I ended up getting the official WiFi from Pine64.org, and assumed that would go a lot easier (it did), and assumed the same of the LCD touchscreen panel (it very much did not). I also got the 5MP camera. (Jury is still out on that.)

My Pine64 has gathered dust, mostly, and run BOINC some, and I've tried various OS's. My dream, however, is to get a working "Kitchen Computer" that will track various household things, fairly distribute chores to household members, show & edit Google calendar items for the family, edit our individual to-do's, birthdays, track taking meds, feeding the pets, if it's a recycle/bulky-trash/trash day, how long it's been since something got changed (A/C filter, oil filters), and so on. Google and Amazon have since developed similar ideas, but my dream idea (which has similarly gathered dust) is something that I can program myself, and can excel in ways that the lame, pathetic, limited-imagination programmers of Google & Amazon & their users would never dream or at least bother to do (well).

For years (?), I've known that the official (Pine64-sold) LCD touchscreen panel is a steal, compared to RasPi, etc. What I didn't know was why it was so inexpensive (or who was doing the stealing). 

The LCD arrived along with the WiFi and camera. I noticed that the 7" LCD touchscreen has a slot for a camera to go in, but the Pine64 5MP camera is much too big to fit. (Could you make it fit, somehow?) I decided to get them working one at a time, the WiFi first. It was pretty much a no-brainer. Then the LCD. Nothing. Black screen.

I vaguely remembered there being separate Pine64 images for HDMI and LCD output. So I researched into that, and was greatly disappointed in the support of the community for something I thought that (surely, by now) would be supported: the original Pine64+ running some form of Linux with the LCD touchscreen.

(Could you get a non-standard touchscreen, with matching ribbon connections?)

The research came up with:
  • modsbyus.com has a working Armbian image that used the LCD screen and touch interface
  • earlier (standard Pine64) versions of Armbian worked with the LCD with tweaks to a text file (/boot/armbianEnv.txt), at least for some
  • Some buyers of the 7" LCD have accidentally rendered it trash, by tearing a ribbon connection on it. I vowed that this would not occur to me and my precious LCD.
An official image is naturally preferable, since it is more likely to be kept going in the future, and less likely to have little errors, important omissions or even intentional trickery hidden in it.

The problem is that the current, standard images of Pine64 Armbian desktop do not work with the LCD. You have to find an earlier version, up to _______.___. And good luck finding that. You could ask the community. I know I've occasionally downloaded an image for my Pine64 over the years, and never used it.

So I took the risk, and tried modsbyus.com Armbian. It worked. The LCD screen was working! The touchscreen interface was fine. Joy!

That is, it worked after a sort. When I tried to connect to my WiFi, up popped a password request that wasn't asking for my WiFi password, nor asking for the credentials that modsbyus.com had already supplied.

During the next little delay, while I went back to seeing if any of the images of Armbian I had would work with the LCD, I discovered that the fragile ribbon connector had somehow torn, despite my efforts to treat it all very gingerly.

You can scoff all you want at my lack of research into the LCD before I purchased it. Perhaps I deserve that.

If you want to use the LCD with Android, it will. But I would disconnect the LCD from the Pine after each use, until you're ready to put it in an enclosure. That main ribbon cable may seem sturdy enough at first, but it can tear VERY easily.

My LCD is now in the trash, and you all have my dream idea to do with, as you will. But I know that my ideas for programming it would have been ideal, at least for me and my household.]]> <![CDATA[DSI mainline branches]]> https://forum.pine64.org/showthread.php?tid=7911 Wed, 28 Aug 2019 17:07:29 +0000 fpoussin]]> https://forum.pine64.org/showthread.php?tid=7911
I've been working on DSI to use my panel with the Sopine but I wanted a mainline kernel.

I've used the patches from the amarula fork (this) and rebased them on latest stable/rc versions, plus a few fixes. These are supposed to go upstream at some point.

[Image: image0.jpg]

You can find the 5.2.x code here

Let me know if that works with other panels.]]>
I've been working on DSI to use my panel with the Sopine but I wanted a mainline kernel.

I've used the patches from the amarula fork (this) and rebased them on latest stable/rc versions, plus a few fixes. These are supposed to go upstream at some point.

[Image: image0.jpg]

You can find the 5.2.x code here

Let me know if that works with other panels.]]> <![CDATA[LCD Troubleshooting Help]]> https://forum.pine64.org/showthread.php?tid=7458 Sun, 05 May 2019 18:57:05 +0000 k0mxl]]> https://forum.pine64.org/showthread.php?tid=7458
Apparently I'm not using the correct terms to search the forums or something, because in my quest to RTFM, I can't even FIND TFM, so I'm going to try the direct approach.

In order to determine whether I'm dealing with a hardware issue (i.e. the LCD itself, or the connections), or a software / OS issue, I'd appreciate it if someone would please answer the following questions:

How do I determine if the LCD is connected properly?  I see no activity - not even the backlight - during boot.

Are there voltages that can be measured with a DVOM on the ribbon connector that will tell me if the LCD is receiving power from the board?

Should I be seeing some indication of the LCD being detected in dmesg if booting Armbian?

Is there a current image that automatically detects and supports the LCD with or without touchscreen?  

Put another way, what current images - of any type,  Linux, Android, or other - support the LCD with little or no tweaking required?  

I've tried the most recent Armbian Linux images, editing armbianEnv.txt as directed, and I've tried what I think are the most current Android 7 and 6 images but I'm not sure I've made the correct changes in the (name escapes me at the moment) config file.


Constructive suggestions and help appreciated...flames can be directed to /dev/null.

Thank you.]]>
Apparently I'm not using the correct terms to search the forums or something, because in my quest to RTFM, I can't even FIND TFM, so I'm going to try the direct approach.

In order to determine whether I'm dealing with a hardware issue (i.e. the LCD itself, or the connections), or a software / OS issue, I'd appreciate it if someone would please answer the following questions:

How do I determine if the LCD is connected properly?  I see no activity - not even the backlight - during boot.

Are there voltages that can be measured with a DVOM on the ribbon connector that will tell me if the LCD is receiving power from the board?

Should I be seeing some indication of the LCD being detected in dmesg if booting Armbian?

Is there a current image that automatically detects and supports the LCD with or without touchscreen?  

Put another way, what current images - of any type,  Linux, Android, or other - support the LCD with little or no tweaking required?  

I've tried the most recent Armbian Linux images, editing armbianEnv.txt as directed, and I've tried what I think are the most current Android 7 and 6 images but I'm not sure I've made the correct changes in the (name escapes me at the moment) config file.


Constructive suggestions and help appreciated...flames can be directed to /dev/null.

Thank you.]]> <![CDATA[About DSI's RGB888 format]]> https://forum.pine64.org/showthread.php?tid=7192 Fri, 22 Feb 2019 01:38:13 +0000 r.tanaka]]> https://forum.pine64.org/showthread.php?tid=7192
I set the DSI format to RGB888.
However, looking at the output of DSI seemed to be BGR888 format, why?.

About DSI format I confirmed the Allwinner A64 SoC specification, but I did not understand it well.


The software and hardware used are as follows.
 software: Armbian
 hardware: Pine A64-LTS

Thank you.]]>
I set the DSI format to RGB888.
However, looking at the output of DSI seemed to be BGR888 format, why?.

About DSI format I confirmed the Allwinner A64 SoC specification, but I did not understand it well.


The software and hardware used are as follows.
 software: Armbian
 hardware: Pine A64-LTS

Thank you.]]> <![CDATA[How to change DSI Clock]]> https://forum.pine64.org/showthread.php?tid=6718 Mon, 29 Oct 2018 10:03:43 +0000 r.tanaka]]> https://forum.pine64.org/showthread.php?tid=6718
How do I change the DSI clock?

The software and hardware used are as follows.

Hardware: PINE A64-LTS
Software: Armbian

Thank you.]]>
How do I change the DSI clock?

The software and hardware used are as follows.

Hardware: PINE A64-LTS
Software: Armbian

Thank you.]]> <![CDATA[How to customize DSI RGB format]]> https://forum.pine64.org/showthread.php?tid=6473 Tue, 28 Aug 2018 10:40:22 +0000 r.tanaka]]> https://forum.pine64.org/showthread.php?tid=6473
I would like to change the DSI format to RGB565.

Therefore, fix the following setting values from DTS.

[sun50i-a64-pine64-plus.dts]

Code:
2182             lcd_dsi_if = <0x2>;
2183             lcd_dsi_lane = <0x4>;
2184             lcd_dsi_format = <0x3>;
2185             lcd_dsi_eotp = <0x0>;
2186             lcd_dsi_vc = <0x0>;
2187             lcd_dsi_te = <0x0>;
"lcd_dsi_format" has been changed from 0 to 3


But, the RGB format of DSI was not changed.
I confirmed with the fbset command.
Code:
pine64@pine64:~$ fbset -i

mode "1024x600-80"
   # D: 55.002 MHz, H: 97.178 kHz, V: 79.981 Hz
   geometry 1024 600 1024 1200 32
   timings 18181 16 -478 4 610 4 1
   rgba 8/16,8/8,8/0,8/24
endmode

Frame buffer device information:
   Name        :
   Address     : 0x57354000
   Size        : 4915200
   Type        : PACKED PIXELS
   Visual      : TRUECOLOR
   XPanStep    : 1
   YPanStep    : 1
   YWrapStep   : 0
   LineLength  : 4096
   Accelerator : No
pine64@pine64:~$



Is there a mistake in how to change the DSI RGB format?
Also, I tryed change to RGB format with reference to the following page.
http://linux-sunxi.org/Fex_Guide#FEX_Description

[sun50i-a64-pine64-plus.dts]
Code:
2136         disp@01000000 {
2137             compatible = "allwinner,sun50i-disp";
2138             reg = <0x0 0x1000000 0x0 0x300000 0x0 0x1c0c000 0x0 0x7fc 0x0 0x1c0d000 0x0 0x7fc 0x0 0x1ca0000 0x0 0x10fc>;
2139             interrupts = <0x0 0x56 0x104 0x0 0x57 0x104 0x0 0x59 0x104>;
2140             clocks = <0x6a 0x6b 0x6c 0x6d 0x6e>;
2141             status = "okay";
2142             device_type = "disp";
2143             disp_init_enable = <0x1>;
2144             disp_mode = <0x0>;
2145             screen0_output_type = <0x3>;
2146             screen0_output_mode = <0x5>;
2147             screen1_output_type = <0x1>;
2148             screen1_output_mode = <0x5>;
2149             fb0_format = <0x5>;
2150             fb0_width = <0x0>;
2151             fb0_height = <0x0>;
2152             fb1_format = <0x0>;
2153             fb1_width = <0x0>;
2154             fb1_height = <0x0>;
2155         };
"fb0_format" has been changed from 0 to 5


But, the result did not change.]]>
I would like to change the DSI format to RGB565.

Therefore, fix the following setting values from DTS.

[sun50i-a64-pine64-plus.dts]

Code:
2182             lcd_dsi_if = <0x2>;
2183             lcd_dsi_lane = <0x4>;
2184             lcd_dsi_format = <0x3>;
2185             lcd_dsi_eotp = <0x0>;
2186             lcd_dsi_vc = <0x0>;
2187             lcd_dsi_te = <0x0>;
"lcd_dsi_format" has been changed from 0 to 3


But, the RGB format of DSI was not changed.
I confirmed with the fbset command.
Code:
pine64@pine64:~$ fbset -i

mode "1024x600-80"
   # D: 55.002 MHz, H: 97.178 kHz, V: 79.981 Hz
   geometry 1024 600 1024 1200 32
   timings 18181 16 -478 4 610 4 1
   rgba 8/16,8/8,8/0,8/24
endmode

Frame buffer device information:
   Name        :
   Address     : 0x57354000
   Size        : 4915200
   Type        : PACKED PIXELS
   Visual      : TRUECOLOR
   XPanStep    : 1
   YPanStep    : 1
   YWrapStep   : 0
   LineLength  : 4096
   Accelerator : No
pine64@pine64:~$



Is there a mistake in how to change the DSI RGB format?
Also, I tryed change to RGB format with reference to the following page.
http://linux-sunxi.org/Fex_Guide#FEX_Description

[sun50i-a64-pine64-plus.dts]
Code:
2136         disp@01000000 {
2137             compatible = "allwinner,sun50i-disp";
2138             reg = <0x0 0x1000000 0x0 0x300000 0x0 0x1c0c000 0x0 0x7fc 0x0 0x1c0d000 0x0 0x7fc 0x0 0x1ca0000 0x0 0x10fc>;
2139             interrupts = <0x0 0x56 0x104 0x0 0x57 0x104 0x0 0x59 0x104>;
2140             clocks = <0x6a 0x6b 0x6c 0x6d 0x6e>;
2141             status = "okay";
2142             device_type = "disp";
2143             disp_init_enable = <0x1>;
2144             disp_mode = <0x0>;
2145             screen0_output_type = <0x3>;
2146             screen0_output_mode = <0x5>;
2147             screen1_output_type = <0x1>;
2148             screen1_output_mode = <0x5>;
2149             fb0_format = <0x5>;
2150             fb0_width = <0x0>;
2151             fb0_height = <0x0>;
2152             fb1_format = <0x0>;
2153             fb1_width = <0x0>;
2154             fb1_height = <0x0>;
2155         };
"fb0_format" has been changed from 0 to 5


But, the result did not change.]]> <![CDATA[Customize LCD]]> https://forum.pine64.org/showthread.php?tid=6450 Thu, 23 Aug 2018 04:44:06 +0000 r.tanaka]]> https://forum.pine64.org/showthread.php?tid=6450
I'd like to change the setting value (resolution, format, porch, etc..) of DSI.

Therefore, do the following procedure.

1. edit /boot/uEnv.txt
 add disp_screen0=lcd

2. edit /boot/pine64/sun50i-a64-pine64-plus.dtb 
Code:
       lcd0@01c0c000 {
           compatible = "allwinner,sunxi-lcd0";
           pinctrl-names = "active", "sleep";
           status = "okay";
           device_type = "lcd0";
           lcd_used = <0x0>;
           lcd_driver_name = "mb709_mipi";
           lcd_backlight = <0x32>;
           lcd_if = <0x4>;
           lcd_x = <0x216>;
           lcd_y = <0x4B0>;
           lcd_width = <0x0>;
           lcd_height = <0x0>;
           lcd_dclk_freq = <0x37>;
           lcd_pwm_used = <0x1>;
           lcd_pwm_ch = <0x10>;
           lcd_pwm_freq = <0xc350>;
           lcd_pwm_pol = <0x1>;
           lcd_pwm_max_limit = <0xfa>;
           lcd_hbp = <0x78>;
           lcd_ht = <0x604>;
           lcd_hspw = <0x14>;
           lcd_vbp = <0x17>;
           lcd_vt = <0x27b>;
           lcd_vspw = <0x2>;
           lcd_dsi_if = <0x2>;
           lcd_dsi_lane = <0x4>;
           lcd_dsi_format = <0x0>;
           lcd_dsi_eotp = <0x0>;
           lcd_dsi_vc = <0x0>;
           lcd_dsi_te = <0x0>;
           lcd_frm = <0x0>;
           lcd_gamma_en = <0x0>;
           lcd_bright_curve_en = <0x0>;
           lcd_cmap_en = <0x0>;
           lcd_bl_en = <0x30 0x7 0xa 0x1 0x0 0xffffffff 0x1>;
           lcd_bl_en_power = "none";
           lcd_power = "vcc-mipi";
           lcd_fix_power = "vcc-dsi-33";
           lcd_gpio_0 = <0x30 0x3 0x18 0x1 0x0 0xffffffff 0x1>;
       };

The modified part is lcd_x and lcd_y.

3. reboot

When rebooted, a kernel panic has occurred.

Is there a mistake in the procedure?

Thank you.]]>
I'd like to change the setting value (resolution, format, porch, etc..) of DSI.

Therefore, do the following procedure.

1. edit /boot/uEnv.txt
 add disp_screen0=lcd

2. edit /boot/pine64/sun50i-a64-pine64-plus.dtb 
Code:
       lcd0@01c0c000 {
           compatible = "allwinner,sunxi-lcd0";
           pinctrl-names = "active", "sleep";
           status = "okay";
           device_type = "lcd0";
           lcd_used = <0x0>;
           lcd_driver_name = "mb709_mipi";
           lcd_backlight = <0x32>;
           lcd_if = <0x4>;
           lcd_x = <0x216>;
           lcd_y = <0x4B0>;
           lcd_width = <0x0>;
           lcd_height = <0x0>;
           lcd_dclk_freq = <0x37>;
           lcd_pwm_used = <0x1>;
           lcd_pwm_ch = <0x10>;
           lcd_pwm_freq = <0xc350>;
           lcd_pwm_pol = <0x1>;
           lcd_pwm_max_limit = <0xfa>;
           lcd_hbp = <0x78>;
           lcd_ht = <0x604>;
           lcd_hspw = <0x14>;
           lcd_vbp = <0x17>;
           lcd_vt = <0x27b>;
           lcd_vspw = <0x2>;
           lcd_dsi_if = <0x2>;
           lcd_dsi_lane = <0x4>;
           lcd_dsi_format = <0x0>;
           lcd_dsi_eotp = <0x0>;
           lcd_dsi_vc = <0x0>;
           lcd_dsi_te = <0x0>;
           lcd_frm = <0x0>;
           lcd_gamma_en = <0x0>;
           lcd_bright_curve_en = <0x0>;
           lcd_cmap_en = <0x0>;
           lcd_bl_en = <0x30 0x7 0xa 0x1 0x0 0xffffffff 0x1>;
           lcd_bl_en_power = "none";
           lcd_power = "vcc-mipi";
           lcd_fix_power = "vcc-dsi-33";
           lcd_gpio_0 = <0x30 0x3 0x18 0x1 0x0 0xffffffff 0x1>;
       };

The modified part is lcd_x and lcd_y.

3. reboot

When rebooted, a kernel panic has occurred.

Is there a mistake in the procedure?

Thank you.]]> <![CDATA[Search Compatible 10.1" touchscreen]]> https://forum.pine64.org/showthread.php?tid=6248 Fri, 06 Jul 2018 09:48:42 +0000 alfredo78]]> https://forum.pine64.org/showthread.php?tid=6248 Do you help me ?
Thanks, L.A.]]> Do you help me ?
Thanks, L.A.]]> <![CDATA[OpenAuto]]> https://forum.pine64.org/showthread.php?tid=5952 Mon, 09 Apr 2018 01:15:39 +0000 polybius]]> https://forum.pine64.org/showthread.php?tid=5952 OpenAuto. It looks like this would be a good use for the kit and I might finally get some use out of it. I tried to set everything up with the Armbian image but I couldn't get aasdk compiled properly because I didn't have the correct version of protobuf or something. Any help would be appreciated!]]> OpenAuto. It looks like this would be a good use for the kit and I might finally get some use out of it. I tried to set everything up with the Armbian image but I couldn't get aasdk compiled properly because I didn't have the correct version of protobuf or something. Any help would be appreciated!]]> <![CDATA[Pine64 + LCD + Volumio]]> https://forum.pine64.org/showthread.php?tid=5240 Mon, 09 Oct 2017 16:24:50 +0000 kodachrome]]> https://forum.pine64.org/showthread.php?tid=5240
Got one of the original Kickstarter Pine64 Plus models with the LCD output. Can I use the LCD touchscreen on the site:
https://www.pine64.org/?product=7-lcd-to...reen-panel

With Volumio OS and make a cool standalone Spotify player?


Im aware there was some early Linux support issues.. that all taken care of now?]]>
Got one of the original Kickstarter Pine64 Plus models with the LCD output. Can I use the LCD touchscreen on the site:
https://www.pine64.org/?product=7-lcd-to...reen-panel

With Volumio OS and make a cool standalone Spotify player?


Im aware there was some early Linux support issues.. that all taken care of now?]]> <![CDATA[Compatible LCD DSI]]> https://forum.pine64.org/showthread.php?tid=5205 Tue, 03 Oct 2017 04:42:39 +0000 drock]]> https://forum.pine64.org/showthread.php?tid=5205 https://www.aliexpress.com/store/product...64052.html


Has anyone used on of these on the pine?  If my understanding is correct this is the only DSI MIPI screen that we have a driver for?]]> https://www.aliexpress.com/store/product...64052.html


Has anyone used on of these on the pine?  If my understanding is correct this is the only DSI MIPI screen that we have a driver for?]]>