it seems is not a hardware configuration related problem.
searching on FTDI support forum, I found this:
and indeed, on W10 each port have it's own serial number
I'll do some research later, this aspect does not affect the hat functionality
searching on FTDI support forum, I found this:
Quote:The udev system on Linux will only pull the ATTRS{serial} attribute from the parent device and note the individual interfaces on the device. this is why the channel letters are not appended to the serial number when udev is used to obtain attributes for a device (this appears to be what serial.tools.list_ports.comports() is doing).
Please see the attached 'udev.png' for an example of the output for the following command issued when a FT4232H was enumerated on an Ubuntu system:
udevadm info --name=/dev/ttyUSB0 --attribute-walk
Please note the output is for the parent device.
It is possible via the D2XX driver to obtain and access devices via their serial number, please see simple.PNG for an example output from the 'simple' Sample included in the D2XX driver download for Linux. This lists the serial numbers of all connected devices and then opens the first one it can find, in this case channel A of the FT4232H.
Best Regards,
FTDI Community
and indeed, on W10 each port have it's own serial number
I'll do some research later, this aspect does not affect the hat functionality
███ - SV Haimana