Post by thread:[PIC] MPLAB 8.73

Tagged > Message[302] C:\ASM\BOO.ASM 89 : Register in operand not > in bank 0. Ensure that bank bits are correct. > Anyone know why this happens? It's just a reminder See Help/Topics/MPASM Assembler/Messages/Assembler You'll note that the build completes, which wouldn't happen with a real erro

John Gardner wrote 2012-02-13 03:29: > These snazzy late-model PICs have a lot of pgm memory. > And you need it, to turn off all the "features" that keep your > pgm from working.... Grumble grumble.... > > Anyway, thanks. What "fetures" keeps your pgm from working ?? If this has anything to do with the warning about banks, that doesn't keep anything from wokring. It is just a *warning* after all... Jan-Erik

On Sun, February 12, 2012 5:16 pm, John Gardner wrote: > Thanks, Joe. > > That's where all that stuff is - I rummaged through HELP earlier > and managed to not see it, I guess. > > Worries me, but I know what'll happen if I turn it off... If you're worried about turning off the warning, you don't have to do it globally- you can put an 'errorlevel -302' to turn off the warning immediately preceding the opcode, and then turn it back on with an 'errorlevel +302' (I may not have gotten the syntax exactly correct, but it is something on that level) In general, warnings are there for good reason, though I think the bank warnings can get overwhelming. I'm sure enough people got burned and complained about it- which is why it is the default setting. Matt Bennett Just outside of Austin, TX 30.51,-97.91 The views I express are my own, not that of my employer, a large multinational corporation that you are familiar with

Matt Bennett wrote 2012-02-13 14:54: > On Sun, February 12, 2012 5:16 pm, John Gardner wrote: >> Thanks, Joe. >> >> That's where all that stuff is - I rummaged through HELP earlier >> and managed to not see it, I guess. >> >> Worries me, but I know what'll happen if I turn it off... > > If you're worried about turning off the warning, you don't have to do it > globally- you can put an 'errorlevel -302' to turn off the warning > immediately preceding the opcode, and then turn it back on with an > 'errorlevel +302' (I may not have gotten the syntax exactly correct, but > it is something on that level) > > In general, warnings are there for good reason, though I think the bank > warnings can get overwhelming. I'm sure enough people got burned and > complained about it- which is why it is the default setting. > And it's hard to find any assembler source code where that particular warning is *not* turned off... :-) And, of course, disabling a warning doesn't change the way the code works as such in any way. Jan-Erik. > > Matt Bennett > Just outside of Austin, TX > 30.51,-97.91 > > The views I express are my own, not that of my employer, a large > multinational corporation that you are familiar with

On Mon, Feb 13, 2012 at 9:10 AM, Jan-Erik Soderholm <spam_OUTjan-erik.soderholmTakeThisOuTtelia.com> wrote: > And it's hard to find any assembler source code where that > particular warning is *not* turned off... :-) > > And, of course, disabling a warning doesn't change the way the > code works as such in any way. Disabling warnings is like riding a bike without a helmet. When you fall, it could ruin your day. -- Martin K

Thanks, everyone. I'm pretty reluctant to inhibit assembler messages - You <can> turn off just messages in "Build Options", without affecting Warnings & Errors. Seemingly. The trouble with all the bogus messages is they condition you to ignore messages, period - So you'll miss the one that matters. Matt's idea sounds worth pursuing - Maybe a banksel macro that includes suppressing -302 messages? Presumably Warnings & Errors will still surface... still generate a warning

M.L. wrote 2012-02-13 16:06: > On Mon, Feb 13, 2012 at 9:10 AM, Jan-Erik Soderholm > <.....jan-erik.soderholmKILLspam@spam@telia.com> wrote: >> And it's hard to find any assembler source code where that >> particular warning is *not* turned off... :-) >> >> And, of course, disabling a warning doesn't change the way the >> code works as such in any way. > > Disabling warnings is like riding a bike without a helmet. When you > fall, it could ruin your day. > Now, no one talked about disabling *ALL* warnings. *Only* the specific 302 warnings about banks.

John Gardner wrote 2012-02-13 19:19: > Thanks, everyone. I'm pretty reluctant to inhibit assembler > messages - You<can> turn off just messages in "Build > Options", without affecting Warnings& Errors. > > Seemingly. The trouble with all the bogus messages is they > condition you to ignore messages, period - So you'll miss > the one that matters. > > Matt's idea sounds worth pursuing - Maybe a banksel macro > that includes suppressing -302 messages? > Doesn't work, of course. It is not the banksel as such that produce the 302 messages (not warning as I wrote in an earlier post). It is any other command that access a register *not* in bank 0. Most just add a single directive to supress the 302 messages and are happy with that. :-) Jan-Erik. > Presumably Warnings& Errors will still surface... > still generate a warning