# Processing.io.\*

**URL:** <https://discourse.processing.org/t/processing-io/45253>\
**Category:** Processing for Pi\
**Created:** [October 31, 2024, 12:59pm UTC](https://discourse.processing.org/t/processing-io/45253 "2024-10-31T12:59:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![josephh](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/josephh/32/210_2.png) [@josephh](https://discourse.processing.org/u/josephh)\
**Post date:** [November 6, 2024, 3:08pm UTC](https://discourse.processing.org/t/processing-io/45253/2 "2024-11-06T15:08:33Z")

</div>

Hi @DonPabloCZ ,

Welcome to the community 😉

I found the following topic which describes the same issue:

> [@Issue with GPIO Access on Raspberry Pi 5 Using Processing 4](https://discourse.processing.org/t/issue-with-gpio-access-on-raspberry-pi-5-using-processing-4/43337):
>
> Hello everyone, I’ve been encountering an issue with GPIO programming on the Raspberry Pi 5 using Processing 4. I’m getting an error when running code related to GPIO operations, stating “Invalid argument” and “GPIO pin 17 does not seem to be available on your platform” (as shown in the attached image). It seems there have been changes to the GPIO memory mapping on the Raspberry Pi 5, which might be causing compatibility issues with libraries like RPi.GPIO. I’m using the latest version of Proc…

But there’s no answers… let’s hope someone can help on this one!

---

_[View the full topic](https://discourse.processing.org/t/processing-io/45253)._