>> One issue which I need to investigate, is the colours.
>> At boot, the Penguin appears with Blue feet, and not
Yellow/Orange and the
>> customer splash screen and applications also have the
wrong colour.
> [Franklin] I believe that color issue has to-do with the
am335x errata
> (http://www.ti.com/lit/er/sprz360f/sprz360f.pdf (page 8). )
> The BBB is hooked up to display correctly in 16bpp mode
but if you use 24bpp then your colors will look messed up.
> I recommend posting this question to e2e.ti.com and the right
people can help you with this.
Did a posting there, yet to get a reply, so I am posting here as
well.
My custom device-tree file was based on the LCD4 device tree files.
Some excerpts:
lcdc: lcdc@0x4830e000 {
compatible = "ti,am33xx-tilcdc";
reg = <0x4830e000 0x1000>;
interrupt-parent = <&intc>;
interrupts = <36>;
clocks = <&lcd_gclk>;
clock-names = "fck";
ti,hwmods = "lcdc";
status = "okay";
};
/* fbdev entry */
&lcdc {
pinctrl-names = "default";
pinctrl-0 = <&bone_lcd4_cape_lcd_pins>;
status = "okay";
display-timings {
480x272 {
clock-frequency = <9000000>;
hactive = <480>;
vactive = <272>;
hfront-porch = <9>;
hback-porch = <44>;
hsync-len = <5>;
vback-porch = <13>;
vfront-porch = <4>;
vsync-len = <10>;
hsync-active = <0>;
vsync-active = <0>;
};
};
};
Any view on the correctness of this?
"omaplfb" loads with this. Is this because it (compatible = "ti")
is true?
The "tilcdc" driver is not even compiled.
Is there any documentation on device tree bindings for the
"omaplfb"?
Meanwhile, I am adding 'bpp = <16>;' based on other examples
lcdc: lcdc@0x4830e000 {
compatible = "ti,am33xx-tilcdc";
reg = <0x4830e000 0x1000>;
interrupt-parent = <&intc>;
interrupts = <36>;
bpp = <16>;
clocks = <&lcd_gclk>;
clock-names = "fck";
ti,hwmods = "lcdc";
status = "okay";
};
BR
Ulf Samuelsson