Hi Chris
the screen shots show the correct driver and the correct hex in the uart, plus the QT version using the same set up always connects as does the app from 1 of 11. This tends to make me think it is an app problem.
Interestingly, if you view the screen output of the ini file, entering a non existent port number results in an immediate error message, however entering the allocated port number shows nothing, program just hangs and a second attempt to connect to the port crashes program.
joe
toggle quoted message
Show quoted text
On 21/12/2021 10:10, Chris Gardner via groups.io wrote:
I had something similar happen... Once windows decides the type of device (right or wrong), it assigns a driver. Often, when you try to load the correct driver, windows will insist it already has the "best" driver.
Perhaps the Nano had been connected, before the required driver was loaded first, that can cause windows to load the incorrect driver.
I used a program called Zadig Available here ===> Select show all devices, find the one in question, then load the generic usb driver
Next load the correct ST Microdevices driver.
