simulavr-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Simulavr-devel] register trace not longer available?


From: Klaus Rudolph
Subject: Re: [Simulavr-devel] register trace not longer available?
Date: Mon, 23 Apr 2012 20:32:36 +0200
User-agent: Thunderbird 2.0.0.23 (X11/20090817)

Lars Immisch schrieb:
> Hi,
> 
>> after I found that serialrx/serialtx is not longer working, I tried
>> out to trace the execution of a file. I see, that there is no
>> memory tracing anymore.
>> 
>> Why this feature is removed?
>> 
>> Older versions prints e.g. for registers:
>> 
>> LD R31, Y+ Z=0x1234
>> 
>> Actually no memory access is traceable.
>> 
>> Is someone else interested to get the old features back? If so, I
>> would restart my project from my old sources and try to integrate
>> the new devices and keep the old features.
> 
> I'd be interested. I'm starting to use simulavr for regression
> testing via python.
> 
> I have a few patches open on the tracker that make it possible to run
> multiple simulations within one process, and also one that allows to
> implement HasPinNotify in Python.

Why we need a patch for that (sorry, I have not looked in in the moment)?

As I could remember, swig wraps simply all header files and this makes
all methods available. I am wrong?


> 
> A small bit of code that uses this is here: If you are interested,
> see here:
> https://github.com/larsimmisch/arduino--/tree/master/test/simulation
> 
>> Maybe we could split up to variants of simulator and try to create
>> equal interfaces.
>> 
>> But the actual version of simulavr is useless for me, because it
>> only could operate with gdb, but multiple core debugging with
>> tracing is also broken. :-(
> 
> I noticed that the multicore regression tests are broken. I'd like
> that feature.

I simply put the very old systemclock.h/.cpp in the src path and
compile. After removing a few interface errors the simulation links and
works! Also with multi-core simulation, serialrx/tx is working, the gui
runs as expected. So I have no idea why there are so many changes in
that file which only brake the functionality. Maybe I killed some new
features? I don't know. Can someone help to clarify this topic?

At that point I noticed that tracing for non core devices was also
removed. I reentered the feature also, cause the old interface of
systemclock needs that. After that I was also able to trace the
serialrx/tx pin changes and so on.

I also would like to reenable the trace and debug features. I need the
systemclock time (simulation time in ns) in the trace output and also
the memory changes and register contents. I have no idea why this was
removed but it seems not so easy to put that back again.

In addition the aborts from simulavr while using the trace feature must
be fixed. But I recently did not understand why there is a console
manager which rises the errors. Maybe this is a new module which is
needed by windows? I had not understood that. Can anyone help?

Maybe there is only a big misunderstanding in my use of the actual
sources? But if so many features have been removed, there is a lot of
work to bring them back.

If I am the only user of trace output, it makes no sence, but if others
also want the features back, we should spend some time for it.




Regards
 Klaus



reply via email to

[Prev in Thread] Current Thread [Next in Thread]