- Thu Oct 01, 2015 9:51 am
#30264
The black one (v1.0), i'm using windows 10.
Moderator: igrr
- Thu Oct 01, 2015 11:38 pm
#30325
I'm using Windows 10. I was having problems with a NodeMCU 0.9 DevKit from my laptop, but not desktop computer. I just tried again and had the same problem. I also had a 1.0 DevKit, but I hadn't installed the signed drivers. After installing the signed drivers it worked fine. And the funny thing is that now I have no problems at all programming the 0.9 board. Odd.
I've been seeing some strange behavior with the 0.9 board, which use the CH340G USB to UART adapter. For some reason it always shows up as COM3, even if I already have another device attached to COM3. I've also read there are issue with the CH340G on Macs. So I'm beginning to loose interest in the 0.9 board because of the CH340G chip. And I'm guessing this is why they switched to using the CP2102 USB to UART chip in the 1.0 board.
I've been seeing some strange behavior with the 0.9 board, which use the CH340G USB to UART adapter. For some reason it always shows up as COM3, even if I already have another device attached to COM3. I've also read there are issue with the CH340G on Macs. So I'm beginning to loose interest in the 0.9 board because of the CH340G chip. And I'm guessing this is why they switched to using the CP2102 USB to UART chip in the 1.0 board.
