If you are using only one virtual watchdog, you could
add code that traces you application. When you enter a
procedure save a unique token indicating where the
code is. And when a timeout occurs, you can detect
that on reset and see where the code is when it
timeout.

Steve

I know IDA very well (I use it in my 80x86 projects) and it's great, but I
don't want to write a new Rabbit module... :-(

Thank you forn answering

Massimo

Yes I'm using virtual watchdogs... and I cannot find where (and why) the
watchdog timeout expires.

Thanks for answering
Massimo

You can turn on the generate assembly list file to show your whole
program disassembled. Are you using virtual watchdogs in your program?

Hello Massimo,

The BEST disassembler I ever seen is a IDA Pro by Ilfak Guilfanov. It
is distributed by DataRescue. I'm not sure that it have
disassembler/CPU emulation module for Rabbit, but there was
information that SDK is available for creation of new modules. Also,
there was offers to develop processor modules by special order.

You can also generate listing file during compile, but it is also
nearly useless. I keep these listings for every released version of
firmware, and once even was able top locate a bug by analyzing system
logs from unit in the field and such listing, but it was VERY time
consuming.

BR,
Yuri.

I'm missing something or in DC there is'nt a (good) disassembler?
The only way I found to disassemble code is by using the disassemble window,
that shows only few bytes without "navigation" features (useless).
There is another way?

I'm trying to solve a "virtual watchdog timeout" that pops up randomly (but
network related) in my code. There is another way (other than disassembled
code) to find where the problem is?

Regards
Massimo