Re: [Machinekit] using hal_spi module

2018-09-23 Thread mngr
Thanks for the explanation about machinkit workings, I played with the stamps and found that it was blocking on while (!(BCM2835_SPICS & SPI_CS_DONE)); (Line 438) removing it halrun loads, now I will see if and what it writes. maybe I will have to control the low level implementation... but now

Re: [Machinekit] using hal_spi module

2018-09-23 Thread schoone...@gmail.com
Sep 23 15:03:17 realtimepi rtapi:0: 4:rtapi_app:701:user hal_spi.so default iparms: '' Sep 23 15:03:17 realtimepi rtapi:0: 1:rtapi_app:701:user : hal_spi initerr Sep 23 15:03:17 realtimepi rtapi:0: 4:rtapi_app:701:user : hal_spi initdbg Sep 23 15:03:17

Re: [Machinekit] using hal_spi module

2018-09-23 Thread schoone...@gmail.com
OK, good there is some progress. You will probably find that whilst loaded, it may not work. That while statement is actually while(!( *(spi + 0) & 0x0001) which is extremely specific and if something has changed or if SPI is not enabled, it will hang

Re: [Machinekit] GUI Geared towards Embedded Platforms

2018-09-23 Thread schoone...@gmail.com
HI Travis, I will be interested to have a look at this later. The includes you want should be in the flavor package https://github.com/machinekit/machinekit/blob/master/debian/machinekit-rt-preempt.install.in#L4 We don't have a -dev package and each kernel has a specific sub package which

Re: [Machinekit] GUI Geared towards Embedded Platforms

2018-09-23 Thread schoone...@gmail.com
Had a look at the forum thread in linuxcnc, sounds interesting. There is obviously a github repo somewhere you have shared with Michel Wijnja If you would like to do the same, I will be happy to test build. On 23/09/18 07:11, schoone...@gmail.com

Re: [Machinekit] executing from source, pango problems

2018-09-23 Thread mngr
I messed with the RPi so I had to redo that part, I run also the ./configure --with-platform-raspberry and it gave no error Il giorno domenica 23 settembre 2018 10:29:58 UTC+2, mngr ha scritto: > > Now it works: > The missing packages were those > > libpth-dev libpth20 tcl-dev tk-dev >

Re: [Machinekit] using hal_spi module

2018-09-23 Thread mngr
Il giorno venerdì 21 settembre 2018 16:44:50 UTC+2, Schooner ha scritto: > > You are not running with DEBUG=5 > I edited DEBUG = 5 in ini file(in EMC section), nothing changed, then I exported DEBUG=5 in bash. what is the difference? what is the deBUG setting in the ini file for? Attached

Re: [Machinekit] executing from source, pango problems

2018-09-23 Thread mngr
Now it works: The missing packages were those libpth-dev libpth20 tcl-dev tk-dev libusb-dev #here was still not working automake1.11 avahi-discover cmake cmake-data libarchive13 libavahi-compat-libdnssd-dev libavahi-compat-libdnssd1 libblas-common libblas3 libdbus-glib-1-2 libgfortran3

Re: [Machinekit] using hal_spi module

2018-09-23 Thread mngr
Il giorno domenica 23 settembre 2018 15:34:58 UTC+2, Schooner ha scritto: > > It's not about doubt > cat /proc/cpuinfo > will tell you whether you have BCM2835 > Thanks didn't know about that! on the rpi is written 2837, bit cpuinfo says 2835! So at least the part that writes in the SPI

Re: [Machinekit] using hal_spi module

2018-09-23 Thread schoone...@gmail.com
The log does not show what your earlier email showed, there is not mention of an error from insmod I think you need to get right back to basics. This driver was written 5 years ago and is specific to the BCM2835 chip It can only have been meant to support

Re: [Machinekit] using hal_spi module

2018-09-23 Thread schoone...@gmail.com
On 23/09/18 15:16, mngr wrote: Il giorno domenica 23 settembre 2018 15:34:58 UTC+2, Schooner ha scritto: It's not about doubt cat /proc/cpuinfo will tell you whether you have BCM2835

Re: [Machinekit] using hal_spi module

2018-09-23 Thread mngr
Il giorno domenica 23 settembre 2018 13:41:42 UTC+2, Schooner ha scritto: > > The log does not show what your earlier email showed, there is not mention > of an error from insmod > > I think you need to get right back to basics. > > This driver was written 5 years ago and is specific to the

Re: [Machinekit] using hal_spi module

2018-09-23 Thread mngr
Attached. In the log you can see the message I added in the hal_spi rtapi_app_main. pi@realtimepi:~ $ halcmd loadrt hal_spi :0: insmod failed, returned -1: rtapi_rpc(): reply timeout See /var/log/linuxcnc.log for more information. pi@realtimepi:~ $ halcmd show all halcmd: cant connect to

Re: [Machinekit] using hal_spi module

2018-09-23 Thread mngr
I am really sorry Schooner, I was excited about the findings... I actually don't know which args suits my setup, I looked in the source, but I don't know how to find where they are used, I tried to scroll it all, but found no place that seems to use them. My board is a Raspberry Pi 3 model B V

Re: [Machinekit] RT demon is not running. rtapi_app_main(rtapi): -22 Invalid argument ???

2018-09-23 Thread Magnus Wiberg
Hi! I'm trying to make the py-uio work. I'm new to device tree and have trouble understanding where I should put the device tree fragment. I'm assuming it is in the am57xx-beagle-x15-revc.dts after #include "am57xx-beagle-x15-common.dtsi"? And then compile with dtc, but where to put the device