6 hours for a comma, a space, and some caps.....

[Chris Barron]

I'm not sure if this will aid anyone, but I do feel the need to expose my own stupidity

The problems turned out to be all right here

 
ASM
INT_LIST  macro    ; IntSource,        Label,  Type, ResetFlag?
        INT_Handler   TMR1_INT,  _Transmit,   PBP,  yes
        INT_Handler   TMR0_INT,  _BlankGain,   PBP,  yes
        INT_HANDLER   CMP2_INT   _ GetEcho,    PBP,  yes
    endm
    INT_CREATE               ; Creates the interrupt processor
ENDASM

There are three errors that I let slip in there.
Bo

Okay if you're being stupid, then I will have to expose my extreme stupidity (and curiosity) by asking you to explain what the errors were in the code, please !

I'm not familiar with this interupt technique but if i were to use it what should I be aware of ?

[Archangel]

Hi Bo,
Don't feel like the Lone Ranger, we all have that soft spot in our foreheads (see mister_e's avatar ). What you might try in this particular situation is copy Darrel's code, into the top of your's, rather than including it, then <b> "I THINK" </b>MCS will compile and give you accurate line number info for the error.<br>
Chris:
extra space between int_list and macro, missing comma after CMP2_INT, MPASM is fussier than your 5th grade English teacher.

[ErnieM]

6 hours is nothing, I spent most of a working week finding some missing brackets on CODE THAT COMPILED WITHOUT EVEN A WARNING.

(Note from user: bad code (syntax) should provoke a good compiler to say something.)

[boroko]

Hi All,
I was presenting all this primarily show that this kind of thing can really take you for a ride.

Navaidstech: I agree that taking a break gives you new eyes to look at things. It doesn't make up for my ignorance, but it usually helps me.

Chris: Joe S. explained the things that I missed. To amplify, the third was the capitalization of the third INT_HANDLER. As for the interupt technique, it is a macro that is at the heart of DT_INTS. If you haven't used it before, you may want to look at it. I was afraid to use interrupts before I found Darrel Taylor's program that simplifies the whole process. Absolutely wonderful piece of work.

Joe S: I hadn't thought of literally copying the code in like that. That is obvious once you think of it and definitely a "soft forehead" moment.

Those are the kind of thing that I was trying to pull out of the list by starting this. Maybe a thread where people are exposing the traps that they have fell into and the way that they got out of them. A place to go to reduce some of the noise on the list and improve all of our skills. Maybe the effort will keep the list from burning out the major contributors, so we can preserve their attention for the cool stuff.

I hope that someday, when I grow up, one of my posts will become a sticky. Then I will have arrived.....

Bo

[Darrel Taylor]

I hadn't thought of literally copying the code in like that. That is obvious once you think of it and definitely a "soft forehead" moment.

Noooooo .... please don't do that.

That's my biggest pet peeve.
It's an Include module, not a cut&paste snippet.

And as you've already found out, the errors were in your code, not the include file, so it would have accomplished nothing.

Yes, you would have received errors with line numbers referenced to your main program file, but they would not have been any more informative since those lines would still not have pointed to the original problem. And now your main program is filled with stuff that looks like Russian or Chinese (a.k.a. ASM macros). Trying to find errors in your own code only becomes more difficult and confusing.

Then you end up editing something that shouldn't be edited and suddenly nothing works, and I get blamed again.

Put the Include file down and step away from the computer, before you hurt someone.
<br>

[Archangel]

Noooooo .... please don't do that.

That's my biggest pet peeve.
It's an Include module, not a cut&paste snippet.


<br>

I meant it for troubleshooting only Darrel, not to steal your code. Of course the final cut must use it as "licensed" by you, as an include file.

[Darrel Taylor]

I meant it for troubleshooting only Darrel, not to steal your code. Of course the final cut must use it as "licensed" by you, as an include file.

Well, the only "License" is ... Yours to use as you see fit.

So it's just my own personal problem, wish, desire ... peeve.

I seem to be getting more of those, which are Directly proportional to the lack of color in my hair at any given time.
<br>