View previous topic :: View next topic |
Author |
Message |
slahiri Guest
|
Picstart plus |
Posted: Wed Mar 05, 2003 5:53 am |
|
|
Hi guys,
Is anyone using PICstart--plus. When I try to burn my code it is giving me configuration bits error. I was able burn once when I was working with LCD and I was able to display some thing on the LCD so I know my code works. Now it is keep on giving me this error. Any idea what is going on here.
___________________________
This message was ported from CCS's old forum
Original Post ID: 12367 |
|
|
Steve H. Guest
|
Re: Picstart plus |
Posted: Wed Mar 05, 2003 1:33 pm |
|
|
If you had the code protect bits set you won't ever be able to reprogram the device again.
-OR-
If the device is Windowed you need to UV erase it after every write.
Steve H.
___________________________
This message was ported from CCS's old forum
Original Post ID: 12385 |
|
|
Hans Wedemeyer Guest
|
Re: Picstart plus |
Posted: Wed Mar 05, 2003 4:49 pm |
|
|
If it is a flash device PIC16F or PIC18F, Click the "Erase Flash device" button first, then program as normal.
If it is a flash device and it is code protected, you can reprogram the deive by using "erase flash device" or program the entire device.
___________________________
This message was ported from CCS's old forum
Original Post ID: 12405 |
|
|
slahiri Guest
|
Re: Picstart plus |
Posted: Thu Mar 06, 2003 6:16 am |
|
|
:=If it is a flash device PIC16F or PIC18F, Click the "Erase Flash device" button first, then program as normal.
:=
:=If it is a flash device and it is code protected, you can reprogram the deive by using "erase flash device" or program the entire device.
Thank you I will try that.
___________________________
This message was ported from CCS's old forum
Original Post ID: 12420 |
|
|
slahiri Guest
|
Re: Picstart plus |
Posted: Sat Mar 08, 2003 7:01 am |
|
|
:=If you had the code protect bits set you won't ever be able to reprogram the device again.
:=
:=-OR-
:=
:=If the device is Windowed you need to UV erase it after every write.
:=
:=Steve H.
It was still doing the same thing I called microchip they told me I needed the upgarde and they will send me the upgrade kit. Thanks
___________________________
This message was ported from CCS's old forum
Original Post ID: 12478 |
|
|
Guest_X44 Guest
|
PICStart Plus Communications Error |
Posted: Mon May 03, 2004 6:46 pm |
|
|
I'm using PICStart Plus R11 to program a 16f84.
Sometimes it works, most of the time it doesn't.
I receive a communications error saying it "cannot receive.".
I didn't change anything at all when it previously worked.
Am I missing out on the setup? |
|
|
Guest_X44 Guest
|
PICStart Plus Communications Error |
Posted: Mon May 03, 2004 6:47 pm |
|
|
Another thing, I'm launching the PICStart Plus within MPLAB 5.11 |
|
|
caffca
Joined: 28 Apr 2004 Posts: 5
|
LED PWM |
Posted: Tue May 04, 2004 11:53 am |
|
|
Hi there,
I am also using picstart plus with MPLAB 5.11.......
I could really do with some pointers..... I am trying to get even just 1 LED to pulse via PWM.... I seem to be able to read and write to the pic chip on the picstart plus, but nothing happens on my circuit - i.e. the LED doesn't do anything.....
I'm using a quartz clock - AEL121-CSN 8.000 as the clock.....
And I'm using a PIC16F873
Any help on this matter would be greatly appreciated..... maybe a very simple source code example and matching schematic.....
Regards,
L |
|
|
ali_baba
Joined: 04 Feb 2011 Posts: 3
|
CCS PICSTART Plus |
Posted: Fri Feb 04, 2011 9:11 am |
|
|
Hi,
I have CCS C compiler and PICSTART plus.
I have compiled my sw, but I haven't sent to 16F74 via PICSTART.
I try import hex file to MPLAB but it gave an error 'not recognize file'.
How can I send hex file to PICSTART?
Anybody can help me please. |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9245 Location: Greensville,Ontario
|
|
Posted: Fri Feb 04, 2011 12:59 pm |
|
|
Ok...FIRST...
Look in the pulldown 'PROJECT' and see if there's a 'Build Configuration' option.
If so be sure to select 'release' and recompile your code.
You need to do this in order to get rid of the 'debug' code that MPLAB will insert into your program and well as 'other things'.
I've been told by the MPLAB guys that a user selectable option will be allowed in MPLAB release 8.66, later this month.
I'm using 2 Picstart Plus programmers, have for years (ok, decades). Current firmware is v 04.50.03 and both are 'flash upgradeable' types.
Is your PS+ connected to a read comport (DE-9 connector) or a USB<>RS232 dongle ?
Hmm.. your version of MPLAB is rather old. v7.51 (on Win 98SE) was stable and did not have the 'debug' problem. I'm running v8.63 (on Win XP Pro) now but have to select 'release' for every project.
Might want to check on Microchip's site to see if it's a Windows version vs. MPLAB conflict.
As already stated, be sure to erase the PIC before you program it. Also check the config bits in the pulldown window to be sure they're correct. |
|
|
ali_baba
Joined: 04 Feb 2011 Posts: 3
|
Thank you temtronic |
Posted: Sun Feb 06, 2011 3:50 pm |
|
|
Hi temtronic,
I have download and installed last MPLAB, and updated PICSTART Plus software. And happy end.
Thank you very much. |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9245 Location: Greensville,Ontario
|
|
Posted: Sun Feb 06, 2011 6:01 pm |
|
|
Glad you're 'up and running'...!
Just be sure to set the build configuration option to 'release' and recompile (build) your project other wise MPLAB will be in 'debug' mode and your code won't work as expected. You only have to do this once per project.
v8.66 will fix this bug. |
|
|
ali_baba
Joined: 04 Feb 2011 Posts: 3
|
LCD vertical lines problem |
Posted: Wed Feb 09, 2011 3:34 pm |
|
|
Hi temtronic,
I have data collector which includes 2x16 LCD. I have developed it with PIC16F74 and assembler. LCD runs normally but rarely I see absurd vertical lines on it. I heard it is error of PIC microcontrollers. Do you have information about this problem?
Thank you. |
|
|
temtronic
Joined: 01 Jul 2010 Posts: 9245 Location: Greensville,Ontario
|
|
Posted: Wed Feb 09, 2011 4:41 pm |
|
|
If it's the LCD not updating data correctly, it could be a timing problem due to another LCD module used instead of the original one.
You'ld have to see when it occours, rather hard I know. Maybe when the data is being stored into eeprom AND a keyboard input OR a serial interrupt is happening 'at the same' time?
Maybe due to external EMI ? Some equipment is briefly causing a 'glitch', say a CFL ,mig welder,toaster oven ?
Is the power supply well filtered, all solder joints good,shielded enclosure?
The list is endless and may be very hard to track down. There is nothing inherently wrong with PICs. If the code works well for days on end, I'd rather suspect some 'external' force(EMI) or a combination of tasks happening when you don't think they are. |
|
|
|