Can you post your 18F6520.inc file here?
Can you post your 18F6520.inc file here?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I can post that. However, what's the best way to make sure I find and post the right file?
I ask because I have PicBasic, PicBasicPro and the free IDE from Microchip on my computer. So I got to thinking that there might be more than one version on my computer. Is there a way to tell where PicBasicPro is looking?
Thank you
OK, the file i'm talking about is located in the PBP folder. Just to make sure it's the right one, you could still rename it and try to compile... if this return an error, you got it.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Alright, so needless to say with the different free IDE's I'd downloaded before I finally coughed up for the paid versions, I had several duplicate files on my computer. I found the one the computer was using and it is now attached. I looked at the file and saw the areas that it looks like the code is noting to change but wasn't sure how to change.
Okay, so I tried to make changes and deleted some lines and played around with others and then just got more errors. But I viewed that as a positive thing as I was able to at least evoke a change to the system. Going in the wrong direction, but sometimes any movement is good!
I appreciate everyone's patience and input.
Miip, that's the one MPLAB/MPASM use, the one you need to find and modify is located in your PBP folder and should, once modified, looks like the following
If you're using MicrocCode studio, click on View>Compile and Program Option In Compiler tab it should write the compiler path just over the Find automatically button. In my case C:\pbpCode:;**************************************************************** ;* 18F6520.INC * ;* * ;* By : Leonard Zerman, Jeff Schmoyer * ;* Notice : Copyright (c) 2007 microEngineering Labs, Inc. * ;* All Rights Reserved * ;* Date : 07/09/07 * ;* Version : 2.50 * ;* Notes : * ;**************************************************************** NOLIST ifdef PM_USED LIST "Error: PM does not support this device. Use MPASM." NOLIST else LIST LIST p = 18F6520, r = dec, w = -311, w = -230, f = inhx32 INCLUDE "P18F6520.INC" ; MPASM Header ;__CONFIG _CONFIG1H, _OSC_XT_1H ;__CONFIG _CONFIG2H, _WDT_ON_2H & _WDTPS_128_2H ;__CONFIG _CONFIG4L, _LVP_OFF_4L NOLIST endif LIST EEPROM_START EQU 0F00000h BLOCK_SIZE EQU 8
This should cure the problem.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Huh, it worked, sweet!
I copied the notes from the top of the code into the file and it compiled without problem.
I haven't programmed the chip yet to confirm everything in real life, but this is very cool!
So for future learnings, what is the file that we modified? Is this a normal thing to have to change these settings and what are these settings?
Is there a good beginners book, text or source (other than bugging the forum) that would help me in learning?
Thank you, I'll let you know once I test it on the chip.
The best thread i would suggest is the following
http://www.picbasic.co.uk/forum/showthread.php?t=543
Yeah it's an huge one, but everything is covered in. I would suggest Melabs to add a specific statement which could allow to set the configuration fuse in the code, without having to comment them in their .INC file every time we choose a new PIC model. That could be sweet. But yes, this would probably imply they change all .INC file. On the other side... once they're commented... there's no more problem. No default config fuse is still an option.
Probably there's still a pre-compilation access we could have.... who knows. I have a few ideas and i plan to do something around that one day.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks