I am having the chip power a motor and send PWM signals. When it switches from from forward to reverse direction several times, something weird happens where the motor stops performing as necessary and instead, the nSLEEP pin starts to toggle on and off for a few times. This is with the breakout board from Pololu (www.pololu.com/.../4038). Essentially, I need this motor to go forward and backwards very rapidly, but it can't trigger the SLEEP pin. I'm also unaware if the breakout board has the TOFF pin connected to the SLEEP pin, so maybe the TOFF pin is the issue that's driving the SLEEP pin to low and thus pausing the motor. If I get readings from the oscilloscope, the fault pin is pulled up to 3.3 (with an external pullup 10kOhm resistor). The SLEEP (and maybe TOFF) pins are alternating high to low at approximately 0.6 seconds. The motor will spin while the SLEEP is high (at whatever last PWM signal it was given), but it won't stop doing this until I do a power reset. All other pins seem to be worked as planned. If I force the SLEEP pin to high (just plug it into 3V3 instead of a GPIO pin), the high-low switching of the GPIO doesn't start/stop the motor, but then the motor is just spinning at it's previous speed and won't change no matter what the controller is giving it. For reference, I'm making a gimbal. There's an IMU that communicates with I2C to a Nucleo L476RG. A PD controller takes in the error (how far away the system is from equilibrium) from the IMU and converts it into the PWM signal to send to the motor to correct this. When the system is close to equilibrium (such as alternating between +1 degrees and -1 degrees), the motor starts doing the weird stuff. The motor is going forward/backwards fast, but there's not a huge current draw that I have measured (under about 60mA, seems completely reasonable).