First off thank you for testing this on 2 of your Pi's I was thinking of testing on my Pi4 as well. I ran the test several more times on the Pi5 which it did the same thing "Random Testing" It would show 4-5 OK then get that error the next one did like 8-9 as ok then the same error. I looked at the Pin layout for it and Pin GPIO8 is where it seems to stop which is also called (SPIO CEO) I have a expansion board normally connected for the little projects (currently not connected for testing) and it shows several of the Pins lite when I have nothing connected to them. I dont know if there is a memory of previous projects that used those pins or if it is part of when I set up everything through the raspi-config ??I think there is something not quite right with pintest. It giveson a Pi4 running Bookworm after 5 GPIO have been shown as ok. Re-running it gives 5 different GPIO as ok then throws the error. That Pi4 is known to be good but has one-wire enabled.Code:
pintest: error: 'GPIO busy'
On a Pi5 running Bookworm it gives the same error but seemingly random GPIO are ok - that seems to be because a python script is running in the background flashing an LED every second on GPIO21
Maybe something is running on your Pi5?
You could try using pinctrl to read all GPIO and to set a GPIO high/low e.g.Code:
pinctrl set 21 op dh
anyway thank you it may be nothing I'm just curious especially since it has nothing to do with the 3v/grnd pins I shorted one time.
Thank you
Krampapas
Statistics: Posted by Krampapas — Sun Apr 27, 2025 7:07 pm