pikeyd doesn't work anymore on RPi3...

[dl9sec]

Pikeyd doesn't work anymore on my RPi3 (worked fine on my RPi1). It seems, that people having a RPi2 have the same problem.

Any ideas, workarounds, alternatives, patches?

Regards, Thorsten

[bushrat011899]

It's funny you mention this cause I just got a Pi3 and can't get mine working with PikeyD either. I assumed it was my wiring job but perhaps there's a larger problem.

Could you describe exactly what happens? Does the program compile? Does it launch? Does it crash with an error message?

Thanks,
Zac.

On Thu, Aug 25, 2016 at 3:52 AM, dl9sec < notifications@github.com [notifications@github.com] > wrote:
Pikeyd doesn't work anymore on my RPi3 (worked fine on my RPi1). It seems, that people having a RPi2 have the same problem.

Any ideas, workarounds, alternatives, patches?

Regards, Thorsten

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [https://github.com//issues/3] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ACHVRm9Khk_ngxujGy7g9ewchvaLtVqiks5qjITbgaJpZM4JsRn4] .

[dl9sec]

Hi,

i spotted the problem:

On RPi2 and RPi3 the GPIO_PERI_BASE address has changed from 0x20000000 to 0x3f000000.
So just change #define GPIO_PERI_BASE in joy_RPi.c to 0x3f000000 and it will work like a charm on a RPi3 (couldn't test it on a RPi2) :-)

Regards, Thorsten

[bushrat011899]

That's fantastic to hear thank you for solving this! I was having this and a few other problems and they're all fixed now. Can confirm this fix also works with any I2C MCP23017 (or MCP23008) chips too.

Thanks,
Zac.

On Thu, Aug 25, 2016 at 2:57 PM, dl9sec < notifications@github.com [notifications@github.com] > wrote:
Hi,

i spotted the problem:

On RPi2 and RPi3 the GPIO_PERI_BASE address has changed from 0x20000000 to 0x3f000000.
So just change #define GPIO_PERI_BASE in joy_RPi.c to 0x3f000000 and it will work like a charm on a RPi3 (couldn't test it on a RPi2) :-)

Regards, Thorsten

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [https://github.com//issues/3#issuecomment-242281106] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ACHVRvFYYFXAE9uzHVrREVPZFMu0LcD_ks5qjSCigaJpZM4JsRn4] .

[1210360]

Hi @dl9sec
I do not know how to do that, could you help me?

[porkus-rex]

Type into terminal-
sudo nano /home/pi/pikeyd/joy_RPi.c
Find the part of the files that's says-
0x20000000
To-
0x3f000000
Press Ctrl+x to save followed by Y followed by ENTER

[porkus-rex]

Depending when you installed pikeyd the file directory might be slightly differant

[apraetor]

It's line 43. Is this an issue relevant to all RPi 2/3 users? If so, maybe
a change to the source is in order? I know a little C (basically enough to
read existing code, not write my own), but not enough to set up compilation
directives.

--Matthew

On Wed, Nov 16, 2016 at 12:37 PM porkus-rex notifications@github.com
wrote:

Type into terminal-
sudo nano /home/pi/pikeyd/joy_RPi.c
Find the part of the files that's says-
0x20000000
To-
0x3f000000
Press Ctrl+x to save followed by Y followed by ENTER

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA475pPEuAl3lekpJaPxY4KAigggPV8Bks5q-z9FgaJpZM4JsRn4
.

[mriale]

I just submitted a change to remove the need for the hard-coded memory address of the GPIO pins. I was able to successfully run the same executable on Pi 1,2, and 3.

This is the change:
mriale@a983917