Serious Debugging required
1. With LCD i also toggle ports and thy do toggle.
2. Checked Connections multiple time with connectivity meter too
3. I wrote simple lcd test program at same pin connections it works like charm(Just ground the RW pin of LCD) .
The confusion is if the Proteus is showing the correct working LCD program it should replicate on hardware. What are my possible directions to dig into this issue? Ofcourse this is debugging but i have done what i knew you guys may help me debugging.
What can be the difference between pic hex or mplab xc8 hex that makes proteus run them correct but not the hardware
[ Edited Wed May 01 2013, 11:17 pm ]
I Also Managed to run another opensource library. It showed perfect output at ISIS. When i write it to controller it does not show anything just straight boxes. Ofcourse this means that lcd is not initialized or something. It points that something is wrong with the hardware right? but No, Why? because of following reasons
1. With LCD i also toggle ports and thy do toggle.
2. Checked Connections multiple time with connectivity meter too
3. I wrote simple lcd test program at same pin connections it works like charm(Just ground the RW pin of LCD) .
The confusion is if the Proteus is showing the correct working LCD program it should replicate on hardware. What are my possible directions to dig into this issue? Ofcourse this is debugging but i have done what i knew you guys may help me debugging.
What can be the difference between pic hex or mplab xc8 hex that makes proteus run them correct but not the hardware
EDIT
I imported the library that i was using in MPLAB to MikroC.
Now it is same code but different tools............ What could be wrong?
[ Edited Thu May 02 2013, 10:13 am ]
[ Edited Thu May 02 2013, 08:48 pm ]
LCD interfacing with Microcontrollers tutorial - 4-bit Mode