Driver issue v1 main board to Windows  [SOLVED]

Post Reply
User avatar
Cees
Posts: 1
Joined: Tue Feb 26, 2019 2:09 am

Driver issue v1 main board to Windows  [SOLVED]

Post by Cees »

I had trouble connecting the v1 main board I have, with Putty or indeed any software.
It turns out you need to downgrade the driver, see explanation here: http://wp.brodzinski.net/hardware/fake- ... o-install/ .
Someting to do with the PL2303 chip being fake?
Anyway, you need version 3.3.2.105, downloadable here: http://wp.brodzinski.net/wp-content/upl ... olific.zip .

Perhaps something to add as a known issue.
User avatar
johu
Site Admin
Posts: 5788
Joined: Thu Nov 08, 2018 10:52 pm
Location: Kassel/Germany
Has thanked: 157 times
Been thanked: 1022 times
Contact:

Re: Driver issue v1 main board to Windows

Post by johu »

Oh, good to know, thanks for reporting. Ouch, so fake chips... Good thing the esp8266 chips I include nowadays are Chinese in the first place ;)
Support R/D and forum on Patreon: https://patreon.com/openinverter - Subscribe on odysee: https://odysee.com/@openinverter:9
User avatar
dima
Posts: 157
Joined: Sun Dec 09, 2018 9:35 pm
Location: Canada

Re: Driver issue v1 main board to Windows

Post by dima »

Something else I noticed with "Chinezium USB-TTL". They don't like Stop-Bit 2. Maybe it is driver related who knows. But when I set Stop-Bit as 1 it works fine ...even though the firmware code has 2.

/src/project/hwinit.cpp

Code: Select all

usart_set_baudrate(TERM_USART, USART_BAUDRATE);
usart_set_databits(TERM_USART, 8);
usart_set_stopbits(TERM_USART, USART_STOPBITS_2);
nailgg
Posts: 119
Joined: Sat Dec 22, 2018 8:40 pm

Re: Driver issue v1 main board to Windows

Post by nailgg »

dima wrote: Wed Feb 27, 2019 11:01 pm Something else I noticed with "Chinezium USB-TTL". They don't like Stop-Bit 2. Maybe it is driver related who knows. But when I set Stop-Bit as 1 it works fine ...even though the firmware code has 2.

I have a Zigbee module here and for some reason it doesn't like 115200 baud rate and 2 stop bits, the "json" command returns partially corrupted data on the serial console, even when the receiver and transmitter are very close. Web interfaces don't work properly because of this. So I'm using 1 stop bit with 38400 baud rate.
Post Reply