Hi, architeuthis, bodokaiser and esavkin! Thank you so much for your reply! The problem seems to be solved.
Following the guide on https://git.m-labs.hk/sinara-hw/assembly/src/branch/master/src/sw_sup/uart_logs.md, I read the following UART logs:
__ __ _ ____ ____
| \/ (_) ___| ___ / ___|
| |\/| | \___ \ / _ \| |
| | | | |___) | (_) | |___
|_| |_|_|____/ \___/ \____|
MiSoC Bootloader
Copy right (c) 2017-2022 M-Labs Limited
Bootloader CRC passed
Gateware ident 7.8047.163 93ef.beta;ustc7
Initializing SDRAM...
Read leveling scan:
Module 1:
0000000000011111 1111100000000000
Module 0:
00000000001111111111100000000000
Read leveling: 15+-5 15 +-5 done
SDRAM initialized
Memory test passed
Booting from flash...
Starting firmwar e.
[ 0.000011s] INFO(runtime): ARTIQ runtime starting...
[ 0.003929s] IN FO(runtime): software ident 7.8047.16393ef.beta;ustc7
[ 0.010379s] INFO(runt ime): gateware ident 7.8047.16393ef.beta;ustc7
[ 0.016879s] INFO(runtime): l og level set to INFO by default
[ 0.022601s] INFO(runtime): UART log level s et to INFO by default
[ 0.139422s] WARN(runtime::rtio_clocking): rtio_clock setting not recognised. Falling back to default.
[ 0.147527s] INFO(runtime:: rtio_clocking): using internal 125MHz RTIO clock
[ 0.424006s] INFO(board_art iq::si5324): waiting for Si5324 lock...
[ 4.589120s] INFO(board_artiq::si532 4): ...locked
[ 4.592755s] INFO(runtime::rtio_clocking::crg): Using intern al RTIO clock
[ 4.625239s] INFO(runtime): network addresses: MAC=e8-eb-1b-45 -dd-84 IPv4=192.168.1.75 IPv6-LL=fe80::eaeb:1bff:fe45:dd84 IPv6=no configured ad dress
[ 4.639122s] INFO(runtime::mgmt): management interface active
[ 4.6 65357s] INFO(runtime::session): accepting network sessions
[ 4.678441s] INF O(runtime::session): running startup kernel
[ 4.682931s] INFO(runtime::sessi on): no startup kernel found
[ 4.688697s] INFO(runtime::session): no connect ion, starting idle kernel
[ 4.695549s] INFO(runtime::session): no idle kerne l found
My supervisor told me to connect a cable directly between the Kasli board and the computer, and manually set the computer's IP address to 192.168.1.1
. After this, ping 192.168.1.75
command succeeded. I changed Kasli's IP address into 192.168.110.75 using $ artiq_coremgmt -D 192.168.1.75 config write -s ip 192.168.110.75
and $ artiq_coremgmt -D 192.168.1.75 reboot
, for the original IP address of the lab computer starts with 192.168.110
. Finally I reconnected the computer and the board into the local network and edited device_db.py. Now the Kasli board becomes accessible under the new address and example experiments like led.py are runnable.