This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
using GPIOs
#1
Hello,

I am curious if there is some "standardization" for using GPIO pins.
I mean, what GPIO is used/recommended/preferred for various signals like 1wire, seatalk, shutdown and so on

I am trying to develop some kind of hat and I want to do that without conflicting with other hats, like MacArthur.
By example, MacArthur hat is using GPIO20 for seatalk_rx, GPIO21 for shutdown, GPIO26 for power_off and GPIO19 for 1wire.

Other "serious" hardware devices are sticking on same pins?

Also, maybe we can try to do a list with the most used signals and their GPIOs pins. I hope will be useful for hardware design.

Fair wind,
Seb
- SV Haimana
Reply
#2
https://pinout.xyz/

https://github.com/raspberrypi/firmware/...ays/README
Reply
#3
thanks, but this is not what I asked...
- SV Haimana
Reply
#4
hi sebba

there are no standard for HATs, some bring even an dedicated rom filled with software...

you have to check you system which ports are used if you build your own hardware.

better go for the i2C and onewire as these are neatly bus systems and with them are many
devices possible at the same time without much effort.
Reply
#5
got it, thank you
- SV Haimana
Reply
#6
The MacArthur HAT is probably on the extreme end in number of GPIOs used. So if your HAT works with that, it's probably going to play with most other HATs too.

The only additional pins to avoid are 27 (GPIO0) and 28 (GPIO1). These pins are reserved for an I2C EEPROM to store configuration info for the Pi.

As Holger wrote, there is no hard standard. But ignoring MacArthur, most HATs are connecting through UART0, SPI0, or I2C1. A trick to work around unexpected conflicts is to add a jumper on the trace connecting to the Pi GPIO, either as a solder jumper, or as a pin header like we use for the CAN termination. That way it's easy to rewire the connection if needed.
Reply
#7
(2024-02-22, 07:32 PM)Adrian Wrote: The MacArthur HAT is probably on the extreme end in number of GPIOs used. So if your HAT works with that, it's probably going to play with most other HATs too.

The only additional pins to avoid are 27 (GPIO0) and 28 (GPIO1). These pins are reserved for an I2C EEPROM to store configuration info for the Pi.

As Holger wrote, there is no hard standard. But ignoring MacArthur, most HATs are connecting through UART0, SPI0, or I2C1. A trick to work around unexpected conflicts is to add a jumper on the trace connecting to the Pi GPIO, either as a solder jumper, or as a pin header like we use for the CAN termination. That way it's easy to rewire the connection if needed.

I would also check the GPIO usage of PiCAN-M Hat, Sailor Hat and any of the Waveshare CAN Hats and stay away from those as well
Reply
#8
Good information, @Adrian and @Techstyle, thank you both!
- SV Haimana
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)