FEZ Raptor and motorDriverL298 - Motor1 runs while waiting for the target to be ready

Only happens to motor1 and not motor2 on a empty Gadgeteer project.

Debug Output

Waiting for device to initialize… ---- Motor1 starts running

The debugging target runtime is loading the application assemblies and starting execution.
Ready. ----- Motor1 stops running

@ andre.m -

Release SDK 2016 R1

Loader (TinyBooter) version information: on this computer. on this device.

The Loader (TinyBooter) is up to date. <<<

Firmware (TinyCLR) version information: on this computer. on this device.

The Firmware (TinyCLR) is up to date. <<<
Please wait for the device to reboot… Done.

I have seen this as well. I believe it’s due to the PWM pin for motor1 going HIGH during a reset/init. See this thread: [url]https://www.ghielectronics.com/community/forum/topic?id=17015[/url]
I could not get the resistor suggestion to work. I did not try using a capacitor, but I don’t see how that would work unless you only used low duty cycles. I don’t think there is an Enable pin broken out in the MotorDriverL298 gadgeteer board which is probably what it needs. Unless GHI can change the behavior of that pin on the G400?

As far as I know, this is known behavior. I just use a relay, and manually enable power to the controller boards once I’m powered up and ready.

(for my raptor-based robotics)