1. Forum
  3. Search

Advanced Search

Search Results (Searched for: raspberry pi 3)

  • unknown
  • unknown
26 May 2025 01:02
Replied by unknown on topic Not able to get outputs on GPIO of Raspberry5

Not able to get outputs on GPIO of Raspberry5

Category: Installing LinuxCNC

Link to manpage
linuxcnc.org/docs/devel/html/drivers/hal_gpio.html

First hint is here:
The GPIO line PIN3 can not be found.

PIN3 isn't a name of a pin, pins are named as per man page.
  • unknown
  • unknown
25 May 2025 23:08
Replied by unknown on topic Not able to get outputs on GPIO of Raspberry5

Not able to get outputs on GPIO of Raspberry5

Category: Installing LinuxCNC

forum.linuxcnc.org/38-general-linuxcnc-q...official-images-only

Index to major thread, there's a section regarding your query with an example for a simple 3 axis machine that works.
  • AndyCNC
  • AndyCNC
25 May 2025 16:56
Replied by AndyCNC on topic Not able to get outputs on GPIO of Raspberry5

Not able to get outputs on GPIO of Raspberry5

Category: Installing LinuxCNC

Thanks for your fast reply.
That's the output of "gpioinfo", looks ok for me:
[color=#55ff55][b]cnc@fraese[/b][/color]:[color=#5555ff][b]~[/b][/color]$ gpioinfo
gpiochip0 - 54 lines:
	line   0:     "ID_SDA"       unused   input  active-high 
	line   1:     "ID_SCL"       unused   input  active-high 
	line   2:      "GPIO2"       unused   input  active-high 
	line   3:      "GPIO3"       unused   input  active-high 
	line   4:      "GPIO4"       unused   input  active-high 
	line   5:      "GPIO5"       unused   input  active-high 
	line   6:      "GPIO6"       unused   input  active-high 
	line   7:      "GPIO7"   "spi0 CS1"  output   active-low [used]
	line   8:      "GPIO8"   "spi0 CS0"  output   active-low [used]
	line   9:      "GPIO9"       unused   input  active-high 
	line  10:     "GPIO10"       unused   input  active-high 
	line  11:     "GPIO11"       unused   input  active-high 
	line  12:     "GPIO12"       unused   input  active-high 
	line  13:     "GPIO13"       unused   input  active-high 
	line  14:     "GPIO14"       unused   input  active-high 
	line  15:     "GPIO15"       unused   input  active-high 
	line  16:     "GPIO16"       unused   input  active-high 
	line  17:     "GPIO17"       unused   input  active-high 
	line  18:     "GPIO18"       unused   input  active-high 
	line  19:     "GPIO19"       unused   input  active-high 
	line  20:     "GPIO20"       unused   input  active-high 
	line  21:     "GPIO21"       unused   input  active-high 
	line  22:     "GPIO22"       unused   input  active-high 
	line  23:     "GPIO23"       unused   input  active-high 
	line  24:     "GPIO24"       unused   input  active-high 
	line  25:     "GPIO25"       unused   input  active-high 
	line  26:     "GPIO26"       unused   input  active-high 
	line  27:     "GPIO27"       unused   input  active-high 
	line  28: "PCIE_RP1_WAKE" unused input active-high 
	line  29:   "FAN_TACH"       unused   input  active-high 
	line  30:   "HOST_SDA"       unused   input  active-high 
	line  31:   "HOST_SCL"       unused   input  active-high 
	line  32:  "ETH_RST_N"  "phy-reset"  output   active-low [used]
	line  33:          "-"       unused   input  active-high 
	line  34: "CD0_IO0_MICCLK" "cam0_reg" output active-high [used]
	line  35: "CD0_IO0_MICDAT0" unused input active-high 
	line  36: "RP1_PCIE_CLKREQ_N" unused input active-high 
	line  37:          "-"       unused   input  active-high 
	line  38:    "CD0_SDA"       unused   input  active-high 
	line  39:    "CD0_SCL"       unused   input  active-high 
	line  40:    "CD1_SDA"       unused   input  active-high 
	line  41:    "CD1_SCL"       unused   input  active-high 
	line  42: "USB_VBUS_EN" unused output active-high 
	line  43:   "USB_OC_N"       unused   input  active-high 
	line  44: "RP1_STAT_LED" "PWR" output active-low [used]
	line  45:    "FAN_PWM"       unused  output  active-high 
	line  46: "CD1_IO0_MICCLK" "cam1_reg" output active-high [used]
	line  47:  "2712_WAKE"       unused   input  active-high 
	line  48: "CD1_IO1_MICDAT1" unused input active-high 
	line  49: "EN_MAX_USB_CUR" unused output active-high 
	line  50:          "-"       unused   input  active-high 
	line  51:          "-"       unused   input  active-high 
	line  52:          "-"       unused   input  active-high 
	line  53:          "-"       unused   input  active-high 
gpiochip10 - 32 lines:
	line   0:          "-"       unused   input  active-high 
	line   1: "2712_BOOT_CS_N" "spi10 CS0" output active-low [used]
	line   2: "2712_BOOT_MISO" unused input active-high 
	line   3: "2712_BOOT_MOSI" unused input active-high 
	line   4: "2712_BOOT_SCLK" unused input active-high 
	line   5:          "-"       unused   input  active-high 
	line   6:          "-"       unused   input  active-high 
	line   7:          "-"       unused   input  active-high 
	line   8:          "-"       unused   input  active-high 
	line   9:          "-"       unused   input  active-high 
	line  10:          "-"       unused   input  active-high 
	line  11:          "-"       unused   input  active-high 
	line  12:          "-"       unused   input  active-high 
	line  13:          "-"       unused   input  active-high 
	line  14:   "PCIE_SDA"       unused   input  active-high 
	line  15:   "PCIE_SCL"       unused   input  active-high 
	line  16:          "-"       unused   input  active-high 
	line  17:          "-"       unused   input  active-high 
	line  18:          "-"       unused   input  active-high 
	line  19:          "-"       unused   input  active-high 
	line  20:   "PWR_GPIO" "pwr_button"   input   active-low [used]
	line  21: "2712_G21_FS" unused input active-high 
	line  22:          "-"       unused   input  active-high 
	line  23:          "-"       unused   input  active-high 
	line  24:     "BT_RTS"       unused   input  active-high 
	line  25:     "BT_CTS"       unused   input  active-high 
	line  26:     "BT_TXD"       unused   input  active-high 
	line  27:     "BT_RXD"       unused   input  active-high 
	line  28:      "WL_ON"  "wl_on_reg"  output  active-high [used]
	line  29:      "BT_ON"   "shutdown"  output  active-high [used]
	line  30: "WIFI_SDIO_CLK" unused input active-high 
	line  31: "WIFI_SDIO_CMD" unused input active-high 
gpiochip11 - 15 lines:
	line   0:    "RP1_SDA"       unused   input  active-high 
	line   1:    "RP1_SCL"       unused   input  active-high 
	line   2:    "RP1_RUN" "RP1 RUN pin" output active-high [used]
	line   3: "SD_IOVDD_SEL" "vdd-sd-io" output active-high [used]
	line   4:  "SD_PWR_ON" "sd_vcc_reg"  output  active-high [used]
	line   5:  "SD_CDET_N"         "cd"   input   active-low [used]
	line   6:   "SD_FLG_N"       unused   input  active-high 
	line   7:          "-"       unused   input  active-high 
	line   8:  "2712_WAKE"       unused   input  active-high 
	line   9: "2712_STAT_LED" "ACT" output active-low [used]
	line  10:          "-"       unused   input  active-high 
	line  11:          "-"       unused   input  active-high 
	line  12:   "PMIC_INT"       unused   input  active-high 
	line  13: "UART_TX_FS"       unused   input  active-high 
	line  14: "UART_RX_FS"       unused   input  active-high 
gpiochip12 - 6 lines:
	line   0:  "HDMI0_SCL"       unused   input  active-high 
	line   1:  "HDMI0_SDA"       unused   input  active-high 
	line   2:  "HDMI1_SCL"       unused   input  active-high 
	line   3:  "HDMI1_SDA"       unused   input  active-high 
	line   4:   "PMIC_SCL"       unused   input  active-high 
	line   5:   "PMIC_SDA"       unused   input  active-high 
gpiochip13 - 4 lines:
	line   0: "WIFI_SDIO_D0" unused input active-high 
	line   1: "WIFI_SDIO_D1" unused input active-high 
	line   2: "WIFI_SDIO_D2" unused input active-high 
	line   3: "WIFI_SDIO_D3" unused input active-high

And group "dialout" seems to fit also:
[color=#55ff55][b]cnc@fraese[/b][/color]:[color=#5555ff][b]~[/b][/color]$ groups cnc
cnc : cnc tty disk dialout sudo audio video plugdev users input render netdev i2c bluetooth gpio spi
[color=#55ff55][b]cnc@fraese[/b][/color]:[color=#5555ff][b]~[/b][/color]$
  • andypugh
  • andypugh's Avatar
25 May 2025 15:54
Replied by andypugh on topic Not able to get outputs on GPIO of Raspberry5

Not able to get outputs on GPIO of Raspberry5

Category: Installing LinuxCNC

Have you run the "gpioinfo" command? That will list the available pins. If it doesn't work that may mean that you don't have gpiod installed.

Is your user account a member of the "dialout" group?

forums.raspberrypi.com/viewtopic.php?t=225274
  • AndyCNC
  • AndyCNC
25 May 2025 15:49
Not able to get outputs on GPIO of Raspberry5 was created by AndyCNC

Not able to get outputs on GPIO of Raspberry5

Category: Installing LinuxCNC

Hi,
I'm a bit desperate. I want to replace my very old pc based linuxcnc with the actual version running on a raspberry pi 5.
I've been trying to get signals to the pin header for a day now.
First of all: Is there a tutorial for raspberry configuration? I found nothing except the general docu and then went from one error message to another.
What I did is:
1. Started Stepconf wizard
2. Replaced parallel port Pins with hal_gpioxxx, see attached hal file

File Attachment:

File Name: AndyCNC.hal
File Size:3 KB

When I start this Setup following error occurs:  

File Attachment:

File Name: linuxcnc_report.txt
File Size:6 KB


This was my try to set the PINs:
halcmd: loadrt hal_gpio inputs=PIN3,PIN5,PIN7 outputs=PIN5,PIN6,PIN9,PIN10,PIN11,PIN17,PIN22,PIN27
Note: Using POSIX realtime
The GPIO line PIN3 can not be found
hal_gpio: rtapi_app_main: Operation not permitted (-1)
<stdin>:12: waitpid failed /usr/bin/rtapi_app hal_gpio
<stdin>:12: /usr/bin/rtapi_app exited without becoming ready
<stdin>:12: insmod for hal_gpio failed, returned -1
halcmd: Note: Using POSIX realtime

Would be nice if onyone could show my where I'm wrong.

Andy

 
  • mikereid0817
  • mikereid0817
21 May 2025 21:06
Replied by mikereid0817 on topic unable to get gpio to work on Raspberry Pi 5 using latest image

unable to get gpio to work on Raspberry Pi 5 using latest image

Category: Advanced Configuration

Thanks, Andy, you steered me in the right direction.

GPIO13 would not work at all, continuing to research that.

GPIO25, once pullup=GPIO25 was added, works.

I only have 1 limit switch setup, so I'm fully functional with the official image, Byte2Bot board, and my old Probotix motor driver setup.  Attached are the .hal and .ini files that worked, and my config.txt

 

File Attachment:

File Name: cncrouter.hal
File Size:3 KB

File Attachment:

File Name: cncrouter.ini
File Size:3 KB

File Attachment:

File Name: config.txt
File Size:3 KB
  • andypugh
  • andypugh's Avatar
20 May 2025 11:27
Replied by andypugh on topic unable to get gpio to work on Raspberry Pi 5 using latest image

unable to get gpio to work on Raspberry Pi 5 using latest image

Category: Advanced Configuration

Hi Andy... I am muddling my way through this and have things working really well, except inputs. Gpio reads gpio13 fine in python, hal_gpio always shows high in hal scope, meter etc. Any ideas? Is there a way to set gpio characteristics with hal?
 

You can try setting the various modifiers for GPIO13 and see if that helps.
opendrain
opensource
biasdisable
pulldown
pullup
As described in linuxcnc.org/docs/devel/html/drivers/hal_gpio.html#_usage

I am not clear if you are saying that it is always set and the input can not be changed, even if pulled low?

Have you checked with gpioinfo that nothing is claiming the pin?
 
  • unknown
  • unknown
20 May 2025 06:50
Replied by unknown on topic Important Info Regarding Rpi4/5 Images.

Important Info Regarding Rpi4/5 Images.

Category: Computers and Hardware

For the Linuxcnc Raspberry Pi images just don't do dist-upgrade, it will break things, this has been proven.

You get get away without doing any kind of upgrade.

If you are worried about security, updates are only a small part of the picture. The first step should always be physical security, which should be the number one priority with a computer running a cnc machine.I'd take data loss over damage to a cnc machine any day of the week, you can't back up a cnc machine.
  • unknown
  • unknown
20 May 2025 02:23
Replied by unknown on topic unable to get gpio to work on Raspberry Pi 5 using latest image

unable to get gpio to work on Raspberry Pi 5 using latest image

Category: Advanced Configuration

If you want help, you will have to upload your hal & ini files, otherwise no one knows exactly what you are doing.
  • mikereid0817
  • mikereid0817
20 May 2025 01:26
Replied by mikereid0817 on topic unable to get gpio to work on Raspberry Pi 5 using latest image

unable to get gpio to work on Raspberry Pi 5 using latest image

Category: Advanced Configuration

Hi Andy... I am muddling my way through this and have things working really well, except inputs. Gpio reads gpio13 fine in python, hal_gpio always shows high in hal scope, meter etc. Any ideas? Is there a way to set gpio characteristics with hal?
  • pgf
  • pgf
20 May 2025 00:27
RPi + Mesa + high CPU load gives stepper stuttering was created by pgf

RPi + Mesa + high CPU load gives stepper stuttering

Category: Computers and Hardware

I think I've probably been having this problem since I first started using a raspberry pi to drive my mill.  I noticed some CPU-related "hiccups" from the motors early on, and got rid of some background processes that were causing them, and didn't think anything more about it.  But today I noticed some new stutters/hiccups from the motors, and while trying to reproduce, started dragging the Axis window around on the screen.

Well, hoo boy...  the mill sure didn't like that!  Obviously, system load is affecting LinuxCNC in ways that it shouldn't.

So.  I must be doing something wrong, because I assume other people run X11 on their RPi HDMI monitor, and don't have this symptom?

I'm running the RPi 2.9.4 .iso (kernel was built 1/27/2025).

It's driving a Mesa 7i96.  I don't use wireless.  One ethernet is the built-in Pi interface, the other is a reliable USB/Ethernet dongle.  It doesn't matter which drives the Mesa, the symptom remains.

My cmdline.txt looks like this:
console=serial0,115200 console=tty1 root=PARTUUID=c8fda93c-02 rootfstype=ext4 fsck.repair=yes loglevel=5 net.ifnames=0 processor.max_cstate=1 isolcpus=3 firmware_class.path=/lib/firmware/updates/brcm rootwait skew_tick=1 kthread_cpus=0-2 irqaffinity=0-2 rcu_nocb_poll rcu_nocbs=3 nohz=on nohz_full=3

Most of that cmdline came from other posts on the forum.

I tried adjusting the IRQ affinity for the Mesa ethernet, to move those interrupts onto core 3 along with the rest of the real-time stuff, but that didn't help.

I'm sure I can find a PC that will work (I did some tests today on an older Thinkpad, with surprisingly good results), but I use the RPi gpio pins to help work around a LinuxCNC shortcoming, and I'd rather not lose that.  I will if I have to, though.

Any ideas, suggestions for things to try?

 
  • scotta
  • scotta's Avatar
19 May 2025 20:30
Replied by scotta on topic Remora - ethernet NVEM / EC300 / EC500 cnc board

Remora - ethernet NVEM / EC300 / EC500 cnc board

Category: Computers and Hardware

Hello scotta,

thank you for your quick reply. Yes, that is exactly what I thought myself.

The EC500 is powered by an external power supply. From the 6 pin header, GND, SCK and SDO have been connected to one of the probes.

I don´t have any kind of schematic on hands for the EC500. So I am not shure, why the header pin is labeled SDO. I would expect SDIO for a sufficient SWD connector. Is your header labeled with a SDO too?

My EC500 is labeled with IMXR_EC500 2023-05-18

Up to now, there has not been a single successful flash. From within MCUExpresso, I am at least able to build your application.

If this is not going to be successful: do you think, your actual project with W5500 and raspberry pi pico is as powerful as the 1052 solution and could be a viable alternative?

Thank you very much. I will try to give more details tomorrow.

Cheers Julius


 

I'll need to check the labelling on my boards. With MCUExpressoIDE does it report an error when trying to connect. It may give some clues.
Remora supports quite a number of 3D printer boards. The EC300/500 being 24V IO is more suited when using industrial hardware.
  • unknown
  • unknown
19 May 2025 07:48
Replied by unknown on topic Linuxcnc & the Raspberry Pi (4 & 5) Official Images Only!!!

Linuxcnc & the Raspberry Pi (4 & 5) Official Images Only!!!

Category: Installing LinuxCNC

Read through this thread, there is an example in this very thread.
  • mikereid0817
  • mikereid0817
19 May 2025 03:40
Replied by mikereid0817 on topic Linuxcnc & the Raspberry Pi (4 & 5) Official Images Only!!!

Linuxcnc & the Raspberry Pi (4 & 5) Official Images Only!!!

Category: Installing LinuxCNC

I have installed the PI5 image (25-01-27) and have gotten everything working EXCEPT the hal_gpio input pins. Outputs...done, inputs... no luck. I can read the input pins with GPIO from python... but not within linuxcnc.

Any ideas?
Displaying 46 - 60 out of 907 results.
  1. Forum
  3. Search
Time to create page: 1.041 seconds
Powered by Kunena Forum