Modifications

Par la suite, d'autres broches furent ajoutées pour d'autres utilisations générales, SPI, I2C et port série. Cela fut également mis en avant sur Wiki du Raspberry Pi.

Par la suite, d'autres broches furent ajoutées pour d'autres utilisations générales, SPI, I2C et port série. Cela fut également mis en avant sur Wiki du Raspberry Pi.

So when initially writing wiringPi, I chose to have the same default pin numbering scheme and numbered them from 0 upwards. This is no different to how the Arduino operates – “Pin 13″ on the Arduino is Port B, bit 5 for example. The underlying hardware definitions are hidden by a simplified numbering scheme. On the Pi, using wiringPi, pin 0 is BCM_GPIO pin 17 for example)

Lors de l'écriture initiale de WiringPi, Gordon décida d'utiliser le même schéma de numérotation des broches (schéma par défaut) en commençant par 0. Cela n'est pas différent de la façon dont Arduino gère les numéros de broches – par exemple, la "Pin 13" sur un Arduino correspond au bit 5 du port B. La définition matériel sous-jacente est caché sous un schéma de numérotation simplifié (comme la numérotation de 0 à 13 pour les broches Arduino).  

 

Par exemple, en utilisant WiringPi sur votre Raspberry, la "pin 0" correspond à la broche "GPIO broche 17" du BCM.

However this has subsequently been viewed as “wrong” and several people have expressed concern about my numbering scheme, however I’ve stuck with it (as by then people were using wiringPi). and it’s proven its worth over the hardware board revisions where some pins changed their hardware definitions, however wiringPi was able to hide this from the user. As a result (for example) a program that uses wiringPi pin 2 on a Rev. 1 Pi will work unchanged on a Rev 2. Pi, however someone using BCM_GPIO pin 21 on a Rev 1 Pi will need to change their program to use BCM_GPIO pin 27 on a Rev 2.}}

However this has subsequently been viewed as “wrong” and several people have expressed concern about my numbering scheme, however I’ve stuck with it (as by then people were using wiringPi). and it’s proven its worth over the hardware board revisions where some pins changed their hardware definitions, however wiringPi was able to hide this from the user. As a result (for example) a program that uses wiringPi pin 2 on a Rev. 1 Pi will work unchanged on a Rev 2. Pi, however someone using BCM_GPIO pin 21 on a Rev 1 Pi will need to change their program to use BCM_GPIO pin 27 on a Rev 2.}}