Havn't upgraded to 2.5 yet. Still on 2.47 with MCSP 3.0. I did get the newer version of MPASM but that didn't help.
I'll grab my plastic money and send Bruce the upgrade order. I think he provided my last upgrade.
Thanks for the quick reply..
Havn't upgraded to 2.5 yet. Still on 2.47 with MCSP 3.0. I did get the newer version of MPASM but that didn't help.
I'll grab my plastic money and send Bruce the upgrade order. I think he provided my last upgrade.
Thanks for the quick reply..
"It will never happen here!" just happened here.
My thoughts and prayers for Sandy Hook victims and families.
While getting the last PBP version is good and still cheap, i don't think it solve the problem as it has nothing to do with PBP but MPASM.
You need to open p18f2525.inc file in MPASM Suite directory and and look at the bottom where all config fuses are defined. If you don't find it, you have a faulty file.
Could also be a typo mistake I could be a 1
Make sure the right path is set for the last MPASM version. You may need to point manually MCS to the right path.
Last edited by mister_e; - 17th November 2007 at 21:26.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Lets keep this our secret. I told my wife this was a "must have" upgrade to continue using the software. Already ordered from MCUmart(original supplier).
I looked at the .inc file and found 2 versions in 2 seperate MPASM Suites. Both versions were different. Must be my screwup when upgrading. I've removed 2 old versions of MPLABs and will install the new version next.
Hope this helps..
"It will never happen here!" just happened here.
My thoughts and prayers for Sandy Hook victims and families.
After cleaning up all my garbage and reloading MPLAB 8 I compile to the same error.
Not sure what to try next.
Any suggestions are greatly appreciated.
"It will never happen here!" just happened here.
My thoughts and prayers for Sandy Hook victims and families.
paste your pbp code, mpasm file and pbp .inc file here
Did you manually point MCS to your new MPASM folder?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Thanks for the help Steve. I had MCS pointing to the wrong folder.
It now compiles without errors. The code doesn't work yet but I think it's just setup for the interrupt. Time to RTFM... for the 18F2525.
"It will never happen here!" just happened here.
My thoughts and prayers for Sandy Hook victims and families.
<table><tr><td></td><td>Hehe sh*t happen. Don't worry, i'm not going to tell your wife... 'till you have the software in your hands
</td><td>
</td></tr></table>
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Bookmarks