Update networking and add UART logs for windows

Signed-off-by: Egor Savkin <es@m-labs.hk>

src/sw_sup/networking.md

@@ -13,13 +13,16 @@ a-la `I can't connect, please help`.
 5. Incompatible Ethernet cables/SFP RJ45. Try different cables and SFP adapters. 
    We usually test them with CAT6 cables, but lower categories should be supported too.
 6. SFP or Ethernet are not pushed til the end.
-7. Some weird bugs in Vivado, leading to not working SFP on certain combinations of builds and Kaslis 
+7. Some weird bugs in Vivado, leading to not working SFP on certain combinations of builds and Kaslis (very rare)
+8. Running configured for external reference Kasli without external reference clock signal 
+9. Using legacy firmware with newer hardware. ARTIQ-6 doesn't support Kasli v2.0.2
 
 ## Ways to diagnose
 
 1. `ping` the device. If destination is unreachable, than it is either didn't connect to the network
     or connected to different address. If the packets just do not respond then it is not as clear, we cannot know all the truth.
-2. See the SFP0 light
+2. See the SFP0 LED
-3. UART logs. TODO here is a link to ways to obtain them
+3. See the ERR LED
-4. `nmap` and `arp` to scan your network to help your Kasli get discovered. May be restricted in your network.
+4. UART logs. TODO here is a link to ways to obtain them
-5. Become a router and capture all the packets when your Kasli tries to connect to the network.
+5. `nmap` and `arp` to scan your network to help your Kasli get discovered. May be restricted in your network.
+6. Become a router and capture all the packets when your Kasli tries to connect to the network.

src/sw_sup/uart_logs.md

@@ -22,4 +22,28 @@ until its fully loaded.
 
 ### Windows
 
-TODO
+#### Drivers
+
+Use following instructions to set correct drivers for the COM ports.
+At choosing FTDI drivers stage you may have longer list of drivers. 
+In that case, choose respective `USB Serial Converter X` (A for 0, B for 1, C for 2, D for 3) driver. 
+You may also need to reboot your PC after doing this.
+
+1. ![com_driver_set0.png](../img/win32/com_driver_set0.png)
+2. ![com_driver_set1.png](../img/win32/com_driver_set1.png)
+3. ![com_driver_set2.png](../img/win32/com_driver_set2.png)
+4. ![com_driver_set3.png](../img/win32/com_driver_set3.png)
+5. ![com_driver_set4.png](../img/win32/com_driver_set4.png)
+6. ![com_driver_set5.png](../img/win32/com_driver_set5.png)
+7. ![com_driver_set6.png](../img/win32/com_driver_set6.png)
+
+
+#### Connecting with PuTTY
+
+1. Enable options shown on picture:
+   ![putty_lfcr.png](../img/win32/putty_lfcr.png)
+2. Be aware of these options:
+   ![putty_com_settings.png](../img/win32/putty_com_settings.png)
+3. Connect to every COM port you find on connecting the device (usually connecting the the third port is enough)
+4. Restart the device with `artiq_flash start`, or by power-cycling it (wait 30 seconds before turning on)
+5. See which COM port produces meaningful output and close others :)