[Arm-netbook] 480 × 272 5" LCD lash up ready for testing

[luke.leighton]

On Thu, Sep 19, 2013 at 11:29 AM, joem <joem at martindale-electric.co.uk> wrote:

>>  yes there is. on
>> http://rhombus-tech.net/community_ideas/micro_engineering_board/
>>  you can see it's pin 29.
>
> That be the EN signal which tells the LCD to tell when to load
> in the data for each horizontal line, and ignore data when the
> LCD controller reconfigures itself for the next line of horizontal
> line data.
>
> The DEN signal prevents the display from working
> until after CPU has booted and set its IO lines.

 ok - then that sounds like it's a job for a GPIO pin.

 put that into say.... ooo, i dunno... the lcd_power = parameter of [lcd0_para]


>> > At the moment the LCD is not being initialised properly.
>> > The boot log is here
>> > http://www.gplsquared.com/eoma_boot/lcd_boot_log.txt
>>
>> <4>[DISP] *** Err01: Violate "lcd_hbp > lcd_hspw"
>> [    5.635979] [DISP] *** Err01: Violate "lcd_hbp > lcd_hspw"
>> <4>[DISP] *** Err02: Violate "lcd_vbp > lcd_vspw"
>> [    5.645902] [DISP] *** Err02: Violate "lcd_vbp > lcd_vspw"
>> <4>[DISP] *** Err03: Violate "lcd_ht >= (lcd_hbp+lcd_x*1+4)"
>> [    5.656779] [DISP] *** Err03: Violate "lcd_ht >= (lcd_hbp+lcd_x*1+4)"
>> <4>[DISP] *** Err04: Violate "(lcd_vt/2) >= (lcd_vbp+lcd_y+2)"
>> [    5.673792] [DISP] *** Err04: Violate "(lcd_vt/2) >= (lcd_vbp+lcd_y+2)"
>>
>>  ok so you need to change those values so that the double-checks pass.
>>  just experiment until you have it ok?  although... to be honest, that
>> LCD's so common i'm sure you'd be able to find someone who's done this
>> already.
>>
>> > The script.fex used is here
>> > http://www.gplsquared.com/eoma_boot/script.fex
>
>
> As can be seen, the fex file is set up correctly, but boot log says
> the  software thinks lcd_x, lcd_y etc are all set at 0!

 hmmm, that's very weird.  try doing bin2fex on the script.bin then
use "diff -u" to compare with the original.

l.