simulavr-devel
[Top][All Lists]
Advanced

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

Re: [Simulavr-devel] simulavr is very unreliable executing a bootloader


From: Albrecht Frenzel
Subject: Re: [Simulavr-devel] simulavr is very unreliable executing a bootloader
Date: Fri, 5 Feb 2016 10:57:43 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1

As the AVR (undocumentedly) treats opcode ffff as a NOP, I think
the simulator could even just continue.

That's a good idea, but why not make it configurable: in normal mode it is NOP, but on demand ffff can act as BREAK?

Albrecht


On 05.02.2016 08:02, Joerg Wunsch wrote:
As Albrecht Frenzel wrote:

The strange thing: sometimes pc gets loaded with the correct pc
0x7e00 and it is possible to step through the code using the same
.elf-file.
You can always set the current PC address in GDB before proceeding:

set $pc = 0x7e00

Regarding Illegal opcode 'ff ff': wouldn't it be better to simply
stop simulavr instead of terminating? That would give a chance to
investigate.
As the AVR (undocumentedly) treats opcode ffff as a NOP, I think
the simulator could even just continue.  There are possible
scenarios where this feature could be used deliberately, e. g.
by including a patch area in the code that is simply run through
as long as it is ffff but which can be written later on to
include additional features.




reply via email to

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