Hello,
Yes, it is possible to potentially cause damage the MCU devices in a number of ways. The following possibilities come to mind -
- Incorrect connections between the two MCUs.
- The two MCUs have different Vdd supply voltages.
- The two MCUs operate using different power sources, and one of the sources is turned off.
- Both MCUs are simultaneously configured for SPI master operation.
- The interconnections between the two MCUs have been subjected to severe static discharge, or other over-voltage.
Items 1, 2, 3 and 4 can result in over-current stress. When experimenting, it is probably a good idea to fit series resistors (say 1k) in each of the interconnections, so as to limit any excess current. SPI communications is not intended to cater for wide physical separation between master and slave(s). They should be in very close proximity, preferably on the same circuit board. This is likely to minimize the possibility of static discharge problems.
Have you been able to ascertain whether both MCUs are damaged? When you send a byte from the master SPI (with slave disconnected), can you observe the presence of either the clock output signal, or the MOSI data signal? You will need to monitor these using an oscilloscope, preferably with single sweep capture. The monitoring process will be much easier if you significantly slow the SPI clock rate of the master.
Finally, did you successfully achieve SPI communications prior to the damage occurring?
Regards,
Mac
Message Edited by bigmac on
2007-12-13 06:26 AM