For any system that uses relocatable objects plus a linker, it's
the linker that decides about the final locations things are being
placed to, so that's whom you gotta tell about your interrupt
And I gotta ask - why did you choose this two month old thread about C....
What software license are you using to license the code? I did not see anything about this in the package.
What I should specify in the source?
I was looking for a complete solution to the problem and discovered that the thread in google.
The Board helps those that help themselves.
First good rule: PUSH any registers that youR assembler code wants to use on to the stack and POP them off upon exit. That way you know you are screwing nobody up.
Then C argument passing convention is that a first argument is passed in R22,R23; second argument in R24,R25 and beyond that you'll have to Google it.
So passing one byte uses two registers, but you can pass two unrelated byte arguments in R22,R23 for example.
Paul you are resurrecting a 9YO thread.
Ampertronics Pty. Ltd.
* Electronic Design * Custom Products * Contract Assembly
And you are wrong about the ABI anyway. I don't really understand the point in guessing (wrongly) at some answer that even goes on to say "Google the rest"?
And you are wrong about the ABI anyway.
Well, depends on your toolchain. ;) But moot given the necromancer aspects today.
 Oops -- I missed that this was a multi-page thread and no mention of toolchain on the second page. Indeed the thread starts out specifying GCC.
You can put lipstick on a pig, but it is still a pig.
I've never met a pig I didn't like, as long as you have some salt and pepper.
He seems to be making a habit of that:
© 2021 Microchip Technology Inc.