<p>In an attempt to upgrade my Ender 3 to <code>TMC2208</code>, I bought an MKS GENL 1.0 board from Banggood, but it doesn't get recognized from the Windows Device Manager at all: no COM port, no "Unknown Device", no beep when connected/disconnected via USB.</p>

<p>I have some Arduino and electronics experience and having an USBasp I've decided to give a go to reflashing the bootloader, with no joy. I tried flashing both the <code>stk500boot_v2_mega2560.hex</code> and the <code>ATmegaBOOT.hex</code> using <code>avrdude</code> like the following (copy pasted from Arduino IDE):</p>

<pre><code>bin\avrdude -Cetc\avrdude.conf -v -patmega2560 -cusbasp -Pusb -Uflash:w:..\..\arduino\avr\bootloaders\atmega8\ATmegaBOOT.hex:i -Ulock:w:0x0F:m
</code></pre>

<p>Whatever I do the board seems dead: tried alternative cables (also double checked using a plain inkjet printer to confirm it wasn't that) and also alternative PCs (all running Windows)... I believe it might be possible for me to upload Marlin via ICSP, but without USB I'll have not much use for it anyway...</p>

<p>It might be worth noting the board uses a <code>CH340</code> USB chip (drivers already installed), which seems to be getting only <code>2.6 V</code> at VCC...</p>

<p>When connected via USB the red <em>power on</em> LED <code>D7</code> turns on, but nothing else happens...</p>

<p>I'm about to throw the board into the bin and buy another one from Amazon, unless somebody has any suggestion that might revive it...</p>

CC BY-SA 4.0
2019-05-07T20:19:20.417Z
You *might* need a CH340 driver to be manually installed, although Windows normally installs that for you (whereas for OSX it is much more of a nightmare). See [this](https://www.instructables.com/id/Arduino-Nano-USB-Not-Recognizing-Fix/) for example, although, I presume (from your description) that Windows isn't even showing you an *unknown device* in **Device Manager**?. What is the error (if any) that you get when using avrdude? I've had issues like this before, and I've always been able to get them going again, usually with judicious use of the reset button and timing it just right.
Greenonline
CC BY-SA 4.0
2019-05-07T21:59:48.473Z
CH340 driver is installed, but as windows in not recognizing ANY device I have no COM port to specify to avrdude. The usbasp bootloader programming via ICSP seems to complete nicely (both write and verify steps completed).
I would generally agree with you with regards to resetting the board, but in this case it seems it's the CH340 being gone...
Roberto Lo Giacco
CC BY-SA 4.0
2019-05-07T22:09:19.347Z
Hm, it doesn't sound good. This is a bit of a long shot, but the *only* thing that I can think of (at the moment) is to carefully monitor **Device Manager** *whilst* plugging in the board, and/or resetting the board. I had a mis-behaving Arduino-clone once that had a icon flash up only ***momentarily*** in the device manager (upon reset or plugging in) and if you weren't actually watching the device manager at the time you would never have known that it showed up briefly, and then disappeared. See [here](https://gr33nonline.wordpress.com/2015/08/05/the-case-of-the-broken-micro/) & its sequel.
Greenonline
CC BY-SA 4.0
2019-05-07T22:27:25.027Z
Presumably you've seen this: [Mks Gen L and nothing!](https://reprap.org/forum/read.php?13,840289) (where the solution appears to be buy a new board!) and more promisingly [Marlin compile and upload fails–MKS Gen L 1.0 (SOLVED)](https://www.v1engineering.com/forum/topic/marlin-compile-and-upload-fails-mks-gen-l-1-0/) - among the many hints and tips, possibly there is a need for a CH341SER driver (rather than a CH340[G])?
Greenonline
CC BY-SA 4.0
2019-05-08T21:27:03.950Z
@Greenonline the alt driver didn't help either, as I was expecting due the fact no device shows up to the device manager, not even momentarily. I also went a little to a lower level, trying to use zadiq to scan for any device having any USB signature, but the only USB devices recognized are those I already know (mouse, keyboard, USB hub, etc...)
I would definitely rule out the driver problem at this stage... But thanks a lot for providing all that info and links
Roberto Lo Giacco
CC BY-SA 4.0
2019-05-08T22:13:40.697Z
OK, fair enough... :-) Like I said it was a long shot. I've just had a CH340G nightmare this evening, but yes, at least my board showed up, as *unknown* in the USB list in Device Manager - whereas yours isn't. Well, I'm out of ideas, I'm afraid. Good luck to you anyway, but yeah, sounds like the board is toast. :-(
Greenonline
CC BY-SA 4.0
2019-05-16T12:22:19.747Z
What do you mean by: "it might be worth noting the board uses a CH340 USB chip (drivers already installed), which seems to be getting only 2.6 V at VCC..." Where are you measuring VCC, and how are you powering the board when you make this measurement?
gwideman
CC BY-SA 4.0
2019-05-16T12:51:55.337Z
Powered from USB and measuring between GND and VCC pins of the integrated circuit
Roberto Lo Giacco
<electronics><arduino-mega-2650><repair><usb><serial-connection>
MKS GEN L looks dead
Roberto Lo Giacco
# MKS GEN L looks dead

(Asked by: username_0 on 2019-05-07)

In an attempt to upgrade my Ender 3 to `TMC2208`, I bought an MKS GENL 1.0 board from Banggood, but it doesn't get recognized from the Windows Device Manager at all: no COM port, no "Unknown Device", no beep when connected/disconnected via USB.

I have some Arduino and electronics experience and having an USBasp I've decided to give a go to reflashing the bootloader, with no joy. I tried flashing both the `stk500boot_v2_mega2560.hex` and the `ATmegaBOOT.hex` using `avrdude` like the following (copy pasted from Arduino IDE):

```
bin\avrdude -Cetc\avrdude.conf -v -patmega2560 -cusbasp -Pusb -Uflash:w:..\..\arduino\avr\bootloaders\atmega8\ATmegaBOOT.hex:i -Ulock:w:0x0F:m

```

Whatever I do the board seems dead: tried alternative cables (also double checked using a plain inkjet printer to confirm it wasn't that) and also alternative PCs (all running Windows)... I believe it might be possible for me to upload Marlin via ICSP, but without USB I'll have not much use for it anyway...

It might be worth noting the board uses a `CH340` USB chip (drivers already installed), which seems to be getting only `2.6 V` at VCC...

When connected via USB the red *power on* LED `D7` turns on, but nothing else happens...

I'm about to throw the board into the bin and buy another one from Amazon, unless somebody has any suggestion that might revive it...

**Tags:** electronics, arduino-mega-2650, repair, usb, serial-connection

> **Comments:**
> **username_1**: You *might* need a CH340 driver to be manually installed, although Windows normally installs that for you (whereas for OSX it is much more of a nightmare). See [this](https://www.instructables.com/id/Arduino-Nano-USB-Not-Recognizing-Fix/) for example, although, I presume (from your description) that Windows isn't even showing you an *unknown device* in **Device Manager**?. What is the error (if any) that you get when using avrdude? I've had issues like this before, and I've always been able to get them going again, usually with judicious use of the reset button and timing it just right.  
> **username_0**: CH340 driver is installed, but as windows in not recognizing ANY device I have no COM port to specify to avrdude. The usbasp bootloader programming via ICSP seems to complete nicely (both write and verify steps completed). I would generally agree with you with regards to resetting the board, but in this case it seems it's the CH340 being gone...  
> **username_1**: Hm, it doesn't sound good. This is a bit of a long shot, but the *only* thing that I can think of (at the moment) is to carefully monitor **Device Manager** *whilst* plugging in the board, and/or resetting the board. I had a mis-behaving Arduino-clone once that had a icon flash up only ***momentarily*** in the device manager (upon reset or plugging in) and if you weren't actually watching the device manager at the time you would never have known that it showed up briefly, and then disappeared. See [here](https://gr33nonline.wordpress.com/2015/08/05/the-case-of-the-broken-micro/) & its sequel.  
> **username_1**: Presumably you've seen this: [Mks Gen L and nothing!](https://reprap.org/forum/read.php?13,840289) (where the solution appears to be buy a new board!) and more promisingly [Marlin compile and upload fails–MKS Gen L 1.0 (SOLVED)](https://www.v1engineering.com/forum/topic/marlin-compile-and-upload-fails-mks-gen-l-1-0/) - among the many hints and tips, possibly there is a need for a CH341SER driver (rather than a CH340[G])?  
> **username_0**: @username_1 the alt driver didn't help either, as I was expecting due the fact no device shows up to the device manager, not even momentarily. I also went a little to a lower level, trying to use zadiq to scan for any device having any USB signature, but the only USB devices recognized are those I already know (mouse, keyboard, USB hub, etc...) I would definitely rule out the driver problem at this stage... But thanks a lot for providing all that info and links  
> **username_1**: OK, fair enough... :-) Like I said it was a long shot. I've just had a CH340G nightmare this evening, but yes, at least my board showed up, as *unknown* in the USB list in Device Manager - whereas yours isn't. Well, I'm out of ideas, I'm afraid. Good luck to you anyway, but yeah, sounds like the board is toast. :-(  
> **username_2**: What do you mean by: "it might be worth noting the board uses a CH340 USB chip (drivers already installed), which seems to be getting only 2.6 V at VCC..." Where are you measuring VCC, and how are you powering the board when you make this measurement?  
> **username_0**: Powered from USB and measuring between GND and VCC pins of the integrated circuit  

---

## 0 answers

