David Kelly wrote:
On Wed, Jan 14, 2009 at 09:14:20AM -0700, dlc wrote:
The solution is to NOT call functions from within your ISR. That is
just evil. Get your data in the ISR, put it in a mailbox or buffer
and have a regularly scheduled function handle the details from
outside the ISR
not. It just isn't that
easy in the AVR with GCC and the code overhead in the ISR was
staggering to me. I don't yet know all the ins and outs of how gcc/AVR
handle ISR's, stack, and other things that I know very well on the PIC.
I'll get there.
DLC
David Kelly wrote:
On Wed, Jan 14, 2009 at 12
I've noticed that too. My Arduino bootloader fits into the 512 byte
boot section when compiled with avr-gcc 3.4, but doesn't when compiled
with avr-gcc 4.3.
You've found an even closer gap with the jump between 4.1 and 4.3.
DLC
Nicholas Vinen wrote:
This seems rather unfortunate
the trick.
I'm going to experiment with this a bit, I like this ability since I
_know_ what variables I'll be playing with. I can set aside a global
temp variable to use whose value does not need saved and handle the
essential register saves myself.
Fun stuff,
DLC
Best regards,
Stu Bell
, but ISR's have to be much more
carefully considered!
have fun,
DLC
Bob Paddock wrote:
Look up:
__attribute__((naked))
That should get you down to the bare metal where you have to do it all.
On Sat, Dec 27, 2008 at 2:52 AM, dlc d...@frii.com
mailto:d...@frii.com wrote:
The subject
. Realistically ISR's are a
thing apart from the rest of the program (usually) so this is rarely an
issue.
IMO, IME,
DLC
Mr Foo
___
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
) and some MEGA (Mega8535). Time to change anyway.
DLC
-dave
--
-
Dennis Clark TTT Enterprises
www.techtoystoday.com
-
___
AVR-GCC-list mailing
plugin
To debug a program? It seems a lot of effort to create avarice to
connect to the ADB engine for debugging for no one to use it. Is there
a group dedicated to that topic perhaps?
thanks,
DLC
--
-
Dennis Clark TTT Enterprises
and all seems fine but for that
nagging warning. What is that? How do I get rid of it? Again, the
compiler does its thing, the linker, elf, hex, list files are all
created and there. But that warning irritates me because I can't find
its origins. Any ideas?
thanks,
DLC
why this code will not function properly? Any
ideas accepted, including Dennis you ignorant expletive deleted...
In the mean time, I'm going to examine the assembler output...
many thanks,
DLC
--
-
Dennis Clark TTT Enterprises
out of date. Can some kind soul tell me where to get a Max OS X distro,
or lacking that, how I can pull in the requisite projects to build them?
What I have works fine for me, but I'm looking at some new parts...
many thanks,
DLC
--
-
Dennis
11 matches
Mail list logo