Hi Petr, On 04/01/12 22:57, Petr Hluzín wrote: > What do you use the instruction for? As I already wrote, I need more than the limited hardware assisted break-/watchpoints while maintaining full MCU speed. Another positiv point for me is, in the seldom cases where my code hints the break instruction (mostly false assertions), I can easily start interactive debugging, which is more comfortable than analyzing a static coredump.
> How does the break instruction depend on fuses? If On-Chip-Debugging (OCD) is not programmed, the BREAK instruction is nothing else than a NOP ;) > Devices with small instruction set do not implement the BREAK > instruction, however this looks like a limitation of silicon, not a > feature. It would be useful if libraries could use this instruction in > assertions on any device (in simulator). > Is it useful to simulate the limitation? When/why? In my opinion, I would not implement the limitation but rather notify the user that break is not supported on every device. I again want to mention, that I use the same binaries for simulation and in the real system. Bye, Stan. _______________________________________________ Simulavr-devel mailing list Simulavr-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/simulavr-devel
