View previous topic :: View next topic |
Author |
Message |
Zaki
Joined: 30 Nov 2005 Posts: 8
|
Help required urgently !!!! |
Posted: Tue Jan 17, 2006 8:01 am |
|
|
Ok now i had my codee burned onto the PIC 18f252 then i used the erase function in the mplab ....
Trying to burn again onto the chip just configure the configuration bits ... |
|
|
rwyoung
Joined: 12 Nov 2003 Posts: 563 Location: Lawrence, KS USA
|
|
Posted: Tue Jan 17, 2006 9:03 am |
|
|
Why not just reprogram the chip, including the config bits this time. _________________ Rob Young
The Screw-Up Fairy may just visit you but he has crashed on my couch for the last month! |
|
|
Zaki
Joined: 30 Nov 2005 Posts: 8
|
|
Posted: Sun Jan 22, 2006 11:48 pm |
|
|
I dont know how . I got the PIC 18f252 and i wrote code using PCH compiler , then i programmed that code onto the PIC and it was functioning . Then i decided i want to change the code . So i erased that code . Erasing the code just erased with it the past configuration bits and ID . But i aked myself here how come , even if i try putting the old code again i get the same problem ? So i concluded the problem is not with my code its that the configuration bits and Id were somthing already there on the PIC before i put my code . I dont know how to restore them back ?? |
|
|
rwyoung
Joined: 12 Nov 2003 Posts: 563 Location: Lawrence, KS USA
|
|
Posted: Mon Jan 23, 2006 8:39 am |
|
|
What programmer are you using?
Have you read its manual?
When you look at the HEX file created after compiling you should be able to identify the line(s) with the CONFIG bits. I don't believe it is possible to tell the PCH compilers to exclude them.
You do have a #FUSE statement or statements at the start of your program, right? Look at your code and LST file to be sure the resultant bits are correct. _________________ Rob Young
The Screw-Up Fairy may just visit you but he has crashed on my couch for the last month! |
|
|
|