A tft addin for pbp3

[richard]

The first of my tft modules arrived today a 1.8 inch st7735 with spi interface

so far I have a scalable chr32 to 90 font and a rectangle fill utility . no one responded to my previous offer to make joint effort to develop this idea but now that I have something working it might be different . so I will have one more go ,if no one is interested I will just develop it for myself .
this is just a demo and not documented at all ( it would be a waste of time if there is no interest)

[richard]

a photo of the output

[pedja089]

Very nice. And nice example for using USERCOMMAND

[Heckler]

That's very nice!

yes, please do share... I'd live to try one of those little displays.

thanks

[richard]

tft now with duck, drawimage now works
and a python script to convert utf565 generated c file to pbp friendly format

[richard]

forgot the python script

[richard]

The dev board I'm using for this project has a w25q32 flash memory chip on board , unfortunately on the same spi port as the display. this little display does a really fine job on graphics but transferring image data from flash to display is turning out to be much more complicated than expected. the other spi port is loaded up with a rtc and an eeprom (both i2c) . I'm not sure how they will react to the spi signals if I move the display to that port.
hoping to avoid smoke
here is the flash usercommand file so far

[richard]

glad to see some interest

some ideas needed :-

currently to display a string

fg=$F800  ; set colour
 TEXTSIZE=2 
 ARRAYWRITE buffer,["HELLO WORLD",0]
 GLCDC 1,63     ; set x ,y position
 ch=0
 WHILE (ch< 32) AND (buffer[ch]>0  )  ; check for end of string
 GLCDC  buffer[ch]        ; disp ch
 ch=ch +1
 WEND

I would rather have a usercommand

GLCDS 1,63 ,buffer
but I can't figure a way of getting the address of buffer from the usercommand macros
GLCDS 1,63 ,"HELLO WORLD"
but I can't figure a way of getting the string data from the usercommand macros

I would like to put the display hardware dependent code into a separate include file (that way other displays could be incorporated)

not all the useful input combinations have had their macros written for each user command

more user commands are required

drawHline,drawVline,drawline,drawcircle,drawrect,f illcircle

the hardware connection interface is defined like this

  tft_dc_bit con 4
  tft_cs_bit con 1
  tft_rst_bit con 8
  tft_port var latd

its a bit clunky I sure there are better ways

bit banging the data could be investigated

over to you

[richard]

I have a bit of conditional compiling going on to select mssp1 or mssp2 but is there a way to conditionally check if the pic18 chosen to compile for has 1,2 or no mssp modules .

#IFNDEF TFT_SPI
    #DEFINE TFT_SPI 1 
      ;DEFAULT
 #ENDIF   



 #IF   TFT_SPI = 1
     SSP1_IF VAR pir1.3    
 #ELSE
     SSP1_IF VAR PIR3.7
 #ENDIF

      
TFT_CMD:
spi_cbyte :
    tft_port =  tft_port & (~ tft_dc_bit )
TFT_DATA:    
spi_byte :
'@       movff    INTCON , _p_int 
'@       bcf     INTCON ,7 
    tft_port =  tft_port& (~ tft_cs_bit )
    SSP1_IF = 0
    #IF   TFT_SPI = 1
    SSP1BUF = CMD 
    #else
    SSP2BUF = CMD 
    #endif
    WHILE   SSP1_IF =0 ' wait for SPI interupt flag
    wend
    tft_port = tft_port |   ( tft_dc_bit|  tft_cs_bit   )
    
'@     movff  _p_int  , INTCON 
return

the problem is that if the pic has only one mssp then sspbuffer becomes sspbuf where as for two its ssp1buf or ssp2buf.
and it would nice to have shiftout as an option.

other than that it nearly a done deal

[HenrikOlsson]

Hi Richard,
Apart from including a list of all PICs with two MSSP modules and checking against that list I don't know a way of telling at compile time. There's probably a way to have the assembler do it but then its too late.....

However, looking at the P18F45K22.INC file, as an example, one can see that SSPBUF and SSP1BUF are both declared and pointing at the same adress so I think you should be safe using SSPBUF and SSP2BUF. Obviously one can't know if Microchip will continue to alias SSPBUF to SSP1BUF on devices with multiple MSSP modules...

/Henrik.

[richard]

hi henrik

in asm I can do this

 asm
  ifdef SSPIF
     #define  ssp_1  0
    endif


    ifdef SSP1IF
     #define  ssp_1  1 
    endif

endasm

but a #define thats made here seems unreadable to the pbp compiler
and I don't really want to do the whole routine in asm

[richard]

tried using
SSPBUF = CMD
when ssp1buf exists and it syntax errors it really wants SSP1BUF = CMD

tried
sspbuf var ssp1buf

result
syntax error var is already an alias

[HenrikOlsson]

Hi Richard,
Which device are you targeting?

/Henrik.

[visnja30]

Is it possible that I destroy my TFT-display because my power supply for PIC18f4520 is 5volt?Communication between PIC and ILI9341 is on 5 volt.

[richard]

done a bit more

have added tft_sleep tft_wake tft_on tft_off subs, added DRAWRRECT usercmd (draw round cornered rectangle).
change way buttons are defined . can have rectangular buttons , a button colour scheme and the button "title" text is now stored in pgm memory
attached is a demo for a pic18f2520 using sleep/ wake on touch interrupt , backlight modulation using a pnp trany bc557 (full 10 bit)

can supply cct if req

[visnja30]

Hello people
if someone tried Richard's example with PIC18F2520 or PIC18f4520
I tried his example with PIC18F4520 and unfortunately not working. I have just a white screen.
If someone can send me a hex file or an example of code that works with the PIC18F4520 so that I know if my screen working properly or it is damaged.

my connection from TFT to PIC
tft_dc_bit con 8 ;ie bit 3 PORT B.3
tft_cs_bit con 32 ;ie bit 5 PORTB.5
tft_rst_bit con 16 ;ie bit 4 PORTB.4
tft mosi PORTC.5
tft sck PORTC.3



when I change value of this variable the led intensity is change on port C.2 , so PIC is working
cont=50 ;half brightness

[richard]

another pic

[pedja089]

Never done something like that, but as DT said there is no better manual than .mac and .lib files.
So here is what I found.

Compiler use this macro from pbppic18.mac file when LCDOUT STR is used

;****************************************************************
;* LCDOUTSTR?B : Macro - Lcdout string                          *
;*                                                              *
;* Input      : B[]                                             *
;* Output     : None                                            *
;*                                                              *
;* Notes      :                                                 *
;****************************************************************

LCDOUTSTR?B macro Bin
        MOVE?CW LCDOUTJ, R8 'dont know what this line do
	MOVE?CB	high (Bin), FSR2H 'load highbyte of adr, from pbppic18.lib Macro - Move BYTE Variable into WORD Variable
        MOVE?CA	low (Bin) 'load low byte of adr to w, from pbppic18.lib MOVE?CA    : Macro - Move constant into W 
 
        L?CALL  SEROUT2STR
    endm

SEROUT2STR is in file pbppic18.

SEROUT2STR movwf FSR2L          ; Set up for index
serout2strloop movf POSTINC2, W	; Get a character
	bnz	serout2str1	; Not null char

So you could use in your program something like this:

TFTSTR?B macro Bin
	MOVE?CB	high (Bin), FSR2H ;load highbyte  
        MOVE?CB	low  (Bin), FSR2L ;load low byte  
local tftstrloop 
local tftStrDone
tftstrloop movf POSTINC2, W	; Get a character, then increment pointer
        BZ  tftStrDone ;All strings must end with 0
       ;Not Null char 
        L?CALL tftWoutput; CALL print char in W to TFT 
        BRA tftstrloop ;Get next chr
      
tftStrDone: ;Null char

endm ;end of macro

EDIT:
You could also use PBP's routine like LCDOUTSTR do, but you must see what this flags do
LCDOUTJ_USED = 1
SEROUT2STR_USED = 1
And how JUMPMAN is used.

[Archangel]

Hi Richard,
Where is the subroutine tft_init ?
I have ordered 2 from your seller should get then before Christmas . . .
These look very promising .. .

[richard]

updated version , complete this time {end must have fallen off first time}

[richard]

MOVE?CB high (Bin), FSR2H ;load highbyte
MOVE?CB low (Bin), FSR2L ;load low byte

that's what I was looking for thanks pedja089

[richard]

that's one down , works like a dream

GLCDSTR?CCB  macro Xin ,Yin ,Bin
        movlw    Xin
        CHK?RP    _X
        MOVWF     _X
        movlw    Yin
        CHK?RP    _Y
        MOVWF     _Y
        MOVE?CB high (Bin), FSR2H ;load highbyte 
        MOVE?CB low (Bin), FSR2L ;load low byte
strloop movf POSTINC2, W ; Get a character
        bnz outstr1 ; Not null char 
        bra exstr
outstr1 MOVWF _g_chr   
        L?CALL _gcga  
        bra   strloop
exstr   
    endm

[richard]

woops - looping in macro for multiple calls is a no go
needs to be like this

GLCDSTR?CCB  macro Xin ,Yin ,Bin
        movlw    Xin
        CHK?RP    _X
        MOVWF     _X
        movlw    Yin
        CHK?RP    _Y
        MOVWF     _Y
        MOVE?CB high (Bin), FSR2H ;load highbyte 
        MOVE?CB low (Bin), FSR2L ;load low byte
        L?CALL  bfill
  
    endm           


  
bfill
Next_Char 
        movf POSTINC2, W	; Get a character
        bnz	outchr	; Not null char 
        bra exstr2
outchr	MOVWF _g_chr 
        L?CALL _gcga  
        bra   Next_Char 
exstr2  return

[richard]

And if you want to avoid CHK?RP, declare variable to BANKA.

the book says that to declare a variable in BANKA is not guaranteed its just a suggestion to the compile process. if this is just an addon to a much larger project I'm thinking CHK?RP is probably a good thing just in case
but I'm open to suggestion

[pedja089]

If variable doesn't fit into BANKA, then MPASM show error.
Used almost in all my project, and always worked fine. Also when coding in ASM, I use SYSTEM, so there is no annoying underscore in front of variable name.
EDIT:
From manual:
BANKx Instructs PBP to locate the variable in a specific bank of RAM.
If things as address of variable, and bank of variable not guarantied if you specify them, then that is idiotic
I'm sure if you specify location and bank of variable, compiler will try to fit in that location, otherwise throw error or at last warning.

[richard]

If variable doesn't fit into BANKA, then MPASM show error.
Used almost in all my project, and always worked fine. Also when coding in ASM, I use SYSTEM, so there is no annoying underscore in front of variable name.
EDIT:
From manual:
BANKx Instructs PBP to locate the variable in a specific bank of RAM.
If things as address of variable, and bank of variable not guarantied if you specify them, then that is idiotic
I'm sure if you specify location and bank of variable, compiler will try to fit in that location, otherwise throw error or at last warning.

yet in 7.3

You can suggest to PBP a particular bank to place the variable in:
penny VAR WORD
BANK0
nickel VAR BYTE
BANK1
If specific bank requests are made, those are handled first. If there is not enough room in a requested bank, the first available space is used and a warning is issued.

but you get a warning

[pedja089]

I newer see that syntax...
I use pdf that came with PBP 3
PICBASIC PRO™ Compiler
REFERENCE MANUAL
Revised March 6, 2013

Bank should be stated after variable type.
eg
ticker VAR BYTE BANK0 SYSTEM 'Creates "ticker" as a BYTE in BANK0, with no Assembly prefix character
wsave VAR BYTE $70 'Creates "wsave" at RAM address 0x70 (hex)

[HenrikOlsson]

Richard,
I'd be happy to help if I can. You're WAY ahead of me with the usercommand and assembly type stuff so I just sit back and admire your work.

Unfortunately the forum (or my computer(s)) no longer allows me to download any attachments. Even when logged all it serves me is a file called attachment.php. Had that happen before, then it worked with another computer but not any more.

/Henrik.

[richard]

I newer see that syntax...
I use pdf that came with PBP 3
PICBASIC PRO™ Compiler
REFERENCE MANUAL
Revised March 6, 2013

Bank should be stated after variable type.
eg
ticker VAR BYTE BANK0 SYSTEM 'Creates "ticker" as a BYTE in BANK0, with no Assembly prefix character
wsave VAR BYTE $70 'Creates "wsave" at RAM address 0x70 (hex)

the forum messes with the white space so the layout of my post was a bit off looking, but look at your reference manual pdf section 7.3 ram allocation page 265 ,thats what I'm referring to.

[richard]

circles and lines and constant string

[richard]

The 2.2 " ili9341 (ili9340c how do tell) arrived today , after resoldering all the dry joints on the module it works .
I have separated things out like this main pbp pgm --- usercommand pbpmod file , an include bas file for either st7735 or ili9341 and a font bas file


in the pbp file
your hardware connections

;----GLOBAL----HW---------   
    SSP_IF VAR PIR3.7      ; must match your spi port 
   tft_dc_bit con  32     ;5      binary weighted pin values 
    tft_cs_bit con 16   ;4 
    tft_rst_bit con 128   ;7
    tft_port var lath ;          ; the output port for control signals

includes

    INCLUDE "glcd_chr.pbpmod"        ;glcdc
    include "tft-ILI9431.bas"      one or the other  not both
;    include "tft-ST7735.bas"      one or the other  not both

    INCLUDE "DT_INTS-18.bas"
    INCLUDE "ReEnterPBP-18.bas"
    INCLUDE "Elapsed_INT-18.bas"
    INCLUDE "font7x8.bas"

in the usercommand file glcd_chr
WIDTH con 320;160 X
HEIGHT con 240; 128 Y
set to appropriate values

and this bit needs to match your spi port too a definite conditional compile potential here

     
TFT_CMD:
spi_cbyte :
    tft_port =  tft_port & (~ tft_dc_bit )
TFT_DATA:    
spi_byte :
@       movff    INTCON , _p_int 
@       bcf     INTCON ,7 
    tft_port =  tft_port& (~ tft_cs_bit )
    SSP_IF = 0
    SSP2BUF = CMD 
    WHILE   SSP_IF =0 ' wait for SPI interupt flag
    wend
    tft_port = tft_port |   ( tft_dc_bit|  tft_cs_bit   )
    
@     movff  _p_int  , INTCON 
return

and off you go

I would have liked to have the hw connections and the height width in the relevant hw include file but that presented too many issues for me

[Aussie Barry]

Hi Richard,

I am keen to replicate the great work you are doing with these TFT displays.
I have looked on eBay for an ILI9341 display and there appears to be a gazillion of them to choose from.
Can you share information on the eBay seller you bought your display from?

Cheers
Barry
VK2XBP

[richard]

hi barry ,these are what I used I'm sure the others would be ok too just make sure the I/f is spi
http://www.ebay.com.au/itm/271683495...%3AMEBIDX%3AIT
http://www.ebay.com.au/itm/191534577...%3AMEBIDX%3AIT

[Aussie Barry]

Thanks Richard.

I have now placed an order and hope to take delivery some time in July.

Cheers
Barry
VK2XBP

[Gusse]

Very nice work Richard!
ILI9341 based TFT display with resistive touch screen could be the module that I was searching.
With STMPE610 touch controller (SPI/I2C) it would be easy to make systems that do not need any additional input devices (buttons/joystick).

[visnja30]

hi Richard,

today arrived TFT display to me from eBay.

I can not wait to start playing with it

Do you can tell me if this is the correct way to connecting peripherals with a PIC processor (pic18f87J11)



TOUCH PANEL connection to PIC

TOUCH PANEL PIC
T_CS PORT F.2
T_DIN PORT F.3
T_DO PORT F.4
T_CLK PORT F.1
T_IRQ PORT F.5


TFT display connection to PIC

TFT DISPLAY PIC
DC PORT C.2
CS PORT C.1
RST PORT C.0
MOSI PORT C.5
SCK PORT C.3




FLASH MEMORY W25Q32 connection to PIC
FLASH W25Q32 PIC

CS PORT H.0
SO PORT D.5
SI PORT D.4
SCK PORT D.6




My TFT module have a XPT2046 touch controller is this the some controller on your board?
Model of my tft module is : TJTCM24028-SPI 2.8 TFT SPI 240X320 v1.1

[richard]

is the correct way to connecting peripherals with a PIC processor (pic18f87J11)

its not the only way but its the way my demo platform is connected

Model of my tft module is : TJTCM24028-SPI 2.8 TFT SPI 240X320 v1.1

my tft touch module is : TJTCM24024-SPI 2.8 TFT SPI 240X320 , I got no docs with it and have not been able to identify the controller. but it has XPT2046 stamped on the chip so it looks the same as yours

[ruijc]

I was looking on ebay and i could not find any 2.8" TJTCM24024.
The only TJTCM24024 i could find is a 2.4"

see here:
http://www.ebay.com/itm/2-4-240x320-...item20eaff07d1

Also the TJTCM24028:
http://www.ebay.com/itm/240x320-2-8-...item41998b289b


Maybe the 24028 means 2.8" and the 24024 means 2.4".

@Richard,
Can you double check you your display is really 2.4" or 2.8"?

Thanks

Regards
Rui

[richard]

forgot the happy snap

[visnja30]

HELLO Richard,
If you could give me some explanations about connections of the LCD display on PIC processor.
I just ordered one piece from eBay and on it I have these pins:


LCD DISPLAY ILI9341 --------> PIC-PROCESSOR
VCC---->3.3V
GND--->ground
LED--->
CS---->
D/C------->
RESET---->
SDI------>
SDO----->
SCK------->

I don't now how to connect it on PIC?