From drive-shares-noreply at google.com Thu Jan 4 13:53:12 2018 From: drive-shares-noreply at google.com (Tim Ansell (via Google Docs)) Date: Thu, 04 Jan 2018 02:53:12 +0000 Subject: [fpga-miniconf] FPGA Miniconf Set Up Instructions References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> Message-ID: <001a114701ccc5ba120561ea6ee5@google.com> I've shared an item with you: FPGA Miniconf Set Up Instructions https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 It's not an attachment ? it's stored online. To open this item, just click the link above. Hi! This is the initial attempt at set up instructions for the LCA2018 FPGA Miniconf. Please attempt to follow these instructions and add comments where you encounter issues and we will try to update the instructions with fixes. Looking forward to seeing everyone at an awesome Linux.conf.au 2018! Thanks! Tim 'mithro' Ansell -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Fri Jan 5 10:44:01 2018 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 5 Jan 2018 10:44:01 +1100 Subject: [fpga-miniconf] FPGA Miniconf Set Up Instructions In-Reply-To: <001a114701ccc5ba120561ea6ee5@google.com> References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> Message-ID: <20180104234401.GB3903@dimstar.local.net> Hi Tim, On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) wrote: > I've shared an item with you: > > FPGA Miniconf Set Up Instructions > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > It's not an attachment ??? it's stored online. To open this item, just click > the link above. > > Hi! > > This is the initial attempt at set up instructions for the LCA2018 FPGA > Miniconf. Please attempt to follow these instructions and add comments where > you encounter issues and we will try to update the instructions with fixes. > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > Thanks! > > Tim 'mithro' Ansell I can't seem to be able to select & paste from this. Any ideas how to fix? Cheers ... Duncan. From duncan_roe at optusnet.com.au Fri Jan 5 21:42:16 2018 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 5 Jan 2018 21:42:16 +1100 Subject: [fpga-miniconf] download-env got "unexpected error" - please suggest what I can do to fix In-Reply-To: <001a114701ccc5ba120561ea6ee5@google.com> References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> Message-ID: <20180105104216.GA3938@dimstar.local.net> Hi Tim, On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) wrote: > I've shared an item with you: > > FPGA Miniconf Set Up Instructions > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > It's not an attachment ??? it's stored online. To open this item, just click > the link above. > > Hi! > > This is the initial attempt at set up instructions for the LCA2018 FPGA > Miniconf. Please attempt to follow these instructions and add comments where > you encounter issues and we will try to update the instructions with fixes. > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > Thanks! > > Tim 'mithro' Ansell Everything was going well until this: > Installing openocd (jtag tool for programming and debug) > Solving environment: done > > ## Package Plan ## > > environment location: /usr/src/litex-buildenv/build/conda > > added / updated specs: > - openocd=0.10.0 > > > The following NEW packages will be INSTALLED: > > openocd: 0.10.0_226_g1c2e3d41d-20180101_0708 timvideos > > Preparing transaction: done > Verifying transaction: failed > > # >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<< > > Traceback (most recent call last): > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/exceptions.py", line 724, in __call__ > return func(*args, **kwargs) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/cli/main.py", line 78, in _main > exit_code = do_call(args, p) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/cli/conda_argparse.py", line 76, in do_call > exit_code = getattr(module, func_name)(args, parser) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/cli/main_install.py", line 11, in execute > install(args, parser, 'install') > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/cli/install.py", line 255, in install > handle_txn(progressive_fetch_extract, unlink_link_transaction, prefix, args, newenv) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/cli/install.py", line 285, in handle_txn > unlink_link_transaction.execute() > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/core/link.py", line 220, in execute > self.verify() > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/common/io.py", line 415, in decorated > return f(*args, **kwds) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/core/link.py", line 207, in verify > exceptions = self._verify(self.prefix_setups, self.prefix_action_groups) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/core/link.py", line 460, in _verify > cls._verify_transaction_level(prefix_setups), > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/core/link.py", line 455, in > exceptions = tuple(exc for exc in concatv( > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/core/link.py", line 323, in _verify_individual_level > error_result = axn.verify() > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/site-packages/conda/core/path_actions.py", line 258, in verify > if self.link_type != LinkType.directory and not lexists(self.source_full_path): # pragma: no cover # NOQA > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/posixpath.py", line 171, in lexists > os.lstat(path) > UnicodeEncodeError: 'latin-1' codec can't encode characters in position 118-119: ordinal not in range(256) > > `$ /usr/src/litex-buildenv/build/conda/bin/conda install -y openocd=0.10.0` > > environment variables: > CIO_TEST= > CONDA_ROOT=/usr/src/litex-buildenv/build/conda > CPLUS_INCLUDE_PATH=/usr/lib64/qt/include > INFOPATH=/usr/info > LADSPA_PATH=/usr/lib64/ladspa > LV2_PATH=/usr/lib64/lv2 > MANPATH=/usr/local/man:/usr/man:/usr/lib64/java/man:/usr/share/texmf/man > PATH=/usr/src/litex-buildenv/build/conda/bin:/opt/Xilinx/Vivado/2017.3/bin: > /home/dunc/bin64:/home/dunc/bin:/home/dunc/command_line_tools/bin:/usr > /local/bin:/usr/bin:/bin:/usr/games:/opt/FDK/Tools/linux:/usr/lib64/ja > va/bin:/usr/lib64/java/jre/bin:/usr/lib64/kde4/libexec:/usr/lib64/qt/b > in:/usr/lib64/qt5/bin:/usr/share/texmf/bin:/usr/local/sbin:/usr/sbin:/ > sbin:/sbin > PKG_CONFIG_PATH=/usr/lib64/pkgconfig:/usr/share/pkgconfig > PYTHONHASHSEED=0 > REQUESTS_CA_BUNDLE= > SSL_CERT_FILE= > VAMP_PATH=/usr/lib64/vamp > > active environment : None > user config file : /home/dunc/.condarc > populated config files : /home/dunc/.condarc > conda version : 4.4.6 > conda-build version : not installed > python version : 3.5.4.final.0 > base environment : /usr/src/litex-buildenv/build/conda (writable) > channel URLs : https://conda.anaconda.org/timvideos/linux-64 > https://conda.anaconda.org/timvideos/noarch > https://repo.continuum.io/pkgs/main/linux-64 > https://repo.continuum.io/pkgs/main/noarch > https://repo.continuum.io/pkgs/free/linux-64 > https://repo.continuum.io/pkgs/free/noarch > https://repo.continuum.io/pkgs/r/linux-64 > https://repo.continuum.io/pkgs/r/noarch > https://repo.continuum.io/pkgs/pro/linux-64 > https://repo.continuum.io/pkgs/pro/noarch > package cache : /usr/src/litex-buildenv/build/conda/pkgs > /home/dunc/.conda/pkgs > envs directories : /usr/src/litex-buildenv/build/conda/envs > /home/dunc/.conda/envs > platform : linux-64 > user-agent : conda/4.4.6 requests/2.18.4 CPython/3.5.4 Linux/4.13.13-k8_64 slackware/14.2 glibc/2.23 > UID:GID : 501:100 > netrc file : None > offline mode : False > > > An unexpected error has occurred. Conda has prepared the above report. > Upload successful. I tried "export LC_ALL=C" and re-run, but it still failed. Only difference I could see was > UnicodeEncodeError: 'ascii' codec can't encode characters in position 118-119: ordinal not in range(128) i.e. "ascii" replaces "latin-1" above. Let me know if I can provide any otherdata that might help, Cheers ... Duncan. From mithro at mithis.com Fri Jan 5 21:48:09 2018 From: mithro at mithis.com (Tim Ansell) Date: Fri, 5 Jan 2018 10:48:09 +0000 Subject: [fpga-miniconf] download-env got "unexpected error" - please suggest what I can do to fix In-Reply-To: <20180105104216.GA3938@dimstar.local.net> References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180105104216.GA3938@dimstar.local.net> Message-ID: Something has a unicode character in the path. I'm on my phone at the moment so can't get you the exact value, but you want something like; export LC_ALL=en_US.UTF-8 export LANG=en_US.UTF-8 export LANGUAGE=en_US.UTF-8 If that works can you log an issue and we will make sure to add them to the script to solve it for everyone? Tim 'mithro' Ansell On 5 Jan. 2018 6:42 pm, "Duncan Roe" wrote: Hi Tim, On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) wrote: > I've shared an item with you: > > FPGA Miniconf Set Up Instructions > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63 Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > It's not an attachment ??? it's stored online. To open this item, just click > the link above. > > Hi! > > This is the initial attempt at set up instructions for the LCA2018 FPGA > Miniconf. Please attempt to follow these instructions and add comments where > you encounter issues and we will try to update the instructions with fixes. > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > Thanks! > > Tim 'mithro' Ansell Everything was going well until this: > Installing openocd (jtag tool for programming and debug) > Solving environment: done > > ## Package Plan ## > > environment location: /usr/src/litex-buildenv/build/conda > > added / updated specs: > - openocd=0.10.0 > > > The following NEW packages will be INSTALLED: > > openocd: 0.10.0_226_g1c2e3d41d-20180101_0708 timvideos > > Preparing transaction: done > Verifying transaction: failed > > # >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<< > > Traceback (most recent call last): > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/exceptions.py", line 724, in __call__ > return func(*args, **kwargs) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/cli/main.py", line 78, in _main > exit_code = do_call(args, p) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/cli/conda_argparse.py", line 76, in do_call > exit_code = getattr(module, func_name)(args, parser) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/cli/main_install.py", line 11, in execute > install(args, parser, 'install') > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/cli/install.py", line 255, in install > handle_txn(progressive_fetch_extract, unlink_link_transaction, prefix, args, newenv) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/cli/install.py", line 285, in handle_txn > unlink_link_transaction.execute() > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/core/link.py", line 220, in execute > self.verify() > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/common/io.py", line 415, in decorated > return f(*args, **kwds) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/core/link.py", line 207, in verify > exceptions = self._verify(self.prefix_setups, self.prefix_action_groups) > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/core/link.py", line 460, in _verify > cls._verify_transaction_level(prefix_setups), > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/core/link.py", line 455, in > exceptions = tuple(exc for exc in concatv( > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/core/link.py", line 323, in _verify_individual_level > error_result = axn.verify() > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/ site-packages/conda/core/path_actions.py", line 258, in verify > if self.link_type != LinkType.directory and not lexists(self.source_full_path): # pragma: no cover # NOQA > File "/usr/src/litex-buildenv/build/conda/lib/python3.5/posixpath.py", line 171, in lexists > os.lstat(path) > UnicodeEncodeError: 'latin-1' codec can't encode characters in position 118-119: ordinal not in range(256) > > `$ /usr/src/litex-buildenv/build/conda/bin/conda install -y openocd=0.10.0` > > environment variables: > CIO_TEST= > CONDA_ROOT=/usr/src/litex-buildenv/build/conda > CPLUS_INCLUDE_PATH=/usr/lib64/qt/include > INFOPATH=/usr/info > LADSPA_PATH=/usr/lib64/ladspa > LV2_PATH=/usr/lib64/lv2 > MANPATH=/usr/local/man:/usr/ man:/usr/lib64/java/man:/usr/share/texmf/man > PATH=/usr/src/litex-buildenv/ build/conda/bin:/opt/Xilinx/Vivado/2017.3/bin: > /home/dunc/bin64:/home/dunc/ bin:/home/dunc/command_line_tools/bin:/usr > /local/bin:/usr/bin:/bin:/usr/ games:/opt/FDK/Tools/linux:/usr/lib64/ja > va/bin:/usr/lib64/java/jre/ bin:/usr/lib64/kde4/libexec:/usr/lib64/qt/b > in:/usr/lib64/qt5/bin:/usr/ share/texmf/bin:/usr/local/sbin:/usr/sbin:/ > sbin:/sbin > PKG_CONFIG_PATH=/usr/lib64/pkgconfig:/usr/share/pkgconfig > PYTHONHASHSEED=0 > REQUESTS_CA_BUNDLE= > SSL_CERT_FILE= > VAMP_PATH=/usr/lib64/vamp > > active environment : None > user config file : /home/dunc/.condarc > populated config files : /home/dunc/.condarc > conda version : 4.4.6 > conda-build version : not installed > python version : 3.5.4.final.0 > base environment : /usr/src/litex-buildenv/build/conda (writable) > channel URLs : https://conda.anaconda.org/timvideos/linux-64 > https://conda.anaconda.org/timvideos/noarch > https://repo.continuum.io/pkgs/main/linux-64 > https://repo.continuum.io/pkgs/main/noarch > https://repo.continuum.io/pkgs/free/linux-64 > https://repo.continuum.io/pkgs/free/noarch > https://repo.continuum.io/pkgs/r/linux-64 > https://repo.continuum.io/pkgs/r/noarch > https://repo.continuum.io/pkgs/pro/linux-64 > https://repo.continuum.io/pkgs/pro/noarch > package cache : /usr/src/litex-buildenv/build/conda/pkgs > /home/dunc/.conda/pkgs > envs directories : /usr/src/litex-buildenv/build/conda/envs > /home/dunc/.conda/envs > platform : linux-64 > user-agent : conda/4.4.6 requests/2.18.4 CPython/3.5.4 Linux/4.13.13-k8_64 slackware/14.2 glibc/2.23 > UID:GID : 501:100 > netrc file : None > offline mode : False > > > An unexpected error has occurred. Conda has prepared the above report. > Upload successful. I tried "export LC_ALL=C" and re-run, but it still failed. Only difference I could see was > UnicodeEncodeError: 'ascii' codec can't encode characters in position 118-119: ordinal not in range(128) i.e. "ascii" replaces "latin-1" above. Let me know if I can provide any otherdata that might help, Cheers ... Duncan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Fri Jan 5 22:34:06 2018 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 5 Jan 2018 22:34:06 +1100 Subject: [fpga-miniconf] download-env got "unexpected error" - please suggest what I can do to fix In-Reply-To: References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180105104216.GA3938@dimstar.local.net> Message-ID: <20180105113406.GB3938@dimstar.local.net> Hi Tim, On Fri, Jan 05, 2018 at 10:48:09AM +0000, Tim Ansell wrote: > Something has a unicode character in the path. I'm on my phone at the > moment so can't get you the exact value, but you want something like; > > export LC_ALL=en_US.UTF-8 > export LANG=en_US.UTF-8 > export LANGUAGE=en_US.UTF-8 > > If that works can you log an issue and we will make sure to add them to the > script to solve it for everyone? > > Tim 'mithro' Ansell > Thanks for your very prompt reply. That did the trick. I've logged an issue about it, Cheers ... Duncan From mithro at mithis.com Fri Jan 5 23:10:28 2018 From: mithro at mithis.com (Tim Ansell) Date: Fri, 5 Jan 2018 12:10:28 +0000 Subject: [fpga-miniconf] download-env got "unexpected error" - please suggest what I can do to fix In-Reply-To: <20180105113406.GB3938@dimstar.local.net> References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180105104216.GA3938@dimstar.local.net> <20180105113406.GB3938@dimstar.local.net> Message-ID: Glad to hear it! Tim 'mithro' Ansell On 5 Jan. 2018 7:34 pm, "Duncan Roe" wrote: > Hi Tim, > > On Fri, Jan 05, 2018 at 10:48:09AM +0000, Tim Ansell wrote: > > Something has a unicode character in the path. I'm on my phone at the > > moment so can't get you the exact value, but you want something like; > > > > export LC_ALL=en_US.UTF-8 > > export LANG=en_US.UTF-8 > > export LANGUAGE=en_US.UTF-8 > > > > If that works can you log an issue and we will make sure to add them to > the > > script to solve it for everyone? > > > > Tim 'mithro' Ansell > > > Thanks for your very prompt reply. > > That did the trick. I've logged an issue about it, > > Cheers ... Duncan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at optusnet.com.au Sat Jan 6 10:51:36 2018 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sat, 6 Jan 2018 10:51:36 +1100 Subject: [fpga-miniconf] FPGA Miniconf Set Up Instructions select / paste In-Reply-To: <20180104234401.GB3903@dimstar.local.net> References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180104234401.GB3903@dimstar.local.net> Message-ID: <20180105235136.GA4482@dimstar.local.net> On Fri, Jan 05, 2018 at 10:44:01AM +1100, Duncan Roe wrote: > Hi Tim, > > On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) wrote: > > I've shared an item with you: > > > > FPGA Miniconf Set Up Instructions > > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > > > It's not an attachment ??? it's stored online. To open this item, just click > > the link above. > > > > Hi! > > > > This is the initial attempt at set up instructions for the LCA2018 FPGA > > Miniconf. Please attempt to follow these instructions and add comments where > > you encounter issues and we will try to update the instructions with fixes. > > > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > > > Thanks! > > > > Tim 'mithro' Ansell > > I can't seem to be able to select & paste from this. Any ideas how to fix? > > Cheers ... Duncan. Select & ctl-C copies, can ctl-V paste into a blank Libreoffice Writer doc. >From there, can select and middle-button paste into an xterm. I'm happy, Cheers ... Duncan. From jason at ball.net Sun Jan 7 11:02:54 2018 From: jason at ball.net (Jason Ball) Date: Sun, 7 Jan 2018 11:02:54 +1100 Subject: [fpga-miniconf] FPGA Miniconf Set Up Instructions In-Reply-To: <20180104234401.GB3903@dimstar.local.net> References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180104234401.GB3903@dimstar.local.net> Message-ID: Hi Tim, I finally got around to completing the setup and running through all sections. The only note of any import is I found I needed to change the default tftp path so the images could be loaded by qemu. update: /etc/inetd.conf and change: tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 */srv/tftpto*tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 /home/jball/FPGA/litex-buildenv/build/tftpd Obviously changing for the relevant path. Thanks and looking forward to the session. Cheers Jason. On Fri, Jan 5, 2018 at 10:44 AM, Duncan Roe wrote: > Hi Tim, > > On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) > wrote: > > I've shared an item with you: > > > > FPGA Miniconf Set Up Instructions > > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63 > Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > > > It's not an attachment ??? it's stored online. To open this item, just > click > > the link above. > > > > Hi! > > > > This is the initial attempt at set up instructions for the LCA2018 FPGA > > Miniconf. Please attempt to follow these instructions and add comments > where > > you encounter issues and we will try to update the instructions with > fixes. > > > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > > > Thanks! > > > > Tim 'mithro' Ansell > > I can't seem to be able to select & paste from this. Any ideas how to fix? > > Cheers ... Duncan. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -- -- Teach your kids Science, or somebody else will :/ jason at ball.net vk2vjb at google.com callsign: vk2vjb -------------- next part -------------- An HTML attachment was scrubbed... URL: From mames at aconex.com Wed Jan 10 14:12:55 2018 From: mames at aconex.com (Matt Ames) Date: Wed, 10 Jan 2018 03:12:55 +0000 Subject: [fpga-miniconf] FPGA Miniconf Set Up Instructions In-Reply-To: References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180104234401.GB3903@dimstar.local.net>, Message-ID: Hi All, I have gotten the pre-work completed, and I get the following prompt after running build-qemu, however, I can't see an obvious way to log out, and when I exit using "Ctrl-C" it appears to kill atftp as well and it doesn't restart - the only way I can get build-qemu to run again is to reboot my machine. It's probably something simple that I have missed - can someone help? Login prompt:- Welcome to Buildroot buildroot login: root Jan 1 00:00:07 login[63]: root login on 'console' # (I press Ctrl-C to exit here, and here is the output) Jan 10 14:09:10 atftpd[2112.139912238200576]: SIGINT received, stopping threads and exiting. Jan 10 14:09:10 atftpd[2112.139912238200576]: tftpd.c: 444: select: Interrupted system call Jan 10 14:09:10 atftpd[2112.139912238200576]: atftpd terminating Jan 10 14:09:10 atftpd[2112.139912238200576]: Load measurements: Jan 10 14:09:10 atftpd[2112.139912238200576]: User: 0.000s Sys: 0.000s Jan 10 14:09:10 atftpd[2112.139912238200576]: Total: 137.215s CPU: 0.262% Jan 10 14:09:10 atftpd[2112.139912238200576]: Time between connections: Jan 10 14:09:10 atftpd[2112.139912238200576]: Min: 0.001s Max: 1.219s Jan 10 14:09:10 atftpd[2112.139912238200576]: Thread stats: Jan 10 14:09:10 atftpd[2112.139912238200576]: simultaneous threads: 1 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of servers: 1 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of aborts: 0 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of errors: 2 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of files sent: 1 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of files received: 0 qemu-system-or32: terminating on signal 2 Jan 10 14:09:10 atftpd[2112.139912238200576]: Main thread exiting ________________________________ From: fpga-miniconf on behalf of Jason Ball Sent: Sunday, 7 January 2018 11:02:54 AM To: fpga-miniconf at lists.lca2018.linux.org.au Subject: Re: [fpga-miniconf] FPGA Miniconf Set Up Instructions Hi Tim, I finally got around to completing the setup and running through all sections. The only note of any import is I found I needed to change the default tftp path so the images could be loaded by qemu. update: /etc/inetd.conf and change: tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 /srv/tftp to tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 /home/jball/FPGA/litex-buildenv/build/tftpd Obviously changing for the relevant path. Thanks and looking forward to the session. Cheers Jason. On Fri, Jan 5, 2018 at 10:44 AM, Duncan Roe > wrote: Hi Tim, On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) wrote: > I've shared an item with you: > > FPGA Miniconf Set Up Instructions > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > It's not an attachment ??? it's stored online. To open this item, just click > the link above. > > Hi! > > This is the initial attempt at set up instructions for the LCA2018 FPGA > Miniconf. Please attempt to follow these instructions and add comments where > you encounter issues and we will try to update the instructions with fixes. > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > Thanks! > > Tim 'mithro' Ansell I can't seem to be able to select & paste from this. Any ideas how to fix? Cheers ... Duncan. -- fpga-miniconf mailing list fpga-miniconf at lists.lca2018.linux.org.au http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf -- -- Teach your kids Science, or somebody else will :/ jason at ball.net vk2vjb at google.com callsign: vk2vjb -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at merlins.org Thu Jan 11 18:11:57 2018 From: marc at merlins.org (Marc MERLIN) Date: Thu, 11 Jan 2018 08:11:57 +0100 Subject: [fpga-miniconf] could not configure /dev/net/tun (tap0): Operation not permitted Message-ID: <20180111071157.ib6ter4wvgwxhqmy@merlins.org> I now got as far as this: + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio -bios build/arty_net_or1k//software/bios/bios.bin -drive if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 qemu-system-or32: -net tap,ifname=tap0,script=no,downscript=no: could not configure /dev/net/tun (tap0): Operation not permitted (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ l /dev/net/tun crw-rw-rw- 1 root root 10, 200 Jan 10 12:15 /dev/net/tun Any idea why it doesn't work, just add sudo to it? Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From me at mith.ro Thu Jan 11 19:39:43 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Thu, 11 Jan 2018 19:39:43 +1100 Subject: [fpga-miniconf] could not configure /dev/net/tun (tap0): Operation not permitted In-Reply-To: <20180111071157.ib6ter4wvgwxhqmy@merlins.org> References: <20180111071157.ib6ter4wvgwxhqmy@merlins.org> Message-ID: Do you have a /dev/net/tap0? I'm guessing you have failed to have the tap0 be created, you can see the bit of the shell script here -> https://github.com/ timvideos/litex-buildenv/blob/master/scripts/build-qemu.sh#L119-L134 Tim 'mithro' Ansell On 11 January 2018 at 18:11, Marc MERLIN wrote: > I now got as far as this: > + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex > -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio > -bios build/arty_net_or1k//software/bios/bios.bin -drive > if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 > -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 > qemu-system-or32: -net tap,ifname=tap0,script=no,downscript=no: could not > configure /dev/net/tun (tap0): Operation not permitted > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ l /dev/net/tun > crw-rw-rw- 1 root root 10, 200 Jan 10 12:15 /dev/net/tun > > Any idea why it doesn't work, just add sudo to it? > > Thanks, > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - > A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking > Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at merlins.org Fri Jan 12 03:36:24 2018 From: marc at merlins.org (Marc MERLIN) Date: Thu, 11 Jan 2018 17:36:24 +0100 Subject: [fpga-miniconf] could not configure /dev/net/tun (tap0): Operation not permitted In-Reply-To: References: <20180111071157.ib6ter4wvgwxhqmy@merlins.org> Message-ID: <20180111163624.h5n6dln2kbd6z7gd@merlins.org> On Thu, Jan 11, 2018 at 07:39:43PM +1100, Tim 'mithro' Ansell wrote: > Do you have a /dev/net/tap0? > > I'm guessing you have failed to have the tap0 be created, you can see the > bit of the shell script here -> https://github.com/ > timvideos/litex-buildenv/blob/master/scripts/build-qemu.sh#L119-L134 I changed this: saruman:~# l /dev/net/tap0 crw-r--r-- 1 root root 10, 200 Jan 10 10:36 /dev/net/tap0 saruman:~# chmod 666 /dev/net/tap0 But still get: + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio -bios build/arty_net_or1k//software/bios/bios.bin -drive if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 qemu-system-or32: -net tap,ifname=tap0,script=no,downscript=no: could not configure /dev/net/tun (tap0): Operation not permitted I guess I'll have to dig deeper into the shell script to see what's going on. > Tim 'mithro' Ansell > > On 11 January 2018 at 18:11, Marc MERLIN wrote: > > > I now got as far as this: > > + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex > > -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio > > -bios build/arty_net_or1k//software/bios/bios.bin -drive > > if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 > > -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 > > qemu-system-or32: -net tap,ifname=tap0,script=no,downscript=no: could not > > configure /dev/net/tun (tap0): Operation not permitted > > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ l /dev/net/tun > > crw-rw-rw- 1 root root 10, 200 Jan 10 12:15 /dev/net/tun > > > > Any idea why it doesn't work, just add sudo to it? > > > > Thanks, > > Marc > > -- > > "A mouse is a device used to point at the xterm you want to type in" - > > A.S.R. > > Microsoft is to operating systems .... > > .... what McDonalds is to gourmet > > cooking > > Home page: http://marc.merlins.org/ | PGP > > 1024R/763BE901 > > -- > > fpga-miniconf mailing list > > fpga-miniconf at lists.lca2018.linux.org.au > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From me at mith.ro Fri Jan 12 13:06:58 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Fri, 12 Jan 2018 13:06:58 +1100 Subject: [fpga-miniconf] could not configure /dev/net/tun (tap0): Operation not permitted In-Reply-To: <20180111163624.h5n6dln2kbd6z7gd@merlins.org> References: <20180111071157.ib6ter4wvgwxhqmy@merlins.org> <20180111163624.h5n6dln2kbd6z7gd@merlins.org> Message-ID: You might want to check for things like SELinux or AppArmor, the operations on the tun/tap interfaces might require extra privileges that are getting blocked? It could also be that chmod isn't enough and you actually need to do the "sudo tunctl -t tap0 -u $(whoami)" operation? There also seems to be rumors on the internet that you need not just rw but execute permission on the tap/tun interfaces? I don't actually know a huge amount about how tun/tap interfaces work, so if anyone else does - please do chime in! :-P There might be some useful information here; * https://en.wikibooks.org/wiki/QEMU/Networking#TAP_interfaces * https://www.kernel.org/doc/Documentation/networking/tuntap.txt * https://wiki.archlinux.org/index.php/QEMU#Tap_networking_with_QEMU Hope that helps! Tim 'mithro' Ansell PS It would be a good if this script was less of a crufty shell script and more of a nice elegant Python script. :-P On 12 January 2018 at 03:36, Marc MERLIN wrote: > On Thu, Jan 11, 2018 at 07:39:43PM +1100, Tim 'mithro' Ansell wrote: > > Do you have a /dev/net/tap0? > > > > I'm guessing you have failed to have the tap0 be created, you can see the > > bit of the shell script here -> https://github.com/ > > timvideos/litex-buildenv/blob/master/scripts/build-qemu.sh#L119-L134 > > I changed this: > saruman:~# l /dev/net/tap0 > crw-r--r-- 1 root root 10, 200 Jan 10 10:36 /dev/net/tap0 > saruman:~# chmod 666 /dev/net/tap0 > > But still get: > + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex > -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio > -bios build/arty_net_or1k//software/bios/bios.bin -drive > if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 > -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 > qemu-system-or32: -net tap,ifname=tap0,script=no,downscript=no: could not > configure /dev/net/tun (tap0): Operation not permitted > > I guess I'll have to dig deeper into the shell script to see what's > going on. > > > Tim 'mithro' Ansell > > > > On 11 January 2018 at 18:11, Marc MERLIN wrote: > > > > > I now got as far as this: > > > + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex > > > -nographic -nodefaults -monitor telnet::10000,server,nowait -serial > stdio > > > -bios build/arty_net_or1k//software/bios/bios.bin -drive > > > if=mtd,format=qcow2,file=build/arty_net_or1k//qemu. > qcow2,serial=n25q128a13 > > > -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 > > > qemu-system-or32: -net tap,ifname=tap0,script=no,downscript=no: could > not > > > configure /dev/net/tun (tap0): Operation not permitted > > > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ l /dev/net/tun > > > crw-rw-rw- 1 root root 10, 200 Jan 10 12:15 /dev/net/tun > > > > > > Any idea why it doesn't work, just add sudo to it? > > > > > > Thanks, > > > Marc > > > -- > > > "A mouse is a device used to point at the xterm you want to type in" - > > > A.S.R. > > > Microsoft is to operating systems .... > > > .... what McDonalds is to gourmet > > > cooking > > > Home page: http://marc.merlins.org/ | PGP > > > 1024R/763BE901 > > > -- > > > fpga-miniconf mailing list > > > fpga-miniconf at lists.lca2018.linux.org.au > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > > > > -- > "A mouse is a device used to point at the xterm you want to type in" - > A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking > Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at mith.ro Fri Jan 12 14:11:05 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Fri, 12 Jan 2018 14:11:05 +1100 Subject: [fpga-miniconf] FPGA Miniconf Set Up Instructions In-Reply-To: References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180104234401.GB3903@dimstar.local.net> Message-ID: Hi Matt, There are "make tftpd_start" and "make tftpd_stop" commands which can be used to manually start / stop the tftp server. Tim 'mithro' Ansell On 10 January 2018 at 14:12, Matt Ames wrote: > Hi All, > > > I have gotten the pre-work completed, and I get the following prompt after > running build-qemu, however, I can't see an obvious way to log out, and > when I exit using "Ctrl-C" it appears to kill atftp as well and it doesn't > restart - the only way I can get build-qemu to run again is to reboot my > machine. It's probably something simple that I have missed - can someone > help? > > > Login prompt:- > > Welcome to Buildroot > buildroot login: root > Jan 1 00:00:07 login[63]: root login on 'console' > # > > (I press Ctrl-C to exit here, and here is the output) > > > Jan 10 14:09:10 atftpd[2112.139912238200576]: SIGINT > received, stopping threads and exiting. > Jan 10 14:09:10 atftpd[2112.139912238200576]: tftpd.c: > 444: select: Interrupted system call > Jan 10 14:09:10 atftpd[2112.139912238200576]: atftpd > terminating > Jan 10 14:09:10 atftpd[2112.139912238200576]: Load > measurements: > Jan 10 14:09:10 atftpd[2112.139912238200576]: User: > 0.000s Sys: 0.000s > Jan 10 14:09:10 atftpd[2112.139912238200576]: Total: > 137.215s CPU: 0.262% > Jan 10 14:09:10 atftpd[2112.139912238200576]: Time > between connections: > Jan 10 14:09:10 atftpd[2112.139912238200576]: Min: > 0.001s Max: 1.219s > Jan 10 14:09:10 atftpd[2112.139912238200576]: Thread > stats: > Jan 10 14:09:10 atftpd[2112.139912238200576]: > simultaneous threads: 1 > Jan 10 14:09:10 atftpd[2112.139912238200576]: number > of servers: 1 > Jan 10 14:09:10 atftpd[2112.139912238200576]: number > of aborts: 0 > Jan 10 14:09:10 atftpd[2112.139912238200576]: number > of errors: 2 > Jan 10 14:09:10 atftpd[2112.139912238200576]: number > of files sent: 1 > Jan 10 14:09:10 atftpd[2112.139912238200576]: number > of files received: 0 > qemu-system-or32: terminating on signal 2 > Jan 10 14:09:10 atftpd[2112.139912238200576]: Main thread > exiting > > > ------------------------------ > *From:* fpga-miniconf > on behalf of Jason Ball > *Sent:* Sunday, 7 January 2018 11:02:54 AM > *To:* fpga-miniconf at lists.lca2018.linux.org.au > *Subject:* Re: [fpga-miniconf] FPGA Miniconf Set Up Instructions > > Hi Tim, > > I finally got around to completing the setup and running through all > sections. > > The only note of any import is I found I needed to change the default tftp > path so the images could be loaded by qemu. > > update: /etc/inetd.conf and change: > > tftp dgram udp wait nobody /usr/sbin/tcpd > /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 > --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 > > > > */srv/tftp to *tftp dgram udp wait nobody /usr/sbin/tcpd > /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 > --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 > /home/jball/FPGA/litex-buildenv/build/tftpd > > Obviously changing for the relevant path. > > Thanks and looking forward to the session. > > Cheers > Jason. > > > > On Fri, Jan 5, 2018 at 10:44 AM, Duncan Roe > wrote: > > Hi Tim, > > On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) > wrote: > > I've shared an item with you: > > > > FPGA Miniconf Set Up Instructions > > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1Wcrvm > zPA63Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > > > It's not an attachment ??? it's stored online. To open this item, just > click > > the link above. > > > > Hi! > > > > This is the initial attempt at set up instructions for the LCA2018 FPGA > > Miniconf. Please attempt to follow these instructions and add comments > where > > you encounter issues and we will try to update the instructions with > fixes. > > > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > > > Thanks! > > > > Tim 'mithro' Ansell > > I can't seem to be able to select & paste from this. Any ideas how to fix? > > Cheers ... Duncan. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > > > > -- > -- > Teach your kids Science, or somebody else will :/ > > jason at ball.net > vk2vjb at google.com > callsign: vk2vjb > > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mames at aconex.com Fri Jan 12 16:04:05 2018 From: mames at aconex.com (Matt Ames) Date: Fri, 12 Jan 2018 05:04:05 +0000 Subject: [fpga-miniconf] FPGA Miniconf Set Up Instructions In-Reply-To: References: <31c97c00-9b08-47e0-bbbb-af8a95595f7b@docs-share.google.com> <001a114701ccc5ba120561ea6ee5@google.com> <20180104234401.GB3903@dimstar.local.net> , Message-ID: Perfect, that did the trick, thanks! ________________________________ From: Tim 'mithro' Ansell Sent: Friday, 12 January 2018 2:11:05 PM To: Matt Ames Cc: fpga-miniconf at lists.lca2018.linux.org.au; jason at ball.net Subject: Re: [fpga-miniconf] FPGA Miniconf Set Up Instructions Hi Matt, There are "make tftpd_start" and "make tftpd_stop" commands which can be used to manually start / stop the tftp server. Tim 'mithro' Ansell On 10 January 2018 at 14:12, Matt Ames > wrote: Hi All, I have gotten the pre-work completed, and I get the following prompt after running build-qemu, however, I can't see an obvious way to log out, and when I exit using "Ctrl-C" it appears to kill atftp as well and it doesn't restart - the only way I can get build-qemu to run again is to reboot my machine. It's probably something simple that I have missed - can someone help? Login prompt:- Welcome to Buildroot buildroot login: root Jan 1 00:00:07 login[63]: root login on 'console' # (I press Ctrl-C to exit here, and here is the output) Jan 10 14:09:10 atftpd[2112.139912238200576]: SIGINT received, stopping threads and exiting. Jan 10 14:09:10 atftpd[2112.139912238200576]: tftpd.c: 444: select: Interrupted system call Jan 10 14:09:10 atftpd[2112.139912238200576]: atftpd terminating Jan 10 14:09:10 atftpd[2112.139912238200576]: Load measurements: Jan 10 14:09:10 atftpd[2112.139912238200576]: User: 0.000s Sys: 0.000s Jan 10 14:09:10 atftpd[2112.139912238200576]: Total: 137.215s CPU: 0.262% Jan 10 14:09:10 atftpd[2112.139912238200576]: Time between connections: Jan 10 14:09:10 atftpd[2112.139912238200576]: Min: 0.001s Max: 1.219s Jan 10 14:09:10 atftpd[2112.139912238200576]: Thread stats: Jan 10 14:09:10 atftpd[2112.139912238200576]: simultaneous threads: 1 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of servers: 1 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of aborts: 0 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of errors: 2 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of files sent: 1 Jan 10 14:09:10 atftpd[2112.139912238200576]: number of files received: 0 qemu-system-or32: terminating on signal 2 Jan 10 14:09:10 atftpd[2112.139912238200576]: Main thread exiting ________________________________ From: fpga-miniconf > on behalf of Jason Ball > Sent: Sunday, 7 January 2018 11:02:54 AM To: fpga-miniconf at lists.lca2018.linux.org.au Subject: Re: [fpga-miniconf] FPGA Miniconf Set Up Instructions Hi Tim, I finally got around to completing the setup and running through all sections. The only note of any import is I found I needed to change the default tftp path so the images could be loaded by qemu. update: /etc/inetd.conf and change: tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 /srv/tftp to tftp dgram udp wait nobody /usr/sbin/tcpd /usr/sbin/in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=7 /home/jball/FPGA/litex-buildenv/build/tftpd Obviously changing for the relevant path. Thanks and looking forward to the session. Cheers Jason. On Fri, Jan 5, 2018 at 10:44 AM, Duncan Roe > wrote: Hi Tim, On Thu, Jan 04, 2018 at 02:53:12AM +0000, Tim Ansell (via Google Docs) wrote: > I've shared an item with you: > > FPGA Miniconf Set Up Instructions > https://docs.google.com/document/d/1b2rBju9Fxjlcv6y3Ib1WcrvmzPA63Pe-pnBaziJXZNY/edit?usp=sharing&ts=5a4d9718 > > It's not an attachment ??? it's stored online. To open this item, just click > the link above. > > Hi! > > This is the initial attempt at set up instructions for the LCA2018 FPGA > Miniconf. Please attempt to follow these instructions and add comments where > you encounter issues and we will try to update the instructions with fixes. > > Looking forward to seeing everyone at an awesome Linux.conf.au 2018! > > Thanks! > > Tim 'mithro' Ansell I can't seem to be able to select & paste from this. Any ideas how to fix? Cheers ... Duncan. -- fpga-miniconf mailing list fpga-miniconf at lists.lca2018.linux.org.au http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf -- -- Teach your kids Science, or somebody else will :/ jason at ball.net vk2vjb at google.com callsign: vk2vjb -- fpga-miniconf mailing list fpga-miniconf at lists.lca2018.linux.org.au http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at merlins.org Fri Jan 12 17:25:16 2018 From: marc at merlins.org (Marc MERLIN) Date: Fri, 12 Jan 2018 07:25:16 +0100 Subject: [fpga-miniconf] could not configure /dev/net/tun (tap0): Operation not permitted In-Reply-To: References: <20180111071157.ib6ter4wvgwxhqmy@merlins.org> <20180111163624.h5n6dln2kbd6z7gd@merlins.org> Message-ID: <20180112062516.bthch5nb6mhrj3cu@merlins.org> On Fri, Jan 12, 2018 at 01:06:58PM +1100, Tim 'mithro' Ansell wrote: > You might want to check for things like SELinux or AppArmor, the operations > on the tun/tap interfaces might require extra privileges that are getting > blocked? > > It could also be that chmod isn't enough and you actually need to do the > "sudo tunctl -t tap0 -u $(whoami)" operation? There also seems to be rumors > on the internet that you need not just rw but execute permission on the > tap/tun interfaces? Well, that was the issue, tunctl fixed it. Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From marc at merlins.org Tue Jan 16 00:51:10 2018 From: marc at merlins.org (Marc MERLIN) Date: Mon, 15 Jan 2018 14:51:10 +0100 Subject: [fpga-miniconf] Unable to download boot.bin over TFTP Message-ID: <20180115135110.3zmhryct5g6s2imz@merlins.org> Seems that (LX P=arty C=or1k) $ ./scripts/build-qemu.sh does not copy boot.bin to /srv/tftp/initrd.bin and then tftp fails? mkdir -p build/tftpd/ cp build/arty_net_or1k//software/firmware/firmware.bin build/tftpd//boot.bin + EXTRA_ARGS+=("-gdb tcp::10001") ++ grep spiflash_model platforms/arty.py ++ sed '-es/[^"]*"//' '-es/".*$//' + SPIFLASH_MODEL=n25q128a13 + echo n25q128a13 n25q128a13 + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio -bios build/arty_net_or1k//software/bios/bios.bin -drive if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 bitbang_ssi: init(cpol:0, cpha:0, size:8) Using spiflash type n25q128a13 : m25p80_realize: Binding to IF_MTD drive Resetting PC to: 0x0 : reset_memory: Reset done. LiteX SoC BIOS (or1k) (c) Copyright 2012-2017 Enjoy-Digital (c) Copyright 2007-2017 M-Labs Limited Built Jan 7 2018 20:53:45 BIOS CRC passed (3f31133f) Timer with delta zero, disabling Timer with delta zero, disabling Timer with delta zero, disabling Initializing SDRAM... Read delays: 1:32-33 0:32-33 completed Memtest OK Booting from serial... Press Q or ESC to abort boot completely. sL5DdSMmkekro Timer with delta zero, disabling Timeout Booting from network... Local IP : 192.168.100.50 Remote IP: 192.168.100.100 Unable to download boot.bin over TFTP Network boot failed No boot medium found BIOS> It seems however that said server isn't configured right? [pid 22066] sendto(3, "<29>Jan 15 14:35:48 atftpd[17187"..., 74, MSG_NOSIGNAL, NULL, 0) = 74 [pid 22066] open("/srv/tftp/boot.bin", O_RDONLY) = -1 ENOENT (No such file or directory) [pid 22066] sendto(4, "\0\5\0\1File not found\0", 19, 0, {sa_family=AF_INET, sin_port=htons(7642), sin_addr=inet_addr("192.168.100.50")}, 128) = 19 /srv/tftp was empty. Was I supposed to symlink it to my tree? Ok, I did this manually: (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ sudo cp build/tftpd/boot.bin /srv/tftp/boot.bin This seems to help, now I finally have: Reading value 0000bc00 fr MDIO PHY 00000000 REG 00000011 MDIO mode: 1000Mbps / link: up uIP init done with ip 192.168.100.50 Etherbone listening on port 1234 Telnet listening on port 23 H2U 00:00:00> H2U 00:00:24> H2U 00:00:24> I'm better now, but what's the correct fix? Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From me at mith.ro Tue Jan 16 13:49:53 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Tue, 16 Jan 2018 13:49:53 +1100 Subject: [fpga-miniconf] Unable to download boot.bin over TFTP In-Reply-To: <20180115135110.3zmhryct5g6s2imz@merlins.org> References: <20180115135110.3zmhryct5g6s2imz@merlins.org> Message-ID: Hi Marc! There are a couple of options here; (a) Use an existing tftp server and set TFTP_DIR environment variable to the root of the server. "make tftp" will then copy the current firmware you are operating on into the tftp serving directory. (b) Let litex-buildenv start a tftp server for you. You can do this with "make tftpd_start" and "make tftpd_stop". This has the advantage that if you have aftpd you get debugging output on the console every time a tftp transfer is started. Many people have found that installing tftpd ends up with it configured to load automatically via inetd or xinetd which prevents the litex-buildenv from starting up it's own tftp server. A whole bunch of people have run into various issues with getting the tftp server going, so I've opened an issue here -> https://github.com/timvideos/litex-buildenv/issues/3 to look at doing a better job of detecting and verifying a working tftp set up. It would also be good if we could run the tftp server on an unprivileged port, so I've logged https://github.com/timvideos/litex-buildenv/issues/6 for that. Of course being an open source project, we would love help fixing those! :-) Tim 'mithro' Ansell On 16 January 2018 at 00:51, Marc MERLIN wrote: > Seems that (LX P=arty C=or1k) $ ./scripts/build-qemu.sh does not copy > boot.bin to /srv/tftp/initrd.bin and then tftp fails? > > mkdir -p build/tftpd/ > cp build/arty_net_or1k//software/firmware/firmware.bin > build/tftpd//boot.bin > + EXTRA_ARGS+=("-gdb tcp::10001") > ++ grep spiflash_model platforms/arty.py > ++ sed '-es/[^"]*"//' '-es/".*$//' > + SPIFLASH_MODEL=n25q128a13 > + echo n25q128a13 > n25q128a13 > + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex > -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio > -bios build/arty_net_or1k//software/bios/bios.bin -drive > if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 > -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 > bitbang_ssi: init(cpol:0, cpha:0, size:8) > Using spiflash type n25q128a13 > : m25p80_realize: Binding to IF_MTD drive > Resetting PC to: 0x0 > : reset_memory: Reset done. > > LiteX SoC BIOS (or1k) > (c) Copyright 2012-2017 Enjoy-Digital > (c) Copyright 2007-2017 M-Labs Limited > Built Jan 7 2018 20:53:45 > > BIOS CRC passed (3f31133f) > Timer with delta zero, disabling > Timer with delta zero, disabling > Timer with delta zero, disabling > Initializing SDRAM... > Read delays: 1:32-33 0:32-33 completed > Memtest OK > Booting from serial... > Press Q or ESC to abort boot completely. > sL5DdSMmkekro > Timer with delta zero, disabling > Timeout > Booting from network... > Local IP : 192.168.100.50 > Remote IP: 192.168.100.100 > Unable to download boot.bin over TFTP > Network boot failed > No boot medium found > BIOS> > > > It seems however that said server isn't configured right? > [pid 22066] sendto(3, "<29>Jan 15 14:35:48 atftpd[17187"..., 74, > MSG_NOSIGNAL, NULL, 0) = 74 > [pid 22066] open("/srv/tftp/boot.bin", O_RDONLY) = -1 ENOENT (No such file > or directory) > [pid 22066] sendto(4, "\0\5\0\1File not found\0", 19, 0, > {sa_family=AF_INET, sin_port=htons(7642), sin_addr=inet_addr("192.168.100.50")}, > 128) = 19 > > /srv/tftp was empty. Was I supposed to symlink it to my tree? > > Ok, I did this manually: > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ sudo cp > build/tftpd/boot.bin /srv/tftp/boot.bin > > This seems to help, now I finally have: > Reading value 0000bc00 fr MDIO PHY 00000000 REG 00000011 > MDIO mode: 1000Mbps / link: up > uIP init done with ip 192.168.100.50 > Etherbone listening on port 1234 > Telnet listening on port 23 > H2U 00:00:00> > H2U 00:00:24> > H2U 00:00:24> > > I'm better now, but what's the correct fix? > > Thanks, > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - > A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking > Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at mith.ro Tue Jan 16 19:50:51 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Tue, 16 Jan 2018 19:50:51 +1100 Subject: [fpga-miniconf] Reminder: FPGA Miniconf prework _must_ be done *before* the Miniconf starts! Message-ID: Hello everyone, With just under a week until we do some epic hacking on FPGAs and Linux, I want to remind everyone that they **must** complete the prework **before** the FPGA Miniconf starts. If you haven't completed the prework, you will be **unable** to attend FPGA Miniconf. The prework is found in the "FPGA Miniconf Set Up Instructions" doc at http://j.mp/pre-fpga-lca2018 You must complete up to the paragraph which says the following in bright red; > The instructions from here can only be done > after you receive hardware. > You can stop here if completing the prework. We have been improving the doc and repository as people run into problems, so if you have gotten stuck, please check back and see if a solution is now available. It seems getting a working tftp setup is causing people the most problems. Please check this section carefully. See you all soon! Tim 'mithro' Ansell -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt-lca2018 at handcraftedcomputers.com.au Tue Jan 16 21:14:08 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Tue, 16 Jan 2018 20:44:08 +1030 Subject: [fpga-miniconf] =?utf-8?q?Reminder=3A_FPGA_Miniconf_prework_=5Fm?= =?utf-8?q?ust=5F_be_done_*before*_the_Miniconf_starts!?= In-Reply-To: References: Message-ID: On Tue, 16 Jan 2018 19:50:51 +1100, Tim 'mithro' Ansell wrote: > With just under a week until we do some epic hacking on FPGAs and > Linux, I > want to remind everyone that they **must** complete the prework > **before** > the FPGA Miniconf starts. Given the size of some of the downloads encountered so far, is there anything we can precache before the mini-conf starts? -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From me at mith.ro Tue Jan 16 21:18:16 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Tue, 16 Jan 2018 21:18:16 +1100 Subject: [fpga-miniconf] Reminder: FPGA Miniconf prework _must_ be done *before* the Miniconf starts! In-Reply-To: References: Message-ID: We won't be downloading anything large during the miniconf, all the large downloads are done as part of the prework (one of the resources it has to be done before hand!). Tim 'mithro' Ansell On 16 January 2018 at 21:14, Daryl Tester < dt-lca2018 at handcraftedcomputers.com.au> wrote: > On Tue, 16 Jan 2018 19:50:51 +1100, Tim 'mithro' Ansell wrote: > > With just under a week until we do some epic hacking on FPGAs and Linux, I >> want to remind everyone that they **must** complete the prework **before** >> the FPGA Miniconf starts. >> > > Given the size of some of the downloads encountered so far, is there > anything > we can precache before the mini-conf starts? > > > -- > Regards, > Daryl Tester > Handcrafted Computers Pty. Ltd. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt-lca2018 at handcraftedcomputers.com.au Tue Jan 16 22:42:36 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Tue, 16 Jan 2018 22:12:36 +1030 Subject: [fpga-miniconf] Reminder: FPGA Miniconf prework _must_ be done *before* the Miniconf starts! In-Reply-To: References: Message-ID: Cool bananas! Cheers. On 16/01/18 20:48, Tim 'mithro' Ansell wrote: > We won't be downloading anything large during the miniconf, all the large downloads are done as part of the prework (one of the resources it has to be done before hand!). > > Tim 'mithro' Ansell > > On 16 January 2018 at 21:14, Daryl Tester > wrote: > > On Tue, 16 Jan 2018 19:50:51 +1100, Tim 'mithro' Ansell wrote: > > With just under a week until we do some epic hacking on FPGAs and Linux, I > want to remind everyone that they **must** complete the prework **before** > the FPGA Miniconf starts. > > > Given the size of some of the downloads encountered so far, is there anything > we can precache before the mini-conf starts? > > > -- > Regards, > ? Daryl Tester > ? Handcrafted Computers Pty. Ltd. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From marc at merlins.org Wed Jan 17 02:33:55 2018 From: marc at merlins.org (Marc MERLIN) Date: Tue, 16 Jan 2018 16:33:55 +0100 Subject: [fpga-miniconf] Reminder: FPGA Miniconf prework _must_ be done *before* the Miniconf starts! In-Reply-To: References: Message-ID: <20180116153355.6gnacdomtogah3oz@merlins.org> On Tue, Jan 16, 2018 at 07:50:51PM +1100, Tim 'mithro' Ansell wrote: > Hello everyone, > > With just under a week until we do some epic hacking on FPGAs and Linux, I > want to remind everyone that they **must** complete the prework **before** > the FPGA Miniconf starts. Since I did most of it, don't wait until the last day because some steps could go wrong and then you'll need help to proceed further. Even if everything works great, expect maybe 2 to 6H of clock time (that includes the very big download and working around some issues) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From marc at merlins.org Wed Jan 17 02:58:36 2018 From: marc at merlins.org (Marc MERLIN) Date: Tue, 16 Jan 2018 16:58:36 +0100 Subject: [fpga-miniconf] Unable to download boot.bin over TFTP In-Reply-To: References: <20180115135110.3zmhryct5g6s2imz@merlins.org> Message-ID: <20180116155836.rq6dwl7qrpwjcdzv@merlins.org> On Tue, Jan 16, 2018 at 01:49:53PM +1100, Tim 'mithro' Ansell wrote: > Hi Marc! > > There are a couple of options here; > > (a) Use an existing tftp server and set TFTP_DIR environment variable to > the root of the server. "make tftp" will then copy the current firmware you > are operating on into the tftp serving directory. > (b) Let litex-buildenv start a tftp server for you. You can do this with > "make tftpd_start" and "make tftpd_stop". This has the advantage that if > you have aftpd you get debugging output on the console every time a tftp > transfer is started. > > Many people have found that installing tftpd ends up with it configured to > load automatically via inetd or xinetd which prevents the litex-buildenv > from starting up it's own tftp server. Right, (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ make tftpd_start works too, but it was not mentioned anywhere in the doc around build-qemu.sh I've added a suggestion line to add it, see under "net booting firmware in qemu" See also my Error #2 suggestion in the doc Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From dt-lca2018 at handcraftedcomputers.com.au Wed Jan 17 09:07:37 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Wed, 17 Jan 2018 08:37:37 +1030 Subject: [fpga-miniconf] Unable to download boot.bin over TFTP In-Reply-To: <20180116155836.rq6dwl7qrpwjcdzv@merlins.org> References: <20180115135110.3zmhryct5g6s2imz@merlins.org> <20180116155836.rq6dwl7qrpwjcdzv@merlins.org> Message-ID: <90f5168e401e024bc77a61d486151513@webbmaul.handcraftedcomputers.com.au> On Tue, 16 Jan 2018 16:58:36 +0100, Marc MERLIN wrote: > Right, > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ make > tftpd_start > works too, but it was not mentioned anywhere in the doc around > build-qemu.sh Note that it's run as part of (I think) build-qemu.sh. It's only a problem when the original tftpd is still running (which bit me as well, because installing it also configures it for running). Cheers. -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From marc at merlins.org Wed Jan 17 23:11:47 2018 From: marc at merlins.org (Marc MERLIN) Date: Wed, 17 Jan 2018 13:11:47 +0100 Subject: [fpga-miniconf] Unable to download boot.bin over TFTP In-Reply-To: <90f5168e401e024bc77a61d486151513@webbmaul.handcraftedcomputers.com.au> References: <20180115135110.3zmhryct5g6s2imz@merlins.org> <20180116155836.rq6dwl7qrpwjcdzv@merlins.org> <90f5168e401e024bc77a61d486151513@webbmaul.handcraftedcomputers.com.au> Message-ID: <20180117121147.fgiascxhhn7zajf5@merlins.org> On Wed, Jan 17, 2018 at 08:37:37AM +1030, Daryl Tester wrote: > On Tue, 16 Jan 2018 16:58:36 +0100, Marc MERLIN wrote: > > > Right, > > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ make tftpd_start > > works too, but it was not mentioned anywhere in the doc around > > build-qemu.sh > > Note that it's run as part of (I think) build-qemu.sh. It's only a problem > when the original tftpd is still running (which bit me as well, because > installing it also configures it for running). I was all confused because it was my understanding too, but I just tried again, and tftp is not running, I really checked (and it's not in inetd anymore). (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ ./scripts/build-qemu.sh just fails due to lack of tftpd. If I start it with (LX P=arty C=or1k) $ make tftpd_start then everything works. Tim nicely included my suggestion to add some hints about tftp Looks like I made a couple of mistaken suggestions on the doc, sorry for those and thanks for rejecting them :) Thanks Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From me at mith.ro Thu Jan 18 16:44:08 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Thu, 18 Jan 2018 16:44:08 +1100 Subject: [fpga-miniconf] Timetable for FPGA Miniconf - Please read! Message-ID: Hello everyone, Due to the amount of content to get through at the FPGA Miniconf, we will be running on a modified schedule (including changes to lunch + breaks). You should also expect to be at the FPGA Miniconf for the whole day and to have no time to do anything else! Unlike the rest of the conference, lunch *will* be provided for FPGA Miniconf attendees. There will be a presentation during lunch. We also plan to have a self funded social dinner on the evening of the FPGA Miniconf. 9:00 am -> 10:10 am -- Linux.conf.au Keynote 10:10 am -> 10:15 am -- Move from Keynote venue to FPGA Miniconf venue 10:15 am -- Miniconf Start! (No time for morning tea) 10:15 am -> 5:25 pm -- FPGA Miniconf (lunch provided) 5:25 pm -- Miniconf Finished 5:25 pm -> 7:30 pm -- Extra Hacking time 7:30 pm -> 9:30 pm -- Social Dinner for FPGA hackers If you have any questions, please respond to this email! Tim 'mithro' Ansell -------------- next part -------------- An HTML attachment was scrubbed... URL: From mithro at mithis.com Sun Jan 21 16:32:57 2018 From: mithro at mithis.com (Tim Ansell) Date: Sun, 21 Jan 2018 16:32:57 +1100 Subject: [fpga-miniconf] Unable to download boot.bin over TFTP In-Reply-To: <20180117121147.fgiascxhhn7zajf5@merlins.org> References: <20180115135110.3zmhryct5g6s2imz@merlins.org> <20180116155836.rq6dwl7qrpwjcdzv@merlins.org> <90f5168e401e024bc77a61d486151513@webbmaul.handcraftedcomputers.com.au> <20180117121147.fgiascxhhn7zajf5@merlins.org> Message-ID: I have improved the build-qemu script to do the tap set up and configuration even if things are in partially configured state. Tim 'mithro' Ansell On 17 Jan. 2018 11:12 pm, "Marc MERLIN" wrote: > On Wed, Jan 17, 2018 at 08:37:37AM +1030, Daryl Tester wrote: > > On Tue, 16 Jan 2018 16:58:36 +0100, Marc MERLIN wrote: > > > > > Right, > > > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ make tftpd_start > > > works too, but it was not mentioned anywhere in the doc around > > > build-qemu.sh > > > > Note that it's run as part of (I think) build-qemu.sh. It's only a > problem > > when the original tftpd is still running (which bit me as well, because > > installing it also configures it for running). > > I was all confused because it was my understanding too, but I just tried > again, and tftp is not running, I really checked (and it's not in > inetd anymore). > > (LX P=arty C=or1k) saruman:~/src/fpga/litex-buildenv$ > ./scripts/build-qemu.sh > just fails due to lack of tftpd. > If I start it with (LX P=arty C=or1k) $ make tftpd_start > then everything works. > > Tim nicely included my suggestion to add some hints about tftp > > Looks like I made a couple of mistaken suggestions on the doc, sorry for > those and thanks for rejecting them :) > > Thanks > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - > A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking > Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at mith.ro Sun Jan 21 19:09:04 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Sun, 21 Jan 2018 19:09:04 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... Message-ID: Hello everyone, With just over 24 hours until the FPGA Miniconf, this is the final reminder that everyone **must** complete the prework at http://j.mp/pre-fpga-lca2018 You must complete up to the paragraph which says the following in bright red; > The instructions from here can only be done after you receive hardware. > You can stop here if completing the prework. If you have not completed the prework you will not be able to attend -- that includes observing or anything similar. If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers will be available to help. They should be available during morning tea, lunch and afternoon tea somewhere near the Tomu test station. Hopefully they will be able to solve any issues you are having. There will also be an opportunity to pick up the hardware kits during lunch at the same location. This will allow you to get a head start on setup we need to do at the start of the Miniconf. It would be a good for everyone to update their litex-buildenv sometime Monday evening -- there have been a large number of updates since the last email was sent out. This can be done by doing the following and then following the prework instructions for testing QEmu / Linux. cd litex-buildenv git pull export CPU=or1k PLATFORM=arty TARGET=net ./scripts/download-env.sh source ./scripts/enter-env.sh Depending on internet speeds, updating should only take 10-15 minutes. People are also reminded that the FPGA Miniconf is on Tuesday, 23 January 2018 and will be starting at 10:15AM. This is right after the Matthew Todd's keynote talk. Please make sure you make a beeline from the keynote venue to Large POD Room CB11.04.400 when the keynote finishes. Please see the schedule email for the full details. Look forward to seeing everyone on Tuesday! Tim 'mithro' Ansell -------------- next part -------------- An HTML attachment was scrubbed... URL: From ballmeister at gmail.com Sun Jan 21 19:13:17 2018 From: ballmeister at gmail.com (Jason Ball) Date: Sun, 21 Jan 2018 19:13:17 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: Other than registering tomorrow morning i won't be on site to pickup the kit for Tuesday as i will need to go to work. Is there as I chance we can work around this? On 21 Jan 2018 7:09 PM, "Tim 'mithro' Ansell" wrote: > Hello everyone, > > With just over 24 hours until the FPGA Miniconf, this is the final > reminder that everyone **must** complete the prework at > http://j.mp/pre-fpga-lca2018 > > You must complete up to the paragraph which says the following in bright > red; > >> The instructions from here can only be done after you receive hardware. >> You can stop here if completing the prework. > > > If you have not completed the prework you will not be able to attend -- > that includes observing or anything similar. > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers will be > available to help. They should be available during morning tea, lunch and > afternoon tea somewhere near the Tomu test station. Hopefully they will be > able to solve any issues you are having. > > There will also be an opportunity to pick up the hardware kits during > lunch at the same location. This will allow you to get a head start on > setup we need to do at the start of the Miniconf. > > It would be a good for everyone to update their litex-buildenv sometime > Monday evening -- there have been a large number of updates since the last > email was sent out. This can be done by doing the following and then > following the prework instructions for testing QEmu / Linux. > > > cd litex-buildenv > git pull > export CPU=or1k PLATFORM=arty TARGET=net > ./scripts/download-env.sh > source ./scripts/enter-env.sh > > > Depending on internet speeds, updating should only take 10-15 minutes. > > People are also reminded that the FPGA Miniconf is on Tuesday, 23 January > 2018 and will be starting at 10:15AM. This is right after the Matthew > Todd's keynote talk. Please make sure you make a beeline from the keynote > venue to Large POD Room CB11.04.400 when the keynote finishes. Please see > the schedule email for the full details. > > Look forward to seeing everyone on Tuesday! > > Tim 'mithro' Ansell > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at mith.ro Sun Jan 21 19:16:49 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Sun, 21 Jan 2018 19:16:49 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: Sorry for the confusion. The kits will be *available* on Monday if you want to get a head start. It is fine to get your kit on Tuesday morning at the start of the Miniconf. Tim 'mithro' Ansell On 21 January 2018 at 19:13, Jason Ball wrote: > Other than registering tomorrow morning i won't be on site to pickup the > kit for Tuesday as i will need to go to work. > > Is there as I chance we can work around this? > > On 21 Jan 2018 7:09 PM, "Tim 'mithro' Ansell" wrote: > >> Hello everyone, >> >> With just over 24 hours until the FPGA Miniconf, this is the final >> reminder that everyone **must** complete the prework at >> http://j.mp/pre-fpga-lca2018 >> >> You must complete up to the paragraph which says the following in bright >> red; >> >>> The instructions from here can only be done after you receive hardware. >>> You can stop here if completing the prework. >> >> >> If you have not completed the prework you will not be able to attend -- >> that includes observing or anything similar. >> >> If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers will be >> available to help. They should be available during morning tea, lunch and >> afternoon tea somewhere near the Tomu test station. Hopefully they will be >> able to solve any issues you are having. >> >> There will also be an opportunity to pick up the hardware kits during >> lunch at the same location. This will allow you to get a head start on >> setup we need to do at the start of the Miniconf. >> >> It would be a good for everyone to update their litex-buildenv sometime >> Monday evening -- there have been a large number of updates since the last >> email was sent out. This can be done by doing the following and then >> following the prework instructions for testing QEmu / Linux. >> >> >> cd litex-buildenv >> git pull >> export CPU=or1k PLATFORM=arty TARGET=net >> ./scripts/download-env.sh >> source ./scripts/enter-env.sh >> >> >> Depending on internet speeds, updating should only take 10-15 minutes. >> >> People are also reminded that the FPGA Miniconf is on Tuesday, 23 January >> 2018 and will be starting at 10:15AM. This is right after the Matthew >> Todd's keynote talk. Please make sure you make a beeline from the keynote >> venue to Large POD Room CB11.04.400 when the keynote finishes. Please see >> the schedule email for the full details. >> >> Look forward to seeing everyone on Tuesday! >> >> Tim 'mithro' Ansell >> >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jason at ball.net Sun Jan 21 19:17:43 2018 From: jason at ball.net (Jason Ball) Date: Sun, 21 Jan 2018 19:17:43 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: Thank you. On 21 Jan 2018 7:17 PM, "Tim 'mithro' Ansell" wrote: > Sorry for the confusion. The kits will be *available* on Monday if you > want to get a head start. It is fine to get your kit on Tuesday morning at > the start of the Miniconf. > > Tim 'mithro' Ansell > > On 21 January 2018 at 19:13, Jason Ball wrote: > >> Other than registering tomorrow morning i won't be on site to pickup the >> kit for Tuesday as i will need to go to work. >> >> Is there as I chance we can work around this? >> >> On 21 Jan 2018 7:09 PM, "Tim 'mithro' Ansell" wrote: >> >>> Hello everyone, >>> >>> With just over 24 hours until the FPGA Miniconf, this is the final >>> reminder that everyone **must** complete the prework at >>> http://j.mp/pre-fpga-lca2018 >>> >>> You must complete up to the paragraph which says the following in bright >>> red; >>> >>>> The instructions from here can only be done after you receive hardware. >>>> You can stop here if completing the prework. >>> >>> >>> If you have not completed the prework you will not be able to attend -- >>> that includes observing or anything similar. >>> >>> If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers will be >>> available to help. They should be available during morning tea, lunch and >>> afternoon tea somewhere near the Tomu test station. Hopefully they will be >>> able to solve any issues you are having. >>> >>> There will also be an opportunity to pick up the hardware kits during >>> lunch at the same location. This will allow you to get a head start on >>> setup we need to do at the start of the Miniconf. >>> >>> It would be a good for everyone to update their litex-buildenv sometime >>> Monday evening -- there have been a large number of updates since the last >>> email was sent out. This can be done by doing the following and then >>> following the prework instructions for testing QEmu / Linux. >>> >>> >>> cd litex-buildenv >>> git pull >>> export CPU=or1k PLATFORM=arty TARGET=net >>> ./scripts/download-env.sh >>> source ./scripts/enter-env.sh >>> >>> >>> Depending on internet speeds, updating should only take 10-15 minutes. >>> >>> People are also reminded that the FPGA Miniconf is on Tuesday, 23 >>> January 2018 and will be starting at 10:15AM. This is right after the >>> Matthew Todd's keynote talk. Please make sure you make a beeline from the >>> keynote venue to Large POD Room CB11.04.400 when the keynote finishes. >>> Please see the schedule email for the full details. >>> >>> Look forward to seeing everyone on Tuesday! >>> >>> Tim 'mithro' Ansell >>> >>> -- >>> fpga-miniconf mailing list >>> fpga-miniconf at lists.lca2018.linux.org.au >>> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>> >>> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt-lca2018 at handcraftedcomputers.com.au Sun Jan 21 23:07:13 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Sun, 21 Jan 2018 22:37:13 +1030 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> On 21/01/18 18:39, Tim 'mithro' Ansell wrote: ... > It would be a good for everyone to update their litex-buildenv sometime Monday evening -- there have been a large number of updates since the last email was sent out. This can be done by doing the following and then following the prework instructions for testing QEmu / Linux. > > > cd litex-buildenv > git pull > export CPU=or1k PLATFORM=arty TARGET=net > ./scripts/download-env.sh > source ./scripts/enter-env.sh Yeah, busted now (this was working). Highlights: $ scripts/build-qemu.sh ... + ifconfig tap0 + grep -q UP scripts/build-qemu.sh: line 166: ifconfig: command not found + sudo true + sudo ifconfig tap0 192.168.100.100 netmask 255.255.255.0 up + make tftpd_stop # FIXME: This is dangerous... atftpd: no process found in.tftpd: no process found + make tftpd_start mkdir -p build/tftpd/ Cannot find an appropriate tftpd binary to launch the server. Makefile:337: recipe for target 'tftpd_start' failed make: *** [tftpd_start] Error 1 $ -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From dt-lca2018 at handcraftedcomputers.com.au Sun Jan 21 23:47:16 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Sun, 21 Jan 2018 23:17:16 +1030 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> References: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> Message-ID: On 21/01/18 22:37, Daryl Tester wrote: (note: platform is debian stretch). Okay, a while since I touched Makefiles, but ... > + make tftpd_start > mkdir -p build/tftpd/ > Cannot find an appropriate tftpd binary to launch the server. > Makefile:337: recipe for target 'tftpd_start' failed > make: *** [tftpd_start] Error 1 > $ --- a/Makefile +++ b/Makefile @@ -314,11 +314,11 @@ bios-flash: $(BIOS_FILE) bios-flash-$(PLATFORM) # We can run the TFTP server as the user if port >= 1024 # otherwise we need to run as root using sudo -ATFTPD=$(shell which atftpd) +ATFTPD=$(shell sudo which atftpd) ATFTPD?=/usr/sbin/atftpd -IN_TFTPD=$(shell which in.tfptd) -IN_TFTPD=?=/usr/sbin/in.tftpd +IN_TFTPD=$(shell sudo which in.tfptd) +IN_TFTPD?=/usr/sbin/in.tftpd tftp: $(FIRMWARE_FILEBASE).bin mkdir -p $(TFTPD_DIR) @@ -339,6 +339,8 @@ tftpd_start: echo "Root required to run TFTP Server, will use sudo"; \ sudo true; \ fi + echo "ATFTPD: $(ATFTPD)" + echo "IN_TFTPD: $(IN_TFTPD)" @if [ -x "$(ATFTPD)" ]; then \ echo "Starting aftpd"; \ if [ $(TFTP_SERVER_PORT) -lt 1024 ]; then \ Typo in "IN_TFTPD=?=/usr/sbin/in.tftpd", but ?= doesn't work anyway as according to GNU Makefile manual: "Note that a variable set to an empty value is still defined, so ??=? will not set that variable." Non-sudo path doesn't include /sbin:/usr/sbin so "sudo which" is used to pick up the path to the tftpd binary (and the ?= is superfluous). I get to BIOS boot from tftpd now and it hangs: Booting from network... Local IP : 192.168.100.50 Remote IP: 192.168.100.100 Fetching from: UDP/6069 Then nothing. I can't see anything with tcpdump across the tap0 interface (which is what I did last time to debug tftpd issues). -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From dt-lca2018 at handcraftedcomputers.com.au Sun Jan 21 23:50:25 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Sun, 21 Jan 2018 23:20:25 +1030 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> Message-ID: <18fc4bc3-b925-b9f1-2163-28615fdc58fc@handcraftedcomputers.com.au> On 21/01/18 23:17, Daryl Tester wrote: > Then nothing.? I can't see anything with tcpdump across the tap0 > interface (which is what I did last time to debug tftpd issues). Before anyone asks: # netstat -pan | grep 6069 warning, got bogus unix line. udp 0 0 192.168.100.100:6069 0.0.0.0:* 5391/atftpd -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From mithro at mithis.com Sun Jan 21 23:52:42 2018 From: mithro at mithis.com (Tim Ansell) Date: Sun, 21 Jan 2018 23:52:42 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: <18fc4bc3-b925-b9f1-2163-28615fdc58fc@handcraftedcomputers.com.au> References: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> <18fc4bc3-b925-b9f1-2163-28615fdc58fc@handcraftedcomputers.com.au> Message-ID: Try doing a make clean and try again. Tim 'mithro' Ansell On 21 Jan. 2018 11:50 pm, "Daryl Tester" < dt-lca2018 at handcraftedcomputers.com.au> wrote: > On 21/01/18 23:17, Daryl Tester wrote: > > Then nothing. I can't see anything with tcpdump across the tap0 >> interface (which is what I did last time to debug tftpd issues). >> > > Before anyone asks: > > # netstat -pan | grep 6069 > warning, got bogus unix line. > udp 0 0 192.168.100.100:6069 0.0.0.0:* > 5391/atftpd > > > -- > Regards, > Daryl Tester > Handcrafted Computers Pty. Ltd. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt-lca2018 at handcraftedcomputers.com.au Mon Jan 22 00:13:42 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Sun, 21 Jan 2018 23:43:42 +1030 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> <18fc4bc3-b925-b9f1-2163-28615fdc58fc@handcraftedcomputers.com.au> Message-ID: <08b66dfe-cae5-007d-924a-1f7547367304@handcraftedcomputers.com.au> On 21/01/18 23:22, Tim Ansell wrote: > Try doing a make clean and try again. Same result. Just to clarify, I'm no longer seeing any PXE boot requests across the tap0 interface, which I could see when this was working. Thought it might have been due to the change in tftpd ports, so dropped the firewall and still no change. -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From mithro at mithis.com Mon Jan 22 00:26:29 2018 From: mithro at mithis.com (Tim Ansell) Date: Mon, 22 Jan 2018 00:26:29 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: <08b66dfe-cae5-007d-924a-1f7547367304@handcraftedcomputers.com.au> References: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> <18fc4bc3-b925-b9f1-2163-28615fdc58fc@handcraftedcomputers.com.au> <08b66dfe-cae5-007d-924a-1f7547367304@handcraftedcomputers.com.au> Message-ID: Can you check that your git submodules are all at the correct revisions? Check both LiteX and LiteEth in third_party. Otherwise I'll look at it tomorrow and see if I can figure out what is going on. Tim 'mithro' Ansell On 22 Jan. 2018 12:13 am, "Daryl Tester" < dt-lca2018 at handcraftedcomputers.com.au> wrote: > On 21/01/18 23:22, Tim Ansell wrote: > > Try doing a make clean and try again. >> > > Same result. > > Just to clarify, I'm no longer seeing any PXE boot requests across > the tap0 interface, which I could see when this was working. > Thought it might have been due to the change in tftpd ports, so > dropped the firewall and still no change. > > > -- > Regards, > Daryl Tester > Handcrafted Computers Pty. Ltd. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt-lca2018 at handcraftedcomputers.com.au Mon Jan 22 00:55:23 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Mon, 22 Jan 2018 00:25:23 +1030 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> <18fc4bc3-b925-b9f1-2163-28615fdc58fc@handcraftedcomputers.com.au> <08b66dfe-cae5-007d-924a-1f7547367304@handcraftedcomputers.com.au> Message-ID: <0068c180-5443-25fd-8726-05907ec90a36@handcraftedcomputers.com.au> On 21/01/18 23:56, Tim Ansell wrote: > Can you check that your git submodules are all at the correct revisions? Check both LiteX and LiteEth in third_party. Well, I'm not sure what "correct revisions" are (I'm not a git expert, and git pull on litex and liteeth indicates they're not on branches), but git pull of qemu-litex and recompile appears to have built it to booting stage. Still yet to finish the remainder of the checks, and it's now well past what was supposed to be an early night. :-/ -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From dt-lca2018 at handcraftedcomputers.com.au Mon Jan 22 01:06:42 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Mon, 22 Jan 2018 00:36:42 +1030 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: <0068c180-5443-25fd-8726-05907ec90a36@handcraftedcomputers.com.au> References: <4857a721-49b4-c29f-738d-f87b9b848fb1@handcraftedcomputers.com.au> <18fc4bc3-b925-b9f1-2163-28615fdc58fc@handcraftedcomputers.com.au> <08b66dfe-cae5-007d-924a-1f7547367304@handcraftedcomputers.com.au> <0068c180-5443-25fd-8726-05907ec90a36@handcraftedcomputers.com.au> Message-ID: <3bd7efb3-affe-1eca-ef33-331c369687cc@handcraftedcomputers.com.au> On 22/01/18 00:25, Daryl Tester wrote: > On 21/01/18 23:56, Tim Ansell wrote: > >> Can you check that your git submodules are all at the correct revisions? Check both LiteX and LiteEth in third_party. > > Well, I'm not sure what "correct revisions" are (I'm not a git expert, and git pull > on litex and liteeth indicates they're not on branches), but git pull of qemu-litex > and recompile appears to have built it to booting stage. Right - now that I'm down at the "Run Linux in QEMU" part of the document I can see Ewan's comment about the tftp hang and needing a newer qemu-litex - that really needs to be duplicated up at "Try running Test Firmware inside QEMU." (I'd attempt to edit it, but I can't even get the commands copied out of that document working). -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From hal.ashburner at gmail.com Mon Jan 22 12:45:36 2018 From: hal.ashburner at gmail.com (Hal Ashburner) Date: Mon, 22 Jan 2018 12:45:36 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: Hey guys. Where are you set up today? On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" wrote: > Hello everyone, > > With just over 24 hours until the FPGA Miniconf, this is the final > reminder that everyone **must** complete the prework at > http://j.mp/pre-fpga-lca2018 > > You must complete up to the paragraph which says the following in bright > red; > >> The instructions from here can only be done after you receive hardware. >> You can stop here if completing the prework. > > > If you have not completed the prework you will not be able to attend -- > that includes observing or anything similar. > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers will be > available to help. They should be available during morning tea, lunch and > afternoon tea somewhere near the Tomu test station. Hopefully they will be > able to solve any issues you are having. > > There will also be an opportunity to pick up the hardware kits during > lunch at the same location. This will allow you to get a head start on > setup we need to do at the start of the Miniconf. > > It would be a good for everyone to update their litex-buildenv sometime > Monday evening -- there have been a large number of updates since the last > email was sent out. This can be done by doing the following and then > following the prework instructions for testing QEmu / Linux. > > > cd litex-buildenv > git pull > export CPU=or1k PLATFORM=arty TARGET=net > ./scripts/download-env.sh > source ./scripts/enter-env.sh > > > Depending on internet speeds, updating should only take 10-15 minutes. > > People are also reminded that the FPGA Miniconf is on Tuesday, 23 January > 2018 and will be starting at 10:15AM. This is right after the Matthew > Todd's keynote talk. Please make sure you make a beeline from the keynote > venue to Large POD Room CB11.04.400 when the keynote finishes. Please see > the schedule email for the full details. > > Look forward to seeing everyone on Tuesday! > > Tim 'mithro' Ansell > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jason at ball.net Mon Jan 22 13:14:05 2018 From: jason at ball.net (Jason Ball) Date: Mon, 22 Jan 2018 13:14:05 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: For that matter, could I drop in later today to grab the kit so I'm ready for tomorrow's session, latest changes and all. Thanks. On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner wrote: > Hey guys. Where are you set up today? > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" wrote: > >> Hello everyone, >> >> With just over 24 hours until the FPGA Miniconf, this is the final >> reminder that everyone **must** complete the prework at >> http://j.mp/pre-fpga-lca2018 >> >> You must complete up to the paragraph which says the following in bright >> red; >> >>> The instructions from here can only be done after you receive hardware. >>> You can stop here if completing the prework. >> >> >> If you have not completed the prework you will not be able to attend -- >> that includes observing or anything similar. >> >> If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers will be >> available to help. They should be available during morning tea, lunch and >> afternoon tea somewhere near the Tomu test station. Hopefully they will be >> able to solve any issues you are having. >> >> There will also be an opportunity to pick up the hardware kits during >> lunch at the same location. This will allow you to get a head start on >> setup we need to do at the start of the Miniconf. >> >> It would be a good for everyone to update their litex-buildenv sometime >> Monday evening -- there have been a large number of updates since the last >> email was sent out. This can be done by doing the following and then >> following the prework instructions for testing QEmu / Linux. >> >> >> cd litex-buildenv >> git pull >> export CPU=or1k PLATFORM=arty TARGET=net >> ./scripts/download-env.sh >> source ./scripts/enter-env.sh >> >> >> Depending on internet speeds, updating should only take 10-15 minutes. >> >> People are also reminded that the FPGA Miniconf is on Tuesday, 23 January >> 2018 and will be starting at 10:15AM. This is right after the Matthew >> Todd's keynote talk. Please make sure you make a beeline from the keynote >> venue to Large POD Room CB11.04.400 when the keynote finishes. Please see >> the schedule email for the full details. >> >> Look forward to seeing everyone on Tuesday! >> >> Tim 'mithro' Ansell >> >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> >> > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -- -- Teach your kids Science, or somebody else will :/ jason at ball.net vk2vjb at google.com callsign: vk2vjb -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.stan at gmail.com Mon Jan 22 14:19:18 2018 From: joel.stan at gmail.com (joel.stan at gmail.com) Date: Sun, 21 Jan 2018 21:19:18 -0600 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: I will be at the top of the stairs at 3pm with the kits. I'm in a blue tshirt. Come say hi and grab your kit. Cheers, Joel On 22 Jan. 2018 13:14, "Jason Ball" wrote: For that matter, could I drop in later today to grab the kit so I'm ready for tomorrow's session, latest changes and all. Thanks. On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner wrote: > Hey guys. Where are you set up today? > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" wrote: > >> Hello everyone, >> >> With just over 24 hours until the FPGA Miniconf, this is the final >> reminder that everyone **must** complete the prework at >> http://j.mp/pre-fpga-lca2018 >> >> You must complete up to the paragraph which says the following in bright >> red; >> >>> The instructions from here can only be done after you receive hardware. >>> You can stop here if completing the prework. >> >> >> If you have not completed the prework you will not be able to attend -- >> that includes observing or anything similar. >> >> If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers will be >> available to help. They should be available during morning tea, lunch and >> afternoon tea somewhere near the Tomu test station. Hopefully they will be >> able to solve any issues you are having. >> >> There will also be an opportunity to pick up the hardware kits during >> lunch at the same location. This will allow you to get a head start on >> setup we need to do at the start of the Miniconf. >> >> It would be a good for everyone to update their litex-buildenv sometime >> Monday evening -- there have been a large number of updates since the last >> email was sent out. This can be done by doing the following and then >> following the prework instructions for testing QEmu / Linux. >> >> >> cd litex-buildenv >> git pull >> export CPU=or1k PLATFORM=arty TARGET=net >> ./scripts/download-env.sh >> source ./scripts/enter-env.sh >> >> >> Depending on internet speeds, updating should only take 10-15 minutes. >> >> People are also reminded that the FPGA Miniconf is on Tuesday, 23 January >> 2018 and will be starting at 10:15AM. This is right after the Matthew >> Todd's keynote talk. Please make sure you make a beeline from the keynote >> venue to Large POD Room CB11.04.400 when the keynote finishes. Please see >> the schedule email for the full details. >> >> Look forward to seeing everyone on Tuesday! >> >> Tim 'mithro' Ansell >> >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> >> > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -- -- Teach your kids Science, or somebody else will :/ jason at ball.net vk2vjb at google.com callsign: vk2vjb -- fpga-miniconf mailing list fpga-miniconf at lists.lca2018.linux.org.au http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim.mussared at gmail.com Mon Jan 22 14:58:21 2018 From: jim.mussared at gmail.com (Jim Mussared) Date: Mon, 22 Jan 2018 14:58:21 +1100 Subject: [fpga-miniconf] Updated timetable for FPGA miniconf Message-ID: Hi FPGA Miniconf attendees, Summary: new start time is 10:45am at CB11.04.400. We're going to return to the normal miniconf schedule for tomorrow. This means you'll still have time for morning tea after the keynote, and more time for lunch (which is still catered for miniconf attendees). We won't be organising a dinner, so you should make your own plans to hang out with other conference attendees! So the new schedule is: 9:00am - 10:10am - Keynote 10:10am - 10:45am - Morning tea (catered by LCA) 10:45am - 12:25am - Morning session 12:25am - 1:40pm - Lunch (catered for miniconf attendees) 1:40pm - 3:20pm - Afternoon session 3:20pm - 3:50pm - Afternoon tea (catered by LCA) 3:50pm - onwards - Free time As Joel said, we're handing out kits at 3pm-3:30pm at the top of the main stairs -- next to the yellow doors to the great hall. Look for Joel in a blue shirt and me in a white shirt. Jim From Libing.Chen at uts.edu.au Mon Jan 22 17:43:56 2018 From: Libing.Chen at uts.edu.au (Bing Chen) Date: Mon, 22 Jan 2018 06:43:56 +0000 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: Message-ID: <1516603436.2545.8.camel@uts.edu.au> Hi Joel/Tim, Bing's here, I think my kit is faulty or something, when I tried testing loading gateware on it, I got this error msgs: --- console msg copy --- make[1]: Leaving directory '/home/bing/litex- buildenv/build/arty_net_or1k.linux/software/firmware' real0m1.135s user0m1.046s sys0m0.096s flterm --port=/dev/ttyUSB1 -- kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- speed=115200 [FLTERM] Starting... LiteX SoC BIOS (or1k) (c) Copyright 2012-2017 Enjoy-Digital (c) Copyright 2007-2017 M-Labs Limited Built Jan 12 2018 04:46:47 BIOS CRC passed (046476c5) Initializing SDRAM... Read delays: 1:32-33 0:32-33 completed Memtest bus failed: 64/256 errors Memtest data failed: 524288/524288 errors Memtest addr failed: 8191/8192 errors Memory initialization failed BIOS> ---- Then I tried run serialboot and it stuck at "Executing booted program at 0x40000000" ---- console msg copy ---- BIOS> serialboot Booting from serial... Press Q or ESC to abort boot completely. sL5DdSMmkekro [FLTERM] Received firmware download request from the device. [FLTERM] Uploading kernel (74672 bytes)... [FLTERM] Upload complete (7.7KB/s). [FLTERM] Booting the device. [FLTERM] Done. Executing booted program at 0x40000000 ---- Regards bing On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: > I will be at the top of the stairs at 3pm with the kits. I'm in a > blue tshirt. Come say hi and grab your kit. > > Cheers, > > Joel > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: > > For that matter, could I drop in later today to grab the kit so I'm > > ready for tomorrow's session, latest changes and all. > > > > Thanks. > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner > l.com> wrote: > > > Hey guys. Where are you set up today? > > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" > > > wrote: > > > > Hello everyone, > > > > > > > > With just over 24 hours until the FPGA Miniconf, this is the > > > > final reminder that everyone **must** complete the prework at h > > > > ttp://j.mp/pre-fpga-lca2018 > > > > > > > > You must complete up to the paragraph which says the following > > > > in bright red; > > > > > The instructions from here can only be done after you receive > > > > > hardware. You can stop here if completing the prework. > > > > > > > > If you have not completed the prework you will not be able to > > > > attend -- that includes observing or anything similar. > > > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers > > > > will be available to help. They should be available during > > > > morning tea, lunch and afternoon tea somewhere near the Tomu > > > > test station. Hopefully they will be able to solve any issues > > > > you are having. > > > > > > > > There will also be an opportunity to pick up the hardware kits > > > > during lunch at the same location. This will allow you to get a > > > > head start on setup we need to do at the start of the Miniconf. > > > > > > > > It would be a good for everyone to update their litex-buildenv > > > > sometime Monday evening -- there have been a large number of > > > > updates since the last email was sent out. This can be done by > > > > doing the following and then following the prework instructions > > > > for testing QEmu / Linux. > > > > > cd litex-buildenv > > > > > git pull > > > > > export CPU=or1k PLATFORM=arty TARGET=net > > > > > ./scripts/download-env.sh > > > > > source ./scripts/enter-env.sh > > > > > > > > Depending on internet speeds, updating should only take 10-15 > > > > minutes. > > > > > > > > People are also reminded that the FPGA Miniconf is on Tuesday, > > > > 23 January 2018 and will be starting at 10:15AM. This is right > > > > after the Matthew Todd's keynote talk. Please make sure you > > > > make a beeline from the keynote venue to Large POD Room > > > > CB11.04.400 when the keynote finishes. Please see the schedule > > > > email for the full details. > > > > > > > > Look forward to seeing everyone on Tuesday! > > > > > > > > Tim 'mithro' Ansell > > > > > > > > -- > > > > fpga-miniconf mailing list > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon > > > > f > > > > > > > > > > -- > > > fpga-miniconf mailing list > > > fpga-miniconf at lists.lca2018.linux.org.au > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > > > > > > > > > > -- > > -- > > Teach your kids Science, or somebody else will :/ > > > > jason at ball.net > > vk2vjb at google.com > > callsign: vk2vjb > > > > > > -- > > fpga-miniconf mailing list > > fpga-miniconf at lists.lca2018.linux.org.au > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. From f.kermarrec at gmail.com Mon Jan 22 18:00:40 2018 From: f.kermarrec at gmail.com (Florent Kermarrec) Date: Mon, 22 Jan 2018 08:00:40 +0100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: <1516603436.2545.8.camel@uts.edu.au> References: <1516603436.2545.8.camel@uts.edu.au> Message-ID: Hi Bing, the fact that you see "Read delays: 1:32-33 0:32-33 completed" make me think your are not up to date on both litex and litex-buildenv repository. (or maybe on just one of them) Can you check? Florent 2018-01-22 7:43 GMT+01:00 Bing Chen : > Hi Joel/Tim, > > Bing's here, I think my kit is faulty or something, when I tried > testing loading gateware on it, I got this error msgs: > > --- console msg copy --- > > make[1]: Leaving directory '/home/bing/litex- > buildenv/build/arty_net_or1k.linux/software/firmware' > > real0m1.135s > user0m1.046s > sys0m0.096s > flterm --port=/dev/ttyUSB1 -- > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- > speed=115200 > [FLTERM] Starting... > > LiteX SoC BIOS (or1k) > (c) Copyright 2012-2017 Enjoy-Digital > (c) Copyright 2007-2017 M-Labs Limited > Built Jan 12 2018 04:46:47 > > BIOS CRC passed (046476c5) > Initializing SDRAM... > Read delays: 1:32-33 0:32-33 completed > Memtest bus failed: 64/256 errors > Memtest data failed: 524288/524288 errors > Memtest addr failed: 8191/8192 errors > Memory initialization failed > BIOS> > > ---- > > Then I tried run serialboot and it stuck at "Executing booted program > at 0x40000000" > > ---- console msg copy ---- > > BIOS> serialboot > Booting from serial... > Press Q or ESC to abort boot completely. > sL5DdSMmkekro > [FLTERM] Received firmware download request from the device. > [FLTERM] Uploading kernel (74672 bytes)... > [FLTERM] Upload complete (7.7KB/s). > [FLTERM] Booting the device. > [FLTERM] Done. > Executing booted program at 0x40000000 > > ---- > > > Regards > bing > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: > > I will be at the top of the stairs at 3pm with the kits. I'm in a > > blue tshirt. Come say hi and grab your kit. > > > > Cheers, > > > > Joel > > > > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: > > > For that matter, could I drop in later today to grab the kit so I'm > > > ready for tomorrow's session, latest changes and all. > > > > > > Thanks. > > > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner > > l.com> wrote: > > > > Hey guys. Where are you set up today? > > > > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" > > > > wrote: > > > > > Hello everyone, > > > > > > > > > > With just over 24 hours until the FPGA Miniconf, this is the > > > > > final reminder that everyone **must** complete the prework at h > > > > > ttp://j.mp/pre-fpga-lca2018 > > > > > > > > > > You must complete up to the paragraph which says the following > > > > > in bright red; > > > > > > The instructions from here can only be done after you receive > > > > > > hardware. You can stop here if completing the prework. > > > > > > > > > > If you have not completed the prework you will not be able to > > > > > attend -- that includes observing or anything similar. > > > > > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf helpers > > > > > will be available to help. They should be available during > > > > > morning tea, lunch and afternoon tea somewhere near the Tomu > > > > > test station. Hopefully they will be able to solve any issues > > > > > you are having. > > > > > > > > > > There will also be an opportunity to pick up the hardware kits > > > > > during lunch at the same location. This will allow you to get a > > > > > head start on setup we need to do at the start of the Miniconf. > > > > > > > > > > It would be a good for everyone to update their litex-buildenv > > > > > sometime Monday evening -- there have been a large number of > > > > > updates since the last email was sent out. This can be done by > > > > > doing the following and then following the prework instructions > > > > > for testing QEmu / Linux. > > > > > > cd litex-buildenv > > > > > > git pull > > > > > > export CPU=or1k PLATFORM=arty TARGET=net > > > > > > ./scripts/download-env.sh > > > > > > source ./scripts/enter-env.sh > > > > > > > > > > Depending on internet speeds, updating should only take 10-15 > > > > > minutes. > > > > > > > > > > People are also reminded that the FPGA Miniconf is on Tuesday, > > > > > 23 January 2018 and will be starting at 10:15AM. This is right > > > > > after the Matthew Todd's keynote talk. Please make sure you > > > > > make a beeline from the keynote venue to Large POD Room > > > > > CB11.04.400 when the keynote finishes. Please see the schedule > > > > > email for the full details. > > > > > > > > > > Look forward to seeing everyone on Tuesday! > > > > > > > > > > Tim 'mithro' Ansell > > > > > > > > > > -- > > > > > fpga-miniconf mailing list > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon > > > > > f > > > > > > > > > > > > > -- > > > > fpga-miniconf mailing list > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > > > > > > > > > > > > > > > -- > > > -- > > > Teach your kids Science, or somebody else will :/ > > > > > > jason at ball.net > > > vk2vjb at google.com > > > callsign: vk2vjb > > > > > > > > > -- > > > fpga-miniconf mailing list > > > fpga-miniconf at lists.lca2018.linux.org.au > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > > > > > > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any > accompanying attachments may contain confidential information. If you are > not the intended recipient, do not read, use, disseminate, distribute or > copy this message or attachments. If you have received this message in > error, please notify the sender immediately and delete this message. Any > views expressed in this message are those of the individual sender, except > where the sender expressly, and with authority, states them to be the views > of the University of Technology Sydney. Before opening any attachments, > please check them for viruses and defects. Think. Green. Do. Please > consider the environment before printing this email. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Libing.Chen at uts.edu.au Mon Jan 22 18:58:47 2018 From: Libing.Chen at uts.edu.au (Bing Chen) Date: Mon, 22 Jan 2018 07:58:47 +0000 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> Message-ID: <1516607926.5051.7.camel@uts.edu.au> Hi Florent, Thanks for reply, I did another git pull in litex-buildenv and ran the download-env.sh again, still the same error when I tried: --- console msg copy --- chmod -x firmware.bin python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi make[1]: Leaving directory '/home/bing/litex- buildenv/build/arty_net_or1k.linux/software/firmware' real0m1.946s user0m2.593s sys0m0.413s flterm --port=/dev/ttyUSB1 -- kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- speed=115200 [FLTERM] Starting... LiteX SoC BIOS (or1k) (c) Copyright 2012-2017 Enjoy-Digital (c) Copyright 2007-2017 M-Labs Limited Built Jan 12 2018 04:46:47 BIOS CRC passed (046476c5) Initializing SDRAM... Read delays: 1:32-33 0:32-33 completed Memtest bus failed: 64/256 errors Memtest data failed: 524288/524288 errors Memtest addr failed: 8191/8192 errors Memory initialization failed BIOS> --- All the prework steps work fine on my box though. Regards bing On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: > Hi Bing, > > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make > me think your are not up to date on both litex and litex-buildenv > repository. (or maybe on just one of them) > > Can you check? > > Florent > > > 2018-01-22 7:43 GMT+01:00 Bing Chen : > > Hi Joel/Tim, > > > > Bing's here, I think my kit is faulty or something, when I tried > > testing loading gateware on it, I got this error msgs: > > > > --- console msg copy --- > > > > make[1]: Leaving directory '/home/bing/litex- > > buildenv/build/arty_net_or1k.linux/software/firmware' > > > > real0m1.135s > > user0m1.046s > > sys0m0.096s > > flterm --port=/dev/ttyUSB1 -- > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- > > speed=115200 > > [FLTERM] Starting... > > > > LiteX SoC BIOS (or1k) > > (c) Copyright 2012-2017 Enjoy-Digital > > (c) Copyright 2007-2017 M-Labs Limited > > Built Jan 12 2018 04:46:47 > > > > BIOS CRC passed (046476c5) > > Initializing SDRAM... > > Read delays: 1:32-33 0:32-33 completed > > Memtest bus failed: 64/256 errors > > Memtest data failed: 524288/524288 errors > > Memtest addr failed: 8191/8192 errors > > Memory initialization failed > > BIOS> > > > > ---- > > > > Then I tried run serialboot and it stuck at "Executing booted > > program > > at 0x40000000" > > > > ---- console msg copy ---- > > > > BIOS> serialboot > > Booting from serial... > > Press Q or ESC to abort boot completely. > > sL5DdSMmkekro > > [FLTERM] Received firmware download request from the device. > > [FLTERM] Uploading kernel (74672 bytes)... > > [FLTERM] Upload complete (7.7KB/s). > > [FLTERM] Booting the device. > > [FLTERM] Done. > > Executing booted program at 0x40000000 > > > > ---- > > > > > > Regards > > bing > > > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: > > > I will be at the top of the stairs at 3pm with the kits. I'm in a > > > blue tshirt. Come say hi and grab your kit. > > > > > > Cheers, > > > > > > Joel > > > > > > > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: > > > > For that matter, could I drop in later today to grab the kit so > > I'm > > > > ready for tomorrow's session, latest changes and all. > > > > > > > > Thanks. > > > > > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner > gmai > > > > l.com> wrote: > > > > > Hey guys. Where are you set up today? > > > > > > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" > > > > > wrote: > > > > > > Hello everyone, > > > > > > > > > > > > With just over 24 hours until the FPGA Miniconf, this is > > the > > > > > > final reminder that everyone **must** complete the prework > > at h > > > > > > ttp://j.mp/pre-fpga-lca2018 > > > > > > > > > > > > You must complete up to the paragraph which says the > > following > > > > > > in bright red; > > > > > > > The instructions from here can only be done after you > > receive > > > > > > > hardware. You can stop here if completing the prework. > > > > > > > > > > > > If you have not completed the prework you will not be able > > to > > > > > > attend -- that includes observing or anything similar. > > > > > > > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf > > helpers > > > > > > will be available to help. They should be available during > > > > > > morning tea, lunch and afternoon tea somewhere near the > > Tomu > > > > > > test station. Hopefully they will be able to solve any > > issues > > > > > > you are having. > > > > > > > > > > > > There will also be an opportunity to pick up the hardware > > kits > > > > > > during lunch at the same location. This will allow you to > > get a > > > > > > head start on setup we need to do at the start of the > > Miniconf. > > > > > > > > > > > > It would be a good for everyone to update their litex- > > buildenv > > > > > > sometime Monday evening -- there have been a large number > > of > > > > > > updates since the last email was sent out. This can be done > > by > > > > > > doing the following and then following the prework > > instructions > > > > > > for testing QEmu / Linux. > > > > > > > cd litex-buildenv > > > > > > > git pull > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net > > > > > > > ./scripts/download-env.sh > > > > > > > source ./scripts/enter-env.sh > > > > > > > > > > > > Depending on internet speeds, updating should only take 10- > > 15 > > > > > > minutes. > > > > > > > > > > > > People are also reminded that the FPGA Miniconf is on > > Tuesday, > > > > > > 23 January 2018 and will be starting at 10:15AM. This is > > right > > > > > > after the Matthew Todd's keynote talk. Please make sure you > > > > > > make a beeline from the keynote venue to Large POD Room > > > > > > CB11.04.400 when the keynote finishes. Please see the > > schedule > > > > > > email for the full details. > > > > > > > > > > > > Look forward to seeing everyone on Tuesday! > > > > > > > > > > > > Tim 'mithro' Ansell > > > > > > > > > > > > -- > > > > > > fpga-miniconf mailing list > > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-min > > icon > > > > > > f > > > > > > > > > > > > > > > > -- > > > > > fpga-miniconf mailing list > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minic > > onf > > > > > > > > > > > > > > > > > > > > > -- > > > > -- > > > > Teach your kids Science, or somebody else will :/ > > > > > > > > jason at ball.net > > > > vk2vjb at google.com > > > > callsign: vk2vjb > > > > > > > > > > > > -- > > > > fpga-miniconf mailing list > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon > > f > > > > > > > > > > > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and > > any accompanying attachments may contain confidential information. > > If you are not the intended recipient, do not read, use, > > disseminate, distribute or copy this message or attachments. If you > > have received this message in error, please notify the sender > > immediately and delete this message. Any views expressed in this > > message are those of the individual sender, except where the sender > > expressly, and with authority, states them to be the views of the > > University of Technology Sydney. Before opening any attachments, > > please check them for viruses and defects. Think. Green. Do. Please > > consider the environment before printing this email. > > -- > > fpga-miniconf mailing list > > fpga-miniconf at lists.lca2018.linux.org.au > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. From rohit91.2008 at gmail.com Mon Jan 22 19:25:17 2018 From: rohit91.2008 at gmail.com (Rohit Kumar Singh) Date: Mon, 22 Jan 2018 19:25:17 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: <1516607926.5051.7.camel@uts.edu.au> References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> Message-ID: Hi Bing! Sorry for repeat mail! I forgot to cc the mailing list in the last reply. I'm guessing your litex/litex-buildenv still might old. Because here is what I get: LiteX SoC BIOS (or1k) > (c) Copyright 2012-2018 Enjoy-Digital > (c) Copyright 2007-2018 M-Labs Limited > Built *Jan 20* 2018 22:57:55 Cloning a new repo and building the gateware and image again should work. Ideally, make clean, and git pull should have been sufficient. Thanks & Regards, Rohit On Mon, Jan 22, 2018 at 6:58 PM, Bing Chen wrote: > Hi Florent, > > Thanks for reply, I did another git pull in litex-buildenv and ran the > download-env.sh again, still the same error when I tried: > > --- console msg copy --- > > chmod -x firmware.bin > python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi > make[1]: Leaving directory '/home/bing/litex- > buildenv/build/arty_net_or1k.linux/software/firmware' > > real0m1.946s > user0m2.593s > sys0m0.413s > flterm --port=/dev/ttyUSB1 -- > kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- > speed=115200 > [FLTERM] Starting... > > LiteX SoC BIOS (or1k) > (c) Copyright 2012-2017 Enjoy-Digital > (c) Copyright 2007-2017 M-Labs Limited > Built Jan 12 2018 04:46:47 > > BIOS CRC passed (046476c5) > Initializing SDRAM... > Read delays: 1:32-33 0:32-33 completed > Memtest bus failed: 64/256 errors > Memtest data failed: 524288/524288 errors > Memtest addr failed: 8191/8192 errors > Memory initialization failed > BIOS> > --- > > All the prework steps work fine on my box though. > > Regards > bing > > On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: > > Hi Bing, > > > > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make > > me think your are not up to date on both litex and litex-buildenv > > repository. (or maybe on just one of them) > > > > Can you check? > > > > Florent > > > > > > 2018-01-22 7:43 GMT+01:00 Bing Chen : > > > Hi Joel/Tim, > > > > > > Bing's here, I think my kit is faulty or something, when I tried > > > testing loading gateware on it, I got this error msgs: > > > > > > --- console msg copy --- > > > > > > make[1]: Leaving directory '/home/bing/litex- > > > buildenv/build/arty_net_or1k.linux/software/firmware' > > > > > > real0m1.135s > > > user0m1.046s > > > sys0m0.096s > > > flterm --port=/dev/ttyUSB1 -- > > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- > > > speed=115200 > > > [FLTERM] Starting... > > > > > > LiteX SoC BIOS (or1k) > > > (c) Copyright 2012-2017 Enjoy-Digital > > > (c) Copyright 2007-2017 M-Labs Limited > > > Built Jan 12 2018 04:46:47 > > > > > > BIOS CRC passed (046476c5) > > > Initializing SDRAM... > > > Read delays: 1:32-33 0:32-33 completed > > > Memtest bus failed: 64/256 errors > > > Memtest data failed: 524288/524288 errors > > > Memtest addr failed: 8191/8192 errors > > > Memory initialization failed > > > BIOS> > > > > > > ---- > > > > > > Then I tried run serialboot and it stuck at "Executing booted > > > program > > > at 0x40000000" > > > > > > ---- console msg copy ---- > > > > > > BIOS> serialboot > > > Booting from serial... > > > Press Q or ESC to abort boot completely. > > > sL5DdSMmkekro > > > [FLTERM] Received firmware download request from the device. > > > [FLTERM] Uploading kernel (74672 bytes)... > > > [FLTERM] Upload complete (7.7KB/s). > > > [FLTERM] Booting the device. > > > [FLTERM] Done. > > > Executing booted program at 0x40000000 > > > > > > ---- > > > > > > > > > Regards > > > bing > > > > > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: > > > > I will be at the top of the stairs at 3pm with the kits. I'm in a > > > > blue tshirt. Come say hi and grab your kit. > > > > > > > > Cheers, > > > > > > > > Joel > > > > > > > > > > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: > > > > > For that matter, could I drop in later today to grab the kit so > > > I'm > > > > > ready for tomorrow's session, latest changes and all. > > > > > > > > > > Thanks. > > > > > > > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner > > gmai > > > > > l.com> wrote: > > > > > > Hey guys. Where are you set up today? > > > > > > > > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" > > > > > > wrote: > > > > > > > Hello everyone, > > > > > > > > > > > > > > With just over 24 hours until the FPGA Miniconf, this is > > > the > > > > > > > final reminder that everyone **must** complete the prework > > > at h > > > > > > > ttp://j.mp/pre-fpga-lca2018 > > > > > > > > > > > > > > You must complete up to the paragraph which says the > > > following > > > > > > > in bright red; > > > > > > > > The instructions from here can only be done after you > > > receive > > > > > > > > hardware. You can stop here if completing the prework. > > > > > > > > > > > > > > If you have not completed the prework you will not be able > > > to > > > > > > > attend -- that includes observing or anything similar. > > > > > > > > > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf > > > helpers > > > > > > > will be available to help. They should be available during > > > > > > > morning tea, lunch and afternoon tea somewhere near the > > > Tomu > > > > > > > test station. Hopefully they will be able to solve any > > > issues > > > > > > > you are having. > > > > > > > > > > > > > > There will also be an opportunity to pick up the hardware > > > kits > > > > > > > during lunch at the same location. This will allow you to > > > get a > > > > > > > head start on setup we need to do at the start of the > > > Miniconf. > > > > > > > > > > > > > > It would be a good for everyone to update their litex- > > > buildenv > > > > > > > sometime Monday evening -- there have been a large number > > > of > > > > > > > updates since the last email was sent out. This can be done > > > by > > > > > > > doing the following and then following the prework > > > instructions > > > > > > > for testing QEmu / Linux. > > > > > > > > cd litex-buildenv > > > > > > > > git pull > > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net > > > > > > > > ./scripts/download-env.sh > > > > > > > > source ./scripts/enter-env.sh > > > > > > > > > > > > > > Depending on internet speeds, updating should only take 10- > > > 15 > > > > > > > minutes. > > > > > > > > > > > > > > People are also reminded that the FPGA Miniconf is on > > > Tuesday, > > > > > > > 23 January 2018 and will be starting at 10:15AM. This is > > > right > > > > > > > after the Matthew Todd's keynote talk. Please make sure you > > > > > > > make a beeline from the keynote venue to Large POD Room > > > > > > > CB11.04.400 when the keynote finishes. Please see the > > > schedule > > > > > > > email for the full details. > > > > > > > > > > > > > > Look forward to seeing everyone on Tuesday! > > > > > > > > > > > > > > Tim 'mithro' Ansell > > > > > > > > > > > > > > -- > > > > > > > fpga-miniconf mailing list > > > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-min > > > icon > > > > > > > f > > > > > > > > > > > > > > > > > > > -- > > > > > > fpga-miniconf mailing list > > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minic > > > onf > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > -- > > > > > Teach your kids Science, or somebody else will :/ > > > > > > > > > > jason at ball.net > > > > > vk2vjb at google.com > > > > > callsign: vk2vjb > > > > > > > > > > > > > > > -- > > > > > fpga-miniconf mailing list > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon > > > f > > > > > > > > > > > > > > > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and > > > any accompanying attachments may contain confidential information. > > > If you are not the intended recipient, do not read, use, > > > disseminate, distribute or copy this message or attachments. If you > > > have received this message in error, please notify the sender > > > immediately and delete this message. Any views expressed in this > > > message are those of the individual sender, except where the sender > > > expressly, and with authority, states them to be the views of the > > > University of Technology Sydney. Before opening any attachments, > > > please check them for viruses and defects. Think. Green. Do. Please > > > consider the environment before printing this email. > > > -- > > > fpga-miniconf mailing list > > > fpga-miniconf at lists.lca2018.linux.org.au > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > > > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any > accompanying attachments may contain confidential information. If you are > not the intended recipient, do not read, use, disseminate, distribute or > copy this message or attachments. If you have received this message in > error, please notify the sender immediately and delete this message. Any > views expressed in this message are those of the individual sender, except > where the sender expressly, and with authority, states them to be the views > of the University of Technology Sydney. Before opening any attachments, > please check them for viruses and defects. Think. Green. Do. Please > consider the environment before printing this email. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim.mussared at gmail.com Mon Jan 22 20:18:22 2018 From: jim.mussared at gmail.com (Jim Mussared) Date: Mon, 22 Jan 2018 20:18:22 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> Message-ID: Rather than recloning the whole repo, it shpuld be sufficient just to git pull in litex-buildenv, then make gateware / make image (make gateware should update all the submodules, including litex, which is what Florent is referring to). Unless I missed something, doesn't look like you made a new gateware since doing a pull (just reflashed the old one) On 22 Jan. 2018 7:25 pm, "Rohit Kumar Singh" wrote: > Hi Bing! > > Sorry for repeat mail! I forgot to cc the mailing list in the last reply. > > I'm guessing your litex/litex-buildenv still might old. Because here is > what I get: > > LiteX SoC BIOS (or1k) >> (c) Copyright 2012-2018 Enjoy-Digital >> (c) Copyright 2007-2018 M-Labs Limited >> Built *Jan 20* 2018 22:57:55 > > > Cloning a new repo and building the gateware and image again should work. > Ideally, make clean, and git pull should have been sufficient. > > Thanks & Regards, > Rohit > > On Mon, Jan 22, 2018 at 6:58 PM, Bing Chen wrote: > >> Hi Florent, >> >> Thanks for reply, I did another git pull in litex-buildenv and ran the >> download-env.sh again, still the same error when I tried: >> >> --- console msg copy --- >> >> chmod -x firmware.bin >> python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi >> make[1]: Leaving directory '/home/bing/litex- >> buildenv/build/arty_net_or1k.linux/software/firmware' >> >> real0m1.946s >> user0m2.593s >> sys0m0.413s >> flterm --port=/dev/ttyUSB1 -- >> kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- >> speed=115200 >> [FLTERM] Starting... >> >> LiteX SoC BIOS (or1k) >> (c) Copyright 2012-2017 Enjoy-Digital >> (c) Copyright 2007-2017 M-Labs Limited >> Built Jan 12 2018 04:46:47 >> >> BIOS CRC passed (046476c5) >> Initializing SDRAM... >> Read delays: 1:32-33 0:32-33 completed >> Memtest bus failed: 64/256 errors >> Memtest data failed: 524288/524288 errors >> Memtest addr failed: 8191/8192 errors >> Memory initialization failed >> BIOS> >> --- >> >> All the prework steps work fine on my box though. >> >> Regards >> bing >> >> On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: >> > Hi Bing, >> > >> > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make >> > me think your are not up to date on both litex and litex-buildenv >> > repository. (or maybe on just one of them) >> > >> > Can you check? >> > >> > Florent >> > >> > >> > 2018-01-22 7:43 GMT+01:00 Bing Chen : >> > > Hi Joel/Tim, >> > > >> > > Bing's here, I think my kit is faulty or something, when I tried >> > > testing loading gateware on it, I got this error msgs: >> > > >> > > --- console msg copy --- >> > > >> > > make[1]: Leaving directory '/home/bing/litex- >> > > buildenv/build/arty_net_or1k.linux/software/firmware' >> > > >> > > real0m1.135s >> > > user0m1.046s >> > > sys0m0.096s >> > > flterm --port=/dev/ttyUSB1 -- >> > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- >> > > speed=115200 >> > > [FLTERM] Starting... >> > > >> > > LiteX SoC BIOS (or1k) >> > > (c) Copyright 2012-2017 Enjoy-Digital >> > > (c) Copyright 2007-2017 M-Labs Limited >> > > Built Jan 12 2018 04:46:47 >> > > >> > > BIOS CRC passed (046476c5) >> > > Initializing SDRAM... >> > > Read delays: 1:32-33 0:32-33 completed >> > > Memtest bus failed: 64/256 errors >> > > Memtest data failed: 524288/524288 errors >> > > Memtest addr failed: 8191/8192 errors >> > > Memory initialization failed >> > > BIOS> >> > > >> > > ---- >> > > >> > > Then I tried run serialboot and it stuck at "Executing booted >> > > program >> > > at 0x40000000" >> > > >> > > ---- console msg copy ---- >> > > >> > > BIOS> serialboot >> > > Booting from serial... >> > > Press Q or ESC to abort boot completely. >> > > sL5DdSMmkekro >> > > [FLTERM] Received firmware download request from the device. >> > > [FLTERM] Uploading kernel (74672 bytes)... >> > > [FLTERM] Upload complete (7.7KB/s). >> > > [FLTERM] Booting the device. >> > > [FLTERM] Done. >> > > Executing booted program at 0x40000000 >> > > >> > > ---- >> > > >> > > >> > > Regards >> > > bing >> > > >> > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: >> > > > I will be at the top of the stairs at 3pm with the kits. I'm in a >> > > > blue tshirt. Come say hi and grab your kit. >> > > > >> > > > Cheers, >> > > > >> > > > Joel >> > > > >> > > > >> > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: >> > > > > For that matter, could I drop in later today to grab the kit so >> > > I'm >> > > > > ready for tomorrow's session, latest changes and all. >> > > > > >> > > > > Thanks. >> > > > > >> > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner > > > gmai >> > > > > l.com> wrote: >> > > > > > Hey guys. Where are you set up today? >> > > > > > >> > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" >> > > > > > wrote: >> > > > > > > Hello everyone, >> > > > > > > >> > > > > > > With just over 24 hours until the FPGA Miniconf, this is >> > > the >> > > > > > > final reminder that everyone **must** complete the prework >> > > at h >> > > > > > > ttp://j.mp/pre-fpga-lca2018 >> > > > > > > >> > > > > > > You must complete up to the paragraph which says the >> > > following >> > > > > > > in bright red; >> > > > > > > > The instructions from here can only be done after you >> > > receive >> > > > > > > > hardware. You can stop here if completing the prework. >> > > > > > > >> > > > > > > If you have not completed the prework you will not be able >> > > to >> > > > > > > attend -- that includes observing or anything similar. >> > > > > > > >> > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf >> > > helpers >> > > > > > > will be available to help. They should be available during >> > > > > > > morning tea, lunch and afternoon tea somewhere near the >> > > Tomu >> > > > > > > test station. Hopefully they will be able to solve any >> > > issues >> > > > > > > you are having. >> > > > > > > >> > > > > > > There will also be an opportunity to pick up the hardware >> > > kits >> > > > > > > during lunch at the same location. This will allow you to >> > > get a >> > > > > > > head start on setup we need to do at the start of the >> > > Miniconf. >> > > > > > > >> > > > > > > It would be a good for everyone to update their litex- >> > > buildenv >> > > > > > > sometime Monday evening -- there have been a large number >> > > of >> > > > > > > updates since the last email was sent out. This can be done >> > > by >> > > > > > > doing the following and then following the prework >> > > instructions >> > > > > > > for testing QEmu / Linux. >> > > > > > > > cd litex-buildenv >> > > > > > > > git pull >> > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net >> > > > > > > > ./scripts/download-env.sh >> > > > > > > > source ./scripts/enter-env.sh >> > > > > > > >> > > > > > > Depending on internet speeds, updating should only take 10- >> > > 15 >> > > > > > > minutes. >> > > > > > > >> > > > > > > People are also reminded that the FPGA Miniconf is on >> > > Tuesday, >> > > > > > > 23 January 2018 and will be starting at 10:15AM. This is >> > > right >> > > > > > > after the Matthew Todd's keynote talk. Please make sure you >> > > > > > > make a beeline from the keynote venue to Large POD Room >> > > > > > > CB11.04.400 when the keynote finishes. Please see the >> > > schedule >> > > > > > > email for the full details. >> > > > > > > >> > > > > > > Look forward to seeing everyone on Tuesday! >> > > > > > > >> > > > > > > Tim 'mithro' Ansell >> > > > > > > >> > > > > > > -- >> > > > > > > fpga-miniconf mailing list >> > > > > > > fpga-miniconf at lists.lca2018.linux.org.au >> > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-min >> > > icon >> > > > > > > f >> > > > > > > >> > > > > > >> > > > > > -- >> > > > > > fpga-miniconf mailing list >> > > > > > fpga-miniconf at lists.lca2018.linux.org.au >> > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minic >> > > onf >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > -- >> > > > > Teach your kids Science, or somebody else will :/ >> > > > > >> > > > > jason at ball.net >> > > > > vk2vjb at google.com >> > > > > callsign: vk2vjb >> > > > > >> > > > > >> > > > > -- >> > > > > fpga-miniconf mailing list >> > > > > fpga-miniconf at lists.lca2018.linux.org.au >> > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon >> > > f >> > > > > >> > > > >> > > > >> > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and >> > > any accompanying attachments may contain confidential information. >> > > If you are not the intended recipient, do not read, use, >> > > disseminate, distribute or copy this message or attachments. If you >> > > have received this message in error, please notify the sender >> > > immediately and delete this message. Any views expressed in this >> > > message are those of the individual sender, except where the sender >> > > expressly, and with authority, states them to be the views of the >> > > University of Technology Sydney. Before opening any attachments, >> > > please check them for viruses and defects. Think. Green. Do. Please >> > > consider the environment before printing this email. >> > > -- >> > > fpga-miniconf mailing list >> > > fpga-miniconf at lists.lca2018.linux.org.au >> > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> > >> > >> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any >> accompanying attachments may contain confidential information. If you are >> not the intended recipient, do not read, use, disseminate, distribute or >> copy this message or attachments. If you have received this message in >> error, please notify the sender immediately and delete this message. Any >> views expressed in this message are those of the individual sender, except >> where the sender expressly, and with authority, states them to be the views >> of the University of Technology Sydney. Before opening any attachments, >> please check them for viruses and defects. Think. Green. Do. Please >> consider the environment before printing this email. >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> > > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mibus at mibus.org Mon Jan 22 20:19:34 2018 From: mibus at mibus.org (Robert Mibus) Date: Mon, 22 Jan 2018 09:19:34 +0000 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> Message-ID: I had the same problem as Bing (the "BIOS>" prompt and it showing an older build date than I expected, despite having re-run all the "make"s etc). I ran "make clean" (I'd already done a git pull) and re-ran the verification steps from the doc. I also had to change USB ports on my laptop (one of them is a bit particular about devices; it saw the USB hub but didn't work with the USB ethernet adapter) and set up /etc/network/interfaces per the doc. Now I'm TFTP-loading the kernel via "make firmware-load" and so far so good... On Mon, Jan 22, 2018 at 7:25 PM Rohit Kumar Singh wrote: > Hi Bing! > > Sorry for repeat mail! I forgot to cc the mailing list in the last reply. > > I'm guessing your litex/litex-buildenv still might old. Because here is > what I get: > > LiteX SoC BIOS (or1k) >> (c) Copyright 2012-2018 Enjoy-Digital >> (c) Copyright 2007-2018 M-Labs Limited >> Built *Jan 20* 2018 22:57:55 > > > Cloning a new repo and building the gateware and image again should work. > Ideally, make clean, and git pull should have been sufficient. > > Thanks & Regards, > Rohit > > On Mon, Jan 22, 2018 at 6:58 PM, Bing Chen wrote: > >> Hi Florent, >> >> Thanks for reply, I did another git pull in litex-buildenv and ran the >> download-env.sh again, still the same error when I tried: >> >> --- console msg copy --- >> >> chmod -x firmware.bin >> python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi >> make[1]: Leaving directory '/home/bing/litex- >> buildenv/build/arty_net_or1k.linux/software/firmware' >> >> real0m1.946s >> user0m2.593s >> sys0m0.413s >> flterm --port=/dev/ttyUSB1 -- >> kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- >> speed=115200 >> [FLTERM] Starting... >> >> LiteX SoC BIOS (or1k) >> (c) Copyright 2012-2017 Enjoy-Digital >> (c) Copyright 2007-2017 M-Labs Limited >> Built Jan 12 2018 04:46:47 >> >> BIOS CRC passed (046476c5) >> Initializing SDRAM... >> Read delays: 1:32-33 0:32-33 completed >> Memtest bus failed: 64/256 errors >> Memtest data failed: 524288/524288 errors >> Memtest addr failed: 8191/8192 errors >> Memory initialization failed >> BIOS> >> --- >> >> All the prework steps work fine on my box though. >> >> Regards >> bing >> >> On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: >> > Hi Bing, >> > >> > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make >> > me think your are not up to date on both litex and litex-buildenv >> > repository. (or maybe on just one of them) >> > >> > Can you check? >> > >> > Florent >> > >> > >> > 2018-01-22 7:43 GMT+01:00 Bing Chen : >> > > Hi Joel/Tim, >> > > >> > > Bing's here, I think my kit is faulty or something, when I tried >> > > testing loading gateware on it, I got this error msgs: >> > > >> > > --- console msg copy --- >> > > >> > > make[1]: Leaving directory '/home/bing/litex- >> > > buildenv/build/arty_net_or1k.linux/software/firmware' >> > > >> > > real0m1.135s >> > > user0m1.046s >> > > sys0m0.096s >> > > flterm --port=/dev/ttyUSB1 -- >> > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- >> > > speed=115200 >> > > [FLTERM] Starting... >> > > >> > > LiteX SoC BIOS (or1k) >> > > (c) Copyright 2012-2017 Enjoy-Digital >> > > (c) Copyright 2007-2017 M-Labs Limited >> > > Built Jan 12 2018 04:46:47 >> > > >> > > BIOS CRC passed (046476c5) >> > > Initializing SDRAM... >> > > Read delays: 1:32-33 0:32-33 completed >> > > Memtest bus failed: 64/256 errors >> > > Memtest data failed: 524288/524288 errors >> > > Memtest addr failed: 8191/8192 errors >> > > Memory initialization failed >> > > BIOS> >> > > >> > > ---- >> > > >> > > Then I tried run serialboot and it stuck at "Executing booted >> > > program >> > > at 0x40000000" >> > > >> > > ---- console msg copy ---- >> > > >> > > BIOS> serialboot >> > > Booting from serial... >> > > Press Q or ESC to abort boot completely. >> > > sL5DdSMmkekro >> > > [FLTERM] Received firmware download request from the device. >> > > [FLTERM] Uploading kernel (74672 bytes)... >> > > [FLTERM] Upload complete (7.7KB/s). >> > > [FLTERM] Booting the device. >> > > [FLTERM] Done. >> > > Executing booted program at 0x40000000 >> > > >> > > ---- >> > > >> > > >> > > Regards >> > > bing >> > > >> > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: >> > > > I will be at the top of the stairs at 3pm with the kits. I'm in a >> > > > blue tshirt. Come say hi and grab your kit. >> > > > >> > > > Cheers, >> > > > >> > > > Joel >> > > > >> > > > >> > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: >> > > > > For that matter, could I drop in later today to grab the kit so >> > > I'm >> > > > > ready for tomorrow's session, latest changes and all. >> > > > > >> > > > > Thanks. >> > > > > >> > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner > > > gmai >> > > > > l.com> wrote: >> > > > > > Hey guys. Where are you set up today? >> > > > > > >> > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" >> > > > > > wrote: >> > > > > > > Hello everyone, >> > > > > > > >> > > > > > > With just over 24 hours until the FPGA Miniconf, this is >> > > the >> > > > > > > final reminder that everyone **must** complete the prework >> > > at h >> > > > > > > ttp://j.mp/pre-fpga-lca2018 >> > > > > > > >> > > > > > > You must complete up to the paragraph which says the >> > > following >> > > > > > > in bright red; >> > > > > > > > The instructions from here can only be done after you >> > > receive >> > > > > > > > hardware. You can stop here if completing the prework. >> > > > > > > >> > > > > > > If you have not completed the prework you will not be able >> > > to >> > > > > > > attend -- that includes observing or anything similar. >> > > > > > > >> > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf >> > > helpers >> > > > > > > will be available to help. They should be available during >> > > > > > > morning tea, lunch and afternoon tea somewhere near the >> > > Tomu >> > > > > > > test station. Hopefully they will be able to solve any >> > > issues >> > > > > > > you are having. >> > > > > > > >> > > > > > > There will also be an opportunity to pick up the hardware >> > > kits >> > > > > > > during lunch at the same location. This will allow you to >> > > get a >> > > > > > > head start on setup we need to do at the start of the >> > > Miniconf. >> > > > > > > >> > > > > > > It would be a good for everyone to update their litex- >> > > buildenv >> > > > > > > sometime Monday evening -- there have been a large number >> > > of >> > > > > > > updates since the last email was sent out. This can be done >> > > by >> > > > > > > doing the following and then following the prework >> > > instructions >> > > > > > > for testing QEmu / Linux. >> > > > > > > > cd litex-buildenv >> > > > > > > > git pull >> > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net >> > > > > > > > ./scripts/download-env.sh >> > > > > > > > source ./scripts/enter-env.sh >> > > > > > > >> > > > > > > Depending on internet speeds, updating should only take 10- >> > > 15 >> > > > > > > minutes. >> > > > > > > >> > > > > > > People are also reminded that the FPGA Miniconf is on >> > > Tuesday, >> > > > > > > 23 January 2018 and will be starting at 10:15AM. This is >> > > right >> > > > > > > after the Matthew Todd's keynote talk. Please make sure you >> > > > > > > make a beeline from the keynote venue to Large POD Room >> > > > > > > CB11.04.400 when the keynote finishes. Please see the >> > > schedule >> > > > > > > email for the full details. >> > > > > > > >> > > > > > > Look forward to seeing everyone on Tuesday! >> > > > > > > >> > > > > > > Tim 'mithro' Ansell >> > > > > > > >> > > > > > > -- >> > > > > > > fpga-miniconf mailing list >> > > > > > > fpga-miniconf at lists.lca2018.linux.org.au >> > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-min >> > > icon >> > > > > > > f >> > > > > > > >> > > > > > >> > > > > > -- >> > > > > > fpga-miniconf mailing list >> > > > > > fpga-miniconf at lists.lca2018.linux.org.au >> > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minic >> > > onf >> > > > > > >> > > > > >> > > > > >> > > > > >> > > > > -- >> > > > > -- >> > > > > Teach your kids Science, or somebody else will :/ >> > > > > >> > > > > jason at ball.net >> > > > > vk2vjb at google.com >> > > > > callsign: vk2vjb >> > > > > >> > > > > >> > > > > -- >> > > > > fpga-miniconf mailing list >> > > > > fpga-miniconf at lists.lca2018.linux.org.au >> > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon >> > > f >> > > > > >> > > > >> > > > >> > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and >> > > any accompanying attachments may contain confidential information. >> > > If you are not the intended recipient, do not read, use, >> > > disseminate, distribute or copy this message or attachments. If you >> > > have received this message in error, please notify the sender >> > > immediately and delete this message. Any views expressed in this >> > > message are those of the individual sender, except where the sender >> > > expressly, and with authority, states them to be the views of the >> > > University of Technology Sydney. Before opening any attachments, >> > > please check them for viruses and defects. Think. Green. Do. Please >> > > consider the environment before printing this email. >> > > -- >> > > fpga-miniconf mailing list >> > > fpga-miniconf at lists.lca2018.linux.org.au >> > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> > >> > >> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any >> accompanying attachments may contain confidential information. If you are >> not the intended recipient, do not read, use, disseminate, distribute or >> copy this message or attachments. If you have received this message in >> error, please notify the sender immediately and delete this message. Any >> views expressed in this message are those of the individual sender, except >> where the sender expressly, and with authority, states them to be the views >> of the University of Technology Sydney. Before opening any attachments, >> please check them for viruses and defects. Think. Green. Do. Please >> consider the environment before printing this email. >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -- Robert Mibus -------------- next part -------------- An HTML attachment was scrubbed... URL: From Libing.Chen at uts.edu.au Tue Jan 23 00:42:00 2018 From: Libing.Chen at uts.edu.au (Bing Chen) Date: Mon, 22 Jan 2018 13:42:00 +0000 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> , Message-ID: Hi Jim, Rohit, After a 'make clean' and re-make I finally got the buildroot login, thanks for the help! Regards Bing Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Jim Mussared Date: 22/1/18 8:18 pm (GMT+10:00) To: Rohit Kumar Singh Cc: Bing Chen , fpga-miniconf at lists.lca2018.linux.org.au, me at mith.ro Subject: Re: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... Rather than recloning the whole repo, it shpuld be sufficient just to git pull in litex-buildenv, then make gateware / make image (make gateware should update all the submodules, including litex, which is what Florent is referring to). Unless I missed something, doesn't look like you made a new gateware since doing a pull (just reflashed the old one) On 22 Jan. 2018 7:25 pm, "Rohit Kumar Singh" > wrote: Hi Bing! Sorry for repeat mail! I forgot to cc the mailing list in the last reply. I'm guessing your litex/litex-buildenv still might old. Because here is what I get: LiteX SoC BIOS (or1k) (c) Copyright 2012-2018 Enjoy-Digital (c) Copyright 2007-2018 M-Labs Limited Built Jan 20 2018 22:57:55 Cloning a new repo and building the gateware and image again should work. Ideally, make clean, and git pull should have been sufficient. Thanks & Regards, Rohit On Mon, Jan 22, 2018 at 6:58 PM, Bing Chen > wrote: Hi Florent, Thanks for reply, I did another git pull in litex-buildenv and ran the download-env.sh again, still the same error when I tried: --- console msg copy --- chmod -x firmware.bin python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi make[1]: Leaving directory '/home/bing/litex- buildenv/build/arty_net_or1k.linux/software/firmware' real0m1.946s user0m2.593s sys0m0.413s flterm --port=/dev/ttyUSB1 -- kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- speed=115200 [FLTERM] Starting... LiteX SoC BIOS (or1k) (c) Copyright 2012-2017 Enjoy-Digital (c) Copyright 2007-2017 M-Labs Limited Built Jan 12 2018 04:46:47 BIOS CRC passed (046476c5) Initializing SDRAM... Read delays: 1:32-33 0:32-33 completed Memtest bus failed: 64/256 errors Memtest data failed: 524288/524288 errors Memtest addr failed: 8191/8192 errors Memory initialization failed BIOS> --- All the prework steps work fine on my box though. Regards bing On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: > Hi Bing, > > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make > me think your are not up to date on both litex and litex-buildenv > repository. (or maybe on just one of them) > > Can you check? > > Florent > > > 2018-01-22 7:43 GMT+01:00 Bing Chen >: > > Hi Joel/Tim, > > > > Bing's here, I think my kit is faulty or something, when I tried > > testing loading gateware on it, I got this error msgs: > > > > --- console msg copy --- > > > > make[1]: Leaving directory '/home/bing/litex- > > buildenv/build/arty_net_or1k.linux/software/firmware' > > > > real0m1.135s > > user0m1.046s > > sys0m0.096s > > flterm --port=/dev/ttyUSB1 -- > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- > > speed=115200 > > [FLTERM] Starting... > > > > LiteX SoC BIOS (or1k) > > (c) Copyright 2012-2017 Enjoy-Digital > > (c) Copyright 2007-2017 M-Labs Limited > > Built Jan 12 2018 04:46:47 > > > > BIOS CRC passed (046476c5) > > Initializing SDRAM... > > Read delays: 1:32-33 0:32-33 completed > > Memtest bus failed: 64/256 errors > > Memtest data failed: 524288/524288 errors > > Memtest addr failed: 8191/8192 errors > > Memory initialization failed > > BIOS> > > > > ---- > > > > Then I tried run serialboot and it stuck at "Executing booted > > program > > at 0x40000000" > > > > ---- console msg copy ---- > > > > BIOS> serialboot > > Booting from serial... > > Press Q or ESC to abort boot completely. > > sL5DdSMmkekro > > [FLTERM] Received firmware download request from the device. > > [FLTERM] Uploading kernel (74672 bytes)... > > [FLTERM] Upload complete (7.7KB/s). > > [FLTERM] Booting the device. > > [FLTERM] Done. > > Executing booted program at 0x40000000 > > > > ---- > > > > > > Regards > > bing > > > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: > > > I will be at the top of the stairs at 3pm with the kits. I'm in a > > > blue tshirt. Come say hi and grab your kit. > > > > > > Cheers, > > > > > > Joel > > > > > > > > > On 22 Jan. 2018 13:14, "Jason Ball" > wrote: > > > > For that matter, could I drop in later today to grab the kit so > > I'm > > > > ready for tomorrow's session, latest changes and all. > > > > > > > > Thanks. > > > > > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner > gmai > > > > l.com> wrote: > > > > > Hey guys. Where are you set up today? > > > > > > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" > > > > > > wrote: > > > > > > Hello everyone, > > > > > > > > > > > > With just over 24 hours until the FPGA Miniconf, this is > > the > > > > > > final reminder that everyone **must** complete the prework > > at h > > > > > > ttp://j.mp/pre-fpga-lca2018 > > > > > > > > > > > > You must complete up to the paragraph which says the > > following > > > > > > in bright red; > > > > > > > The instructions from here can only be done after you > > receive > > > > > > > hardware. You can stop here if completing the prework. > > > > > > > > > > > > If you have not completed the prework you will not be able > > to > > > > > > attend -- that includes observing or anything similar. > > > > > > > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf > > helpers > > > > > > will be available to help. They should be available during > > > > > > morning tea, lunch and afternoon tea somewhere near the > > Tomu > > > > > > test station. Hopefully they will be able to solve any > > issues > > > > > > you are having. > > > > > > > > > > > > There will also be an opportunity to pick up the hardware > > kits > > > > > > during lunch at the same location. This will allow you to > > get a > > > > > > head start on setup we need to do at the start of the > > Miniconf. > > > > > > > > > > > > It would be a good for everyone to update their litex- > > buildenv > > > > > > sometime Monday evening -- there have been a large number > > of > > > > > > updates since the last email was sent out. This can be done > > by > > > > > > doing the following and then following the prework > > instructions > > > > > > for testing QEmu / Linux. > > > > > > > cd litex-buildenv > > > > > > > git pull > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net > > > > > > > ./scripts/download-env.sh > > > > > > > source ./scripts/enter-env.sh > > > > > > > > > > > > Depending on internet speeds, updating should only take 10- > > 15 > > > > > > minutes. > > > > > > > > > > > > People are also reminded that the FPGA Miniconf is on > > Tuesday, > > > > > > 23 January 2018 and will be starting at 10:15AM. This is > > right > > > > > > after the Matthew Todd's keynote talk. Please make sure you > > > > > > make a beeline from the keynote venue to Large POD Room > > > > > > CB11.04.400 when the keynote finishes. Please see the > > schedule > > > > > > email for the full details. > > > > > > > > > > > > Look forward to seeing everyone on Tuesday! > > > > > > > > > > > > Tim 'mithro' Ansell > > > > > > > > > > > > -- > > > > > > fpga-miniconf mailing list > > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-min > > icon > > > > > > f > > > > > > > > > > > > > > > > -- > > > > > fpga-miniconf mailing list > > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minic > > onf > > > > > > > > > > > > > > > > > > > > > -- > > > > -- > > > > Teach your kids Science, or somebody else will :/ > > > > > > > > jason at ball.net > > > > vk2vjb at google.com > > > > callsign: vk2vjb > > > > > > > > > > > > -- > > > > fpga-miniconf mailing list > > > > fpga-miniconf at lists.lca2018.linux.org.au > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon > > f > > > > > > > > > > > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and > > any accompanying attachments may contain confidential information. > > If you are not the intended recipient, do not read, use, > > disseminate, distribute or copy this message or attachments. If you > > have received this message in error, please notify the sender > > immediately and delete this message. Any views expressed in this > > message are those of the individual sender, except where the sender > > expressly, and with authority, states them to be the views of the > > University of Technology Sydney. Before opening any attachments, > > please check them for viruses and defects. Think. Green. Do. Please > > consider the environment before printing this email. > > -- > > fpga-miniconf mailing list > > fpga-miniconf at lists.lca2018.linux.org.au > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. -- fpga-miniconf mailing list fpga-miniconf at lists.lca2018.linux.org.au http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf -- fpga-miniconf mailing list fpga-miniconf at lists.lca2018.linux.org.au http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects. Think. Green. Do. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan at ryant.org Tue Jan 23 09:52:06 2018 From: ryan at ryant.org (Ryan Thomas) Date: Tue, 23 Jan 2018 09:52:06 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> Message-ID: I had this working last week, but today I decided to update and rebuild it with the new litex commits. Now after *make gateware; make image; scripts/build-qemu.sh* I get the following: Booting from network... Local IP : 192.168.100.50 Remote IP: 192.168.100.100 Fetching from: UDP/6069 And it just sits there, with the qemu-system-or32 process at 100%. Any help / ideas for how to rectify this? Cheers, Ryan On 23 January 2018 at 00:42, Bing Chen wrote: > Hi Jim, Rohit, > > After a 'make clean' and re-make I finally got the buildroot login, thanks > for the help! > > Regards > Bing > Sent from my Samsung Galaxy smartphone. > > > -------- Original message -------- > From: Jim Mussared > Date: 22/1/18 8:18 pm (GMT+10:00) > To: Rohit Kumar Singh > Cc: Bing Chen , fpga-miniconf at lists.lca2018. > linux.org.au, me at mith.ro > Subject: Re: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and > other notes.... > > Rather than recloning the whole repo, it shpuld be sufficient just to git > pull in litex-buildenv, then make gateware / make image (make gateware > should update all the submodules, including litex, which is what Florent is > referring to). > > Unless I missed something, doesn't look like you made a new gateware since > doing a pull (just reflashed the old one) > > On 22 Jan. 2018 7:25 pm, "Rohit Kumar Singh" > wrote: > >> Hi Bing! >> >> Sorry for repeat mail! I forgot to cc the mailing list in the last reply. >> >> I'm guessing your litex/litex-buildenv still might old. Because here is >> what I get: >> >> LiteX SoC BIOS (or1k) >>> (c) Copyright 2012-2018 Enjoy-Digital >>> (c) Copyright 2007-2018 M-Labs Limited >>> Built *Jan 20* 2018 22:57:55 >> >> >> Cloning a new repo and building the gateware and image again should >> work. Ideally, make clean, and git pull should have been sufficient. >> >> Thanks & Regards, >> Rohit >> >> On Mon, Jan 22, 2018 at 6:58 PM, Bing Chen >> wrote: >> >>> Hi Florent, >>> >>> Thanks for reply, I did another git pull in litex-buildenv and ran the >>> download-env.sh again, still the same error when I tried: >>> >>> --- console msg copy --- >>> >>> chmod -x firmware.bin >>> python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi >>> make[1]: Leaving directory '/home/bing/litex- >>> buildenv/build/arty_net_or1k.linux/software/firmware' >>> >>> real0m1.946s >>> user0m2.593s >>> sys0m0.413s >>> flterm --port=/dev/ttyUSB1 -- >>> kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- >>> speed=115200 >>> [FLTERM] Starting... >>> >>> LiteX SoC BIOS (or1k) >>> (c) Copyright 2012-2017 Enjoy-Digital >>> (c) Copyright 2007-2017 M-Labs Limited >>> Built Jan 12 2018 04:46:47 >>> >>> BIOS CRC passed (046476c5) >>> Initializing SDRAM... >>> Read delays: 1:32-33 0:32-33 completed >>> Memtest bus failed: 64/256 errors >>> Memtest data failed: 524288/524288 errors >>> Memtest addr failed: 8191/8192 errors >>> Memory initialization failed >>> BIOS> >>> --- >>> >>> All the prework steps work fine on my box though. >>> >>> Regards >>> bing >>> >>> On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: >>> > Hi Bing, >>> > >>> > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make >>> > me think your are not up to date on both litex and litex-buildenv >>> > repository. (or maybe on just one of them) >>> > >>> > Can you check? >>> > >>> > Florent >>> > >>> > >>> > 2018-01-22 7:43 GMT+01:00 Bing Chen : >>> > > Hi Joel/Tim, >>> > > >>> > > Bing's here, I think my kit is faulty or something, when I tried >>> > > testing loading gateware on it, I got this error msgs: >>> > > >>> > > --- console msg copy --- >>> > > >>> > > make[1]: Leaving directory '/home/bing/litex- >>> > > buildenv/build/arty_net_or1k.linux/software/firmware' >>> > > >>> > > real0m1.135s >>> > > user0m1.046s >>> > > sys0m0.096s >>> > > flterm --port=/dev/ttyUSB1 -- >>> > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- >>> > > speed=115200 >>> > > [FLTERM] Starting... >>> > > >>> > > LiteX SoC BIOS (or1k) >>> > > (c) Copyright 2012-2017 Enjoy-Digital >>> > > (c) Copyright 2007-2017 M-Labs Limited >>> > > Built Jan 12 2018 04:46:47 >>> > > >>> > > BIOS CRC passed (046476c5) >>> > > Initializing SDRAM... >>> > > Read delays: 1:32-33 0:32-33 completed >>> > > Memtest bus failed: 64/256 errors >>> > > Memtest data failed: 524288/524288 errors >>> > > Memtest addr failed: 8191/8192 errors >>> > > Memory initialization failed >>> > > BIOS> >>> > > >>> > > ---- >>> > > >>> > > Then I tried run serialboot and it stuck at "Executing booted >>> > > program >>> > > at 0x40000000" >>> > > >>> > > ---- console msg copy ---- >>> > > >>> > > BIOS> serialboot >>> > > Booting from serial... >>> > > Press Q or ESC to abort boot completely. >>> > > sL5DdSMmkekro >>> > > [FLTERM] Received firmware download request from the device. >>> > > [FLTERM] Uploading kernel (74672 bytes)... >>> > > [FLTERM] Upload complete (7.7KB/s). >>> > > [FLTERM] Booting the device. >>> > > [FLTERM] Done. >>> > > Executing booted program at 0x40000000 >>> > > >>> > > ---- >>> > > >>> > > >>> > > Regards >>> > > bing >>> > > >>> > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: >>> > > > I will be at the top of the stairs at 3pm with the kits. I'm in a >>> > > > blue tshirt. Come say hi and grab your kit. >>> > > > >>> > > > Cheers, >>> > > > >>> > > > Joel >>> > > > >>> > > > >>> > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: >>> > > > > For that matter, could I drop in later today to grab the kit so >>> > > I'm >>> > > > > ready for tomorrow's session, latest changes and all. >>> > > > > >>> > > > > Thanks. >>> > > > > >>> > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner >> > > gmai >>> > > > > l.com> wrote: >>> > > > > > Hey guys. Where are you set up today? >>> > > > > > >>> > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" >>> > > > > > wrote: >>> > > > > > > Hello everyone, >>> > > > > > > >>> > > > > > > With just over 24 hours until the FPGA Miniconf, this is >>> > > the >>> > > > > > > final reminder that everyone **must** complete the prework >>> > > at h >>> > > > > > > ttp://j.mp/pre-fpga-lca2018 >>> > > > > > > >>> > > > > > > You must complete up to the paragraph which says the >>> > > following >>> > > > > > > in bright red; >>> > > > > > > > The instructions from here can only be done after you >>> > > receive >>> > > > > > > > hardware. You can stop here if completing the prework. >>> > > > > > > >>> > > > > > > If you have not completed the prework you will not be able >>> > > to >>> > > > > > > attend -- that includes observing or anything similar. >>> > > > > > > >>> > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf >>> > > helpers >>> > > > > > > will be available to help. They should be available during >>> > > > > > > morning tea, lunch and afternoon tea somewhere near the >>> > > Tomu >>> > > > > > > test station. Hopefully they will be able to solve any >>> > > issues >>> > > > > > > you are having. >>> > > > > > > >>> > > > > > > There will also be an opportunity to pick up the hardware >>> > > kits >>> > > > > > > during lunch at the same location. This will allow you to >>> > > get a >>> > > > > > > head start on setup we need to do at the start of the >>> > > Miniconf. >>> > > > > > > >>> > > > > > > It would be a good for everyone to update their litex- >>> > > buildenv >>> > > > > > > sometime Monday evening -- there have been a large number >>> > > of >>> > > > > > > updates since the last email was sent out. This can be done >>> > > by >>> > > > > > > doing the following and then following the prework >>> > > instructions >>> > > > > > > for testing QEmu / Linux. >>> > > > > > > > cd litex-buildenv >>> > > > > > > > git pull >>> > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net >>> > > > > > > > ./scripts/download-env.sh >>> > > > > > > > source ./scripts/enter-env.sh >>> > > > > > > >>> > > > > > > Depending on internet speeds, updating should only take 10- >>> > > 15 >>> > > > > > > minutes. >>> > > > > > > >>> > > > > > > People are also reminded that the FPGA Miniconf is on >>> > > Tuesday, >>> > > > > > > 23 January 2018 and will be starting at 10:15AM. This is >>> > > right >>> > > > > > > after the Matthew Todd's keynote talk. Please make sure you >>> > > > > > > make a beeline from the keynote venue to Large POD Room >>> > > > > > > CB11.04.400 when the keynote finishes. Please see the >>> > > schedule >>> > > > > > > email for the full details. >>> > > > > > > >>> > > > > > > Look forward to seeing everyone on Tuesday! >>> > > > > > > >>> > > > > > > Tim 'mithro' Ansell >>> > > > > > > >>> > > > > > > -- >>> > > > > > > fpga-miniconf mailing list >>> > > > > > > fpga-miniconf at lists.lca2018.linux.org.au >>> > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-min >>> > > icon >>> > > > > > > f >>> > > > > > > >>> > > > > > >>> > > > > > -- >>> > > > > > fpga-miniconf mailing list >>> > > > > > fpga-miniconf at lists.lca2018.linux.org.au >>> > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minic >>> > > onf >>> > > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > -- >>> > > > > -- >>> > > > > Teach your kids Science, or somebody else will :/ >>> > > > > >>> > > > > jason at ball.net >>> > > > > vk2vjb at google.com >>> > > > > callsign: vk2vjb >>> > > > > >>> > > > > >>> > > > > -- >>> > > > > fpga-miniconf mailing list >>> > > > > fpga-miniconf at lists.lca2018.linux.org.au >>> > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon >>> > > f >>> > > > > >>> > > > >>> > > > >>> > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and >>> > > any accompanying attachments may contain confidential information. >>> > > If you are not the intended recipient, do not read, use, >>> > > disseminate, distribute or copy this message or attachments. If you >>> > > have received this message in error, please notify the sender >>> > > immediately and delete this message. Any views expressed in this >>> > > message are those of the individual sender, except where the sender >>> > > expressly, and with authority, states them to be the views of the >>> > > University of Technology Sydney. Before opening any attachments, >>> > > please check them for viruses and defects. Think. Green. Do. Please >>> > > consider the environment before printing this email. >>> > > -- >>> > > fpga-miniconf mailing list >>> > > fpga-miniconf at lists.lca2018.linux.org.au >>> > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>> > >>> > >>> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any >>> accompanying attachments may contain confidential information. If you are >>> not the intended recipient, do not read, use, disseminate, distribute or >>> copy this message or attachments. If you have received this message in >>> error, please notify the sender immediately and delete this message. Any >>> views expressed in this message are those of the individual sender, except >>> where the sender expressly, and with authority, states them to be the views >>> of the University of Technology Sydney. Before opening any attachments, >>> please check them for viruses and defects. Think. Green. Do. Please >>> consider the environment before printing this email. >>> -- >>> fpga-miniconf mailing list >>> fpga-miniconf at lists.lca2018.linux.org.au >>> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>> >> >> >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> >> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any > accompanying attachments may contain confidential information. If you are > not the intended recipient, do not read, use, disseminate, distribute or > copy this message or attachments. If you have received this message in > error, please notify the sender immediately and delete this message. Any > views expressed in this message are those of the individual sender, except > where the sender expressly, and with authority, states them to be the views > of the University of Technology Sydney. Before opening any attachments, > please check them for viruses and defects. Think. Green. Do. Please > consider the environment before printing this email. > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From joel.stan at gmail.com Tue Jan 23 09:53:30 2018 From: joel.stan at gmail.com (joel.stan at gmail.com) Date: Mon, 22 Jan 2018 16:53:30 -0600 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> Message-ID: Try to "make clean" as repeat the steps On 23 Jan. 2018 09:52, "Ryan Thomas" wrote: > I had this working last week, but today I decided to update and rebuild it > with the new litex commits. > > Now after *make gateware; make image; scripts/build-qemu.sh* I get the > following: > > Booting from network... > Local IP : 192.168.100.50 > Remote IP: 192.168.100.100 > Fetching from: UDP/6069 > > And it just sits there, with the qemu-system-or32 process at 100%. > > Any help / ideas for how to rectify this? > > Cheers, > > Ryan > > On 23 January 2018 at 00:42, Bing Chen wrote: > >> Hi Jim, Rohit, >> >> After a 'make clean' and re-make I finally got the buildroot login, >> thanks for the help! >> >> Regards >> Bing >> Sent from my Samsung Galaxy smartphone. >> >> >> -------- Original message -------- >> From: Jim Mussared >> Date: 22/1/18 8:18 pm (GMT+10:00) >> To: Rohit Kumar Singh >> Cc: Bing Chen , fpga-miniconf at lists.lca2018.li >> nux.org.au, me at mith.ro >> Subject: Re: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and >> other notes.... >> >> Rather than recloning the whole repo, it shpuld be sufficient just to git >> pull in litex-buildenv, then make gateware / make image (make gateware >> should update all the submodules, including litex, which is what Florent is >> referring to). >> >> Unless I missed something, doesn't look like you made a new gateware >> since doing a pull (just reflashed the old one) >> >> On 22 Jan. 2018 7:25 pm, "Rohit Kumar Singh" >> wrote: >> >>> Hi Bing! >>> >>> Sorry for repeat mail! I forgot to cc the mailing list in the last reply. >>> >>> I'm guessing your litex/litex-buildenv still might old. Because here is >>> what I get: >>> >>> LiteX SoC BIOS (or1k) >>>> (c) Copyright 2012-2018 Enjoy-Digital >>>> (c) Copyright 2007-2018 M-Labs Limited >>>> Built *Jan 20* 2018 22:57:55 >>> >>> >>> Cloning a new repo and building the gateware and image again should >>> work. Ideally, make clean, and git pull should have been sufficient. >>> >>> Thanks & Regards, >>> Rohit >>> >>> On Mon, Jan 22, 2018 at 6:58 PM, Bing Chen >>> wrote: >>> >>>> Hi Florent, >>>> >>>> Thanks for reply, I did another git pull in litex-buildenv and ran the >>>> download-env.sh again, still the same error when I tried: >>>> >>>> --- console msg copy --- >>>> >>>> chmod -x firmware.bin >>>> python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi >>>> make[1]: Leaving directory '/home/bing/litex- >>>> buildenv/build/arty_net_or1k.linux/software/firmware' >>>> >>>> real0m1.946s >>>> user0m2.593s >>>> sys0m0.413s >>>> flterm --port=/dev/ttyUSB1 -- >>>> kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- >>>> speed=115200 >>>> [FLTERM] Starting... >>>> >>>> LiteX SoC BIOS (or1k) >>>> (c) Copyright 2012-2017 Enjoy-Digital >>>> (c) Copyright 2007-2017 M-Labs Limited >>>> Built Jan 12 2018 04:46:47 >>>> >>>> BIOS CRC passed (046476c5) >>>> Initializing SDRAM... >>>> Read delays: 1:32-33 0:32-33 completed >>>> Memtest bus failed: 64/256 errors >>>> Memtest data failed: 524288/524288 errors >>>> Memtest addr failed: 8191/8192 errors >>>> Memory initialization failed >>>> BIOS> >>>> --- >>>> >>>> All the prework steps work fine on my box though. >>>> >>>> Regards >>>> bing >>>> >>>> On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: >>>> > Hi Bing, >>>> > >>>> > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make >>>> > me think your are not up to date on both litex and litex-buildenv >>>> > repository. (or maybe on just one of them) >>>> > >>>> > Can you check? >>>> > >>>> > Florent >>>> > >>>> > >>>> > 2018-01-22 7:43 GMT+01:00 Bing Chen : >>>> > > Hi Joel/Tim, >>>> > > >>>> > > Bing's here, I think my kit is faulty or something, when I tried >>>> > > testing loading gateware on it, I got this error msgs: >>>> > > >>>> > > --- console msg copy --- >>>> > > >>>> > > make[1]: Leaving directory '/home/bing/litex- >>>> > > buildenv/build/arty_net_or1k.linux/software/firmware' >>>> > > >>>> > > real0m1.135s >>>> > > user0m1.046s >>>> > > sys0m0.096s >>>> > > flterm --port=/dev/ttyUSB1 -- >>>> > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin -- >>>> > > speed=115200 >>>> > > [FLTERM] Starting... >>>> > > >>>> > > LiteX SoC BIOS (or1k) >>>> > > (c) Copyright 2012-2017 Enjoy-Digital >>>> > > (c) Copyright 2007-2017 M-Labs Limited >>>> > > Built Jan 12 2018 04:46:47 >>>> > > >>>> > > BIOS CRC passed (046476c5) >>>> > > Initializing SDRAM... >>>> > > Read delays: 1:32-33 0:32-33 completed >>>> > > Memtest bus failed: 64/256 errors >>>> > > Memtest data failed: 524288/524288 errors >>>> > > Memtest addr failed: 8191/8192 errors >>>> > > Memory initialization failed >>>> > > BIOS> >>>> > > >>>> > > ---- >>>> > > >>>> > > Then I tried run serialboot and it stuck at "Executing booted >>>> > > program >>>> > > at 0x40000000" >>>> > > >>>> > > ---- console msg copy ---- >>>> > > >>>> > > BIOS> serialboot >>>> > > Booting from serial... >>>> > > Press Q or ESC to abort boot completely. >>>> > > sL5DdSMmkekro >>>> > > [FLTERM] Received firmware download request from the device. >>>> > > [FLTERM] Uploading kernel (74672 bytes)... >>>> > > [FLTERM] Upload complete (7.7KB/s). >>>> > > [FLTERM] Booting the device. >>>> > > [FLTERM] Done. >>>> > > Executing booted program at 0x40000000 >>>> > > >>>> > > ---- >>>> > > >>>> > > >>>> > > Regards >>>> > > bing >>>> > > >>>> > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: >>>> > > > I will be at the top of the stairs at 3pm with the kits. I'm in a >>>> > > > blue tshirt. Come say hi and grab your kit. >>>> > > > >>>> > > > Cheers, >>>> > > > >>>> > > > Joel >>>> > > > >>>> > > > >>>> > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: >>>> > > > > For that matter, could I drop in later today to grab the kit so >>>> > > I'm >>>> > > > > ready for tomorrow's session, latest changes and all. >>>> > > > > >>>> > > > > Thanks. >>>> > > > > >>>> > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner >>> > > gmai >>>> > > > > l.com> wrote: >>>> > > > > > Hey guys. Where are you set up today? >>>> > > > > > >>>> > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" >>>> > > > > > wrote: >>>> > > > > > > Hello everyone, >>>> > > > > > > >>>> > > > > > > With just over 24 hours until the FPGA Miniconf, this is >>>> > > the >>>> > > > > > > final reminder that everyone **must** complete the prework >>>> > > at h >>>> > > > > > > ttp://j.mp/pre-fpga-lca2018 >>>> > > > > > > >>>> > > > > > > You must complete up to the paragraph which says the >>>> > > following >>>> > > > > > > in bright red; >>>> > > > > > > > The instructions from here can only be done after you >>>> > > receive >>>> > > > > > > > hardware. You can stop here if completing the prework. >>>> > > > > > > >>>> > > > > > > If you have not completed the prework you will not be able >>>> > > to >>>> > > > > > > attend -- that includes observing or anything similar. >>>> > > > > > > >>>> > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf >>>> > > helpers >>>> > > > > > > will be available to help. They should be available during >>>> > > > > > > morning tea, lunch and afternoon tea somewhere near the >>>> > > Tomu >>>> > > > > > > test station. Hopefully they will be able to solve any >>>> > > issues >>>> > > > > > > you are having. >>>> > > > > > > >>>> > > > > > > There will also be an opportunity to pick up the hardware >>>> > > kits >>>> > > > > > > during lunch at the same location. This will allow you to >>>> > > get a >>>> > > > > > > head start on setup we need to do at the start of the >>>> > > Miniconf. >>>> > > > > > > >>>> > > > > > > It would be a good for everyone to update their litex- >>>> > > buildenv >>>> > > > > > > sometime Monday evening -- there have been a large number >>>> > > of >>>> > > > > > > updates since the last email was sent out. This can be done >>>> > > by >>>> > > > > > > doing the following and then following the prework >>>> > > instructions >>>> > > > > > > for testing QEmu / Linux. >>>> > > > > > > > cd litex-buildenv >>>> > > > > > > > git pull >>>> > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net >>>> > > > > > > > ./scripts/download-env.sh >>>> > > > > > > > source ./scripts/enter-env.sh >>>> > > > > > > >>>> > > > > > > Depending on internet speeds, updating should only take 10- >>>> > > 15 >>>> > > > > > > minutes. >>>> > > > > > > >>>> > > > > > > People are also reminded that the FPGA Miniconf is on >>>> > > Tuesday, >>>> > > > > > > 23 January 2018 and will be starting at 10:15AM. This is >>>> > > right >>>> > > > > > > after the Matthew Todd's keynote talk. Please make sure you >>>> > > > > > > make a beeline from the keynote venue to Large POD Room >>>> > > > > > > CB11.04.400 when the keynote finishes. Please see the >>>> > > schedule >>>> > > > > > > email for the full details. >>>> > > > > > > >>>> > > > > > > Look forward to seeing everyone on Tuesday! >>>> > > > > > > >>>> > > > > > > Tim 'mithro' Ansell >>>> > > > > > > >>>> > > > > > > -- >>>> > > > > > > fpga-miniconf mailing list >>>> > > > > > > fpga-miniconf at lists.lca2018.linux.org.au >>>> > > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-min >>>> > > icon >>>> > > > > > > f >>>> > > > > > > >>>> > > > > > >>>> > > > > > -- >>>> > > > > > fpga-miniconf mailing list >>>> > > > > > fpga-miniconf at lists.lca2018.linux.org.au >>>> > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minic >>>> > > onf >>>> > > > > > >>>> > > > > >>>> > > > > >>>> > > > > >>>> > > > > -- >>>> > > > > -- >>>> > > > > Teach your kids Science, or somebody else will :/ >>>> > > > > >>>> > > > > jason at ball.net >>>> > > > > vk2vjb at google.com >>>> > > > > callsign: vk2vjb >>>> > > > > >>>> > > > > >>>> > > > > -- >>>> > > > > fpga-miniconf mailing list >>>> > > > > fpga-miniconf at lists.lca2018.linux.org.au >>>> > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-minicon >>>> > > f >>>> > > > > >>>> > > > >>>> > > > >>>> > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and >>>> > > any accompanying attachments may contain confidential information. >>>> > > If you are not the intended recipient, do not read, use, >>>> > > disseminate, distribute or copy this message or attachments. If you >>>> > > have received this message in error, please notify the sender >>>> > > immediately and delete this message. Any views expressed in this >>>> > > message are those of the individual sender, except where the sender >>>> > > expressly, and with authority, states them to be the views of the >>>> > > University of Technology Sydney. Before opening any attachments, >>>> > > please check them for viruses and defects. Think. Green. Do. Please >>>> > > consider the environment before printing this email. >>>> > > -- >>>> > > fpga-miniconf mailing list >>>> > > fpga-miniconf at lists.lca2018.linux.org.au >>>> > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>>> > >>>> > >>>> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any >>>> accompanying attachments may contain confidential information. If you are >>>> not the intended recipient, do not read, use, disseminate, distribute or >>>> copy this message or attachments. If you have received this message in >>>> error, please notify the sender immediately and delete this message. Any >>>> views expressed in this message are those of the individual sender, except >>>> where the sender expressly, and with authority, states them to be the views >>>> of the University of Technology Sydney. Before opening any attachments, >>>> please check them for viruses and defects. Think. Green. Do. Please >>>> consider the environment before printing this email. >>>> -- >>>> fpga-miniconf mailing list >>>> fpga-miniconf at lists.lca2018.linux.org.au >>>> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>>> >>> >>> >>> -- >>> fpga-miniconf mailing list >>> fpga-miniconf at lists.lca2018.linux.org.au >>> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>> >>> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any >> accompanying attachments may contain confidential information. If you are >> not the intended recipient, do not read, use, disseminate, distribute or >> copy this message or attachments. If you have received this message in >> error, please notify the sender immediately and delete this message. Any >> views expressed in this message are those of the individual sender, except >> where the sender expressly, and with authority, states them to be the views >> of the University of Technology Sydney. Before opening any attachments, >> please check them for viruses and defects. Think. Green. Do. Please >> consider the environment before printing this email. >> >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> >> > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan at ryant.org Tue Jan 23 09:58:33 2018 From: ryan at ryant.org (Ryan Thomas) Date: Tue, 23 Jan 2018 09:58:33 +1100 Subject: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and other notes.... In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> Message-ID: Sorry, I meant to say I had run a `make clean` prior to this. I'm attempting the instructions from the start again. On 23 January 2018 at 09:53, joel.stan at gmail.com wrote: > Try to "make clean" as repeat the steps > > On 23 Jan. 2018 09:52, "Ryan Thomas" wrote: > >> I had this working last week, but today I decided to update and rebuild >> it with the new litex commits. >> >> Now after *make gateware; make image; scripts/build-qemu.sh* I get the >> following: >> >> Booting from network... >> Local IP : 192.168.100.50 >> Remote IP: 192.168.100.100 >> Fetching from: UDP/6069 >> >> And it just sits there, with the qemu-system-or32 process at 100%. >> >> Any help / ideas for how to rectify this? >> >> Cheers, >> >> Ryan >> >> On 23 January 2018 at 00:42, Bing Chen wrote: >> >>> Hi Jim, Rohit, >>> >>> After a 'make clean' and re-make I finally got the buildroot login, >>> thanks for the help! >>> >>> Regards >>> Bing >>> Sent from my Samsung Galaxy smartphone. >>> >>> >>> -------- Original message -------- >>> From: Jim Mussared >>> Date: 22/1/18 8:18 pm (GMT+10:00) >>> To: Rohit Kumar Singh >>> Cc: Bing Chen , fpga-miniconf at lists.lca2018.li >>> nux.org.au, me at mith.ro >>> Subject: Re: [fpga-miniconf] Final Reminder of FPGA Miniconf prework and >>> other notes.... >>> >>> Rather than recloning the whole repo, it shpuld be sufficient just to >>> git pull in litex-buildenv, then make gateware / make image (make gateware >>> should update all the submodules, including litex, which is what Florent is >>> referring to). >>> >>> Unless I missed something, doesn't look like you made a new gateware >>> since doing a pull (just reflashed the old one) >>> >>> On 22 Jan. 2018 7:25 pm, "Rohit Kumar Singh" >>> wrote: >>> >>>> Hi Bing! >>>> >>>> Sorry for repeat mail! I forgot to cc the mailing list in the last >>>> reply. >>>> >>>> I'm guessing your litex/litex-buildenv still might old. Because here is >>>> what I get: >>>> >>>> LiteX SoC BIOS (or1k) >>>>> (c) Copyright 2012-2018 Enjoy-Digital >>>>> (c) Copyright 2007-2018 M-Labs Limited >>>>> Built *Jan 20* 2018 22:57:55 >>>> >>>> >>>> Cloning a new repo and building the gateware and image again should >>>> work. Ideally, make clean, and git pull should have been sufficient. >>>> >>>> Thanks & Regards, >>>> Rohit >>>> >>>> On Mon, Jan 22, 2018 at 6:58 PM, Bing Chen >>>> wrote: >>>> >>>>> Hi Florent, >>>>> >>>>> Thanks for reply, I did another git pull in litex-buildenv and ran the >>>>> download-env.sh again, still the same error when I tried: >>>>> >>>>> --- console msg copy --- >>>>> >>>>> chmod -x firmware.bin >>>>> python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi >>>>> make[1]: Leaving directory '/home/bing/litex- >>>>> buildenv/build/arty_net_or1k.linux/software/firmware' >>>>> >>>>> real0m1.946s >>>>> user0m2.593s >>>>> sys0m0.413s >>>>> flterm --port=/dev/ttyUSB1 -- >>>>> kernel=build/arty_net_or1k.linux//software/linux/firmware.bin -- >>>>> speed=115200 >>>>> [FLTERM] Starting... >>>>> >>>>> LiteX SoC BIOS (or1k) >>>>> (c) Copyright 2012-2017 Enjoy-Digital >>>>> (c) Copyright 2007-2017 M-Labs Limited >>>>> Built Jan 12 2018 04:46:47 >>>>> >>>>> BIOS CRC passed (046476c5) >>>>> Initializing SDRAM... >>>>> Read delays: 1:32-33 0:32-33 completed >>>>> Memtest bus failed: 64/256 errors >>>>> Memtest data failed: 524288/524288 errors >>>>> Memtest addr failed: 8191/8192 errors >>>>> Memory initialization failed >>>>> BIOS> >>>>> --- >>>>> >>>>> All the prework steps work fine on my box though. >>>>> >>>>> Regards >>>>> bing >>>>> >>>>> On Mon, 2018-01-22 at 08:00 +0100, Florent Kermarrec wrote: >>>>> > Hi Bing, >>>>> > >>>>> > the fact that you see "Read delays: 1:32-33 0:32-33 completed" make >>>>> > me think your are not up to date on both litex and litex-buildenv >>>>> > repository. (or maybe on just one of them) >>>>> > >>>>> > Can you check? >>>>> > >>>>> > Florent >>>>> > >>>>> > >>>>> > 2018-01-22 7:43 GMT+01:00 Bing Chen : >>>>> > > Hi Joel/Tim, >>>>> > > >>>>> > > Bing's here, I think my kit is faulty or something, when I tried >>>>> > > testing loading gateware on it, I got this error msgs: >>>>> > > >>>>> > > --- console msg copy --- >>>>> > > >>>>> > > make[1]: Leaving directory '/home/bing/litex- >>>>> > > buildenv/build/arty_net_or1k.linux/software/firmware' >>>>> > > >>>>> > > real0m1.135s >>>>> > > user0m1.046s >>>>> > > sys0m0.096s >>>>> > > flterm --port=/dev/ttyUSB1 -- >>>>> > > kernel=build/arty_net_or1k.linux//software/firmware/firmware.bin >>>>> -- >>>>> > > speed=115200 >>>>> > > [FLTERM] Starting... >>>>> > > >>>>> > > LiteX SoC BIOS (or1k) >>>>> > > (c) Copyright 2012-2017 Enjoy-Digital >>>>> > > (c) Copyright 2007-2017 M-Labs Limited >>>>> > > Built Jan 12 2018 04:46:47 >>>>> > > >>>>> > > BIOS CRC passed (046476c5) >>>>> > > Initializing SDRAM... >>>>> > > Read delays: 1:32-33 0:32-33 completed >>>>> > > Memtest bus failed: 64/256 errors >>>>> > > Memtest data failed: 524288/524288 errors >>>>> > > Memtest addr failed: 8191/8192 errors >>>>> > > Memory initialization failed >>>>> > > BIOS> >>>>> > > >>>>> > > ---- >>>>> > > >>>>> > > Then I tried run serialboot and it stuck at "Executing booted >>>>> > > program >>>>> > > at 0x40000000" >>>>> > > >>>>> > > ---- console msg copy ---- >>>>> > > >>>>> > > BIOS> serialboot >>>>> > > Booting from serial... >>>>> > > Press Q or ESC to abort boot completely. >>>>> > > sL5DdSMmkekro >>>>> > > [FLTERM] Received firmware download request from the device. >>>>> > > [FLTERM] Uploading kernel (74672 bytes)... >>>>> > > [FLTERM] Upload complete (7.7KB/s). >>>>> > > [FLTERM] Booting the device. >>>>> > > [FLTERM] Done. >>>>> > > Executing booted program at 0x40000000 >>>>> > > >>>>> > > ---- >>>>> > > >>>>> > > >>>>> > > Regards >>>>> > > bing >>>>> > > >>>>> > > On Sun, 2018-01-21 at 21:19 -0600, joel.stan at gmail.com wrote: >>>>> > > > I will be at the top of the stairs at 3pm with the kits. I'm in a >>>>> > > > blue tshirt. Come say hi and grab your kit. >>>>> > > > >>>>> > > > Cheers, >>>>> > > > >>>>> > > > Joel >>>>> > > > >>>>> > > > >>>>> > > > On 22 Jan. 2018 13:14, "Jason Ball" wrote: >>>>> > > > > For that matter, could I drop in later today to grab the kit so >>>>> > > I'm >>>>> > > > > ready for tomorrow's session, latest changes and all. >>>>> > > > > >>>>> > > > > Thanks. >>>>> > > > > >>>>> > > > > On Mon, Jan 22, 2018 at 12:45 PM, Hal Ashburner >>>> > > gmai >>>>> > > > > l.com> wrote: >>>>> > > > > > Hey guys. Where are you set up today? >>>>> > > > > > >>>>> > > > > > On 21 Jan. 2018 7:09 pm, "Tim 'mithro' Ansell" >>>>> > > > > > wrote: >>>>> > > > > > > Hello everyone, >>>>> > > > > > > >>>>> > > > > > > With just over 24 hours until the FPGA Miniconf, this is >>>>> > > the >>>>> > > > > > > final reminder that everyone **must** complete the prework >>>>> > > at h >>>>> > > > > > > ttp://j.mp/pre-fpga-lca2018 >>>>> > > > > > > >>>>> > > > > > > You must complete up to the paragraph which says the >>>>> > > following >>>>> > > > > > > in bright red; >>>>> > > > > > > > The instructions from here can only be done after you >>>>> > > receive >>>>> > > > > > > > hardware. You can stop here if completing the prework. >>>>> > > > > > > >>>>> > > > > > > If you have not completed the prework you will not be able >>>>> > > to >>>>> > > > > > > attend -- that includes observing or anything similar. >>>>> > > > > > > >>>>> > > > > > > If you are stuck, on Monday, 22 Jan 2018, FPGA Miniconf >>>>> > > helpers >>>>> > > > > > > will be available to help. They should be available during >>>>> > > > > > > morning tea, lunch and afternoon tea somewhere near the >>>>> > > Tomu >>>>> > > > > > > test station. Hopefully they will be able to solve any >>>>> > > issues >>>>> > > > > > > you are having. >>>>> > > > > > > >>>>> > > > > > > There will also be an opportunity to pick up the hardware >>>>> > > kits >>>>> > > > > > > during lunch at the same location. This will allow you to >>>>> > > get a >>>>> > > > > > > head start on setup we need to do at the start of the >>>>> > > Miniconf. >>>>> > > > > > > >>>>> > > > > > > It would be a good for everyone to update their litex- >>>>> > > buildenv >>>>> > > > > > > sometime Monday evening -- there have been a large number >>>>> > > of >>>>> > > > > > > updates since the last email was sent out. This can be done >>>>> > > by >>>>> > > > > > > doing the following and then following the prework >>>>> > > instructions >>>>> > > > > > > for testing QEmu / Linux. >>>>> > > > > > > > cd litex-buildenv >>>>> > > > > > > > git pull >>>>> > > > > > > > export CPU=or1k PLATFORM=arty TARGET=net >>>>> > > > > > > > ./scripts/download-env.sh >>>>> > > > > > > > source ./scripts/enter-env.sh >>>>> > > > > > > >>>>> > > > > > > Depending on internet speeds, updating should only take 10- >>>>> > > 15 >>>>> > > > > > > minutes. >>>>> > > > > > > >>>>> > > > > > > People are also reminded that the FPGA Miniconf is on >>>>> > > Tuesday, >>>>> > > > > > > 23 January 2018 and will be starting at 10:15AM. This is >>>>> > > right >>>>> > > > > > > after the Matthew Todd's keynote talk. Please make sure you >>>>> > > > > > > make a beeline from the keynote venue to Large POD Room >>>>> > > > > > > CB11.04.400 when the keynote finishes. Please see the >>>>> > > schedule >>>>> > > > > > > email for the full details. >>>>> > > > > > > >>>>> > > > > > > Look forward to seeing everyone on Tuesday! >>>>> > > > > > > >>>>> > > > > > > Tim 'mithro' Ansell >>>>> > > > > > > >>>>> > > > > > > -- >>>>> > > > > > > fpga-miniconf mailing list >>>>> > > > > > > fpga-miniconf at lists.lca2018.linux.org.au >>>>> > > > > > > http://lists.lca2018.linux.org >>>>> .au/mailman/listinfo/fpga-min >>>>> > > icon >>>>> > > > > > > f >>>>> > > > > > > >>>>> > > > > > >>>>> > > > > > -- >>>>> > > > > > fpga-miniconf mailing list >>>>> > > > > > fpga-miniconf at lists.lca2018.linux.org.au >>>>> > > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-mini >>>>> c >>>>> > > onf >>>>> > > > > > >>>>> > > > > >>>>> > > > > >>>>> > > > > >>>>> > > > > -- >>>>> > > > > -- >>>>> > > > > Teach your kids Science, or somebody else will :/ >>>>> > > > > >>>>> > > > > jason at ball.net >>>>> > > > > vk2vjb at google.com >>>>> > > > > callsign: vk2vjb >>>>> > > > > >>>>> > > > > >>>>> > > > > -- >>>>> > > > > fpga-miniconf mailing list >>>>> > > > > fpga-miniconf at lists.lca2018.linux.org.au >>>>> > > > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-mini >>>>> con >>>>> > > f >>>>> > > > > >>>>> > > > >>>>> > > > >>>>> > > UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and >>>>> > > any accompanying attachments may contain confidential information. >>>>> > > If you are not the intended recipient, do not read, use, >>>>> > > disseminate, distribute or copy this message or attachments. If you >>>>> > > have received this message in error, please notify the sender >>>>> > > immediately and delete this message. Any views expressed in this >>>>> > > message are those of the individual sender, except where the sender >>>>> > > expressly, and with authority, states them to be the views of the >>>>> > > University of Technology Sydney. Before opening any attachments, >>>>> > > please check them for viruses and defects. Think. Green. Do. Please >>>>> > > consider the environment before printing this email. >>>>> > > -- >>>>> > > fpga-miniconf mailing list >>>>> > > fpga-miniconf at lists.lca2018.linux.org.au >>>>> > > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>>>> > >>>>> > >>>>> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and >>>>> any accompanying attachments may contain confidential information. If you >>>>> are not the intended recipient, do not read, use, disseminate, distribute >>>>> or copy this message or attachments. If you have received this message in >>>>> error, please notify the sender immediately and delete this message. Any >>>>> views expressed in this message are those of the individual sender, except >>>>> where the sender expressly, and with authority, states them to be the views >>>>> of the University of Technology Sydney. Before opening any attachments, >>>>> please check them for viruses and defects. Think. Green. Do. Please >>>>> consider the environment before printing this email. >>>>> -- >>>>> fpga-miniconf mailing list >>>>> fpga-miniconf at lists.lca2018.linux.org.au >>>>> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>>>> >>>> >>>> >>>> -- >>>> fpga-miniconf mailing list >>>> fpga-miniconf at lists.lca2018.linux.org.au >>>> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>>> >>>> UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any >>> accompanying attachments may contain confidential information. If you are >>> not the intended recipient, do not read, use, disseminate, distribute or >>> copy this message or attachments. If you have received this message in >>> error, please notify the sender immediately and delete this message. Any >>> views expressed in this message are those of the individual sender, except >>> where the sender expressly, and with authority, states them to be the views >>> of the University of Technology Sydney. Before opening any attachments, >>> please check them for viruses and defects. Think. Green. Do. Please >>> consider the environment before printing this email. >>> >>> -- >>> fpga-miniconf mailing list >>> fpga-miniconf at lists.lca2018.linux.org.au >>> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >>> >>> >> >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at merlins.org Tue Jan 23 11:32:59 2018 From: marc at merlins.org (Marc MERLIN) Date: Tue, 23 Jan 2018 11:32:59 +1100 Subject: [fpga-miniconf] recent updates broke tftp for me In-Reply-To: References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> Message-ID: <20180123003259.lareclo5xhmshu5h@merlins.org> On Tue, Jan 23, 2018 at 09:52:06AM +1100, Ryan Thomas wrote: > I had this working last week, but today I decided to update and rebuild it > with the new litex commits. > > Now after *make gateware; make image; scripts/build-qemu.sh* I get the > following: > > Booting from network... > Local IP : 192.168.100.50 > Remote IP: 192.168.100.100 > Fetching from: UDP/6069 > > And it just sits there, with the qemu-system-or32 process at 100%. > > Any help / ideas for how to rectify this? I have the same exact problem. I was all working, and git pull is not working :( Pasted comment from the doc: I had it working until I got the new code pulled, and now it's broken for me. aftp starts automatically on 6069, I can even talk to it and get the firmware: saruman:~# tftp 192.168.100.100 6069 tftp> get boot.bin Received 75050 bytes in 0.0 seconds But the boot fails to retrieve the firmware: + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio -bios build/arty_net_or1k//software/bios/bios.bin -drive if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 bitbang_ssi: init(cpol:0, cpha:0, size:8) Using spiflash type n25q128a13 : m25p80_realize: Binding to IF_MTD drive Resetting PC to: 0x0 : reset_memory: Reset done. LiteX SoC BIOS (or1k) (c) Copyright 2012-2018 Enjoy-Digital (c) Copyright 2007-2018 M-Labs Limited Built Jan 23 2018 11:01:33 BIOS CRC passed (9cad5b80) Timer with delta zero, disabling Timer with delta zero, disabling Timer with delta zero, disabling Initializing SDRAM... Memtest OK Booting from serial... Press Q or ESC to abort boot completely. sL5DdSMmkekro Timer with delta zero, disabling Timeout Booting from network... Local IP : 192.168.100.50 Remote IP: 192.168.100.100 Fetching from: UDP/6069 (hang) Meanwhile aftp is running and I can still saruman:~# tftp 192.168.100.100 6069 tftp> get boot.bin Received 75050 bytes in 0.1 seconds -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From ryan at ryant.org Tue Jan 23 11:34:25 2018 From: ryan at ryant.org (Ryan Thomas) Date: Tue, 23 Jan 2018 11:34:25 +1100 Subject: [fpga-miniconf] recent updates broke tftp for me In-Reply-To: <20180123003259.lareclo5xhmshu5h@merlins.org> References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> <20180123003259.lareclo5xhmshu5h@merlins.org> Message-ID: I managed to get it working with by doing a git pull on the following: third_party/qemu-litex third_party/litex-devicetree And then, $ make clean ...etc Hope that helps. On 23 January 2018 at 11:32, Marc MERLIN wrote: > On Tue, Jan 23, 2018 at 09:52:06AM +1100, Ryan Thomas wrote: > > I had this working last week, but today I decided to update and rebuild > it > > with the new litex commits. > > > > Now after *make gateware; make image; scripts/build-qemu.sh* I get the > > following: > > > > Booting from network... > > Local IP : 192.168.100.50 > > Remote IP: 192.168.100.100 > > Fetching from: UDP/6069 > > > > And it just sits there, with the qemu-system-or32 process at 100%. > > > > Any help / ideas for how to rectify this? > > I have the same exact problem. I was all working, and git pull is not > working :( > > Pasted comment from the doc: > I had it working until I got the new code pulled, and now it's broken for > me. > aftp starts automatically on 6069, I can even talk to it and get the > firmware: > saruman:~# tftp 192.168.100.100 6069 > tftp> get boot.bin > Received 75050 bytes in 0.0 seconds > > But the boot fails to retrieve the firmware: > + build/arty_net_or1k//qemu/or32-softmmu/qemu-system-or32 -M litex > -nographic -nodefaults -monitor telnet::10000,server,nowait -serial stdio > -bios build/arty_net_or1k//software/bios/bios.bin -drive > if=mtd,format=qcow2,file=build/arty_net_or1k//qemu.qcow2,serial=n25q128a13 > -net nic -net tap,ifname=tap0,script=no,downscript=no -gdb tcp::10001 > bitbang_ssi: init(cpol:0, cpha:0, size:8) > Using spiflash type n25q128a13 > : m25p80_realize: Binding to IF_MTD drive > Resetting PC to: 0x0 > : reset_memory: Reset done. > > LiteX SoC BIOS (or1k) > (c) Copyright 2012-2018 Enjoy-Digital > (c) Copyright 2007-2018 M-Labs Limited > Built Jan 23 2018 11:01:33 > > BIOS CRC passed (9cad5b80) > Timer with delta zero, disabling > Timer with delta zero, disabling > Timer with delta zero, disabling > Initializing SDRAM... > Memtest OK > Booting from serial... > Press Q or ESC to abort boot completely. > sL5DdSMmkekro > Timer with delta zero, disabling > Timeout > Booting from network... > Local IP : 192.168.100.50 > Remote IP: 192.168.100.100 > Fetching from: UDP/6069 > (hang) > > Meanwhile aftp is running and I can still > saruman:~# tftp 192.168.100.100 6069 > tftp> get boot.bin > Received 75050 bytes in 0.1 seconds > > -- > "A mouse is a device used to point at the xterm you want to type in" - > A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking > Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at merlins.org Tue Jan 23 11:46:00 2018 From: marc at merlins.org (Marc MERLIN) Date: Tue, 23 Jan 2018 11:46:00 +1100 Subject: [fpga-miniconf] recent updates broke tftp for me In-Reply-To: <20180123003259.lareclo5xhmshu5h@merlins.org> References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> <20180123003259.lareclo5xhmshu5h@merlins.org> Message-ID: <20180123004600.qdmjmgxoemtse4lm@merlins.org> On Tue, Jan 23, 2018 at 11:32:59AM +1100, Marc MERLIN wrote: > BIOS CRC passed (9cad5b80) > Timer with delta zero, disabling > Timer with delta zero, disabling > Timer with delta zero, disabling > Initializing SDRAM... > Memtest OK > Booting from serial... > Press Q or ESC to abort boot completely. > sL5DdSMmkekro > Timer with delta zero, disabling > Timeout > Booting from network... > Local IP : 192.168.100.50 > Remote IP: 192.168.100.100 > Fetching from: UDP/6069 > (hang) > > Meanwhile aftp is running and I can still > saruman:~# tftp 192.168.100.100 6069 > tftp> get boot.bin > Received 75050 bytes in 0.1 seconds So, git pull doesn't git pull everything. Here is what I was missing: saruman:~/src/fpga/litex-buildenv/third_party/qemu-litex$ git pull Updating d8ebfa9e0c..dc90b3543c Fast-forward hw/net/liteeth.c | 28 ++++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-) Then rebuild and now the new binary can tftp ok. Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From sean at xobs.io Tue Jan 23 11:47:16 2018 From: sean at xobs.io (Sean Cross) Date: Tue, 23 Jan 2018 11:47:16 +1100 Subject: [fpga-miniconf] recent updates broke tftp for me In-Reply-To: <20180123004600.qdmjmgxoemtse4lm@merlins.org> References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> <20180123003259.lareclo5xhmshu5h@merlins.org> <20180123004600.qdmjmgxoemtse4lm@merlins.org> Message-ID: On 1/23/2018 11:46 AM, Marc MERLIN wrote: > On Tue, Jan 23, 2018 at 11:32:59AM +1100, Marc MERLIN wrote: >> BIOS CRC passed (9cad5b80) >> Timer with delta zero, disabling >> Timer with delta zero, disabling >> Timer with delta zero, disabling >> Initializing SDRAM... >> Memtest OK >> Booting from serial... >> Press Q or ESC to abort boot completely. >> sL5DdSMmkekro >> Timer with delta zero, disabling >> Timeout >> Booting from network... >> Local IP : 192.168.100.50 >> Remote IP: 192.168.100.100 >> Fetching from: UDP/6069 >> (hang) >> >> Meanwhile aftp is running and I can still >> saruman:~# tftp 192.168.100.100 6069 >> tftp> get boot.bin >> Received 75050 bytes in 0.1 seconds > So, git pull doesn't git pull everything. > > Here is what I was missing: > saruman:~/src/fpga/litex-buildenv/third_party/qemu-litex$ git pull > Updating d8ebfa9e0c..dc90b3543c > Fast-forward > hw/net/liteeth.c | 28 ++++++++++++++++++++++------ > 1 file changed, 22 insertions(+), 6 deletions(-) > > Then rebuild and now the new binary can tftp ok. The command you're looking for is "git submodule update". From joel.stan at gmail.com Tue Jan 23 11:49:22 2018 From: joel.stan at gmail.com (joel.stan at gmail.com) Date: Mon, 22 Jan 2018 18:49:22 -0600 Subject: [fpga-miniconf] recent updates broke tftp for me In-Reply-To: <20180123004600.qdmjmgxoemtse4lm@merlins.org> References: <1516603436.2545.8.camel@uts.edu.au> <1516607926.5051.7.camel@uts.edu.au> <20180123003259.lareclo5xhmshu5h@merlins.org> <20180123004600.qdmjmgxoemtse4lm@merlins.org> Message-ID: Good find Mark. We need to ensure the submodules are update when doing the pull. git pull git submodule update Do a make clean. I think that should work for everyone. On 23 Jan. 2018 11:46, "Marc MERLIN" wrote: > On Tue, Jan 23, 2018 at 11:32:59AM +1100, Marc MERLIN wrote: > > BIOS CRC passed (9cad5b80) > > Timer with delta zero, disabling > > Timer with delta zero, disabling > > Timer with delta zero, disabling > > Initializing SDRAM... > > Memtest OK > > Booting from serial... > > Press Q or ESC to abort boot completely. > > sL5DdSMmkekro > > Timer with delta zero, disabling > > Timeout > > Booting from network... > > Local IP : 192.168.100.50 > > Remote IP: 192.168.100.100 > > Fetching from: UDP/6069 > > (hang) > > > > Meanwhile aftp is running and I can still > > saruman:~# tftp 192.168.100.100 6069 > > tftp> get boot.bin > > Received 75050 bytes in 0.1 seconds > > So, git pull doesn't git pull everything. > > Here is what I was missing: > saruman:~/src/fpga/litex-buildenv/third_party/qemu-litex$ git pull > Updating d8ebfa9e0c..dc90b3543c > Fast-forward > hw/net/liteeth.c | 28 ++++++++++++++++++++++------ > 1 file changed, 22 insertions(+), 6 deletions(-) > > Then rebuild and now the new binary can tftp ok. > > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - > A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking > Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at merlins.org Tue Jan 23 22:41:17 2018 From: marc at merlins.org (Marc MERLIN) Date: Tue, 23 Jan 2018 22:41:17 +1100 Subject: [fpga-miniconf] Example code for the devices we got with the goodie bag? Message-ID: <20180123114117.mg2mtpegcjkoixm4@merlins.org> Given that it's a bit daunting to start coding from scratching on a non trivial platform with such a slow turnaround time every time you try something, is there a repository with real example code exercising bigger things, maybe even some of the devices we got with the board, like the VGA adapter, audio, PS2 adapter, sdcard, and so forth? Thanks, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | PGP 1024R/763BE901 From paul at mawsonlakes.org Wed Jan 24 17:48:39 2018 From: paul at mawsonlakes.org (Paul Schulz) Date: Wed, 24 Jan 2018 06:48:39 +0000 Subject: [fpga-miniconf] Example code for the devices we got with the goodie bag? In-Reply-To: <20180123114117.mg2mtpegcjkoixm4@merlins.org> References: <20180123114117.mg2mtpegcjkoixm4@merlins.org> Message-ID: .. also, if I checkout litex from github, what are the steps to starting a new gateware from scratch. (Link to instuctions would be sufficient.) On Tue, 23 Jan. 2018, 22:41 Marc MERLIN, wrote: > Given that it's a bit daunting to start coding from scratching on a non > trivial platform with such a slow turnaround time every time you try > something, is there a repository with real example code exercising > bigger things, maybe even some of the devices we got with the board, > like the VGA adapter, audio, PS2 adapter, sdcard, and so forth? > > Thanks, > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - > A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking > Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -- Paul Schulz -------------- next part -------------- An HTML attachment was scrubbed... URL: From mibus at mibus.org Thu Jan 25 07:04:29 2018 From: mibus at mibus.org (Robert Mibus) Date: Wed, 24 Jan 2018 20:04:29 +0000 Subject: [fpga-miniconf] Example code for the devices we got with the goodie bag? In-Reply-To: References: <20180123114117.mg2mtpegcjkoixm4@merlins.org> Message-ID: (from memory) it's something like: * set a new TARGET environment variable (assuming PLATFORM etc are set) * create a file called ${TARGET}.py within litex-buildenv/targets/${PLATFORM}/ ($PLATFORM is "arty" for our board). As for filling the file full of stuff.... I do that the same way I write sendmail configs - copy an existing one and edit it ;) On Wed, Jan 24, 2018 at 5:49 PM Paul Schulz wrote: > .. also, if I checkout litex from github, what are the steps to starting a > new gateware from scratch. > (Link to instuctions would be sufficient.) > > On Tue, 23 Jan. 2018, 22:41 Marc MERLIN, wrote: > >> Given that it's a bit daunting to start coding from scratching on a non >> trivial platform with such a slow turnaround time every time you try >> something, is there a repository with real example code exercising >> bigger things, maybe even some of the devices we got with the board, >> like the VGA adapter, audio, PS2 adapter, sdcard, and so forth? >> >> Thanks, >> Marc >> -- >> "A mouse is a device used to point at the xterm you want to type in" - >> A.S.R. >> Microsoft is to operating systems .... >> .... what McDonalds is to gourmet >> cooking >> Home page: http://marc.merlins.org/ | PGP >> 1024R/763BE901 >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> > > > -- > Paul Schulz > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -- Robert Mibus -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at mith.ro Fri Jan 26 10:13:57 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Fri, 26 Jan 2018 10:13:57 +1100 Subject: [fpga-miniconf] Start of Goodies Kit documentation Message-ID: Hi everyone, I had hope to write this *before* the FPGA Miniconf, but time ran out. I have started a Google doc which contains information about the parts you got in your Goodies kit. You can find it here -> https://bit.ly/lca2018-fpga-goodies We will continue to populate it with more information over the next coming weeks, but you are also encourage to populate it with your own findings too! Open source and community collaboration FTW! Tim 'mithro' Ansell -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt-lca2018 at handcraftedcomputers.com.au Fri Jan 26 12:20:35 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Fri, 26 Jan 2018 12:20:35 +1100 Subject: [fpga-miniconf] Start of Goodies Kit documentation In-Reply-To: References: Message-ID: With regards to this - I cannot cut'n'paste out of Google docs using Firefox (52.5.x), so all of the working was typing manually between doc and xterm. Does anyone else have this issue/workaround? Cheers. On 26/01/18 10:13, Tim 'mithro' Ansell wrote: > Hi everyone, > > I had hope to write this *before* the FPGA Miniconf, but time ran out. I have started a Google doc which contains information about the parts you got in your Goodies kit. > > You can find it here -> https://bit.ly/lca2018-fpga-goodies > > We will continue to populate it with more information over the next coming weeks, but you are also encourage to populate it with your own findings too! Open source and community collaboration FTW! > > Tim 'mithro' Ansell > > -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From me at mith.ro Fri Jan 26 12:30:10 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Fri, 26 Jan 2018 12:30:10 +1100 Subject: [fpga-miniconf] Major merges! -- Lots of new features.... Message-ID: Hi everyone, Before the FPGA Miniconf we were holding off doing some major merges into litex-buildenv. Now the miniconf is over, we have now in the process of doing them. These merges will add; * Support for Python 3.6 (rather than having to downgrade to Python 3.5) * Support for a large number of new boards from Numato (thanks to Rohit and Ewen's work!) * Support for RISC-V 32 (for bare metal and soon micropython) * Improve Linux networking support. These are lots of cool new features but might mean you have a big amount to pull when updating. Tim 'mithro' Ansell -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at mith.ro Fri Jan 26 12:37:03 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Fri, 26 Jan 2018 12:37:03 +1100 Subject: [fpga-miniconf] Start of Goodies Kit documentation In-Reply-To: References: Message-ID: You could download the doc as a PDF? We will eventually move the docs into the wiki @ https://github.com/timvideos/litex-buildenv/wiki (but while things were still under modification it was handy to have the interactive editing). Tim 'mithro' Ansell On 26 January 2018 at 12:20, Daryl Tester < dt-lca2018 at handcraftedcomputers.com.au> wrote: > With regards to this - I cannot cut'n'paste out of Google docs > using Firefox (52.5.x), so all of the working was typing manually > between doc and xterm. Does anyone else have this issue/workaround? > > Cheers. > > > On 26/01/18 10:13, Tim 'mithro' Ansell wrote: > >> Hi everyone, >> >> I had hope to write this *before* the FPGA Miniconf, but time ran out. I >> have started a Google doc which contains information about the parts you >> got in your Goodies kit. >> >> You can find it here -> https://bit.ly/lca2018-fpga-goodies >> >> We will continue to populate it with more information over the next >> coming weeks, but you are also encourage to populate it with your own >> findings too! Open source and community collaboration FTW! >> >> Tim 'mithro' Ansell >> >> >> > -- > Regards, > Daryl Tester > Handcrafted Computers Pty. Ltd. > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt-lca2018 at handcraftedcomputers.com.au Fri Jan 26 14:22:26 2018 From: dt-lca2018 at handcraftedcomputers.com.au (Daryl Tester) Date: Fri, 26 Jan 2018 14:22:26 +1100 Subject: [fpga-miniconf] Start of Goodies Kit documentation In-Reply-To: References: Message-ID: On 26/01/18 12:37, Tim 'mithro' Ansell wrote: > You could download the doc as a PDF? Potentially (not sure I tried it - this week has been a blur for me)(well, according to my download manager, this is a thing I tried - that seems to work). I wanted to ensure that worked before I even dared try editing the document ... Thanks for you and the guys for running a great workshop! Cheers. -- Regards, Daryl Tester Handcrafted Computers Pty. Ltd. From jason at ball.net Mon Jan 29 10:01:49 2018 From: jason at ball.net (Jason Ball) Date: Mon, 29 Jan 2018 10:01:49 +1100 Subject: [fpga-miniconf] Major merges! -- Lots of new features.... In-Reply-To: References: Message-ID: Thanks Tim. Is there an ongoing discussion list for the litex/gateway development at all ? I'm interested in contributing here when possible and I have something useful to contribute. Cheers J. On Fri, Jan 26, 2018 at 12:30 PM, Tim 'mithro' Ansell wrote: > Hi everyone, > > Before the FPGA Miniconf we were holding off doing some major merges into > litex-buildenv. > > Now the miniconf is over, we have now in the process of doing them. These > merges will add; > > * Support for Python 3.6 (rather than having to downgrade to Python 3.5) > * Support for a large number of new boards from Numato (thanks to Rohit > and Ewen's work!) > * Support for RISC-V 32 (for bare metal and soon micropython) > * Improve Linux networking support. > > These are lots of cool new features but might mean you have a big amount > to pull when updating. > > Tim 'mithro' Ansell > > -- > fpga-miniconf mailing list > fpga-miniconf at lists.lca2018.linux.org.au > http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf > > -- -- Teach your kids Science, or somebody else will :/ jason at ball.net vk2vjb at google.com callsign: vk2vjb -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at mith.ro Tue Jan 30 04:23:44 2018 From: me at mith.ro (Tim 'mithro' Ansell) Date: Mon, 29 Jan 2018 09:23:44 -0800 Subject: [fpga-miniconf] Major merges! -- Lots of new features.... In-Reply-To: References: Message-ID: Hi Jason (and anyone else reading this), Most of the discussion around LiteX happens on the #timvideos IRC channel (on freenode) at the moment. I would highly recommend lurking if you are already on IRC. There are a couple of low traffic mailing lists which might be good to join, * HDMI2USB Mailing list -- The LiteX-BuildEnv we used at the hackfest was developed for the HDMI2USB project, so that list could be useful -> https://groups.google.com/forum/#!forum/hdmi2usb * FuPy Mailing List -- If you are interested in running MicroPython on LiteX, then the FuPy mailing list should be interesting -> https://groups.google.com/forum/#!forum/fupy * Linux on LiteX Mailing List -- If you are interested in running Linux on LiteX, then the Linux on LiteX mailing list should be interesting -> https://groups.google.com/forum/#!forum/linux-litex I will probably create a "litex-buildenv" mailing list sometime in the near future, but for the moment it doesn't exist. Will announce it here if I do. For my information, Jason -- what are you most interested in helping out? A couple of areas we really could use help are; (a) Improving both the Linux drivers for LiteX peripherals and QEmu emulation of LiteX peripherals (plus getting them upstream). (b) Now the FPGA Miniconf is over, the prework instructions need to also be moved from the Google Doc at https://j.mp/pre-fpga-lca2018 into the wiki here -> https://github.com/timvideos/litex-buildenv/wiki and made more generic (IE not specific to the Digilent Arty board). (c) Get all the pmod peripherals in the Miniconf's "Goodie" pack working with good examples. (d) Clean up and rewrite of the shell scripts + makefile + Python script mess with something cleaner and more robust (maybe something with meson or waf, bitbake, docker, etc). Looking forward to any contribution you are able to make but understand if it you don't end up with time to do anything! Tim 'mithro' Ansell On 28 January 2018 at 15:01, Jason Ball wrote: > Thanks Tim. > > Is there an ongoing discussion list for the litex/gateway development at > all ? I'm interested in contributing here when possible and I have > something useful to contribute. > > Cheers > J. > > > On Fri, Jan 26, 2018 at 12:30 PM, Tim 'mithro' Ansell wrote: > >> Hi everyone, >> >> Before the FPGA Miniconf we were holding off doing some major merges into >> litex-buildenv. >> >> Now the miniconf is over, we have now in the process of doing them. These >> merges will add; >> >> * Support for Python 3.6 (rather than having to downgrade to Python 3.5) >> * Support for a large number of new boards from Numato (thanks to Rohit >> and Ewen's work!) >> * Support for RISC-V 32 (for bare metal and soon micropython) >> * Improve Linux networking support. >> >> These are lots of cool new features but might mean you have a big amount >> to pull when updating. >> >> Tim 'mithro' Ansell >> >> -- >> fpga-miniconf mailing list >> fpga-miniconf at lists.lca2018.linux.org.au >> http://lists.lca2018.linux.org.au/mailman/listinfo/fpga-miniconf >> >> > > > -- > -- > Teach your kids Science, or somebody else will :/ > > jason at ball.net > vk2vjb at google.com > callsign: vk2vjb > > -------------- next part -------------- An HTML attachment was scrubbed... URL: