Hoi Joep,
I use the 2.4m compiler (2.4n is type mistake, I will change that)
Strange is that when I use “print_string(lcd,str1)” in my main
program
This will give strange display.
But when I add one “print_char_5x7 (“ “)” (so print space) than it
prints everything good even
the print_string(lcd,str1)
so:
const byte str1[] = "Nokia 3310"
const byte str2[] = "HELLO world"
forever loop
print_string(lcd,str1)
print_string(lcd,str2)
end loop
gives NO good reading
const byte str1[] = "Nokia 3310"
const byte str2[] = "HELLO world"
forever loop
print_string(lcd,str1)
print_string(lcd,str2)
print_char_5x7 (“ “)
end loop
gives good reading
as if it needs the procedure print_char_5x7 (“ “) although it was
called in the procedure lcd'put
the first time I tried :
procedure lcd'put(byte in data) is
-- pragma inline -- disabled due to complier bug with inline +
pseudovar/arrays.
print_char_5x7 (data)
end procedure
the _lcd_write_data(data) is only for test and will be removed in
print_char_5x7 (data) if we can get it work.
At this moment I have not the slightest idea, accept that in the first
(no good) situation I see no subroutine print_char_5x7 in the
assembly.
In the second (good) situation there is (off course) a print_char_5x7
subroutine in the assembly.
strange
this evening I will send you complete files
Greetz
Richard
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
