Skip to content
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.

Gpio02 problem #27

Closed
gkunzel opened this issue Jan 2, 2013 · 3 comments
Closed

Gpio02 problem #27

gkunzel opened this issue Jan 2, 2013 · 3 comments
Labels
Milestone

Comments

@gkunzel
Copy link

gkunzel commented Jan 2, 2013

Hi,

I'm using Pi4J version 0.0.4 and I have identified a possible conflict involving the Pi4J's Gpio2 pin (13th pin of the header connector).

I tried use it as output on my RPi but it didn't changed the logic level from 0V to 3.3V. The other gpios are working properly.

On the internet (http://elinux.org/RPi_Low-level_peripherals) I saw that in Rpi rev. 1, the 13th pin of the connector is the GPIO21, while on RPi rev.2, the same 13th pin is the GPIO27. Maybe this change on the board is affecting the use of the gpio2. My RPi board is the new one (model B, 512MB).

Maybe my board has a problem, but I think that you guys might take a look on this.

Thank you,
Gustavo

@savageautomate
Copy link
Member

Please try version 0.0.5-SNAPSHOT.
I believe this has been fixed.

@savageautomate
Copy link
Member

Well bad news maybe ... I just tested it using 0.0.4 and this GPIO pin is working correctly on my 512 Pi.
Make sure you perform the latest software/firmware upgrade just to be sure.

sudo apt-get update
sudo apt-get upgrade

@gkunzel
Copy link
Author

gkunzel commented Jan 2, 2013

I did the update/upgrade that you suggested and now it is working properly. Thank you.

mheath pushed a commit to mheath/pi4j that referenced this issue Feb 16, 2021
mheath pushed a commit to mheath/pi4j that referenced this issue Feb 16, 2021
FIX: Issue Pi4J#27; I2CRegister.write ignores length value

Received confirmation from @hackerjimbo the fix is working as expected.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants