LinuxCNC on Raspberry Pi 5

So what's the password on that image? I can't seem to find it posted anywhere. cnc didn't work for me.

I used the OS customization in the rpi-img program to set them to my own and it worked. It also connected right up to WiFi.

thadwald wrote:

rodw post=287637 userid=20660I did a bit of reading. can you guys try adding this at the beginning of cmdline.txt?

video=HDMI-A-1:1920x1080M@60D 

I also noticed that the RT patch 6.1,66 has been released and the 6.1.66 kernel was merged into the 6.1.y branch yesterday so it would be a good time to build another image.
 
There was no cmdline.txt. Creating one with this line didn't change anything.

cmdline.txt is in a subfolder of /boot

chuckp47 wrote:

This image can be downloaded from here
drive.google.com/file/d/16kKamxMKPdYAeJp...KLf/view?usp=sharing
I installed this and it's quite nice.  Much like the default Pi release, everything came up normally.  The latency historgram looks good.  I'm trying to talk to a Mesa 7c81.  After I set it up for an XZ lathe I get this error report when launch.  The key part seems to be:

Note: Using POSIX realtime
hm2_rpspi: Can't map peripherals: Invalid argument
hm2_rpspi: cannot map peripheral memory.
hm2_rpspi: rtapi_app_main: Invalid argument (-22)
./my_LinuxCNC_machine.hal:9: waitpid failed /usr/bin/rtapi_app hm2_rpspi
./my_LinuxCNC_machine.hal:9: /usr/bin/rtapi_app exited without becoming ready
./my_LinuxCNC_machine.hal:9: insmod for hm2_rpspi failed, returned -1

One of you can probably point out how to correct the memory management.  Suggestions?  There are less errors on the rspi than in the past.  Maybe if I get the memory setup right it can load the rspi driver?
ulimit -l reports 1030416, much bigger than the 20480 noted in the build document.

 



OK it has nothing to do with ulimit.

If you look at the source and do some investigation you find to begin with the driver is detecting the board as a RPi3. Therefore the driver is trying to use a memory location that is completely wrong. I raised this issue on github, along with a few experiments I've made but as of yet no replies other than my own have been made. The hm2_rpspi driver takes over from the kernel driver for spi, in fact it unloads the spi_bcm2835 driver.

If you really want to investigate further the first thing you'll need to do is setup all the required dependencies to build Linuxcnc from source.

I dont know where you got the info regarding the chip select line from. The hm2_spi driver will communicate via SPI when using halrun, unfortunately when being used in a config the driver is not fast enough. This is due to the fact that this driver uses the linux kernel SPI driver, and this is actually noted in the man page for that driver.

The GPIO interface has changed to such a degree, the RPi5 will not work with many of the utils & libraries that access the GPIO on the RPi4.

And yes I do have access to boards that run both 7i90 & 7c81 firmware that run fine on a RP-400.

[/quote]
[/quote]

Thanks. I realized I was wrong about the memory right after posting. The RPi peripherals project (firmware for RP1) says that it's not complete, and CS is one of the things missing. I'm just guessing from my previous experience with SPI that missing CS could be important. If no one else gets to it first I'll get to building the whole thing. Gotta start somewhere.

Do you have a link to "The Rp1 peripherals project" ?

I 've gone thru the draft docs for the RP1 and couldn't find any reference to CS being missing. Nor could I have find any reference to the 2 M3 cores being user accessible, the docs show the memory for the RP1 cores being ROM.

As I said the CS seems to work as the hm2_spi (whic I mixed up with h2_7i90 which is the EPP driver) driver works fine within the context of a halrun session, but not within the context of a running config.