For Flowcode users to discuss projects, flowcharts, and any other issues related to Flowcode 5.
To post in this forum you must have a registered copy of Flowcode 5 or higher.
If the project clock setting and the chip configuration is correct then the display should work with the code as is.
Have you done a 1 second LED flasher test on the hardware to check you have everything setup correctly in Flowcode?
To do this create an endless loop which outputs 1 to a LED, waits a second, outputs 0 to the LED and waits another second. If the delays on the hardware are equal to 1 second then you have everything setup correctly.
i tried this two different ways, 8Mhz (osccon=70 with ppl enabled, and 32Mhz (osccon=fo) with ppl disabled, all i get is a blank lcd....didnt have time to do 1m/s test as im on lunch break but i think it will be fine, my attachement is below, could you take a peek
ben, i finally got around to checking this and something is broke, c command and all is fine but the lcd doesnt work at 32Mhz, shows blank, i do have the 1m/s on/off pulse as veiwed with pico scope, what do you think?
Have you tried at lower speed, e. internal osc 8MHz?
I'm only asking since your RS and enable pins have been swapped.
Are you using your own LCD? If you was using Eblock EB005 with jumper on default settings, then it won't work until you swap RS and enable connections on your flowchart.
I have set up 16F1827 and running int osc at 32MHz.
I can see the issue now.
when running int at 8 MHz: there is a pulse that's on for 319us then off for 7us back on for 319us. LCD is working.
When running at 32MHz the pulse os on for about 319us but this time instead of being off for 7us, it goes off for 0.136us on for 0.136us back off for 0.136us then on for the 319us. LCD is not working.
I will have a play with the delays as see if I can get anywhere. If not you may need to wait for matrix to work out what the issue is.
thanks martin for checking that out and working on it for me, was starting to think i was crazy, i've tried it with multiple displays but never payed attention to scope details as i didnt know what to expect, the reason why i switched the r/s and enable pins is because i designed a new pcb proto board for some friends on an automotive network i frequent (autonerdz)http://dl.dropbox.com/u/10367218/ordere ... 0layer.jpg by switching those pins it makes the traces look pretty
I tried to use a LCD at 32 MHz. Also without succes.
I made a trail and error program in which the delay time in RAWSEND and in START, CLEAR procedures is varied. The oscillator frequencies used are 8,16 and 32 MHz.
In RAWSEND the delay time is varied from 10 to 200 usec. In START and CLEAR from 1 to 4 msec.
The result is that at 8 and 16 MHz, nearly always the LCD is working correctly. With 32 MHZ the LCD is not working correctly.