I have breadboarded a 28X2 driving, via PWM, a MCP1407-E/AT (MOSFET driver, 6A) in turn driving an IRL640BPF (n-channel power MOSFET, 200V 17A). The 28X2 is connected directly to the driver (with a 10K pulldown). The driver is connected to the power MOSFET through a 20 Ohm resistor (also with a 10K pulldown). The power MOSFET source goes to the common ground and drain goes to the load (a small 12V lightbulb) in turn connected to separate +12V power. VDD to the driver is same 5V source as to the 28X2, through a 50 Ohm resistor (and a 1uf cap to ground). All this is per a circuit diagram posted to another thread a while ago. I also have a blinking LED on the 28X2 to see if the thing is running.
The problem is that the circuit will not activate on program download or, after a reset which lasts longer than about 2 seconds. There are however two repeatable ways to get it going:
One is to remove VDD from the driver. The circuit then operates normally (LED blinks, the proper (& clean)PWM input arrives at the power MOSFET input (as per oscilloscope reading) and the load light bulb brightness is proportional to the PWM duty factor. If driver VDD is then reconnected, the circuit continues to operate exactly as before (but with slightly higher PWM voltage at the power MOSFET - about 4V).
The other way is to move the driver input from the 28X2 PWM o/p to the LED o/p. The load bulb will then flash in unison with the LED (as expected). If the driver input is then quickly switched back to the PWM o/p, the circuit begins to operate normally.
When the driver input is removed from the PWM o/p, the LED immediately starts blinking. The same happens when the load bulb is disconnected from the power MOSFET. If the PWM o/p or load bulb are reconnected however the LED stops (and there remains no PWM output signal).
I have also found that a reset (during normal circuit operation) of less than about 2 seconds works normally i.e. the circuit stops functioning on reset and resumes on reset off. One odd thing however is that when the circuit is not operating (no LED or PWM o/p, the chip will still accept a program download so it looks like it is not completly halted).
Similar behaviour BTW is noted when the driver is removed entirely from the circuit (28X2 PWM o/p connected directly to the power MOSFET). If the power MOSFET is disconnected, all works normally up to the driver output.
The reset and serial pins I/O are terminated properly.
It appears that the power MOSFET is interferring somehow with the 28X2 but I have no idea how or why. If anyone has any insight I would be much appreciative as I'm out of anything else to try.
The problem is that the circuit will not activate on program download or, after a reset which lasts longer than about 2 seconds. There are however two repeatable ways to get it going:
One is to remove VDD from the driver. The circuit then operates normally (LED blinks, the proper (& clean)PWM input arrives at the power MOSFET input (as per oscilloscope reading) and the load light bulb brightness is proportional to the PWM duty factor. If driver VDD is then reconnected, the circuit continues to operate exactly as before (but with slightly higher PWM voltage at the power MOSFET - about 4V).
The other way is to move the driver input from the 28X2 PWM o/p to the LED o/p. The load bulb will then flash in unison with the LED (as expected). If the driver input is then quickly switched back to the PWM o/p, the circuit begins to operate normally.
When the driver input is removed from the PWM o/p, the LED immediately starts blinking. The same happens when the load bulb is disconnected from the power MOSFET. If the PWM o/p or load bulb are reconnected however the LED stops (and there remains no PWM output signal).
I have also found that a reset (during normal circuit operation) of less than about 2 seconds works normally i.e. the circuit stops functioning on reset and resumes on reset off. One odd thing however is that when the circuit is not operating (no LED or PWM o/p, the chip will still accept a program download so it looks like it is not completly halted).
Similar behaviour BTW is noted when the driver is removed entirely from the circuit (28X2 PWM o/p connected directly to the power MOSFET). If the power MOSFET is disconnected, all works normally up to the driver output.
The reset and serial pins I/O are terminated properly.
It appears that the power MOSFET is interferring somehow with the 28X2 but I have no idea how or why. If anyone has any insight I would be much appreciative as I'm out of anything else to try.