It happen because you probably have selected INH8XS file format under the MPASM check box. use INHX8M instead.
Yes indeed, CTRL + PrintScr, then you paste it in Paint or whatever else to edit it.Is your result box a screen capture?
It happen because you probably have selected INH8XS file format under the MPASM check box. use INHX8M instead.
Yes indeed, CTRL + PrintScr, then you paste it in Paint or whatever else to edit it.Is your result box a screen capture?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Good, That worked. However, when I add a line to the top of the program as simple as :
TRISA = %00000000
AlarmOUT VAR PORTA.0
I get
Error[113 cbp\pbpic14.lib 1588 : Symbol not previously defined (port A)
Error[113 cbp\pbpic14.lib 1612 : Symbol not previously defined (port A)
Error[113 cbp\pbpic14.lib 1619 : Symbol not previously defined (port A)
.........Etc.
Also, going back to the previously working "elapsed timer demo" and using the MPASM settings I get the same type of errors there if I try to add a port reference.
I can get the result box into Photoshop but can't get the edited image to paste into the forum.
Thanks
Last edited by Homerclese; - 3rd March 2007 at 19:44.
Thanks,
Homerclese
<table><td></td><td>It really drives me nuts when it work here but not elsewhere. Ok then just copy/paste your code here and place it between code bracket. you just need to type...
[code]
---paste your code here---
[/code]
to edit your screen capture, use Windows paint. If you don't find it, click on Start> run then type mspaint. then save it to a .jpg file</td></table>
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
"Not previously defined" error was caused by having PortA instead of PORTA. It's 4AM and I think MPASM is the cause of some strange chip behavior. Only when I uncheck MPASM do I get back to a working 16F877 chip. I patched pic basic Pro to 2.40 but any attempts to go higher are met with "unknown version" errors. I'll hit it again tommorrooowww....
"Homer sleep now".
Thanks,
Homerclese
somehow strange but you could still try to uncheck the Case Sensitive option in MCS.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Darrel,
I recently replaced the On Interrupt code in an existing program with the RX_INT and it works great.The code was reduced by 127 words and I was able to eliminate a interrupt anomaly I sometimes experienced.Though compilation was successful,I would get a warning "Temp variables exceeding T4",which was generated in the ReEnterPBP.bas.I found what caused it in my code was this long comparison evaluation "if (fwd_cycle_comp = 1 and portb.4 = 1 and portb.2 = 1 and porta.0 = 1) or (datain1 > 1638) then".If I shortened the code the warning disappeared.Since everything was working fine I commented out the error routine for T4.I am using the latest Mplab and PBP.
Thanks & Good Job
As long as the long formula isn't in the Interrupt Handler, you should be OK.
There's no way for the program to tell if a complex formula is in the handler or somewhere else. So I err'd on the side of caution and had it give a warning no matter where it is.
Glad you like it.![]()
DT
Bookmarks