Exit terminates the calling task. Terminate kills any task. Try to look at the actual source code for these routines. Most are pretty small and self...
In looking at AvrXWriteEEProm() I noticed that it doesn't appear to turn off interrupts between writing EEMWE and EEWE. Seems to me that this leaves the door...
Yes. Read the source. There are some papers on getting started, etc. And the header file "avrx.h" has info, but to get the true skinny you need to look at...
OK!I'll read those files! BTW,will avrx support other C_compilers,such as CVAVR? and will avrx be port to 51mcu AND msp430? ... etc. And ... need to...
No, no and no. The primary reason AvrX is so great is that it is highly tuned assembly code for the AVR processor. It would be a complete rewrite to support...
I think I've found a rather nasty bug in IntProlog(). I've been having one hell of a time trying to figure out why r1 is occasionally non-zero in my interrupt...
R1 bug in IntProlog()I am impressed: that must have been *very* hard to figure out. What I don't understand is how R1 is getting set with a non-zero value. It...
Actually, I thought it might be the interrupt handlers at first, too. But I spent some time looking at the disassembled code for my interrupt handler and...
BTW, Isn't r1 part of the saved state when interrupting anything but the idle task (which doesn't use r1 itself) ? So I would think that I wouldn't need to...
I ended up getting very sick last night (there's something really evil going around) and my last two emails don't really make much sense. Sorry. -brian...
Hi Larry, Strange that you should mention that nested interrupts may be a problem, because you're right! I spent some time today trying to track down some ...
R1 bug in IntProlog()I have not been able to really focus on this issue due to other projects. My previous projects with AvrX generally have been stable so I...
Yeah, I did mean the RAM. AvrX is actually impressively clean. I really like it, although I've got to get through all of these interrupt issues. I'm starting...
Just to follow up on this issue, for those who have been following it. There doesn't appear to be *any* problem with AvrX. Brian tripped across the problem...
I am in the process of writing code for a fairly large (for me) design. Up to now I have written several little AvrX based programs that test out one or more...
I think your approach is the best way. AvrX is a very simple statically linked system. That is why it is so small and fast. The macro system for creating the...
Hi Leon, I have had the exact same problems as you write about in your posts. I then downloaded the "fixed" version of the timers example from the Files...
The biggest difference between the simulator and the actual hardware is the fuse bit settings. Depending upon chip that could affect your clock options, JTAG...
Hi Larry, I am using the at90s8535, and the 3 fuses "Lock1" "Lock2" and "FSTRT" are all left unprogrammed (Unchecked in PonyProg) /Rene ... hardware is the ......
Then the actual hardware should work identical to the simulated chip. If it doesn't work at all, then you have either a wiring problem, a clock problem or a...
Hey guys, I'm having the same problems. I just downloaded avrx2.6e for WinAVR and I'm trying to get the timers example to work. I'm using an ATMega128 so I...
Hi Chris, I see the same thing, in AVRstudio4 the CPU loops in the AVRX_SIGINT (SIG_OVERFLOW0) when it's not servicing the tasks, maybe it is supposed to ? Put...
The warning you mentioned is just the ELF->COFF converter complaining about stuff it can't figure out. It is actually a limitation of the COFF file format,...
The examples still won't work in target..... could it be possible that someone can compile the timers example to an at90s8535 (LEDS are hardwired to PORTB on...
Hello all i user the program WinAVr to programm and coding Software for my Atmega128. Yesterday i found this great Yahoo group a solve some Problems... But now...