EDIT/UPDATE: This issue is now resolved
- DO NOT run rpi-update
- DO NOT install the development version
Both of these things may leave your Pi doing unexpected things – they represent the ‘bleeding edge’ of development and they’re just not suitable for the vast majority of users.
It is likely that the issue will be fixed in the next week or two. I will report as soon as I receive word on a proper fix and how to install it.
Pimoroni have issued rather good advice concerning their products and agree with me on the state of things and the need to be patient for the proper fix.
Please bear in mind that this bug will affect everything using RPi.GPIO, including the very-popular Pibrella board and also the CamJam EduKits that we sell through The Pi Hut.
GPIO diagram at the top from Raspberry Pi Spy
Change the GPIO peripheral base address from 0x2000000 to 0x3f00000 and the GPIO software works. See /sys/iomem if I remember correctly. We have had to adjust all our sw for RPi2.
How does one do that?
On the plus side, as with the Xenon 2 Megablast issue, it’s notable that the community identified the problem and proposed a workaround, in about a billionth of the time that a closed-source software house would have done. And I bet we’ll see an upstream fix a lot quicker than a certain Redmond-based OS provider would roll out to its users.
How can I turn a Raspberry pi card on my PC?
Can you ask that question in a different way? It doesn’t make sense.
So.. this problem is already solved, or not yet ?
Yep. This problem is now solved.