Hi! I can’t seem to get the 1.8 4-digit 7-segment display to work, I get these errors :
Traceback (most recent call last):
File “/home/pi/ai-lab-kit/python/1.8_4-Digit.py”, line 7, in
SDI = Pin(17,mode=Mode.OUT) # Serial Data Input
^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/dist-packages/fusion_hat/pin.py”, line 169, in init
self.setup(mode, pull, active_state, bounce_time)
File “/usr/local/lib/python3.11/dist-packages/fusion_hat/pin.py”, line 207, in setup
GPIO.setup(self._pin_num, self._mode.value, pull_up_down=self._pull.value)
RuntimeError: Cannot determine SOC peripheral base address
I can get the circuit to work with the Pi5 only (without the Fusion Hat) So it’s not my circuit wiring that’s at fault. Has anybody got it to work with the Fusion Hat?
EDIT: Is it possible that installing the neopixel library with :
(sudo pip3 install adafruit-circuitpython-neopixel-spi --break) in 1.9 NeoPixel LED Strip exercise
broke the dependencies, because I ran the preceding exercises and they give the same error message when using GPIO17, GPIO4’,GPIO24 etc, but when not using the GPIOs like for the servo or the RGB LED the scripts work.
Another question: Can you run a script without the Fusion Hat being involved? Like just connecting the power to the Pi5 not the Hat?
2nd EDIT I just now, made another micro SD card with the Fusion Hat installation and the error message did not appear. So maybe it would be wise and professional to tell or instruct your users either to not install the neopixel library or to do it in a virtual environment.
Thank you for the tip and the instructions, I’ve uninstalled the RPi.GPIO. Now my question is: is that library (RPi.GPIO) compatible with the Raspberry Pi5? I’ve been using RPi-lgpio because of that.
The RPi.GPIO library works fine for output functions on the Raspberry Pi 5, but there are issues with input functions. Of course, you can also test it yourself to see if the input issue has been resolved now.
Did you mean to say RPi.GPIO works fine for input functions rather than it works for output functions? Because it clearly breaks GPIO output functions when on a Pi 5, as OP has demonstrated here.
Yes, RPi.GPIO conflicts with the Raspberry Pi 5. However, since the Raspberry Pi OS and many libraries still retain compatibility with RPi.GPIO, it usually needs to be manually uninstalled.
What I was pointing out was that you said RPi.GPIO works fine for output functions, yet OP was saying he was having problems with output, not input, which you replied to uninstall RPi.GPIO
Thus it seems you meant to say that input functions work with RPi.GPIO as OP and I had issues with GPIO output.on RP 5.
It seems there was a small misunderstanding on my part. To be more precise, the conflict occurs when using the Pin() class – in both libraries, it supports both input and output functions. (The reason I encountered it first during my troubleshooting was when using the input function.)