Unicorn GLCD demo.

crocu · Nov 30, 2010

You're right but i changed this value since i posted, and replacing it to 0X0F does not change the vline issue ...

I'm sorry about that.

crocu · Dec 2, 2010

Hello,

I'm back with some news : i tried to understand why Pommie's code is fully working with 18F4550 and same code ported to 18F2620 won't display anything.

Actually i found a partial response to that problem :

In order to have something displayed with 18F2620 code, ww variable must be set as ROM char :

Code:

unsigned [COLOR="Red"]rom[/COLOR] char ww;

Doing this gets results with 18F2620, now something is been displayed,
but there are sliding pixels and lagging issues, so it is a very bad display.

Here are screen captures of Pommie's 18F4550 code result when passing "ww" has rom char , and when setting ww as a regular unsigned char :

Code:

unsigned char XPos,YPos, ww;

( i of course get the same results if i use 18F2620 )

So in order to recap a bit,
here is the comparaison of results i got when using : 18F4550 vs 18F2620 :

18F4550 displays properly when using ww as normal unsigned char.
18F2620 displays nothing when using ww as normal unsigned char.

18F4550 displays badly when using ww as unsigned rom char.
18F2620 displays badly when using ww as unsigned rom char.

So we can say that the problem comes in when the code return ww.
then something gets wrong inside Pic memory ...
Maybe we need to copy ww from ROM to RAM and then proceed the loop, i don't know how to do that ...

Can someone help me to solve this problem ?

Pommie · Dec 2, 2010

You cannot have variables in ROM. ROM stands for READ Only Memory. I just checked your code and dat is a ROM variable.

Code:

unsigned char i;
unsigned char XPos,YPos;
[COLOR="red"]unsigned far rom char dat[/COLOR];

unsigned char GLCD_Read(void){
        b_GLCD_E=1;
        Delay();
        [COLOR="red"]dat[/COLOR]=GLCD_Data;  [COLOR="red"]//dat will never get written to[/COLOR] 
        b_GLCD_E=0;
        Delay();
        return [COLOR="red"]dat[/COLOR];
}

This will result in GLCD_Read returning 0xff all the time. This would explain the result you are seeing.

Mike.

crocu · Dec 2, 2010

Ok, but how we should explain that "ww" or "dat" ( depends name of variable used ) is getting problem to be returned when using a different Pic familly ?

I tried 18F2620 and also 18F97J60 and i get the same.

I think return dat is not working properly .
Is there a way to change the code and write differently the funtion GLCD_Read(void) that returns "dat" ?

Pommie · Dec 2, 2010

Make the variable local.

Code:

unsigned char GLCD_Read(void){
unsigned char localdat;
        b_GLCD_E=1;
        Delay();
        localdat=GLCD_Data;  //dat will never get written to 
        b_GLCD_E=0;
        //Delay();     not needed
        return localdat;
}

But you must also make dat not ROM as it's used elsewhere.

Mike.

crocu · Dec 2, 2010

no chance, it does not change anything .

crocu · Dec 2, 2010

Pommie :

What is your crystal speed on your board 18F4550 ?
As i can see in the code, you do not use PLL or pre-scaler .

Maybe my 18F2620 has timing issue compared to 18F4550.
My 18F2620 is running OSC = HS with 10 Mhz crystal.

Thanks,

AtomSoft · Dec 2, 2010

Just though id share this here... I converted POMMIEs code and removed unused things and created a buffer to draw to then draw to screen.

https://atomsoft.wordpress.com/2010/12/03/electr-a-sketch/
I fixed the link now heh

crocu · Dec 4, 2010

Hello,

I can't find any solution regarding GLCD_Read function, that getting trouble,

Code:

unsigned char GLCD_Read(void){
        b_GLCD_E=1;
        Delay();
        ww=GLCD_Data;
        b_GLCD_E=0;
        return ww;
}

it looks that "GLCD_Data" is not read properly and "ww" not returned ... then rest of the code is not able to display something on the GLCD.

I tryed to put more delays after b_GLCD_E=1; but nothing changed.

It is very strange because Pommie's code works perfectly with Pic 18F4550 but i can't that same code working with any other Pic ( i tried many ones .... )

Can someone post a Demo code working well with a Pic different as 18F4550, then i will compare it to mine and maybe put me on the way to find out the issue ...

Many thanks,

( i attached here my Demo code )

Pommie · Dec 5, 2010

can you run the following code in main,

Code:

void Test(){
char ret,i;
    for(i=0;i<8;i++){
        SetPos(0,0);
        GLCD_Write_Data(1<<i);
        ret=GLCD_Read_Data();
        if(ret!=(1<<i))
            while(1);
    }
    while(1);
}

Once it's run, stop it and let me know where it stopped and what i and ret are.

Mike.

crocu · Dec 6, 2010

If i understand well, you suggest me to have this in main.c and then run the program in Debug mode in order to read ret variable from Watch windows ?

Code:

void main(void)
{
	char ret,i;
	// disable AD converter and set up Port A as digital I/O
	ADCON0bits.ADON = 0;
	ADCON1 = 0b00001111;
	
	Init_GLCD();
   

    for(i=0;i<8;i++){
        SetPos(0,0);
        GLCD_Write_Data(1<<i);
        ret=GLCD_Read_Data();
        if(ret!=(1<<i))
            while(1);
    }
    while(1);
}

Then i run that code ( Release mode in MPLAB ) from hardware and also Prteus simulator, nothing is been displayed on the GLCD .

I"m testing hardware with a lab board, if you want me to test in Debug mode i will have to wire PGC and PGD and MCLR pins ?

crocu · Dec 6, 2010

When running the code in Debug mode and then stop it, MPLAB points while(1) line

( see screen capture )

then Watch window reports that "ret" value is 0xFF

Still nothing displayed on the GLCD.

What do you think about that ?

AtomSoft · Dec 6, 2010

That code sets the GLCD with data then reads the data back. Its never supposed to hit the while if the data is reading correctly. Maybe a hardware issue..(meaning wiring or actual GLCD)
You could simply:

Code:

GLCD_Write_Data(0x0D);
ret=GLCD_Read_Data();
if(ret!=0x0D)
    //ERROR: INPUT DOESNT MATCH OUTPUT
else
    //Data OK!

Since it stopped there what is the value of RET?

crocu · Dec 6, 2010

Yes indeed, when running and stoping it points here : // ERROR INPUT DOESNT MATCH OUTPUT

Watch windows says ret = out of scope .

Maybe timing issues when GLCD_Write_Data sends to GLCD ?
How to be sure ?

I double checked hardware and it is correct, anyway it get no display with simulator as well...

AtomSoft · Dec 6, 2010

can you post your entire code? like in a zip. I see you were also testing in proteus... can you test current code there as well? Also if you have the proteus DSN file can you post it also. Ill get back to you asap with hopefully a fix! or my own questions heh

crocu · Dec 6, 2010

Sure, here they are :

- MPLAB project
- JPEG schematic ( for those who don't have Proteus )
- Proteus DSN file for simulation and test purposes

I added 2 leds on RA0 and RA1 for test purposes, should help ...

AtomSoft · Dec 6, 2010

Something obvious but still not working for me is:

IN the glcd.h

Code:

#define GLCD_Data   		(LATC)
#define b_GLCD_GCS1 		(LATBbits.LATB1)
#define b_GLCD_GCS2 		(LATBbits.LATB2)  
#define b_GLCD_RS   		(LATBbits.LATB3)   
#define b_GLCD_RW   		(LATBbits.LATB4)  
#define b_GLCD_E    		(LATBbits.LATB5)  
#define b_GLCD_On   		(LATBbits.LATB6) 	// not available on my GLCD
#define b_GLCD_BL   		(LATBbits.LATB7) 

// Define the direction for each Input/Output pin (0-Output, 1-Input) :
#define TRIS_Data    		(TRISC)
#define b_TRIS_GCS1  		(TRISBbits.TRISB1)
#define b_TRIS_GCS2  		(TRISBbits.TRISB2) 
#define b_TRIS_RS    		(TRISBbits.TRISB3) 
#define b_TRIS_RW    		(TRISBbits.TRISB4) 
#define b_TRIS_E     		(TRISBbits.TRISB5) 
#define b_TRIS_On    		(TRISBbits.TRISB6) 	// not available on my GLCD
#define b_TRIS_BL    		(TRISBbits.TRISB7) 

#define LED1	    		(LATAbits.LATA0)
#define LED2	    		(LATAbits.LATA1)

You had some TRIS_Data wrong, also the LED defines where tris not lat. GLCD_Data was PORTC should be LATC

AtomSoft · Dec 6, 2010

Check this out.. if you bypass the wait not busy routine with a normal delay it works fine. I never liked using it heh. Try this out. It has a DSN in it and i replaced your led with actual simulation leds. so you can see then light up heh

crocu · Dec 6, 2010

Thanks, yes i found too late that my leds were not declared properly.

You are right #define TRIS_Data was not set correctly either.
This would help.

However, i think #define GLCD_Data has to be PORT not LAT because we need to read states, not latches.

Now, something is coming-in on the GLCD but i'm still not able to display a picture or vertical line, i don't know why ...
It looks that pixels in vertical lines are being lit very slowly and some of them them are missing ...

btw : would you please tell me how you inserted simulator window inside MPLAB i never saw this before, it is a very interresting feature.

AtomSoft · Dec 6, 2010

Under the debug menu it should say Proteus VSM

Oh yeah we are reading also so PORTC is best. How about

#define GLCD_Data_In PORTC

and use it in the read function only heh

Unicorn GLCD demo.

Member

Member

Attachments

Well-Known Member

Member

Well-Known Member

Member

Member

Well-Known Member

Member

Attachments

Well-Known Member

Member

Member

Attachments

Well-Known Member

Member

Well-Known Member

Member

Attachments

Well-Known Member

Well-Known Member

Attachments

Member

Well-Known Member

Attachments

Similar threads

Privacy & Transparency

Privacy & Transparency