Hello,
I am new to ARTIQ and am currently setting up our Sinara system according to the ARTIQ manual.

I successfully managed to obtain the device binaries and flash them onto the device, but when I try to ping the device in the command prompt I get a timeout error. The device is currently connected to the PC via ethernet through a network switch but directly connecting it to the PC also doesn't work.

I tried pinging the IP address as reported by the device during startup (monitored using PuTTY), as well as the default IP 192.168.1.75 stated in the manual, both without success. The LED labeled 0 next to the ethernet port is on when plugging in the ethernet cable and the cable itself works fine with other devices. Am I missing something?

Here is the information reported by the device during startup:

| \/ (_) ___| ___ / |
| |\/| | _ \ / _ | |
| | | | |) | () | |
|| |||/ _/ ___|

MiSoC Bootloader
Copyright (c) 2017-2022 M-Labs Limited

Bootloader CRC passed
Gateware ident 7.8116.eba143a;erlangen
Initializing SDRAM...
Read leveling scan:
Module 1:
00000000000111111111110000000000
Module 0:
00000000000111111111111000000000
Read leveling: 16+-5 16+-6 done
SDRAM initialized
Memory test passed

Booting from flash...
Starting firmware.
[ 0.000015s] INFO(runtime): ARTIQ runtime starting...
[ 0.003934s] INFO(runtime): software ident 7.8116.eba143a;erlangen
[ 0.010211s] INFO(runtime): gateware ident 7.8116.eba143a;erlangen
[ 0.016493s] INFO(runtime): log level set to INFO by default
[ 0.022224s] INFO(runtime): UART log level set to INFO by default
[ 0.139032s] WARN(runtime::rtio_clocking): rtio_clock setting not recognised. Falling back to default.
[ 0.147132s] WARN(runtime::rtio_clocking): si5324_ext_ref and ext_ref_frequency compile-time options are deprecated. Please use the rtio_clock coreconfig settings instead.
[ 0.162542s] INFO(runtime::rtio_clocking): using 10MHz reference to make 125MHz RTIO clock with PLL
[ 0.427209s] INFO(board_artiq::si5324): waiting for Si5324 lock...
[ 2.548180s] INFO(board_artiq::si5324): ...locked
[ 2.551811s] INFO(runtime::rtio_clocking::crg): Using internal RTIO clock
[ 2.558969s] INFO(runtime): network addresses: MAC=e8-eb-1b-46-5d-af IPv4=10.34.16.100 IPv6-LL=fe80::eaeb:1bff:fe46:5daf IPv6=no configured address
[ 2.573607s] INFO(runtime::mgmt): management interface active
[ 2.599793s] INFO(runtime::session): accepting network sessions
[ 2.612872s] INFO(runtime::session): running startup kernel
[ 2.617321s] INFO(runtime::session): no startup kernel found
[ 2.623141s] INFO(runtime::session): no connection, starting idle kernel
[ 2.629962s] INFO(runtime::session): no idle kernel found

    hdang the default IP 192.168.1.75

    This is not useful, the device has only one IP 10.34.16.100.

      Pinging the device IP 10.34.16.100 unfortunately results in a timeout.

      Is there a way to find out if the error is caused by my PC or the Sinara system?

      Ping another known-good 10.34.16.* IP from the same PC?

      Verify your networking setup. Especially check that your computer will look at that interface when trying to connect to Kasli's IP address. E.g. by adding an IP to the interface that shares a network with Kasli's IP, e.g. 10.34.16.80/24.

      Thank you for your replies!

      The problem was that the Kasli's IP 10.34.16.100 was not on the Windows routing table. Network packets sent from my PC with the IP 10.64.16.80 therefore didn't reach it.

      I followed this guide to add a static route to the routing table:
      https://www.howtogeek.com/howto/windows/adding-a-tcpip-route-to-the-windows-routing-table/

      Here is the specific command that I used in case somebody else also has this issue:
      route -p ADD 10.34.16.100 MASK 255.255.255.255 10.64.16.80

      You can find out the IP of your PC by running the following command in the command prompt:
      ipconfig

      Or just set the netmask to something more sensible e.g. 255.255.255.0, then everything for 10.34.16.* will be sent to this interface.