Hey all,
This is a newbie question:
I am building a TR909 like sequencer using the LPC1769 core and I have a Electronic assembly display DOGM128X6.
I have tested the display but I only get the backlight 
Could someone let me know if I need to change something on a software level to make the display work?
do I need to put something in the MBSEQ_HW.V4 file?
thanks
Jef
When compiling stuff you can set a variable: export MIOS32_LCD=universal
Maybe something has to be altered there. Just not sure what is needed for your display.
Hey Shuriken,
Yeah I know, and I have even put the lcd_type to GLCD_DOG, but I get nothing out of my display.
I actually hope it is my display that is just broken. it has a few strange lines across the display!?
cheers,
jef
It works with my STM32 core (where Iâve soldered the display cables directly on the PCB).
I will desolder the display and check it with the LPC17 core later today.
Best Regards, Thorsten.
I checked the DOGM128 driver on the LPC17 based core, and it works (basically) - there was a bug which caused that only the left half of the display was written, but the initialization was already working correctly.
Here the schematic: http://www.ucapps.de/mbhp/mbhp_lcd_dogm128_mios32.pdf
And here the picture which you should see with the apps/mios32_test/app_lcd/dog_g application:
Best Regards, Thorsten.
I compiled the test driver for the dogm display apps/mios32_test/app_lcd/dog_g
When I upload it I get an error:
[15691.073] GLCD_DOG Demo started.
[15691.073] Configured LCD Parameters in MIOS32 Bootloader Info Range:
[15691.074] lcd_type: 0x00 (CLCD)
[15691.074] num_x: 2
[15691.074] num_y: 1
[15691.075] width: 20
[15691.075] height: 2
[15691.076] WARNING: your core module hasnât been configured for the GLCD_DOG!
[15691.076] Please do this with the bootloader update application!
Ich konnte mir die Frage selbst beantworten. Aber mir stellt sich eine neue: Im Schema ist ein 2.2ĂÂľF vermerkt, sollte da gemäss DOG nicht 9x ein 1ĂÂľF Kondensator rein?
Jep, dem sollte laut Datenblatt so sein. Ist aber nicht kritisch an der Stelle, TK wird sich schon was dabei gedacht haben :whistle:
Wenn ich nun die Tutorialapplikation 21 kompiliere und rauflade geht mein LCD nicht an.
Ich habe es dann mit der Umgebungsvariable MIOS32_LCD=dog_g versucht, aber der Treiber des dog_g scheint mittlerweile im Universal drinn zu sein.
Muss ich der app per mios_studio noch irgendwas mitteilen oder sollte sie von sich aus etwas anzeigen?
UUps wir sind ins deutsche abgeschweift:
If I compile tutorial 21 and load it up, my LCD does not start up.
I tried it with the environment-variable MIOS32_LCD=dog_g but it seems that the driver of the dog_g is implemented in the universal driver yet.
Do I have to communicate with the app via mios studio and give her some commands to start up the LCD?
Yes, the dog_g driver is part of the universal driver.
A pretty good hint can be found in mios32_lcd.c:
s32 MIOS32_LCD_Init(u32 mode)
{
s32 ret;
// currently only mode 0 supported
if( mode != 0 )
return -1; // unsupported mode
// initial LCD parameters
// can be overruled in APP_LCD_Init()
static const mios32_lcd_parameters_t default_parameters = {
.lcd_type = MIOS32_LCD_TYPE_CLCD,
.num_x = 2, // since MBHP_CORE_STM32 and MBHP_CORE_LPC17 has two J15 ports
.num_y = 1,
.width = 20, // since most people will (probably) build the SCS
.height = 2,
.colour_depth = 1,
};
mios32_lcd_parameters = default_parameters;
// ...
[/code]
you'd want to override .lcd\_type in APP\_LCD\_Init with MIOS32\_LCD\_TYPE\_GLCD\_DOG and the rest accordingly.
Hope that helps!
The GLCD has to be selected in the Bootloader Update application.
Just upload it again (donât worry, the update wonât take place) and type âhelpâ in MIOS Terminal.
Probably it will show that a CLCD is selected. Change it with the âlcd_typeâ command.
Best Regards, Thorsten.
âŚand while youâre at it you can give your core a cool new name 