Rasberry Pi 5 support?

[huntercaron]

I recently got a Pi5 and was hoping to set up these panels I have, but don't seem to be getting any LEDs to light up whatsoever.

I'm trying with a single 64x64 1/32 panel with a ICN2037BP chipset, connected directly via jumper cables. (This Panel).

• I've hooked up the E pin
• I've tried led-slowdown-gipio=4

I've powered the panel ok with a Pico so the Panel is fine (but had slow perf so now im here)

From what I’ve read in the issues here, it should be working pretty smoothly. So I am starting to think its something with the Pi5? Happy to give more info here, just not sure what would be helpful

[hzeller]

I have not have adapted the library yet to work with Pi5. Since there were always additions needed with every new Pi, as each GPIO is different, it is no surprise that the new one is not working yet.

Good news: I got a Pi5 so I can work on that.
But bad news: I don't know yet when I'll have time to adapt the library, might be probably around the end of the year. So if you have, use an older Pi for now.

[huntercaron]

Ah makes sense! Thank you for the quick response.

I think I have an older Pi somewhere I will dig up in the meantime. Please let me know if you need any help testing.

[huntercaron]

Update: All is working well with Pi4B for now

[babsher]

@hzeller I am also interested in Pi5 support. Is this in the works still?

[Primek17]

Hi @hzeller. Is there a chance to launch the library on PI5 this month? :)

[hzeller]

I'll try. I am doing this in my spare time, and end-of-year is of course always busy.
But I might have a day or two in the holidays.

[imCharlieB]

Any updates on the pi5 support?

[bsparacino]

I am trying to adapt the code to get the Pi 5 to work but am struggling, maybe someone smarter can figure it out.
I simply followed the process for how other models of the Pi are detected.
The thing I seem to be struggling with is the value for BCM2712_PERI_BASE.

It's possible the Pi 5 drastically changed how its offsets worked, but I can't seem to find a datasheet on the BCM2712 and even if I did, I would still be too confused to know what to do.

My code is here:
master...bsparacino:rpi-rgb-led-matrix:master

[davemaster]

I will try tomorrow just as I do with a RPi 4

[imCharlieB]

i found this little bit of info browsing cant rem what site i saved it in a note so i could look at it later...

The Pi 5 has a huge peripheral area starting at 0x40000000. This is the physical address which is translated to 0x1f00000000 in the 40-bit address space. The /dev/mem file can be used in the usual way but you have to be running with root privileges. The /dev/gpiomem0 file only maps the GPIO area starting at 0x400d0000, or 0x1f000d0000, but it doesn’t need root privileges. In the examples that follow, the mem file is used with root privileges because it works with peripherals other than the GPIO lines.

To access the GPIO area of memory you can map the entire peripherals area into user space using:

int memfd = open("/dev/mem", O_RDWR | O_SYNC);
uint32_t *map = (uint32_t )mmap(
NULL,
64 * 1024 1024,
(PROT_READ | PROT_WRITE),
MAP_SHARED,
memfd,
0x1f00000000
);
if (map == MAP_FAILED)
{
printf("mmap failed: %s\n", strerror(errno));
return (-1);
};
close(memfd);

This maps the entire 64MByte area – if you only want to use the GPIO lines then you can make this smaller, but there is no problem accommodating it in the 4,096MByte, 32-bit address space.

Once you have the address of the peripheral area you can access the registers that control them using offsets from the hardware-specified base address. For example, the GPIO control registers have an address of 0x400d0000, which gives an offset of 0xd0000. As the pointers are to uint32_t we have to remember to divide by 4 so that the correct offset is added. That is, the GPIO registers are located at:

uint32_t *PERIBase = map;
uint32_t *GPIOBase = PERIBase + 0xd0000 / 4;

[IsaacMAllen]

i found this little bit of info browsing cant rem what site i saved it in a note so i could look at it later...

The Pi 5 has a huge peripheral area starting at 0x40000000. This is the physical address which is translated to 0x1f00000000 in the 40-bit address space. The /dev/mem file can be used in the usual way but you have to be running with root privileges. The /dev/gpiomem0 file only maps the GPIO area starting at 0x400d0000, or 0x1f000d0000, but it doesn’t need root privileges. In the examples that follow, the mem file is used with root privileges because it works with peripherals other than the GPIO lines.

To access the GPIO area of memory you can map the entire peripherals area into user space using:

int memfd = open("/dev/mem", O_RDWR | O_SYNC); uint32_t *map = (uint32_t )mmap( NULL, 64 * 1024 1024, (PROT_READ | PROT_WRITE), MAP_SHARED, memfd, 0x1f00000000 ); if (map == MAP_FAILED) { printf("mmap failed: %s\n", strerror(errno)); return (-1); }; close(memfd);

This maps the entire 64MByte area – if you only want to use the GPIO lines then you can make this smaller, but there is no problem accommodating it in the 4,096MByte, 32-bit address space.

Once you have the address of the peripheral area you can access the registers that control them using offsets from the hardware-specified base address. For example, the GPIO control registers have an address of 0x400d0000, which gives an offset of 0xd0000. As the pointers are to uint32_t we have to remember to divide by 4 so that the correct offset is added. That is, the GPIO registers are located at:

uint32_t *PERIBase = map;
uint32_t *GPIOBase = PERIBase + 0xd0000 / 4;

Here's the link:
https://www.i-programmer.info/programming/148-hardware/16887-raspberry-pi-iot-in-c-pi-5-memory-mapped-gpio.html

[DJEF97]

Hi @hzeller. Is there a chance to launch the library on PI5 this month? :)

[bsparacino]

IsaacMAllen
I'm still not having luck trying this.
I am also not 100% sure what to do with this info

uint32_t *PERIBase = map;
uint32_t *GPIOBase = PERIBase + 0xd0000 / 4;

[JimM58]

Ok, I just got a pi5 running bookworm, and trying to run some apps on it. In this case, the adafruit-circuitpython-rgb-display stuff

And I get this

pi@pi5:~/ciq-common $ python3 tfteco.py
Traceback (most recent call last):
File "/home/pi/ciq-common/tfteco.py", line 209, in
cs_pin = digitalio.DigitalInOut(board.CE0)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/digitalio.py", line 185, in init
self.direction = Direction.INPUT
^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/digitalio.py", line 215, in direction
self._pin.init(mode=Pin.IN)
File "/usr/local/lib/python3.11/dist-packages/adafruit_blinka/microcontroller/generic_linux/libgpiod/libgpiod_pin_1_x.py", line 92, in init
self._line.request(
OSError: [Errno 16] Device or resource busy

It runs fine on all earlier pi devices.

Here's what I have on the pi 5 as far as adadfruit packages:

Package Version

---

Adafruit-Blinka 8.32.0
adafruit-circuitpython-bme280 2.6.24
adafruit-circuitpython-busdevice 5.2.6
adafruit-circuitpython-requests 2.0.5
adafruit-circuitpython-rgb-display 3.11.3
adafruit-circuitpython-typing 1.10.0
Adafruit-PlatformDetect 3.60.0
Adafruit-PureIO 1.1.11

[hannescam]

IsaacMAllen I'm still not having luck trying this. I am also not 100% sure what to do with this info

uint32_t *PERIBase = map;
uint32_t *GPIOBase = PERIBase + 0xd0000 / 4;

Do you have any progress with the Raspberry Pi 5 support?
Maybe this will help: opi-rockchip-3b-rgb-led-matrix