The new FPGA bitfile is available, you should be able to grab it via: apt-get update apt-get install socfpga-rbf
I'm still working on getting the Docker image to properly build bitfiles from the mksocfpga repository but that shouldn't hold you up. For anyone interested (and future users who might stumble over this thread), the Docker files in the cdsteinkuehler/QuartusBuildVMs repo on github are fine, but the Docker images in Docker Hub are not current. Even if the Docker images are current (it's easy enough to build your own) the mksocfpga build process currently fails because the machinetalk protobuf stuff has to be compiled before the FPGA (which includes a protobuf message as a ROM for identifying board-level details, rather than having to code these in the hm2 driver as a huge C case statement). To get past this, in your Docker Quartus VM, run: cd /work/HW/machinetalk-protobuf/python python setup.py build python setup.py install cd ../ make ...you can then successfully build FPGA bitfiles with the usual methods. To build a single bit file, simply: cd HW/QuartusProjects/DE0_Nano_SoC_DB25/ ./build.sh <configuration> ...the bit file will be in the output_files directory. I'll try to get everything sorted so the master build process is using images from Docker Hub which are produced from the git repo w/o any changes so the process will be more reproducible for others. On 5/18/2017 10:13 PM, Alexey Volkov wrote: > Hello Charles > > Don't worry, I am away for this weekends. > Just wondering if you plan to put together manual or instruction on how to > make > custom pinout. > > Best regards, > Alexey > > On Thursday, May 18, 2017 at 6:43:13 PM UTC-7, Charles Steinkuehler wrote: > > On 5/18/2017 8:38 PM, Alexey Volkov wrote: > > Thanks. > > I have been in a field trip, haven't had a chance to test it yet. > > Turns out it's not ready yet. > > I made a couple of simple goofs with the first two commits, so the > build failed. So I decided I should try to build locally before > committing any more changes, which resulted in me realizing the Docker > build images are not what is on docker hub, but one-of-a-kind images > on Michael Haberler's host server. > > Now I'm working on creating a working docker build image so anyone can > rebuild the bit files, not just someone with access to Michael's server. > > Hopefully I'll have an image for you to try somewhat soon. If you're > in a hurry, I can go ahead and push one more commit which would > probably build correctly on the existing build host. > > -- > Charles Steinkuehler > [email protected] <javascript:> > > -- > website: http://www.machinekit.io blog: http://blog.machinekit.io github: > https://github.com/machinekit > --- > You received this message because you are subscribed to the Google Groups > "Machinekit" group. > To unsubscribe from this group and stop receiving emails from it, send an > email > to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/machinekit. > For more options, visit https://groups.google.com/d/optout. > -- Charles Steinkuehler [email protected] -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
