Executing command: exec: not started

Hi

I am getting an error "Executing command: exec: not started" when I try to upload the Example Blink sketch (or any other sketch) to a new M0 Pro using create editor. The blink sketch works fine if uploaded using the Offline IDE 1.8.5.

I have a Windows 10 X64 PC, browser Chrome X64 version 65.0.3325.181

Here are the last few lines from the console output:

Sketch uses 10216 bytes (3%) of program storage space. Maximum is 262144 bytes.

Flashing with command:{runtime.tools.openocd.path}/bin/openocd.exe -s {runtime.tools.openocd.path}/share/openocd/scripts/ -f C:/Users/croc/AppData/Local/Temp/arduino-create-agent232586723/arduino_zero.cfg -c telnet_port disabled; program C:/Users/croc/AppData/Local/Temp/arduino-create-agent232586723/Blink.bin verify reset 0x00004000; shutdown

Here is "installed.json":

{"apilevel":"v1","avrdude":"C:\\Users\\croc/.arduino-create/arduino/avrdude/6.3.0-arduino9","avrdude-6.3.0-arduino9":"C:\\Users\\croc/.arduino-create/arduino/avrdude/6.3.0-arduino9","windows-drivers":"C:\\Users\\croc/.arduino-create/arduino/windows-drivers/1.8.0","windows-drivers-1.8.0":"C:\\Users\\croc/.arduino-create/arduino/windows-drivers/1.8.0"}

Regards

Peter

What happens if you try in an INCOGNITO window ?

What security do you have installed as some AV etc can also interrupt the uploads ?

There are some posts at the top of this section that may be worth reading for you to supply additional information.

That is only "partial" information you supplied but thank you for using code tags, it is nice to see !

Ballscrewbob, running in incognito window has the same result. AV is Windows Defender. The create editor uploads fine to an Arduino Uno - it is just on the M0 Pro that it fails.

Thanks for the additional Info.

Windows defender should not cause any issues so I doubt it is that.

Have you tried other USB cables that are known to be good for upload ?

Also dont use USB 3.0 ports or cables as USB 3.0 is known to have some issues.

I have swapped USB cables. Unfortunately, my PC USB ports all seem to be 3.0 :confused:

I have tried with my Chromebook - it works with an Uno, but the M0 Pro is listed as not available for upload.

I am also having an issue with Atmel Studio (latest, with latest board definitions) - it lists the board as Unknown, with detail as follows:

Serial number   FFFFFFFFFFFFFFFFFFFF
Board name  Atmel Embedded Debugger
Manufacturer    Atmel
Target name 
Interfaces  ISP PDI DW AW JTAG SWD SPI TWI UART USART GPIO CDC ERASE PIN

This section is for the CREATE ONLINE editor not Atmel studio.

Getting round the USB 3.0 issue is often best with a decent USB 2.0 POWERED HUB as it tends to act as a throttle / current limiter.

I added the Atmel Studio details as I thought the information may add some information to the CREATE ONLINE problem.

I will try to get a USB 2.0 powered hub, but I suspect that the create web tool does not support the M0 Pro, as I have no problems with the same cables and PC using an Uno. In case the M0 Pro was drawing too much current I provided external 12V via the power jack, and the create editor gives the same problem.

According to the board list it is fully supported.

I would find it hard to believe it wasnt as it is an official board and they have been pretty rigorous about only adding official boards or boards where they can oversee the board definitions fully.

My bet is still on USB 3.0 or another external cause.

I bought a powered USB 2.0 hub, and connected via that. The editor recognised the board, but I get the same error when I upload the "blink" sketch.

Sorry for being late back to this.

Been quite busy with my own projects...

HOWEVER...

I can see this too now under win 7 x64. Oddly it does not seem to affect the MKR series boards ?!?

So far I can reproduce it with a Mega, Uno, Yun, Nano. Left a note and a full error log for the dev team. Will also raise it to GITHUB too.

pfretief: Flashing with command:{runtime.tools.openocd.path}/bin/openocd.exe -s {runtime.tools.openocd.path}/share/openocd/scripts/ -f C:/Users/croc/AppData/Local/Temp/arduino-create-agent232586723/arduino_zero.cfg -c telnet_port disabled; program C:/Users/croc/AppData/Local/Temp/arduino-create-agent232586723/Blink.bin verify reset 0x00004000; shutdown

I suspect the {runtime.tools.openocd.path} is the clue to the problem. If you have the openocd tool installed that property should be replaced by the actual path to where the tool is installed on your system.

From your installed.json:

pfretief: {"apilevel":"v1","avrdude":"C:\\Users\\croc/.arduino-create/arduino/avrdude/6.3.0-arduino9","avrdude-6.3.0-arduino9":"C:\\Users\\croc/.arduino-create/arduino/avrdude/6.3.0-arduino9","windows-drivers":"C:\\Users\\croc/.arduino-create/arduino/windows-drivers/1.8.0","windows-drivers-1.8.0":"C:\\Users\\croc/.arduino-create/arduino/windows-drivers/1.8.0"}

You can see the path to the avrdude tool (used for uploading to the Arduino AVR Boards) is defined but there is nothing for the openocd tool.

The output BallscrewBob posted in their GitHub issue report: https://github.com/arduino/arduino-create-agent/issues/224 looks different because it does have the path to the avrdude tool:

Flashing with command:d:/Users/Bob/.arduino-create/arduino/avrdude/6.3.0-arduino9/bin/avrdude.exe -Cd:/Users/Bob/.arduino-create/arduino/avrdude/6.3.0-arduino9/etc/avrdude.conf -patmega32u4 -cavr109 -PCOM19 -b57600 -D -Uflash:w:d:/Users/Bob/AppData/Local/Temp/arduino-create-agent530033685/exploring_slowLinks.hex:i

@BallscrewBob, you didn't post the exact error message you encountered. Is it the same as what pfretief reported:

pfretief: I am getting an error "Executing command: exec: not started"

I haven't had luck the last cpuple times I tried to install the plugin so I've given up on trying to upload with Arduino Web Editor. I wonder if reinstalling the plugin would maybe solve the issue. I guess the plugin comes with both the avrdude and openocd tools?

Hi Pert forgot to tag this post back to GITHUB

It seems that a FULL un-install then re-install helped a little but the issue is still there. Now seems to only affect MEGA boards from this side.

Certainly getting closer to a fix.

@Pert

What issue did you hit trying to install ?