01:20 <mtrbot-ml> [mattermost] <alexist> alexist joined the team.

02:16 <mtrbot-ml> [mattermost] <alexist> hello, can I ask some question for connecting KC705 FPGA to PC with Ethernet?

02:20 <mtrbot-ml> [mattermost] <alexist> I connceted KC705 to PC with JTAG and Ethernet cable (without UART cable).

02:20 <mtrbot-ml> [mattermost] <alexist> I saw 'artiq_flash' works pretty well, so I think JTAG connection works fine.

02:21 <mtrbot-ml> [mattermost] <alexist> But ethernet connection does not work well.

02:25 <mtrbot-ml> [mattermost] <alexist> it shows only 'connecting' and 'connection failed' at ubuntu network setting

02:25 <mtrbot-ml> [mattermost] <alexist> Although I ran 'artiq_mkfs flash_storage.img -s mac 00:0A:35:02:A1:DF -s ip 192.168.1.50', 'ping' does not work.

02:25 <mtrbot-ml> [mattermost] <alexist> Also, I tried to set FPGA's IP with'$ sudo ifconfig enp3s0 192.168.1.50', but it also doesn't work('ping' return flag even FPGA is disconnected with PC).

02:26 <mtrbot-ml> [mattermost] <alexist> I reinstalled Ubuntu's network driver(r8169 to r8168), but it still doesn't work.

02:27 <mtrbot-ml> [mattermost] <alexist> Should I connect another cable( e.g. UART or SFP) or need more some setting?

02:59 <mtrbot-ml> [mattermost] <alexist> In addition, I’m using Ubuntu 18.04 LTS OS!

09:35 <mtrbot-ml> [mattermost] <sb10q> @alexist check UART output to see if the kc705 boots

09:36 <mtrbot-ml> [mattermost] <sb10q> @alexist and you should study how TCP/IP networking works. it is incorrect to set the same IP on KC705 and computer. try setting up a manual network connection between two Linux PCs first, and once you understand how this works move to the KC705

09:41 <mtrbot-ml> [mattermost] <alexist> Thanks for advise! I should study TCP/IP networking right now😀

15:23 <rjo> dpn: We just comission the ftdi with a serial number corresponding to the eeprom mac and then use the physical topology (/dev/serial/by-path) or the stable semantic names (/dev/serial/by-id). Both have stable names also per-interface. and completely resolve this.

15:27 <rjo> also no need to install and maintain udev rules, freely transfers to other systems without overhead.

18:14 <mtrbot-ml> [mattermost] <sb10q> rjo: how does this help with differentiating between the interfaces withing the same FTDI chip?

18:51 <rjo> you get four different and stable names for the four interfaces. you just use them.

19:12 <mtrbot-ml> [mattermost] <sb10q> @astro have you tried running Chris' artiq-zynq demo?

19:13 <mtrbot-ml> [mattermost] <sb10q> https://git.m-labs.hk/m-labs/artiq-zynq

19:13 <mtrbot-ml> [mattermost] <sb10q> rjo: but this isn't because of the serial number, is it?

19:34 <rjo> If the serial number is not unique then the by-id devices collide.

19:36 <rjo> Using unique serials allows you to not have to rely on fixed bus topology.

21:08 <mtrbot-ml> [mattermost] <astro> ok, I think I now understand how to use `AutoCSR` in migen. it works nicely on the cora.

21:10 <mtrbot-ml> [mattermost] <astro> @sb10q where would you like PRs for the zynq targets? they introduce a dependency on migen-axi - better there instead of migen?

21:39 <mtrbot-ml> [mattermost] <astro> ah, it was migen-axi in the task description...