This is a group for folks designing and programming embedded systems using the Rabbit Semiconductor C-programmable microcontroller. Rabbit Semi is a spin-off from Z-World who makes a variety of embedded modules and tools. This group is not affiliated with either Rabbit or Z-World, but is a user forum for sharing ideas, asking questions,
flaunting knowledge, and other typical user group stuff. The Rabbit is a powerful uC, supported by a full-featured C-compiler.
Whether it is a root cause of damaged the RCM module ? - kara_liao - Aug 8 1:19:22 2008
All, I have a project with a Rabbit RCM3720 and I'm having mistook to
caused my hardware to died in RCM3720. I would like to consult all of
you this mistook for the module output pin (PF4) direct to connect with
+5V whether it is a root cause of damaged the RCM module ?
------------------------------------

(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )
Re: Whether it is a root cause of damaged the RCM module ? - eilidhs_daddy - Aug 8 4:07:11 2008
--- In r...@yahoogroups.com, "kara_liao"
wrote:
>
> All, I have a project with a Rabbit RCM3720 and I'm having mistook to
> caused my hardware to died in RCM3720. I would like to consult all of
> you this mistook for the module output pin (PF4) direct to connect with
> +5V whether it is a root cause of damaged the RCM module ?
>
The ZWorld documentation for this board says:
"Unless otherwise specified, the Rabbit I/O buffers are capable of
sourcing and sinking 6.8 mA of current per pin at full AC switching
speed. Full AC switching assumes a 22.1 MHz CPU clock and capacitive
loading on address and data lines of less than 100 pF per pin. The
absolute maximum operating voltage on all I/O is 5.5 V."
So I guess it depends how much current flowed through the pin, and
whether that would just kill that driver section of the chip, or the
whole chip.
-Kenny
------------------------------------

(You need to be a member of rabbit-semi -- send a blank email to rabbit-semi-subscribe@yahoogroups.com )