You're right. I didn't read all the code. I just took "lcd_command" for a
"command" function, but it actually is a general "write" function.
Ten milliseconds still make a long E pulse. It's not the problem.
Maybe I have not read all the code, but I don't see where (when) the address
is written after "Foobar !", before "Hello".
Jason, you could try:
REG_SEL=0;
lcd_command(0x80); // SET DD RAM ADDRESS
(or send again the init instructions)
in order to set "DDRAM Address" back to the beginning of the first line (0)
before calling
puts_lcd("~Hello")
and see what happens.
Le Monday 07 November 2011, KHMan a écrit :
>
> I think you are completely missing the point. None of the above is
> an issue. Jason knows what he's doing, and it's not a 0.1s delay.
> IIRC, Jason got single char calls working, but the loop output
> does not work. I can't see anything wrong with the rest of the
> code. Might need to check the assembly version of puts_lcd().
--
Never jump into a loop!
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
