1
0
Fork 0

Add UART for linuxes

Signed-off-by: Egor Savkin <es@m-labs.hk>
This commit is contained in:
Egor Savkin 2023-05-12 18:02:47 +08:00
parent 2bda9ed50f
commit f9e7f06d5c
6 changed files with 34 additions and 4 deletions

View File

@ -18,3 +18,4 @@
- [Sinara 8451 Thermostat](./hw/thermostat.md) - [Sinara 8451 Thermostat](./hw/thermostat.md)
- [Software/Support](./sw_sup/software_support.md) - [Software/Support](./sw_sup/software_support.md)
- [Networking](./sw_sup/networking.md) - [Networking](./sw_sup/networking.md)
- [UART Logs](./sw_sup/uart_logs.md)

BIN
src/img/curious_doge.jpg Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 28 KiB

BIN
src/img/uart_cutecom.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 54 KiB

View File

@ -13,11 +13,13 @@ a-la `I can't connect, please help`.
5. Incompatible Ethernet cables/SFP RJ45. Try different cables and SFP adapters. 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. We usually test them with CAT6 cables, but lower categories should be supported too.
6. SFP or Ethernet are not pushed til the end. 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 ## Ways to diagnose
1. `ping` the device. If destination is unreachable, than it is either didn't connect to the network 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. 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 2. See the SFP0 light
3. `nmap` and `arp` to scan your network to help your Kasli get discovered. May be restricted in your network. 3. UART logs. TODO here is a link to ways to obtain them
4. Become a router and capture all the packets when your Kasli tries to connect to the network. 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.

View File

@ -6,3 +6,5 @@ process, which often includes answering similar questions and solving similar pr
In the future, it may be revised and added to the official ARTIQ manual. In the future, it may be revised and added to the official ARTIQ manual.
I hope that helps! I hope that helps!
![curious_doge.jpg](../img/curious_doge.jpg)

25
src/sw_sup/uart_logs.md Normal file
View File

@ -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