Re: [Machinekit] Re: DE10 Nano suggested development environment?
Holy machinekit@mksocfpga-nano-soc:~$ halrun msgd:0 running rtapi:0 running halrun: Realtime already running. Use 'halrun -U' to stop existing realtime session. machinekit@mksocfpga-nano-soc:~$ halrun -U machinekit@mksocfpga-nano-soc:~$ halrun msgd:0 stopped rtapi:0 stopped rtapi_msgd command: /usr/libexec/linuxcnc/rtapi_msgd --instance=0 --rtmsglevel=1 --usrmsglevel=1 --halsize=524288 rtapi_app command: /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0 halcmd: source ~/Desktop/SS_Test_MK.halrun halcmd: show pin *8i20* Component Pins: Comp Inst Type Dir Value Name Epsilon Flags linked to: 517519 float IN 0 hm2_5i25.0.8i20.0.0.angle 0.10--l- 517519 float OUT 0 hm2_5i25.0.8i20.0.0.bus-voltage 0.10--l- 517519 float OUT 0 hm2_5i25.0.8i20.0.0.card-temp 0.10--l- 517519 float IN 0 hm2_5i25.0.8i20.0.0.current 0.10--l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.U-current --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.U-current-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.V-current --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.V-current-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.W-current --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.W-current-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.bus-high --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.bus-high-not--l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.bus-overv --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.bus-overv-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.bus-underv --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.bus-underv-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.framingr --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.framingr-not--l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.module --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.module-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.no-enable --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.no-enable-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.overcurrent --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.overcurrent-no --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.overrun --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.overrun-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.overtemp --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.overtemp-not--l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.watchdog --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.fault.watchdog-not--l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.brake-old --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.brake-old-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.brake-on --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.brake-on-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.bus-underv --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.bus-underv-no --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.current-lim--l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.current-lim-n --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.ext-reset --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.ext-reset-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.no-enable --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.no-enable-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.pid-on --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.pid-on-not --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.sw-reset --l- 517519 bit OUT FALSE hm2_5i25.0.8i20.0.0.status.sw-reset-not --l- 517519 bit OUT FALSE
Re: [Machinekit] Broken CRAMPS.bbio
On Sun, Aug 25, 2019 at 6:01 PM c.glas...@cox.net wrote: > > The CRAMPS.bbio file has a line commented out that drives a test led on the > CRAMPS board. > When this line is enabled by removing the # and run it provokes a series of > error messages starting with P9_25 pinmux file not found! > NOT GOOD!! > > I'm presently running the latest RCN release -- > bone-debian-9.9-machinekit-ARMhf-2019-06-30-4gb > > There is no doubt that all my troubles as noted in my post yesterday are > related to a broken pinmux definition. > > Would anyone care to point to a known good release? P9_25 is hdmi audio... Disable it in /boot/uEnv.txt https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices Regards, -- Robert Nelson https://rcn-ee.com/ -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/CAOCHtYgj6KpgyAgE0wkVJnUMhTm5LduFyqp2UZ%3DSrPft92i%2BfQ%40mail.gmail.com.
[Machinekit] Re: Broken CRAMPS.bbio
I suppose I should also ask, where's the source? On Sunday, August 25, 2019 at 4:01:29 PM UTC-7, c.gl...@cox.net wrote: > > The CRAMPS.bbio file has a line commented out that drives a test led on > the CRAMPS board. > When this line is enabled by removing the # and run it provokes a series > of error messages starting with P9_25 pinmux file not found! > NOT GOOD!! > > I'm presently running the latest RCN release -- > bone-debian-9.9-machinekit-ARMhf-2019-06-30-4gb > > There is no doubt that all my troubles as noted in my post yesterday are > related to a broken pinmux definition. > > Would anyone care to point to a known good release? > > Thanks, > > Chuck > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/7a83f69c-94b6-48e6-8cad-d3127bf0ffe1%40googlegroups.com.
[Machinekit] Broken CRAMPS.bbio
The CRAMPS.bbio file has a line commented out that drives a test led on the CRAMPS board. When this line is enabled by removing the # and run it provokes a series of error messages starting with P9_25 pinmux file not found! NOT GOOD!! I'm presently running the latest RCN release -- bone-debian-9.9-machinekit-ARMhf-2019-06-30-4gb There is no doubt that all my troubles as noted in my post yesterday are related to a broken pinmux definition. Would anyone care to point to a known good release? Thanks, Chuck -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/45533673-bf14-47ef-b7e3-9e41a90efea8%40googlegroups.com.
Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
Aug 25, 2019, 20:52 by mib.holotro...@gmail.com:
> OK decided to attempt the RIP method and after a dependency nightmare (and
> enabling a swap file) got a full compilation,
> with the scripts/build_with_cnc method.
>
> Ready to run full machinekit RIP
>
>
> real 18m56,876s
> user 60m38,652s
> sys 4m32,197s
>
> Later I was able to run machinekit command and the setup GUI pops up very
> satisfying however
> I was not able to run the simulator (havn't tried the sim before :-) )
>
> following messages appear in the console;
> linaro@ultra96:~$ machinekit
> MACHINEKIT - 0.2
> Machine configuration directory is '/home/linaro/machinekit-hal/configs/sim'
> Machine configuration file is 'axis-iocontrolv2-demo-ubuntu8.04.ini'
> Starting Machinekit...
> rtapi_msgd command: /home/linaro/machinekit-hal/libexec/rtapi_msgd
> --instance=0 --rtmsglevel=1 --usrmsglevel=1 --halsize=524288
> rtapi_app command: /home/linaro/machinekit-hal/libexec/rtapi_app_posix
> --instance=0
> iov2 -support-start-change started
> halcmd loadusr iov2 -support-start-change started
> task pid=4400
> emcTaskInit: using builtin interpreter
> Traceback (most recent call last):
> File "/home/linaro/machinekit-hal/bin/axis", line 122, in
> nf.start(root_window)
> File "/home/linaro/machinekit-hal/lib/python/nf.py", line 119, in start
> source_lib_tcl(r, "support.tcl")
> File "/home/linaro/machinekit-hal/lib/python/nf.py", line 111, in
> source_lib_tcl
> r.tk.call("source", os.path.join(tcl_libdir, f))
> _tkinter.TclError: can't find package Img
> Shutting down and cleaning up Machinekit...
>
You seem to be still in hell, this time in run-time section. Try installing
libtk-img or whatever else which seems appropriate. (It is a shotgun approach,
but it worked for me in the past.)
Cern
>
>
>
>
> On Sunday, 25 August 2019 17:54:32 UTC+2, c.gl...@cox.net wrote:
>
>> The Ultra96 is simply the most powerful embedded processor I've ever used!
>>
>> When loaded with PYNQ, a Python environment that runs in Jupyter it turns
>> into a powerful platform for FPGA development. Using a Ultra96 is akin to
>> taking an A10 Warthog to a gunfight.
>>
>
>
>
> --
> 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
> > .
> To view this discussion on the web visit >
> https://groups.google.com/d/msgid/machinekit/bfaef999-7a55-4c03-b485-d083e75e7ff3%40googlegroups.com
>
> >
> .
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/machinekit/Ln9ak1n--3-1%40tuta.io.
Re: [Machinekit] Re: DE10 Nano suggested development environment?
mk-hal deb for test with sserial parse only mod. Due to the number of changes I choose to creative a conservative change only modding the: hm2_sserial_parse_md() function, this is what does the intial probing and pin setting.. The file you should use I think is: machinekit-hal-rt-preempt_0.2.1566764039.gitf3af8e09e-1~stretch_armhf.deb I added the other one just in case... On Saturday, 24 August 2019 20:19:36 UTC+2, Michael Brown wrote: > > Got some scope results: > https://github.com/machinekit/mksocfpga/issues/107#issuecomment-524570613 > > > On Saturday, 24 August 2019 19:31:04 UTC+2, justin White wrote: > > @Michael, if ya need any info from my LCNC machine let me know. It's not > MK but it does have a working SS setup that's easy to check. > > Also, if it makes it any easier for you to test anything I'm about to > order what's hopefully my final board rev. I can whip you one up and send > it your way, might be useful if you get an SS remote on hand. > > On Saturday, August 24, 2019 at 1:20:09 PM UTC-4, justin White wrote: > > I'm not sure if this helps you but SS pins always look like normal I/O if > they don't detect a remote on the channel after coming up. Since I have it > out I connected the 8i20 to my project machine's 7i96 that I don't > typically use SS with. This is LinuxCNC 2.8pre1 > > No 8i20 connected, note IO pins 30 and 31: > shade@Viewer:~$ halrun > halcmd: source /home/shade/linuxcnc/SS_Test.halrun > Note: Using POSIX realtime > hm2: loading Mesa HostMot2 driver version 0.15 > hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2 > hm2_eth: 10.10.10.10: Hardware address: 00:60:1b:16:00:21 > hm2_eth: discovered 7I96 > hm2/hm2_7i96.0: Smart Serial Firmware Version 43 > hm2/hm2_7i96.0: 51 I/O Pins used: > hm2/hm2_7i96.0: IO Pin 000 (TB3-01): IOPort > hm2/hm2_7i96.0: IO Pin 001 (TB3-02): IOPort > hm2/hm2_7i96.0: IO Pin 002 (TB3-03): IOPort > hm2/hm2_7i96.0: IO Pin 003 (TB3-04): IOPort > hm2/hm2_7i96.0: IO Pin 004 (TB3-05): IOPort > hm2/hm2_7i96.0: IO Pin 005 (TB3-06): IOPort > hm2/hm2_7i96.0: IO Pin 006 (TB3-07): IOPort > hm2/hm2_7i96.0: IO Pin 007 (TB3-08): IOPort > hm2/hm2_7i96.0: IO Pin 008 (TB3-09): IOPort > hm2/hm2_7i96.0: IO Pin 009 (TB3-10): IOPort > hm2/hm2_7i96.0: IO Pin 010 (TB3-11): IOPort > hm2/hm2_7i96.0: IO Pin 011 (TB3-13/TB3-14): SSR #0, pin Out-00 (Output) > hm2/hm2_7i96.0: IO Pin 012 (TB3-15/TB3-16): SSR #0, pin Out-01 (Output) > hm2/hm2_7i96.0: IO Pin 013 (TB3-17/TB3-18): SSR #0, pin Out-02 (Output) > hm2/hm2_7i96.0: IO Pin 014 (TB3-19/TB3-20): SSR #0, pin Out-03 (Output) > hm2/hm2_7i96.0: IO Pin 015 (TB3-21/TB3-22): SSR #0, pin Out-04 (Output) > hm2/hm2_7i96.0: IO Pin 016 (TB3-23/TB3-24): SSR #0, pin Out-05 (Output) > hm2/hm2_7i96.0: IO Pin 017 (TB1-02/TB1-03): StepGen #0, pin Step > (Output) > hm2/hm2_7i96.0: IO Pin 018 (TB1-04/TB1-05): StepGen #0, pin Direction > (Output) > hm2/hm2_7i96.0: IO Pin 019 (TB1-08/TB1-09): StepGen #1, pin Step > (Output) > hm2/hm2_7i96.0: IO Pin 020 (TB1-10/TB1-11): StepGen #1, pin Direction > (Output) > hm2/hm2_7i96.0: IO Pin 021 (TB1-14/TB1-15): StepGen #2, pin Step > (Output) > hm2/hm2_7i96.0: IO Pin 022 (TB1-16/TB1-17): StepGen #2, pin Direction > (Output) > hm2/hm2_7i96.0: IO Pin 023 (TB1-20/TB1-21): StepGen #3, pin Step > (Output) > hm2/hm2_7i96.0: IO Pin 024 (TB1-22-TB1-23): StepGen #3, pin Direction > (Output) > hm2/hm2_7i96.0: IO Pin 025 (TB2-01/TB2-03): StepGen #4, pin Step > (Output) > hm2/hm2_7i96.0: IO Pin 026 (TB2-04/TB2-05): StepGen #4, pin Direction > (Output) > hm2/hm2_7i96.0: IO Pin 027 (TB2-07/TB2-08): Encoder #0, pin A (Input) > hm2/hm2_7i96.0: IO Pin 028 (TB2-10/TB2-11): Encoder #0, pin B (Input) > hm2/hm2_7i96.0: IO Pin 029 (TB2-13/TB2-14): Encoder #0, pin Index > (Input) > hm2/hm2_7i96.0: IO Pin 030 (TB2-16/TB2-17): IOPort > hm2/hm2_7i96.0: IO Pin 031 (TB2-18/TB2-19): IOPort > hm2/hm2_7i96.0: IO Pin 032 (internal): IOPort > hm2/hm2_7i96.0: IO Pin 033 (internal): SSR #0, pin AC Ref (internal) > (Output) > hm2/hm2_7i96.0: IO Pin 034 (P1-01): IOPort > hm2/hm2_7i96.0: IO Pin 035 (P1-02): IOPort > hm2/hm2_7i96.0: IO Pin 036 (P1-03): IOPort > hm2/hm2_7i96.0: IO Pin 037 (P1-04): IOPort > hm2/hm2_7i96.0: IO Pin 038 (P1-05): IOPort > hm2/hm2_7i96.0: IO Pin 039 (P1-06): IOPort > hm2/hm2_7i96.0: IO Pin 040 (P1-07): IOPort > hm2/hm2_7i96.0: IO Pin 041 (P1-08): IOPort > hm2/hm2_7i96.0: IO Pin 042 (P1-09): IOPort > hm2/hm2_7i96.0: IO Pin 043 (P1-11): IOPort > hm2/hm2_7i96.0: IO Pin 044 (P1-13): IOPort > hm2/hm2_7i96.0: IO Pin 045 (P1-15): IOPort > hm2/hm2_7i96.0: IO Pin 046 (P1-17): IOPort > hm2/hm2_7i96.0: IO Pin 047 (P1-19): IOPort > hm2/hm2_7i96.0: IO Pin 048 (P1-21): IOPort > hm2/hm2_7i96.0: IO Pin 049 (P1-23): IOPort > hm2/hm2_7i96.0: IO Pin 050 (P1-25): IOPort > hm2/hm2_7i96.0: registered > >
[Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
On Sunday, August 25, 2019 at 11:54:32 AM UTC-4, c.gl...@cox.net wrote: > > The Ultra96 is simply the most powerful embedded processor I've ever used! > > When loaded with PYNQ, a Python environment that runs in Jupyter it turns > into a powerful platform for FPGA development. Using a Ultra96 is akin to > taking an A10 Warthog to a gunfight. > The processor is quad core A53's so it's about the same as a Rpi3 which is probably twice as fast as the dual core A9's on a DE10-Nano and the FPGA is a bit bigger as well. It's by no means "fast" in the ARM world but for an socfpga it's pretty stoudt. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/64799b48-a557-4f0a-96fb-7c37917069f7%40googlegroups.com.
[Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
OK decided to attempt the RIP method and after a dependency nightmare (and
enabling a swap file) got a full compilation,
with the scripts/build_with_cnc method.
Ready to run full machinekit RIP
real18m56,876s
user60m38,652s
sys 4m32,197s
Later I was able to run machinekit command and the setup GUI pops up very
satisfying however
I was not able to run the simulator (havn't tried the sim before :-) )
following messages appear in the console;
linaro@ultra96:~$ machinekit
MACHINEKIT - 0.2
Machine configuration directory is '/home/linaro/machinekit-hal/configs/sim'
Machine configuration file is 'axis-iocontrolv2-demo-ubuntu8.04.ini'
Starting Machinekit...
rtapi_msgd command: /home/linaro/machinekit-hal/libexec/rtapi_msgd
--instance=0 --rtmsglevel=1 --usrmsglevel=1 --halsize=524288
rtapi_app command: /home/linaro/machinekit-hal/libexec/rtapi_app_posix
--instance=0
iov2 -support-start-change started
halcmd loadusr iov2 -support-start-change started
task pid=4400
emcTaskInit: using builtin interpreter
Traceback (most recent call last):
File "/home/linaro/machinekit-hal/bin/axis", line 122, in
nf.start(root_window)
File "/home/linaro/machinekit-hal/lib/python/nf.py", line 119, in start
source_lib_tcl(r, "support.tcl")
File "/home/linaro/machinekit-hal/lib/python/nf.py", line 111, in
source_lib_tcl
r.tk.call("source", os.path.join(tcl_libdir, f))
_tkinter.TclError: can't find package Img
Shutting down and cleaning up Machinekit...
On Sunday, 25 August 2019 17:54:32 UTC+2, c.gl...@cox.net wrote:
>
> The Ultra96 is simply the most powerful embedded processor I've ever used!
>
> When loaded with PYNQ, a Python environment that runs in Jupyter it turns
> into a powerful platform for FPGA development. Using a Ultra96 is akin to
> taking an A10 Warthog to a gunfight.
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/machinekit/bfaef999-7a55-4c03-b485-d083e75e7ff3%40googlegroups.com.
[Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
The Ultra96 is simply the most powerful embedded processor I've ever used! When loaded with PYNQ, a Python environment that runs in Jupyter it turns into a powerful platform for FPGA development. Using a Ultra96 is akin to taking an A10 Warthog to a gunfight. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/ac051158-7c62-4dc0-8981-40d91d4ef2cd%40googlegroups.com.
[Machinekit] Re: Two quesations about QtQuickVCP
Hey, just chipping in here. You could use TCP for Axis also, however, there would be a bit of additional overhead on connections. I've created a little line, called in setup.sh script, that switch from IPC <-> TCP: echo 'Changing to Remote Mode' sed -r '31 s/([^:]+).*/REMOTE=1/' /etc/linuxcnc/machinekit.ini > /tmp/machinekit.ini.temp sudo mv /tmp/machinekit.ini.temp /etc/linuxcnc/machinekit.ini echo 'Changing to Local Mode (IPC)' sed -r '31 s/([^:]+).*/REMOTE=0/' /etc/linuxcnc/machinekit.ini > /tmp/machinekit.ini.temp sudo mv /tmp/machinekit.ini.temp /etc/linuxcnc/machinekit.ini There is probably a better way to do so, as I am not the most proficient in bash scripting :). As for connection time, the first connection would take a little longer, as your client downloads the QML project and also there probably is a bit of overhead setting up the connection for the first - that is, for the first client. Subsequent connections here usually takes less time. Best regards. Paulo Sherring. Em sábado, 17 de agosto de 2019 02:32:00 UTC-3, Boris Skegin escreveu: > > Well, I actually also use stretch, just mixed it up above with jessie. My > present Qt version is 5.12.4. > > Did you check the examples > https://github.com/machinekit/QtQuickVcp/tree/master/examples ? They seem > to work even in the Designer. > > BTW, do you know how to use ipc instead of tcp in haltalk.ini ? As in my > case I have both the GUI and machinekit installation on the same machine... > > > On Wednesday, August 14, 2019 at 6:54:10 PM UTC+2, Joonas wrote: >> >> I've encountered the same on Debian stretch. The gui works but the qt >> creator seems to fail at importing the SDK so the buttons are not visible. >> I haven't had time to look into it much but it seems that either the >> install location is incorrect or they're missing the designer folder and >> metainfo file as outlined here. >> https://doc.qt.io/qtcreator/creator-qml-modules-with-plugins.html > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/6745fe37-c082-4d2a-bf37-71332a098b18%40googlegroups.com.
Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
> > Perhaps it would be possible to run MK armhf style compiled on the >> Ultra96, how to go about testing that and is this a viable solution ? > > I meant run the armhf .debs on the Ultra96 board. On Sunday, 25 August 2019 14:05:53 UTC+2, Michael Brown wrote: > > BTW: > > Beagleboard x15 is armv7-a --> armhf ? > It seems like the rpi3's can run armhf compiled software, I do not know if > this requires the whole os to be armhf compiled also ? > > Perhaps it would be possible to run MK armhf style compiled on the > Ultra96, how to go about testing that and is this a viable solution ? > > On Sunday, 25 August 2019 13:59:58 UTC+2, Michael Brown wrote: >> >> Well I found my notes building debs for the armhf is a peice of cake (and >> takes around 2 min) >> >> ## newest ---# >> cd machinekit-hal >> time scripts/build_docker -t armhf_9 -c deb >> >> cd machinekit-cnc >> time scripts/build_docker -t armhf_9 -c deb >> >> ## ---# >> >> However build scripts / instructions have no arm64 support and I can only >> find scattered attempts of building for arm64 soc's, >> and most importantly no real sucessfull arm64 machinekit run reports. >> >> Since I have no idea how armhf support was added (before mksocfpga), I >> have no clue as to what is needed to be added to gain arm64 >> (deb) compilation support, which I see as a requirement for adding the >> xilinx (arm64) mpsoc based Ultra96 board port to mksocfpga? >> >> I'd rather Not have to start by messing around with (uninstructed) arm64 >> rip builds, and then have to do the Vivado 2018.x fpga work on top of that >> following a (possible) arm64 package build... ? >> >> >> On Saturday, 24 August 2019 14:20:49 UTC+2, Charles Steinkuehler wrote: >>> >>> On 8/24/2019 5:19 AM, Michael Brown wrote: >>> > Now having some experience with Vivado and the Ultra96 I'm thinking of >>> > following up on this.. >>> > Xilinx has a Ultra96 Debian buster image online here as a starting >>> point: >>> > >>> https://www.xilinx.com/products/design-tools/ai-inference/ai-developer-hub.html#edge >>> >>> >>> Looks like an interesting board. The Ultrascale+ parts are really >>> nice to work with. I support a ZCU104 design for my Day Job that runs >>> video compression/streaming between the HDMI ports and Ethernet. >>> >>> NOTE: I have a uSD image that's "Plain ole Debian" if you want >>> something more generic to work with than the Xilinx AI SDK. It's for >>> the ZCU104 but you should be able to use it as-is with the Ultra96 if >>> you swap out the boot files (kernel, device-tree, & U-Boot). Let me >>> know if you're interested. >>> >>> > Next to find out how to install (aarch64) ARM64 Machinekit. >>> > Are there yet arm64 Machinekit packages online ? >>> > Or >>> > What are the commands for building mk-hal/cnc from source (been a >>> while >>> > since I last built debs...) >>> >>> It's been ages since I've compiled from source. I always just look at >>> the CI files and do it manually: >>> >>> https://github.com/machinekit/machinekit/blob/master/.travis.yml#L92 >>> >>> https://github.com/machinekit/machinekit/blob/master/scripts/build_docker >>> >>> -- >>> Charles Steinkuehler >>> cha...@steinkuehler.net >>> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/2fd46088-d63c-42dc-931c-2c61663742da%40googlegroups.com.
Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
BTW: Beagleboard x15 is armv7-a --> armhf ? It seems like the rpi3's can run armhf compiled software, I do not know if this requires the whole os to be armhf compiled also ? Perhaps it would be possible to run MK armhf style compiled on the Ultra96, how to go about testing that and is this a viable solution ? On Sunday, 25 August 2019 13:59:58 UTC+2, Michael Brown wrote: > > Well I found my notes building debs for the armhf is a peice of cake (and > takes around 2 min) > > ## newest ---# > cd machinekit-hal > time scripts/build_docker -t armhf_9 -c deb > > cd machinekit-cnc > time scripts/build_docker -t armhf_9 -c deb > > ## ---# > > However build scripts / instructions have no arm64 support and I can only > find scattered attempts of building for arm64 soc's, > and most importantly no real sucessfull arm64 machinekit run reports. > > Since I have no idea how armhf support was added (before mksocfpga), I > have no clue as to what is needed to be added to gain arm64 > (deb) compilation support, which I see as a requirement for adding the > xilinx (arm64) mpsoc based Ultra96 board port to mksocfpga? > > I'd rather Not have to start by messing around with (uninstructed) arm64 > rip builds, and then have to do the Vivado 2018.x fpga work on top of that > following a (possible) arm64 package build... ? > > > On Saturday, 24 August 2019 14:20:49 UTC+2, Charles Steinkuehler wrote: >> >> On 8/24/2019 5:19 AM, Michael Brown wrote: >> > Now having some experience with Vivado and the Ultra96 I'm thinking of >> > following up on this.. >> > Xilinx has a Ultra96 Debian buster image online here as a starting >> point: >> > >> https://www.xilinx.com/products/design-tools/ai-inference/ai-developer-hub.html#edge >> >> >> Looks like an interesting board. The Ultrascale+ parts are really >> nice to work with. I support a ZCU104 design for my Day Job that runs >> video compression/streaming between the HDMI ports and Ethernet. >> >> NOTE: I have a uSD image that's "Plain ole Debian" if you want >> something more generic to work with than the Xilinx AI SDK. It's for >> the ZCU104 but you should be able to use it as-is with the Ultra96 if >> you swap out the boot files (kernel, device-tree, & U-Boot). Let me >> know if you're interested. >> >> > Next to find out how to install (aarch64) ARM64 Machinekit. >> > Are there yet arm64 Machinekit packages online ? >> > Or >> > What are the commands for building mk-hal/cnc from source (been a while >> > since I last built debs...) >> >> It's been ages since I've compiled from source. I always just look at >> the CI files and do it manually: >> >> https://github.com/machinekit/machinekit/blob/master/.travis.yml#L92 >> >> https://github.com/machinekit/machinekit/blob/master/scripts/build_docker >> >> -- >> Charles Steinkuehler >> cha...@steinkuehler.net >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/ca192eb4-f6a4-4331-97f2-865176a9a225%40googlegroups.com.
