2.6 KiB
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 data micro-USB cable. Once you turn on the device, wait at least 15 seconds until its fully loaded.
Development shell
flterm /dev/ttyUSBX
, whereX
is usually third (index 2) from suggested variants.- Restart the device with
artiq_flash start
- If it didn't work, try all of
/dev/ttyUSBX
, and restart the device
Older Nix and other Linuxes
- Install
cutecom
vianix-shell -p cutecom
or your package manager - Run
cutecom
and follow settings from the picture: - Restart the device with
artiq_flash start
, or by power-cycling it (wait 30 seconds before turning on) - If it didn't work, try all of
/dev/ttyUSBX
, and restart the device
Windows
While Windows 11 tested to be working out-of-the box with both UART and flashing, Windows 10 may need additional drivers manipulations, as shown below.
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. In case you cannot
locate the devices, they may appear in the Other devices section:
You may also need to reboot your PC after doing this.
If you are here after flashing firmware stage, you may fail to see the devices in the described locations.
If you see them in the Universal Serial Bus devices
section, you may need just to uninstall the third Quad device and reconnect the
Kasli/Kasli-SoC to the PC.
Connecting with PuTTY
- Enable options shown on picture:
- Be aware of these options:
- Connect to every COM port you find on connecting the device (usually connecting the the third port is enough)
- Restart the device with
artiq_flash start
, or by power-cycling it (wait 30 seconds before turning on) - See which COM port produces meaningful output and close others :)