I usually troubleshoot my boards by checking the following:
Current consumption - the board itself should take more than 20mA, and less than 100mA by itself. Typically I expect about 60mA. If it is outside these limits, then something is shorted or open on the board.
The two clock circuits (32kHz, ??MHz) should be running when powered. Look at pins 49 and 113 on the rabbit with a scope or frequency counter to make sure they are operating and close to frequency.
Put a scope probe on pin 8 of the programming header (STATUS). Tie pins 9 & 10 high (SMODE0, SMODE1). Tie pin 5 low (/RESET). While watching the scope (STATUS signal) let pin 5 go high. STATUS should toggle.
If #3 works, then the Rabbit processor itself is functioning. In that case, where in the programming cycle does Dynamic C indicate that it’s bad?
The RESOUT Pin is just left OPEN. Is it to be grounded?
The RESET Pin is connected to MAX811R.
Do I have to take care of any other pins?
I have followed the Designer's handbook for designing my module.
Please Reply
But it should not be toggling. Is the /RESET line also toggling? Is the input to the MAX811R also toggling? Try to find out what’s causing the toggling.
I dint connected the target to the host. The SMODE0 and SMODE1 pins are also high.
The RESOUT(50) pin is not toggling continously. But a pulse of 10millisec duration is coming at times.
After connecting to the host, i am able to run diagnostics through SERIELIO.exe and found serial port A and RAM are OK (i am getting intended response).
The RESOUT pin status is different with the working CORE module-RCM3110.
Still I am unable to communicate with RABBIT through Dynamic C. Its showing error message--"No Rabbit Processor found".
I am unable to come to any conclusion whether processor is bad or my design.