[Machinekit] DE0-SoC: any ways to have GPIO's low on Linux boot

2017-05-25 Thread Alexey Volkov
Hello

Is it any ways to make the board to switch GPIO's low on the power up and 
the Linux boot before the Machinekit starts?
What it is by default, High Impedance?

Best regards,
Alexey

-- 
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 machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.


Re: [Machinekit] Re: Machinekit not starting after compilation

2017-05-25 Thread schoone...@btinternet.com

  
  

On 24/05/17 16:40,
  michelvanderbregge...@gmail.com wrote:


  Can anybody tell me against which version of
libprotobuf-dev and libprotoc-dev I should build machinekit?
  


libprotobuf > 2.4.0.
libprotoc the same
Jessie is currently 2.6.1



  

  

  
  Op woensdag 24 mei 2017 13:39:32 UTC+2 schreef michelvand...@gmail.com:
  
How do I prevent the build-script from
  building a RIP version? It seems that it does this
  automaticly
  

  

  


What build script?

The whole point of the instructions you said you followed, is to
build a RIP build.
If you just want binary installs, you can use the packages




  

  

  

  

   Do what Bas
suggested and use DEBUG=5 and look at
/var/log/linuxcnc.log after a failure

  

  

  

  

  


What did the extra debug tell you?



  

  

  

  

  
libwebsockets is optional now since
https://github.com/machinekit/machinekit/commit/320e76dbd51ab5bd2fa8a04dcb4ea90f2394bfbe

If you built a RIP without enabling
libwebsockets, it will be undefined, even though
the library is still there, should not be
connected to your problem.


  



  
  Op woensdag 24 mei 2017 11:44:45 UTC+2
  schreef Schooner:
  It is
saying it cannot find the section
[DISPLAY] INTRO_GRAPHIC 

can't say further without your .ini file


You should not need INTRO_GRAPHIC or
INTRO_TIME, but if you do have them 
what they point to must be valid 



On 24/05/17 10:32, michelvand...@gmail.com
wrote: 
> Can not find -sec DISPLAY -var
INTRO_GRAPHIC -num 1 
> 2511 
>   PID TTY      STAT   TIME COMMAND

> Stopping realtime threads 
> Unloading hal components 

  

  
  -- 
  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 machinekit+...@googlegroups.com.
  Visit this group at https://groups.google.com/group/machinekit.
  For more options, visit https://groups.google.com/d/optout.


  

  

  

  

  
  -- 
  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 machinekit+unsubscr...@googlegroups.com.
  Visit this group at https://groups.google.com/group/machinekit.
  For more options, visit https://groups.google.com/d/optout.


  




--