Hello,
where can I find a driver for the serial port (COM1) for Window10 64 bits for the Fitlet2 Atom-E3930.
Actually, after windows has performed all updates, device manager still shows "unkown devices".
Regards,
Andi
Win10 (64bit) driver for serial ports (Fitlet2 Atom-E3930)
Moderator: Andrey.Mazlin
Re: Win10 (64bit) driver for serial ports (Fitlet2 Atom-E393
You should find Windows 10 drivers at the below link:
http://fit-pc.com/wiki/index.php/Fitlet ... Windows_10
http://fit-pc.com/wiki/index.php/Fitlet ... Windows_10
Re: Win10 (64bit) driver for serial ports (Fitlet2 Atom-E393
Hello Tamir,
thanks for replay.
I set up the Fitlet2 Atom-E3930 with win10 using the "MediaCration-Tool".
As recommended by you, I installed the fitlet2_Win10_Chipset as well as the fitlet2_Win10_SerialIO.
But it doesn't help. Device manager still shows "unkown devices". There is still no COM-Port shown in device manager.
Also the power button seem to have no effect if it gets pressed only short. Windows is not shut down.
Any further recommendations?
Regards Andi
thanks for replay.
I set up the Fitlet2 Atom-E3930 with win10 using the "MediaCration-Tool".
As recommended by you, I installed the fitlet2_Win10_Chipset as well as the fitlet2_Win10_SerialIO.
But it doesn't help. Device manager still shows "unkown devices". There is still no COM-Port shown in device manager.
Also the power button seem to have no effect if it gets pressed only short. Windows is not shut down.
Any further recommendations?
Regards Andi
Re: Win10 (64bit) driver for serial ports (Fitlet2 Atom-E393
I'm having similar problems with the Fitlet2. I can't get it work on a fresh Win10 home install with either the drivers on the website or the drivers obtained from Windows Update.
Here's what happens when I install the latest drivers directly from the Fit-PC website. The UART controller drivers do not start, and the sub-devices are not even detected. If I let Windows Update detect the device instead, it installs a completely different driver. These drivers appear to start, but I still need to install the sub-device driver from the Fit-PC website before the COM Ports appear in device manager. When I combine the two, device manager looks happy. However, it's not possible to open either COM port in PuTTY. I have other software that detects both ports as "COM 0", despite being listed as COM1 and COM2 in device manager. Note the "on Host Controller 5AC0" on the sub-device, which clearly links it to the UART controller pulled through Windows update. It's also concerning that two serial ports are detected when there only appears to be one implemented in hardware.
This is using the sub-device driver that was uploaded to the website on Friday (2018-08-17). All other device drivers on the system are installed and operational (Chipset, TXE etc.). It doesn't seem to make a difference if the other drivers come from Windows Update or the Fit-PC website (I tried both). Windows 10 Home 1803 was installed using the USB media creation tool.
The two configurations were tried with full HDD wipe and reinstall inbetween. I've also got 4 units here which all exhibit this problem. I don't think it's specific to a single unit.
Update: Just tried Win10 Pro and got exactly the same result.
Here's what happens when I install the latest drivers directly from the Fit-PC website. The UART controller drivers do not start, and the sub-devices are not even detected. If I let Windows Update detect the device instead, it installs a completely different driver. These drivers appear to start, but I still need to install the sub-device driver from the Fit-PC website before the COM Ports appear in device manager. When I combine the two, device manager looks happy. However, it's not possible to open either COM port in PuTTY. I have other software that detects both ports as "COM 0", despite being listed as COM1 and COM2 in device manager. Note the "on Host Controller 5AC0" on the sub-device, which clearly links it to the UART controller pulled through Windows update. It's also concerning that two serial ports are detected when there only appears to be one implemented in hardware.
This is using the sub-device driver that was uploaded to the website on Friday (2018-08-17). All other device drivers on the system are installed and operational (Chipset, TXE etc.). It doesn't seem to make a difference if the other drivers come from Windows Update or the Fit-PC website (I tried both). Windows 10 Home 1803 was installed using the USB media creation tool.
The two configurations were tried with full HDD wipe and reinstall inbetween. I've also got 4 units here which all exhibit this problem. I don't think it's specific to a single unit.
Update: Just tried Win10 Pro and got exactly the same result.
Re: Win10 (64bit) driver for serial ports (Fitlet2 Atom-E393
Please update the UART and UART sub device drivers to the latest:
http://www.fit-pc.com/wiki/index.php/Fi ... Windows_10
After that Please confirm the below:
Enter to the BIOS menu, and set 4G decoding to Disabled:
Advanced > PCI Subsystem > 4G Decoding [Disabled]
The driver has been tested with:
Putty
ExtraPutty
MobaXterm terminals
The driver supports the Hardware and None flow control, but doesn't support the Software (XON/XOFF) flow control.
http://www.fit-pc.com/wiki/index.php/Fi ... Windows_10
After that Please confirm the below:
Enter to the BIOS menu, and set 4G decoding to Disabled:
Advanced > PCI Subsystem > 4G Decoding [Disabled]
The driver has been tested with:
Putty
ExtraPutty
MobaXterm terminals
The driver supports the Hardware and None flow control, but doesn't support the Software (XON/XOFF) flow control.