Help suddenly cant upload grbl to my arduino boards

Development Tools Uploading
1

get this error message when i try to upload grbl to my mega and my uno, any help appreciated thanks. it worked before on my uno.. but just went moody it seems.

Arduino: 1.8.13 (Windows 7), Board: "Arduino Mega or Mega 2560, ATmega2560 (Mega 2560)"

Sketch uses 30166 bytes (11%) of program storage space. Maximum is 253952 bytes.

Global variables use 1633 bytes (19%) of dynamic memory, leaving 6559 bytes for local variables. Maximum is 8192 bytes.

avrdude: ser_open(): can't open device "\.\COM16": The system cannot find the file specified.

avrdude: ser_drain(): read error: The handle is invalid.

avrdude: ser_send(): write error: sorry no info avail

avrdude: stk500_send(): failed to send command to serial port

avrdude: ser_recv(): read error: The handle is invalid.

avrdude: stk500v2_ReceiveMessage(): timeout

avrdude: ser_send(): write error: sorry no info avail

avrdude: stk500_send(): failed to send command to serial port

avrdude: ser_recv(): read error: The handle is invalid.

the selected serial port avrdude: stk500_send(): failed to send command to serial port

does not exist or your board is not connected

avrdude: stk500v2_ReceiveMessage(): timeout

avrdude: ser_send(): write error: sorry no info avail

avrdude: stk500_send(): failed to send command to serial port

avrdude: ser_recv(): read error: The handle is invalid.

avrdude: stk500v2_ReceiveMessage(): timeout

avrdude: ser_send(): write error: sorry no info avail

avrdude: stk500_send(): failed to send command to serial port

avrdude: ser_recv(): read error: The handle is invalid.

avrdude: stk500v2_ReceiveMessage(): timeout

avrdude: ser_send(): write error: sorry no info avail

avrdude: stk500_send(): failed to send command to serial port

avrdude: ser_recv(): read error: The handle is invalid.

avrdude: stk500v2_ReceiveMessage(): timeout

avrdude: ser_send(): write error: sorry no info avail

avrdude: stk500_send(): failed to send command to serial port

avrdude: ser_recv(): read error: The handle is invalid.

avrdude: stk500v2_ReceiveMessage(): timeout

avrdude: stk500v2_getsync(): timeout communicating with programmer

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

2

Ensure you have NOTHING connected to the Arduinos and try again.
BTW regular GRBL will not play nice on a MEGA without a lot of work.
There are a couple of versions out there just for the MEGA but you will have to dig to find them.

Could you take a few moments to Learn and Use The Forum

[quote]Hello.

Welcome to the Arduino Forum. This guide explains how to get the best out of this forum. Please read and follow the instructions below. Being new here you might think this is having rules for the sake of rules, but that is not the case. If you don’t follow the guidelines all that happens is there is a long exchange of posts while we try to get you to tell us what we need in order to help you, which is frustrating for you and frustrating for us.

[/quote]

It will help you get the best out of the forum in the future.

  • Your OS and version can be valuable information, please include it along with extra security you are using.

  • Always list the version of the IDE you are using and the board version if applicable.

  • Use quote or add error messages as an attachment NOT a picture.

  • How to insert an image into your post. ( Thanks @sterretje )

  • Add your sketch where applicable but please use CODE TAGS ( </> )

  • Add a SCHEMATIC were needed even if it is hand drawn

  • Add working links to any specific hardware as needed (NOT links to similar items)

  • Remember that the people trying to help cannot see your problem so give as much information as you can

COMMON ISSUES

  • Ensure you have FULLY inserted the USB cables.

  • Check you have a COMMON GROUND where required. ( Thanks @Perry)

  • Where possible use USB 2.0 ports or a USB 2.0 POWERED HUB to rule out USB 3.0 issues.

  • Try other computers where possible.

  • Try other USB leads where possible.

  • You may not have the correct driver installed. CH340/341 or CP2102 or FT232 VCP Drivers - FTDI

  • There may be a problem with the board check or remove your wiring first.

  • Remove any items connected to pins 0 and 1.

COMPUTER RELATED

  • Close any other serial programs before opening the IDE.

  • Ensure you turn off any additional security / antivirus just to test.

  • There may be a problem with the PC try RESTARTING it.

  • You may be selecting the wrong COM port.

  • Avoid cloud/network based installations where possible OR ensure your Network/Cloud software is RUNNING.

  • Clear your browsers CACHE.

  • Close the IDE before using any other serial programs.

  • Preferably install IDE’s as ADMINISTRATOR or your OS equivalent

ARDUINO SPECIFIC BOARDS

  • CH340/341 based clones do not report useful information to the “get board info” button.

  • NANO (Old Types) some require you to use the OLD BOOTLOADER option.

  • NANO (ALL Types) See the specific sections lower in the forum.

  • NANO (NEW Types) Install your board CORE’s.

  • Unless using EXTERNAL PROGRAMMERS please leave the IDE selection at default “AVRISP mkII”.

  • Boards using a MICRO usb connector need a cable that is both DATA and CHARGE. Many are CHARGE ONLY.

CREATE editor install locations.

  • On macOs ~/Applications/ArduinoCreateAgent-1.1/ArduinoCreateAgent.app/Contents/MacOS/config.ini

  • On Linux ~/ArduinoCreateAgent-1.1/config.ini

  • On Windows C:\Users[your user]\AppData\Roaming\ArduinoCreateAgent-1.1

Performing the above actions may help resolve your problem without further help.

Language problem ?

Try a language closer to your native language:

Thanks to all those who helped and added to this list.

3

What does Windows device manager think about your board? Is it still COM16? Any additional yellow triangles when you connect the board?

4

yes still com 16... i think its always been com 16, tried different usb ports, tried uninstalling, tried installing ch340 driver which gave me BSOD... wont upload to uno from arduino, and grbl laser wont connect to it. completely puzzled... i guess im not even going to attempt to do it with my mega because of the hangups associated,,

5

devices and printers says its an ft232r usb uart. i dont recall if this name has ever changed

6

If it's an FT232R, installing CH340 drivers will not help :wink:

I would try a terminal program (e.g. RealTerm) and connect to the port. If that fails as well, it's clearly a Windows issue. If it succeeds, it's an IDE issue.

7

how do i use this realterm????

8

ok so in realterm i typed in some characters and i could see the tx light on my uno blink with each keystroke.... whats that tell you?

9

That should be the RX light?\

Based on avrdude: ser_open(): can't open device "\.\COM16":, it tells me that it is not a Windows problem but an IDE (in the broader sense) problem. I have no idea how to solve it.

10

  1. A quick test would be to download the FTDI drivers.

  2. Disconnect the arduino from the computer.

  3. Remove the 232 device in windows manager but say YES to also remover the driver.

  4. Re-boot the computer.

  5. Turn OFF any additional security for the next part and ensure it really is OFF !

  6. Install the new driver with "complete" ADMINISTRATOR privileges.

  7. Open Device Manager and expand the com and lpt ports.

  8. Connect the arduino board only (no shields etc)

  9. Check that there has been a change and the board is added to device manager either as a COM port or a 232 device.

  10. Open the IDE.

  11. Make sure you have AVRISP MKII selected as the programmer.

  12. Select BLINK from the examples and change the timing of the sketch.

  13. Try to upload.

  14. Take note of any change in error messages.

If you are still failing there is a strong chance you may have a broken Arduino

11

reinstalled drivers and everything from your suggestions when i click upload some lights blink on the board then it takes about 3 min of nothing before it says it failed:

Sketch uses 924 bytes (2%) of program storage space. Maximum is 32256 bytes.
Global variables use 9 bytes (0%) of dynamic memory, leaving 2039 bytes for local variables. Maximum is 2048 bytes.
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x43
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x43

12

Well that is certainly movement in a good direction.

I will leave you now in the hands of those who have more understanding of these mystical codes.

13

Although probably not your cause I will also ask.

Are you by any chance using USB 3.n ?
Also will the board upload on a different computer with a different cable ?
Could you also add a decent picture of YOUR actual boards ?

14

20210522_121003
20210522_1210034160×3120 2.01 MB

15

how do i determine if i am using usb 3.x?? i think my computer may be a little old for that

16

I have a few new unos on the way i think it is probably a fried uno... it worked already i was running my x and y axis from the board a few days ago. will let you know whati find out when i get some new unos

17

looks like it was a broken uno. thank you to everyone who reached out

18

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.