It only shows something if the width is set to 320 (319 works also

) If i set it to 240, 160 or anythig else nothing is happening...
Now i wired the whole display but the result is the same. It's now wired like the schematic on page 22 of the S1D13305 (Figure 3, but with 2 line-drivers instead of one). Theoreticaly i have a resolution of 640x160 dots now. Pictures you can see if you follow the links in the post below...
I took the controller-device of another display (Ampire 320240Q2 with a resolution of 320x240) (
http://www.mscbp.hu/download/LCD/Ampire/ or
http://www.mscbp.hu/download/LCD/Ampire ... e%20driver).pdf ), because this was completely with oscillator and RAM,... I think it shouldn't matter what display is connected to the controller-device, but maybe it does...
I have no more ideas what could be the problem...
Is there any command in the driver that tells the controller to do something special after 64 lines?
Edit: Where can i find the initialization in the source code? There is a W/S flag that is set to 0 if single panel display and to 1 if dual panel display. My lcd is a dual panel... You can see this in the S1D13305 datasheet on page 21 and 22 (and 23). Perhaps this could solve my problem...