Jan Panteltje said:
Actually it was the wrong font, the one with the teletext graphics is this one:
ftp://panteltje.com/pub/txtfont.h.txt
Both are interchangable, but those graphics blocks start above 127 dec.
If you are short of space you can use only 32 through 127 of the table,
and always add 32 (space) for ASCII.
Thanks again, that file had a bit more info too
I got it to display them all on the lcd now,
using just 8x8 as the 9th byte is unused, although I havnt deleted it from
the table.
and croped the table to 32-127 as u said.
had a bit of a headache b4 I realised Id got my nibbles swaped, as it was
only a problem in the few chars wich were wider than 4bits.
I cant say I fully understand these epson LCD timings but after a bit of
jiggling with random delays and swaping edges it seems to work now, although
a touch tempermental, if anyone wants to see the code just ask, but cba to
comment it unless someone needs to use it, I gues these epson LCD are quit
old now.
I find if I use bit set on an output port followed by another bitset on a
different bit on the same port the first bit gets cleared.
Also dont quite understand exactly how it lays down the data in memory when
you specify a data array in the program space on the dspic30f with the
microlab mc30 compiler, as theres only 3 bytes used per 4 bytes of prog
space, looking at the examples I assume it only uses the low word, and so
wastes 1/3 bytes.
Spent a while trying to get the tbldr function to work before I gave up and
put it in the data space and it seems fine, although I think I found other
problems why it wasnt working, probably not got a lot of the 2k ram left
now, maybe il try maping the code space into data space.
When I look at the disaembly it seems to be accesing the normal data array
at 0x810 wich coresponds to actual code, maybe it doesnt show the final
linked addresses, oh wait prog and data are seperate.
Colin =^.^=