Advanced Search

Awesome, thanks, will take a look and see what i can fix, i dont think setting up a config for 6 axis will be a big problem once i actually get the gpio stuff working

Regarding GPIO drivers.

For the Rpi5 please use hal_gpio
For the RPi4 hal_pi_gpio or hal_gpio (this looks like the easier option to setup) , should be no need to mess with permissions

linuxcnc.org/docs/devel/html/drivers/hal_gpio.html
linuxcnc.org/docs/devel/html/drivers/hal_pi_gpio.html

What is the servo thread rate?

How are the ping times?

This may be a starting point
forum.linuxcnc.org/9-installing-linuxcnc...i-5?start=350#320817

But continue reading, as the user did make a few mistakes in the hal file, but these were pointed out in the next post. May not be exactly want you want, being 6 aixs, but it's a starting point.

But yeah it's hal_gpio for the PI5
linuxcnc.org/docs/devel/html/drivers/hal_gpio.html

jhandel wrote:

Got a strange one with a Pi5...   Network seems fine when I am just pinging my Mesa card (a 7i76e) but when I run Linux CNC, things kick on but then the network crashes and I get a bazillion (technical term) hm2/hm2_7i76e.0: error queuing read iter=xxxx) and everything turns back off.. 

Once it dies I can't even ping the Mesa card (10.10.10.10) until I unplug and plug back in the ethernet cord... Then its happy as a clam pinging.. but once I start up Linux CNC again same crash right as the UI inits. 

(Linux CNC 2.9.3, PI5 8Gb, NVMe Boot)
 

You may want to start reading from here:
forum.linuxcnc.org/27-driver-boards/4223...read?start=20#207308

Unfortunately I don't have any ethernet hardware to test with (only SPI), I have a 7i92 but that's in the mill enclosure and is a PITA to access. From reports the 6.12 kernel on the most recent RPi images have better latency, but I can't say whether that would solve your issue.

Grad wrote:

I do not know how you guys even got so far: i have a Raspberry Pi 5 Modell B, 4x 2,4 GHz, 4 GB DDR4 and created images of v. 2.9.4 to SD card & USB drive with 3 different burning software including balenaEtcher. When i boot the RPi5 the drives are not recognized (as bootable) at all. With an image of vanilla Ubuntu it works just fine.

 
According the the RPi docs there is no RPi5 Model B, hmm screwed up on this, should have read further down, it does identify as 5-model-b, which can be found out by the following code snippet.
First thing I would is check the integrity of the download.
linuxcnc.org/iso/rpi-5-debian-bookworm-6...7-0140.img.xz.sha256
I test all images prior to uploading on a RPi5 4GB bought around Nov\Dec 2023 with latest EEPROM and on a RPi400 with latest EEPROM.
What I would suggest is boot to Ubuntu, then with a USB drive that you have written the Linuxcnc image to attempt to mount it.[/quote]

I see, what do i need to do to get it configured for the RP1? Might be a very obvious answer but im a newbie and dont really yet know exactly what im doing.

Do i have to do anything other than redoing the hal file? This issue seems to be a bit deeper than just the hal file (or atleast thats what makes ĺ
sense to me)

Got a strange one with a Pi5...   Network seems fine when I am just pinging my Mesa card (a 7i76e) but when I run Linux CNC, things kick on but then the network crashes and I get a bazillion (technical term) hm2/hm2_7i76e.0: error queuing read iter=xxxx) and everything turns back off.. 

Once it dies I can't even ping the Mesa card (10.10.10.10) until I unplug and plug back in the ethernet cord... Then its happy as a clam pinging.. but once I start up Linux CNC again same crash right as the UI inits. 

(Linux CNC 2.9.3, PI5 8Gb, NVMe Boot)

Looking at the source for hal_pi_gpio it's setup for the BCM2835 (RPi 4). The RPi 5 uses the new RP1 southbridge chip for IO.

Hello everyone, ive been trying to set up linuxcnc to work with my Raspberrypi 5 for a week or two now, ive gotten to a point where i can load the hal_pi_gpio driver with no errors showing up, i have a config running in linuxcnc and i can see in halshow that the pins are activating and deactivating, the issue i have is that the pins only activate and deactivate in the software and not physically, i cannot measure any difference on the physical pin itself, i can use gpioset command to set the pins to high or low manually and that works well, but as soon as i try setting it to high/low using halcmd it just doesnt change state, i would greatly appreciate some assistance in setting this up correctly.

The hal file below was given as an example somewhere online, dont remember exactly where i got it but it is as mentioned supposed to work considering that halshow shows the pins and the fact that they should be changing state.

I do not know how you guys even got so far: i have a Raspberry Pi 5 Modell B, 4x 2,4 GHz, 4 GB DDR4 and created images of v. 2.9.4 to SD card & USB drive with 3 different burning software including balenaEtcher. When i boot the RPi5 the drives are not recognized (as bootable) at all. With an image of vanilla Ubuntu it works just fine.

You are absolutely right. I was extremely happy to see it run successfully
Now I need only connect the right PIN's since between hal_pi_gpio and hal_gpio the pin numbering is physical / BMC.

Anyway I appreciate your effort to help out
JAiro

On the loadrt line you are trying to assign GPIO12 twice
loadrt hal_gpio inputs=GPIO3,GPIO5,GPIO6,GPIO4
outputs=GPIO12,GPIO23,GPIO16,GPIO11,GPIO20,GPIO10,GPIO24,GPIO19,GPIO21,GPIO12,GPIO26,GPIO13

The you have done this, trying to use GOIO12 twiceYou need to fix these issues
You may need to increase your base period over 10000, I tried 15000.
And as you did not supply your postgui_call_list.hal I had to comment out that line, to get everything to load.

These are my HAL and INI files:

drive.google.com/drive/folders/1ZyTfg1zN...FlzQlUXC?usp=sharing

that is remarkable, because I flashed the latest image for pi5 for the second time and double checked my HAL and INI files. (the 'help' was indeed misplaced, and set this discussion on the wrong leg)

This is my loadrt command:

loadrt hal_gpio inputs=GPIO3,GPIO5,GPIO6,GPIO4 outputs=GPIO12,GPIO23,GPIO16,GPIO11,GPIO20,GPIO10,GPIO24,GPIO19,GPIO21,GPIO12,GPIO26,GPIO13

I will try to attach my ful config below.

this is from the report:

Debug file information:
Note: Using POSIX realtime
Failed to register output pin collection
hal_gpio: rtapi_app_main: Operation not permitted (-1)
./my-mill.hal:7: waitpid failed /usr/bin/rtapi_app hal_gpio
./my-mill.hal:7: /usr/bin/rtapi_app exited without becoming ready
./my-mill.hal:7: insmod for hal_gpio failed, returned -1
4465
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

I ready that there is still tricky stuff related to get the pi5 going with hal_grpio, but I don't know exactly what it is.

kind regards,
Jairo