You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I installed the right core for my ESP8266 (esp8266:esp8266:nodemcuv2) and i can upload perfectly by specifying the port manually: arduino-cli upload -p /dev/ttyUSB0
Altough i cant use the attach command with this board: arduino-cli board attach serial:///dev/ttyUSB0
Output: Attach board error: no supported board found at serial:///dev/ttyUSB0
I also tried it without serial:// and by writing the port manually in the sketch.json file but this results in the error message: Error during Upload: uploading error: no upload port provided
when running the command arduino-cli upload.
This is the expected behavior. The only way the board can be identified automatically is if it presents a unique VID/PID pair. This is the case with all the modern official Arduino boards, and some 3rd party boards, but the ESP8266 boards use general purpose USB to serial adapter chips (e.g., CH340) that use the VID/PID provided by the chip manufacturer. There is no way to know which board is on the other side of that general purpose chip.
Fortunately, board identification is merely a convenience feature and so this type of board is still perfectly usable with Arduino CLI.
I installed the right core for my ESP8266 (esp8266:esp8266:nodemcuv2) and i can upload perfectly by specifying the port manually:
arduino-cli upload -p /dev/ttyUSB0
Altough i cant use the attach command with this board:
arduino-cli board attach serial:///dev/ttyUSB0
Output:
Attach board error: no supported board found at serial:///dev/ttyUSB0
I also tried it without
serial://
and by writing the port manually in the sketch.json file but this results in the error message:Error during Upload: uploading error: no upload port provided
when running the command
arduino-cli upload
.I can specify the board fine via attach.
Environment
The text was updated successfully, but these errors were encountered: