diff --git a/src/SUMMARY.md b/src/SUMMARY.md
index 847a44c..ee84894 100644
--- a/src/SUMMARY.md
+++ b/src/SUMMARY.md
@@ -18,3 +18,4 @@
   - [Sinara 8451 Thermostat](./hw/thermostat.md)
 - [Software/Support](./sw_sup/software_support.md)
   - [Networking](./sw_sup/networking.md)
+  - [UART Logs](./sw_sup/uart_logs.md)
diff --git a/src/img/curious_doge.jpg b/src/img/curious_doge.jpg
new file mode 100644
index 0000000..64d109e
Binary files /dev/null and b/src/img/curious_doge.jpg differ
diff --git a/src/img/uart_cutecom.png b/src/img/uart_cutecom.png
new file mode 100644
index 0000000..12ad5a5
Binary files /dev/null and b/src/img/uart_cutecom.png differ
diff --git a/src/sw_sup/networking.md b/src/sw_sup/networking.md
index c95934e..9c97022 100644
--- a/src/sw_sup/networking.md
+++ b/src/sw_sup/networking.md
@@ -13,11 +13,13 @@ 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 
 
 ## 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. UART logs. TODO here is a link to ways to obtain them
-3. `nmap` and `arp` to scan your network to help your Kasli get discovered. May be restricted in your network.
-4. Become a router and capture all the packets when your Kasli tries to connect to the network.
\ No newline at end of file
+2. See the SFP0 light
+3. UART logs. TODO here is a link to ways to obtain them
+4. `nmap` and `arp` to scan your network to help your Kasli get discovered. May be restricted in your network.
+5. Become a router and capture all the packets when your Kasli tries to connect to the network.
\ No newline at end of file
diff --git a/src/sw_sup/software_support.md b/src/sw_sup/software_support.md
index bd6b993..f2d8976 100644
--- a/src/sw_sup/software_support.md
+++ b/src/sw_sup/software_support.md
@@ -5,4 +5,6 @@ regarding software. The main intend of this section is to ease the support
 process, which often includes answering similar questions and solving similar problems.
 In the future, it may be revised and added to the official ARTIQ manual.
 
-I hope that helps!
\ No newline at end of file
+I hope that helps!
+
+![curious_doge.jpg](../img/curious_doge.jpg)
\ No newline at end of file
diff --git a/src/sw_sup/uart_logs.md b/src/sw_sup/uart_logs.md
new file mode 100644
index 0000000..09ebec3
--- /dev/null
+++ b/src/sw_sup/uart_logs.md
@@ -0,0 +1,25 @@
+# UART Logs
+
+Used for network, booting, and most other issues debugging.
+
+## How to get them
+
+First, connect your Kasli/SoC to the PC with a micro-USB cable. Once you turn on the device, wait at least 15 seconds
+until its fully loaded.
+
+### Development shell
+
+1. `flterm /dev/ttyUSBX`, where `X` is usually third (index 2) from suggested variants.
+2. Restart the device with `artiq_flash start`
+3. If it didn't work, try all of `/dev/ttyUSBX`, and restart the device
+
+### Older Nix and other Linuxes
+
+1. Install `cutecom` via `nix-shell -p cutecom` or your package manager
+2. Run `cutecom` and follow settings from the picture: ![uart_cutecom.png](../img/uart_cutecom.png)
+3. Restart the device with `artiq_flash start`, or by power-cycling it (wait 30 seconds before turning on)
+4. If it didn't work, try all of `/dev/ttyUSBX`, and restart the device
+
+### Windows
+
+TODO
\ No newline at end of file