<p>Your motherboard is not an MKS GEN L v1.0, it's a <a href="https://github.com/makerbase-mks/Datasheet/blob/master/English%20datasheet/MKS%20SGen%20Datasheet.pdf" rel="nofollow noreferrer">MKS SGEN L</a> - unfortunately, a very very naming scheme.</p>
<p>Your board is actually a <strong>32-bit board</strong>, and must therefore be flashed with Marlin 2.0, built for the 32-bit board.
The firmware is then updated by placing it on the SD card and restarting the board, as explained in the <a href="https://marlinfw.org/docs/basics/install_platformio_vscode.html" rel="nofollow noreferrer">documentation for Marlin here</a></p>

CC BY-SA 4.0
2020-11-11T06:30:21.017Z
2020-11-11T14:03:52.700Z
2020-11-11T14:03:52.700Z
towe
<p>Your new board may have a counterfeit FT232R USB-to-serial interface chip, and the Windows update channel has installed hobbled FTDI drivers that won't work with counterfeit chips. The use of counterfeit FT232R chips is very common with budget 3D printer controllers, and FTDI are trying to discourage their use. Because of this, a lot of manufacturers have switched to using the CH340 chip, which does not suffer from this problem, and it looks like your old board used a CH340 chip. Try deleting the device and its drivers, and then installing the Windows setup executable from the following website:</p>
<p><a href="https://www.ftdichip.com/Drivers/VCP.htm" rel="nofollow noreferrer">https://www.ftdichip.com/Drivers/VCP.htm</a></p>
<p>The 2.12.28 drivers will work with counterfeit chips.</p>

CC BY-SA 4.0
2020-11-11T02:55:26.233Z
Thanks Mick! I will try that tomorrow. Should I install the VCP, D2xx, or the D3xx?
mcdon482
CC BY-SA 4.0
2020-11-11T02:58:39.940Z
Try the D3xx drivers. The device needs to be presented as a virtual COM port.
Mick
CC BY-SA 4.0
2020-11-11T02:48:24.553Z
2020-11-11T03:10:23.073Z
2020-11-11T03:10:23.073Z
Mick
<p>I bricked my Tevo Tarantula's controller board, and I've decided to just replace it rather than unbrick it because they are relatively cheap. I recently bought a new MKS GEN L v1.0 board, but I've been unable to flash new firmware onto it. Every time I go to upload the firmware, I get an error just as it begins to upload, saying:</p>
<pre><code>&quot;failed to send command to serial port does not exist or is not connected&quot;

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.
</code></pre>
<p>avrdude: stk500v2_ReceiveMessage(): timeout</p>
<pre><code>avrdude: stk500v2_getsync(): timeout communicating with programmer
</code></pre>
<p>Any ideas of what the issue could be? I've tried both the USB ports on my computer and using a USB 2.0 hub (I believe my computer ports are both USB 3.0). I've also made sure that I had the correct port selected in Marlin (1.1.8.13).</p>
<p>I also think that its worth mentioning that my bricked board and new board seem to appear differently in the device manager</p>
<p>Bricked:</p>
<p><a href="https://i.sstatic.net/Ex7ZK.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Ex7ZK.png" alt="enter image description here" /></a></p>
<p>While my new board appears as this:</p>
<p><a href="https://i.sstatic.net/TWYoP.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/TWYoP.png" alt="enter image description here" /></a></p>
<p>The new board also seems to &quot;cut-out&quot; when I first connect it to my computer as well. In the device manager, my computer will indicate that an unknown device is connected, then it will quickly disconnect and disappear, only to reconnect and reappear as pictured above.</p>
<p>Do you guys think there is a hardware issue with the motherboard? Thanks for your help, this is giving me quite the headache!</p>

CC BY-SA 4.0
2020-11-11T00:40:32.853Z
what is the new Motherboard's type?
Trish
CC BY-SA 4.0
2020-11-11T01:14:25.853Z
Its a Kookye mks gen l v 1.0 from Amazon. It has an lpc1768
mcdon482
CC BY-SA 4.0
2020-11-11T01:14:39.180Z
https://www.amazon.com/gp/product/B07Y1PPWVC/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1
mcdon482
CC BY-SA 4.0
2020-11-11T01:43:50.047Z
What drivers is Windows using for the new USB connection?
Mick
CC BY-SA 4.0
2020-11-11T01:56:45.560Z
Its using a microsoft driver 10.0.19041.1
mcdon482
<diy-3d-printer><firmware><usb>
Unable to upload firmware to a new motherboard
mcdon482
# Unable to upload firmware to a new motherboard

(Asked by: username_0 on 2020-11-10)

I bricked my Tevo Tarantula's controller board, and I've decided to just replace it rather than unbrick it because they are relatively cheap. I recently bought a new MKS GEN L v1.0 board, but I've been unable to flash new firmware onto it. Every time I go to upload the firmware, I get an error just as it begins to upload, saying:

```
"failed to send command to serial port does not exist or 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: stk500v2_getsync(): timeout communicating with programmer

```

Any ideas of what the issue could be? I've tried both the USB ports on my computer and using a USB 2.0 hub (I believe my computer ports are both USB 3.0). I've also made sure that I had the correct port selected in Marlin (1.1.8.13).

I also think that its worth mentioning that my bricked board and new board seem to appear differently in the device manager

Bricked:

[![enter image description here](https://i.sstatic.net/Ex7ZK.png)](https://i.sstatic.net/Ex7ZK.png)

While my new board appears as this:

[![enter image description here](https://i.sstatic.net/TWYoP.png)](https://i.sstatic.net/TWYoP.png)

The new board also seems to "cut-out" when I first connect it to my computer as well. In the device manager, my computer will indicate that an unknown device is connected, then it will quickly disconnect and disappear, only to reconnect and reappear as pictured above.

Do you guys think there is a hardware issue with the motherboard? Thanks for your help, this is giving me quite the headache!

**Tags:** diy-3d-printer, firmware, usb

> **Comments:**
> **username_1**: what is the new Motherboard's type?  
> **username_0**: Its a Kookye mks gen l v 1.0 from Amazon. It has an lpc1768  
> **username_0**: https://www.amazon.com/gp/product/B07Y1PPWVC/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1  
> **username_2**: What drivers is Windows using for the new USB connection?  
> **username_0**: Its using a microsoft driver 10.0.19041.1  

---

## 2 answers

### Answer by username_3 on 2020-11-11. Score: 2

Your motherboard is not an MKS GEN L v1.0, it's a [MKS SGEN L](https://github.com/makerbase-mks/Datasheet/blob/master/English%20datasheet/MKS%20SGen%20Datasheet.pdf) - unfortunately, a very very naming scheme.

Your board is actually a **32-bit board**, and must therefore be flashed with Marlin 2.0, built for the 32-bit board.
The firmware is then updated by placing it on the SD card and restarting the board, as explained in the [documentation for Marlin here](https://marlinfw.org/docs/basics/install_platformio_vscode.html)


---

### Answer by username_2 on 2020-11-11. Score: 1

Your new board may have a counterfeit FT232R USB-to-serial interface chip, and the Windows update channel has installed hobbled FTDI drivers that won't work with counterfeit chips. The use of counterfeit FT232R chips is very common with budget 3D printer controllers, and FTDI are trying to discourage their use. Because of this, a lot of manufacturers have switched to using the CH340 chip, which does not suffer from this problem, and it looks like your old board used a CH340 chip. Try deleting the device and its drivers, and then installing the Windows setup executable from the following website:

<https://www.ftdichip.com/Drivers/VCP.htm>

The 2.12.28 drivers will work with counterfeit chips.

> **Comments:**
> **username_0**: Thanks username_2! I will try that tomorrow. Should I install the VCP, D2xx, or the D3xx?  
> **username_2**: Try the D3xx drivers. The device needs to be presented as a virtual COM port.  

---

