On Wednesday, 28 June 2017 17:59:23 UTC+2, Charles Steinkuehler wrote:
>
> On 6/25/2017 5:06 PM, Michael Brown wrote: 
> > 
> > If there is interest and with a helping hand I could attempt to generate 
> some 
> > clean commits to add the adc functionality to master 
> > I have however not been able to understand or get the added soc-mesa 
> fw-id to work. 
>
> Sounds like you've done a lot! 
>
>
Yes
 

> I can try to help with the firmware ID stuff.  IIRC it's important you 
> use a recent Docker build image.  I updated them a short time ago 
> because the "official" images on docker hub didn't build the fw-id, 
> which may be what's causing your problems.  


Being unable to grasp the docker philosophy way of doing things, 

I have been running a standard Quartus debian install updated to 16.1
+ a script built armhf jessie with machinekit rip build.
This I was unable to update with the multicore mk-test build at that time.

After Installing docker on my local workstation,
I have once again tried looking at the docker setups but have been being 
unable to find verbose enough guides
to get anything to work at all.

As it would be nice to cross compile the mk armhf packages I have tried the 
method described here:
https://github.com/machinekit/mk-builder


I have tried using kubuntu(neon)16.04 and Debian Stretch as docker hosts

docker build -t machinekit/mk-builder:$(git rev-parse --abbrev-ref HEAD) .

I keep ending up with these error messages:

Multistrap system installed successfully in /opt/rootfs/. 

proot error: ptrace(TRACEME): Operation not permitted 
proot error: execve("/var/lib/dpkg/info/dash.preinst"): Operation not 
permitted                                              
proot info: possible causes: 
                                                                                
               
 
 * <program> is a script but its interpreter (eg. /bin/sh) was not found; 
                                                  
 * <program> is an ELF but its interpreter (eg. ld-linux.so) was not found; 
                                                
 * <program> is a foreign binary but no <qemu> was specified; 
                                                              
 * <qemu> does not work correctly (if specified). 
                                                                          
fatal error: see `proot --help`. 
                                                                                
           
 
proot warning: can't stat placeholder '/opt/rootfs/etc/ld.so.preload': No 
such file or directory                             
proot warning: can't stat placeholder '/opt/rootfs/host-rootfs': No such 
file or directory                                   
proot warning: can't stat placeholder '/opt/rootfs/dev/urandom': No such 
file or directory                                   
proot error: can't chmod '/tmp/proot-12188-AYMZEs': No such file or 
directory                                               

Next I tried out with the image you pointed to only linking to these 
instructions:

docker pull cdsteinkuehler/jessie-quartus-15.1.2

this gives me an image I then can start with:

docker run -it cdsteinkuehler/jessie-quartus-15.1.2
 
And then what ?

I found this thread:

https://groups.google.com/forum/#!topic/machinekit/zRSeyJ0JcJg

I have no clue as how to carry out the non-verbose instructions in the 3.rd 
post.

 This Dockerfile installs and configures Quartus.  If you run this 
> container, you're ready to checkout a Quartus project (such as 
> mksocfpga) and run "make rbf": 


How ? 
 

> Michael had made some 
> local changes to the build images that hadn't made it back to the 
> docker hub. 
>
> The latest version is 0.1.5, pushed about a month ago: 
> https://hub.docker.com/r/cdsteinkuehler/jessie-quartus-15.1.2/tags/ 
>
> ...if you're using anything older than that it probably explains why 
> fw-id isn't working.  If you still have problems with the latest 
> docker image, let me know. 
>
> -- 
> 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].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to