Re: [avr-gcc-list] Any SimulAVR or avrtest users out there?

Aurelien Francillon wrote: > I don't know if simulavr have one (or plan to have one) but that > would be very useful ... Sure, both the old simulavr as well as simulavrxx offer that feature. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/

Re: [avr-gcc-list] Any SimulAVR or avrtest users out there?

Georg-Johann Lay a écrit : > > IMO it is absolutely required that a simulator can run as gdb server for > avr-gdb. > > Stand alone simulators like avrova seem not to have this functionality. > I just skimmed the avrora site and saw no note pointing in that > direction, maybe I middes it. Avror

RE: [avr-gcc-list] Re: eicall & EIND

At 16:10 11.3.2009, you wrote: > We are using Nut/OS, where you can setup interrupt handler > address at run time. Interesting. Is this done through a single "master interrupt"? You cannot rewrite the vector table real-time. Just curious. 1) I like your laughing approach. But finally "I thi

[avr-gcc-list] Has anyone gotten the Pololu software working on Mac OS X?

There are instructions up to a point, at https://www.blogger.com/comment.g?blogID=5983110881018172452&postID=1421669160224186648&page=1 (pointed to by the Pololu web site), but having followed that path I get a strange failure that I don't know how to diagnose. When I modify Makefile as sugg

RE: [avr-gcc-list] Re: Wierd Calls.

From: d...@mobilefusioninc.com [...] I'm still puzzled as to why the compiler didn't change: // This takes 53uS at 4 MHz Bin = ( A / Data_Divisor ) // Data_Divisor is a constant, 32. into // This takes 8.9uS at 4 MHz Bin = ( A >> 5) Just guessing, but it may be trying to preserve trunc

Re: [avr-gcc-list] Re: Wierd Calls.

> > > > The assembly above comes from the __udivmodhi4 helper function (found > in libgcc.a), which is a helper function for performing a 32-bit > divide. > Let me guess.. It was stuck on below the LCD routines in memory, and AVR Studio didn't know that somehow? Gak.. Ok. I'm still puzzled as t

Re: [avr-gcc-list] Re: Wierd Calls.

Hi David, On Wed, Mar 11, 2009 at 7:23 AM, David VanHorn wrote: > > Well.. Still flogging the horse here. ...snip... > +0622:   1BAA    SUB   R26,R26    Subtract without carry > +0623:   1BBB    SUB   R27,R27    Subtract without carry > +0624:   E151    L

Re: [avr-gcc-list] Any SimulAVR or avrtest users out there?

Weddington, Eric schrieb: Hi All, There's a lot of new work being done at the SimulAVR project: Specifically the "old" simulavr project hasn't had much maintenance done on it in years. There is an "avrtest" project (hosted at WinAVR) that is us

RE: [avr-gcc-list] Any SimulAVR or avrtest users out there?

> -Original Message- > From: > avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org > [mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu. > org] On Behalf Of John Regehr > Sent: Wednesday, March 11, 2009 11:23 AM > To: AVR-GCC > Subject: Re: [avr-gcc-list] Any SimulAVR

Re: [avr-gcc-list] Any SimulAVR or avrtest users out there?

Avrora's main advantage is that it simulates radio chips (CC1000, CC2420, etc.) found on sensor network nodes. These would be a lot of trouble to replicate, so I doubt that Avrora's going to go away no matter how good the new simulavr gets. Avrora is also very easy to extend compared to every

Re: [avr-gcc-list] Any SimulAVR or avrtest users out there?

I agree with Tristan. I looked at simulavr a couple of years ago for the project I was on to do some preliminary testing before I had hardware available. I got frustrated and gave up on that front. So instead we found something else to do until manufacturing had boards available. Pete On Wed,

Re: [avr-gcc-list] Re: Any SimulAVR or avrtest users out there?

On Wed, Mar 11, 2009 at 10:20 AM, Tristan Gingold wrote: > > On Mar 11, 2009, at 5:13 PM, Weddington, Eric wrote: > >> Hi All, >> >> There's a lot of new work being done at the SimulAVR project: >> > > > Before working on avrtest, I tried simulavr.  I

Re: [avr-gcc-list] Any SimulAVR or avrtest users out there?

On Wed, Mar 11, 2009 at 10:13:52AM -0600, Weddington, Eric wrote: There's a lot of new work being done at the SimulAVR project: FYI: There's avrora [1] as well. While it's written in Java (which I detest), it worked so much better for me than simul

[avr-gcc-list] Re: Any SimulAVR or avrtest users out there?

On Mar 11, 2009, at 5:13 PM, Weddington, Eric wrote: Hi All, There's a lot of new work being done at the SimulAVR project: Before working on avrtest, I tried simulavr. It was so broken that I gave up. I think you don't need to keep backward

[avr-gcc-list] Any SimulAVR or avrtest users out there?

Hi All, There's a lot of new work being done at the SimulAVR project: Specifically the "old" simulavr project hasn't had much maintenance done on it in years. There is an "avrtest" project (hosted at WinAVR) that is used exclusively as a simulator

RE: [avr-gcc-list] Re: eicall & EIND

> We are using Nut/OS, where you can setup interrupt handler > address at run time. Interesting. Is this done through a single "master interrupt"? You cannot rewrite the vector table real-time. Just curious. > Now, I have a bootloader. Simple, no interrupts, part of it > is called from an ap

RE: [avr-gcc-list] Re: Wierd Calls.

> -Original Message- > From: > avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org > [mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu. > org] On Behalf Of David VanHorn > Sent: Wednesday, March 11, 2009 8:24 AM > To: AVR-GCC > Subject: Re: [avr-gcc-list] Re: Wierd Ca

Re: [avr-gcc-list] Re: Wierd Calls.

Well.. Still flogging the horse here. I have the .S file, but I don't know how to interpret it. I carved up the statement even further, and moved the declarations so all the vars are in ram so I can watch them easily. A = Raw_Data[0][Raw_Data_Index]; // Gives the expected result. Bi

RE: [avr-gcc-list] Re: eicall & EIND

Hi Stu, I appreciate your explanation and links. Thanks. I know, what are you talking about. Maybe I did not described my case at all. All suggestions are to live with eind==0. For this gcc can generate icall instead. We are using Nut/OS, where you can setup interrupt handler address at run ti