the crystal seems to be timing as i have checked on an oscilloscope
how is pic basic pro different from what i am doing?
and is it easier to learn?
the crystal seems to be timing as i have checked on an oscilloscope
how is pic basic pro different from what i am doing?
and is it easier to learn?
Easier with PicBasic Pro ... yes indeed...
There's still some mistake in your code so far... not sure it's working @32KHz anywaysCode:' ' LCD setup ' ========= DEFINE LCD_DREG PORTB ' LCD data port DEFINE LCD_DBIT 0 ' LCD data starting bit DEFINE LCD_RSREG PORTA ' LCD register select port DEFINE LCD_RSBIT 1 ' LCD register select bit DEFINE LCD_EREG PORTA ' LCD enable port DEFINE LCD_EBIT 2 ' LCD enable bit DEFINE LCD_BITS 4 ' LCD data bus size DEFINE LCD_LINES 2 ' Number lines on LCD DEFINE LCD_COMMANDUS 2000 ' Command delay time in us DEFINE LCD_DATAUS 50 ' Data delay time in us LCDOUT "HELLO WORLD"
V0 to to GND? not sure, should be connected to a POT wiper or PWM driven or voltage divider.
Last edited by mister_e; - 19th June 2007 at 00:18.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
The posted TXT is the HEX compiled version of the program below. Download it, rename is as HEX (this forum doesn't permit HEX extensions on attachments at this time), and stuff it into your PIC. It assumes your PIC is running at 4MHz.
Ensure your connect your LCD EXACTLY as per the schematic. If you haven't already done so, go back and check again. Ensure LCD-D4 connects to PortB0 etc. Ensure LCD-D0 thru LCD-D3 are grounded to Vss (0v).Code:' ' LCD Test Program ' ================ ' ' PIC Defines ' ----------- @ DEVICE pic16F84, XT_OSC ' System Clock Options @ DEVICE pic16F84, WDT_ON ' Watchdog Timer @ DEVICE pic16F84, PWRT_ON ' Power-On Timer @ DEVICE pic16F84, PROTECT_OFF ' Program Code Protection ' ' Hardware Defines ' ================ ' ' LCD Display ' ----------- ' Don't forget to GROUND D0-D3 on LCD. ' Define LCD_DREG PORTB ' Port for LCD Data Define LCD_DBIT 0 ' Use lower 4 bits of Port Define LCD_RSREG PORTA ' Port for RegisterSelect (RS) bit Define LCD_RSBIT 1 ' Port Pin for RS bit Define LCD_EREG PORTA ' Port for Enable (E) bit Define LCD_EBIT 2 ' Port Pin for E bit Define LCB_BITS 4 ' Using 4-bit bus Define LCD_LINES 2 ' Using 2 line Display Define LCD_COMMANDUS 2000 ' Command Delay (uS) Define LCD_DATAUS 50 ' Data Delay (uS) ' ' ' Confidence LED ' -------------- ' This LED will BLINK continuously to prove your program is running ' and will verify your oscillator/xtal is good. ' Connect LED either... ' (a) Anode to Vdd (+5v) via 330R Resistor and Kathode to pin A0 ' or (b) Anode to pin A0 via 330R Resistor and Kathode to Vss (0v). ' BlinkyLED var PortA.0 ' This LED will BLINK ' ' Program Start ' ------------- TRISA=%00000000 ' Set all I/O to OUTPUT TRISB=%00000000 ' Pause 2000 ' Wait 2 seconds for Hardware to settle ' should account for the crappiest and ' slowest junk LCD Loop: LCDOUT $FE,1 ' Clear LCD High BlinkyLED ' Set LED pin High Pause 1000 ' Wait one Second LCDOUT "Hello Dj tempo" ' Write message Low BlinkyLED ' Set LED pin Low Pause 1000 ' Wait one Second Goto Loop ' Loop around and do it forever End
If your connect an LED as directed in the listing and it doesn't blink, check your oscillator circuit. Easiest for novices is to use a 4MHz 3-pin ceramic Resonator with integral Capacitors.
If the LED blinks, but still nothing on the LCD, then connect a 10K Pot between Vdd and Vss with the wiper going the the Contrast Vo pin, instead of having that pin connected directly to Ground. Some LCD's don't like having the Contrast pin connected directly to Vss, it applies TOO MUCH contrast and all you get is solid black squares. Yet if that pin is left unconnected, you don't get anything displaying either.
Good luck with the faultfinding - it's actually the fun part of electronics.
Melanie
if you still want to stick to ASM, try the one in attachment.. yeah same concept here, you'll need to rename it to .asm.
That was fun to do
Enjoy![]()
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
why is it that when i copy any of these text files and try to convert it in to a hex file it always shows up with lots of errors, about 60 errors each time.
therefore i can not copy any of these files and download them on to the micro controller as it is not creating a hex file.
But the code i have written shows with no errors anymore just warnings.
am i doing something wrong?
i normaly create a text file in notepad, then i use MPASM to convert the text file in to a HEX file, i then use PROGPIC 2 along with my velleman hardware programmer board to download on to the PIC, it has worked on other PIC such as 16F627 to create effects such as flashing LED's.
i downloaded that file of yours mel, when an LED is connected between pin A0 and +5v it constantley flashes almost 1 sec on 1 sec off, all other data lines on the LCD are now grounded and a 10k pot between +5V and 0V with the wiper conn to V0 (contrast), adjustment of the pot varies the contrast but still no luck wit writing on lcd, still shows as 2 rows of blocks on line 1 and 3.
Last edited by Dj tempo; - 19th June 2007 at 15:50.
If the PIC is flashing the LED then the device is running OK
You say you use Notepad to generate the HEX code via MPSAM. Why not try downloading the MPLAB from Microchip and use its editor to edit the code and then save the file as an ASM format and then quickbuild the project. I did this with the "final lcd code 2" text copied from your original post on 17th. However whilst it compiles fine, it still throws up a few warnings that might give others a hint as to what might be wrong ?
Code:Clean: Deleting intermediary and output files. Clean: Done. Executing: "C:\Program Files\Microchip\MPASM Suite\MPAsmWin.exe" /q /p16F84 "lcdtest.asm" /l"lcdtest.lst" /e"lcdtest.err" Warning[205] C:\LCDTEST.ASM 13 : Found directive in column 1. (__CONFIG) Warning[202] C:\LCDTEST.ASM 20 : Argument out of range. Least significant bits used. Warning[202] C:\LCDTEST.ASM 28 : Argument out of range. Least significant bits used. Warning[224] C:\LCDTEST.ASM 434 : Use of this instruction is not recommended. Warning[224] C:\LCDTEST.ASM 436 : Use of this instruction is not recommended. Warning[224] C:\LCDTEST.ASM 438 : Use of this instruction is not recommended. Warning[205] C:\LCDTEST.ASM 598 : Found directive in column 1. (END) Loaded C:\lcdtest.COD. BUILD SUCCEEDED: Tue Jun 19 16:02:30 2007
Doing the same with Mister-e's code it compiles fine without any errors
I just don't have the hardware to test the resulting HEX file with a 4 line LCDCode:Clean: Deleting intermediary and output files. Clean: Done. Executing: "C:\Program Files\Microchip\MPASM Suite\MPAsmWin.exe" /q /p16F84A "mretest.asm" /l"mretest.lst" /e"mretest.err" Loaded C:\mretest.COD. BUILD SUCCEEDED: Tue Jun 19 16:13:21 2007
Bookmarks