Raspberry Pi 4

PCW wrote:

Works for me (at least on RPI3,7C81)

Nice.
Then you should also be able to see the log message of the driver stating which RPi you are running it on (if the message/debug level is at INFO).

I dont get that message
is it the hostmot2 debug settings I need to change?

PCW wrote:

I dont get that message
is it the hostmot2 debug settings I need to change?

You can set the "spi_debug" parameter on the hm2_rpspi driver in the configuration to 3 (INFO level) or, if you are adventurous, 4 (DEBUG level). That should get you a noisy log file. Setting it to 5 will enable any and all messages generated by any hal component. Note that this parameter will affect the entire hal message setting, so all modules will start spewing extra information.

This is working with the 7c81 and rpi4, thanks

cakeslob wrote:

This is working with the 7c81 and rpi4, thanks

Success! Thanks for the feedback.

There is probably nothing preventing a pull request now to get this change in the main repo. I guess this should be added to both 2.7, 2.8 and 2.9 branches.

I got linux-5.2.14-rt7 running on my RockPro64. So, I used John Thornton's instruction for the raspberry pi4b and built linuxcnc (userspace) .

I was able to start linuxcnc via ssh from my mac and got the config selector window. I didn't have my 7i76e plugged in because I haven't bought a USB3 to ethernet converter. Now that I have rt_preempt and linuxcnc both apparently running I will have to do that.

Thank you John.

" the 7C80 still needs its inmux firmware module support added to the hostmot2 driver"

What does that mean?

Chris D

I tried again to build linuxcnc-uspace on my rockpro64 but I am getting some errors on
"sudo dpkg -i linuxcnc-uspace_2.8.0~pre1_arm64.deb"

(Reading database ... 185225 files and directories currently installed.)
Preparing to unpack linuxcnc-uspace_2.8.0~pre1_arm64.deb ...
Unpacking linuxcnc-uspace (1:2.8.0~pre1) over (1:2.8.0~pre1) ...
dpkg: dependency problems prevent configuration of linuxcnc-uspace:
linuxcnc-uspace depends on python-gtksourceview2; however:
Package python-gtksourceview2 is not installed.
linuxcnc-uspace depends on python-vte; however:
Package python-vte is not installed.
linuxcnc-uspace depends on gstreamer1.0-plugins-base; however:
Package gstreamer1.0-plugins-base is not installed.
linuxcnc-uspace depends on python-xlib; however:
Package python-xlib is not installed.


The instructions say:

Now edit debian/control.bottom.in and remove the following lines
python-gtksourceview2
python-vte,,

but the lines are not in debian/configure so I can't delete them.

So does anybody have any suggestions??? They are obviously being referenced from somewhere.

andypugh wrote:

Chris wrote:

" the 7C80 still needs its inmux firmware module support added to the hostmot2 driver"
What does that mean?

It sounds like the 7C80 uses a Hostmot2 module that is not currently supported by the LinuxCNC driver.
Hostmot2 defines a number of modules, with an identifying code:
github.com/LinuxCNC/linuxcnc/blob/master...tmot2/hostmot2.h#L92
(I suspect that some marked as "not supported" are actually now supported. But "inmux" is not even listed.)

Each GTAG type has its own driver file, for example GTAG 128, led, is handled by led.c
github.com/LinuxCNC/linuxcnc/blob/master.../mesa-hostmot2/led.c
(I chose that one as it is the simplest of them, but all the driver files follow the same structure)

The very first thing I did with LinuxCNC coding was write the tp_pwmgen driver to enable use of the 7i49 card. If you fancy a project....

Thanks for the information Andy. If I only had time for all the projects I have active now:(

Chris