EADOG xl 160-7 - same as the DOGM wiring?

[istel]

Hi

 

I just received an eadog xl 160-7 (http://www.lcd-module.com/eng/pdf/grafik/dogxl160-7e.pdf) and it seems very nice. Before i just had a normal CLCD on, and i can see that the wiring is different for the DOG.. So i found this schematic, http://www.ucapps.de/mbhp/mbhp_lcd_dogm128_mios32.pdf - but as far as i can see wiring is approximately the same, but there is different terminology on the DOG datasheet and the dogm schematic from ucapps.. Can someone tell me if they are the same? If so, i need to get some 1uF and a 2.2uF caps also apparently, is this also correct? 

 

Thanks!

 

Isak 

Edited February 8, 2014 by istel

[mono]

hi,

 

your display seems to be a new dog-variant. but if u stick to the 4-wire-spi-diagram on page4 and 3.3volts, i cant see a problem with that. you would only need 2 caps 2uF and 1 100nF. this is what i would do:

 

SDA - SI     - J15A/RW

SCK - CLK - J15A/E

CD   - A0   - J15A/RS

CS   - CS   - J15A/D0 (for the 1st display)

 

use the dogm-glcd-driver in the bootloader-configuration and set your resolution to 160x104 px AND dont forget to post, if it works...:-)

 

mOnO

[istel]

hi mono

 

yeah, i just checked out the datasheet on the dogm.. don't know why i didn't do that before ;) 

 

ok, that looks pretty doable. so i would make a ribbon cable with lines for the SDA, SCK, CD, CS, VDD (3,3v) and RESET? And reset goes to J15/RS?

 

Thanks for the help! i'll report back if success!! :)

 

isak

[mono]

hi istel,

 

sry, forgot about the RESET. just connect that to Vdd (3,3volts). all the other pins as described before. i wouldnt use a ribbon cable. have placed my dogm-lcd on sockets on the pcb:

 

 

this way u can re-use them for other projects. they are really good, but still expensive...

 

mOnO

[istel]

hi istel,

 

sry, forgot about the RESET. just connect that to Vdd (3,3volts). all the other pins as described before. i wouldnt use a ribbon cable. have placed my dogm-lcd on sockets on the pcb:

 

 

this way u can re-use them for other projects. they are really good, but still expensive...

 

mOnO

 

okay, sure thing about reset. 

 

yeah, i was thinking of connecting the wires to the back of a proto-board with female pin headers.. i think like you have done, so yeah, you can change 

[mono]

...another reason for using pin-headers for me was, that i had to try all these fancy backlights in combination with all these fancy displays. with the right type of header you dont even need to solder the display on the backlight.

my favourite is the white backlight under the negative display (order-code S). love it..:-)

[istel]

Okay, so i tried making it work today. Made a small proto-board to mount the display on and i think i have made the right connection. If i measure on it, there is 3.3 v where there should be.

I have updated the bootloader config to the dog_glcd and set the resolution to 160x104 and it seemed to say it stored it and when booting the core the MIOS terminal says initializing LCD #1, so i think it got it.

I tried running the 021_glcd tutorial and i have updated my ~/.profile and set the lcd to the uc1610. In there as far as i could see the resolution was already set to 160x104, so that should be in order. The code compiles, but when i try to plug in the display and boot the display shows nothing. I haven't got the backlight, but i would imagine that something would still be showing or some sort of sign of life? It should show the "Tutorial #021" (...), but it doesn't.. I am not sure how to debug this.

Here is two pictures (The ribbon cable goes to LPC1769 core J15)

and

Edited February 22, 2014 by istel

[mono]

hi istel,

 

very adventurous construction btw... anyway first i would change the display-driver in ~/.profile from uc1610 to universal and re-compile everything. next i believe, that pin26 is connected to GND instead of 3.3v. the 100nF cap on pin17 is missing, whereas it should work without that, and im not really sure about the other caps. if you have used electrolytic caps, as it looks to me, make sure the polarity is right, otherwise it cant work...

 

mOnO

[istel]

Hehehe! Yes, slightly adventurous! Now it works - i see how it looks a little funny, but i think everything is wired up correctly now.. The error was the caps - i had read the wrong value in the schematic, i thought it say 0.2 uf and not 2 uf :) swapped them out and now it works!

[mono]

...glad to hear, that you are happy now!

 

mOnO

[istel]

Yeah, this is so nice!! Before it was only a 2x16 CLCD, but this can show so much more info!! 

 

But we are having slight issues - we are two persons working on the software, one OS X and the other is Linux. Every time my friend tries to send an application to the device the screen will fail, and we have to flash the bootloader, update LCD settings and then send the application from my computer (OS X). Is there somewhere where the bootloader config is being set without us knowing? It seems that everytime he tries to send over the application something is being reconfigured with the LCD and it has to be set back to DOG_GLCD, etc etc.. 

 

Here is the prototype (!) :)

 

[mono]

...the operating system shouldnt be the reason for your issue. it sounds more like you havent stored the lcd-parameters with the bootloader application. try that first.

 

also you should try the tiny-font:

 

MIOS32_LCD_FontInit((u8 *)GLCD_FONT_TINY);
 

which gives you the maximum amount of letters on your display. if your compiler cant find the tiny-font, update your mios-sources...

 

mOnO

[istel]

...the operating system shouldnt be the reason for your issue. it sounds more like you havent stored the lcd-parameters with the bootloader application. try that first.

 

also you should try the tiny-font:

 

MIOS32_LCD_FontInit((u8 *)GLCD_FONT_TINY);

 

which gives you the maximum amount of letters on your display. if your compiler cant find the tiny-font, update your mios-sources...

 

mOnO

 

I am quite sure that i have stored the LCD params. I run the lcd_width, lcd_height, lcd_type, lcd_num_x and lcd_num_y and then store afterwards. It says it is saved. I see how it shouldn't be the operating system, but for some reason it is only when sending applications from his computer that we have the issue. 

 

We'll try out the small font, seems like it would be worth it. Saving every pixel!! 

[mono]

...if it has stored, it should work. i never came across that issue. i am using the stm32f4 at the moment, but i have used the lpc1769 before, both under windows7. maybe someone else can help ??

 

saving every pixel was the goal with the tiny font, which i have "designed" in excel. for my current project i will probably use the tiny font on a dogm128x64 display. if i get chance i will "design" an inverted version of the tiny font for my project as well. if you like the tiny-font, let me know, and i can update the mios-svn with the inverted tiny-font...

 

mOnO

[TK.]

It seems that everytime he tries to send over the application something is being reconfigured with the LCD and it has to be set back to DOG_GLCD, etc etc.. 

 

How do you update the application?

 

It should be done via MIOS Studio: http://www.ucapps.de/mios_studio.html

 

If you flash the complete binary instead, the bootloader configuration section will be overwritten, this would explain the problem.

 

Best Regards, Thorsten.