Skip to content

BeagleBone Blue naming convensions #151

@MarkAYoder

Description

@MarkAYoder

Is anyone updating the Adafruit Python library for the Blue?

[2] doesn't appear to have any definitions for the Blue's connectors.

For example, GPIO1_17 appears on the Black at P9_23. On the Blue it appears on pin 4 for the GP0 header[3].

Should this be referred to as GP0_4 since it's pin 4, or should it be GP0_2 since it's the second IO pin on the header, or maybe GP0_1 is we should start numbering with 0?

Another example, The analog in's appear on the ADC header.

Should AIN0 be referred to as AIN0, or ADC_3, or ADC_1, or ADC_0? I can justify every choice.

My suggestion is to make it as easy as possible for the beginner and stick to the schematic and silk screen.

For example:
GP0_0 GPIO1_25
GP0_1 GPIO1_17
GP1_0 GPIO3_2
UT0_RX UART0_RX
S1_MOSI SPI1_MOSI

ADC0 AIN0
AIN0 AIN0 (both refer to AIN0)

What do you think? These should also apply to BoneScript.

--Mark

[2] https://github.com/adafruit/adafruit-beaglebone-io-python/blob/master/source/common.c
[3] https://github.com/beagleboard/beaglebone-blue/raw/master/BeagleBone_Blue_sch.pdf (page 1, bottom middle)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy