Skip to content

docs: add GPIO pin selection guidelines for Radxa ZERO - #2000

Open
tangzz-radxa wants to merge 1 commit into
radxa-docs:mainfrom
tangzz-radxa:docs/zero-gpio-pin-selection-issue503
Open

docs: add GPIO pin selection guidelines for Radxa ZERO#2000
tangzz-radxa wants to merge 1 commit into
radxa-docs:mainfrom
tangzz-radxa:docs/zero-gpio-pin-selection-issue503

Conversation

@tangzz-radxa

Copy link
Copy Markdown
Contributor

Fixes #503

Summary

Add a new page GPIO Pin Selection Guidelines under zero/zero/app-development (bilingual zh/en).

Background

GitHub issue #503 requested documentation for choosing GPIO pins wisely, using Radxa ZERO as an example. The proposed content was reviewed and verified against the official ZERO 40-pin pinout (docs/zero/zero/hardware-design/hardware-interface.md):

  • Pins shared with other hardware functions (SPI/I2C/PWM) cannot be used as GPIO
  • ADC pins (15, 26) cannot be used as GPIO output
  • Pins 8 & 10 are the default debug console (UART_AO_A TXD/RXD)
  • Pins 35 & 38 depend on hardware revision
  • Pins 22 & 36 are open-drain (GPIOC_7 / GPIOH_8)

Changes

  • docs/zero/zero/app-development/gpio-pin-selection.md (zh)
  • i18n/en/docusaurus-plugin-content-docs/current/zero/zero/app-development/gpio-pin-selection.md (en)

Docs-only change; no behavior/functionality affected.

Add a new page under zero/zero/app-development with guidelines for
selecting GPIO pins, addressing issue radxa-docs#503. Content covers:
- Pins shared with other hardware functions (SPI/I2C/PWM) cannot be GPIO
- ADC pins (15, 26) cannot be used as GPIO output
- Avoid debug console pins (8, 10)
- Avoid hardware-revision-dependent pins (35, 38)
- Avoid open-drain pins (22, 36)

Bilingual zh/en versions included.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

添加GPIO引脚选择的方针

1 participant