Closed Unimprezzed closed 7 years ago
What has happened between the time it was working and not? What's the output of i2cdetect -y 1?
Thank you for the reply. Between the time where the system worked properly and when it started to give me trouble was a system update. Basically,
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
I'm afraid that entering the output of that command gets messed up in the text due to formatting isssues, so I've attached the textfile containing output. out.txt
Could you also post the output of raspi-gpio get
?
Edit: also uname -a
and vcgencmd version
Sure thing. Again in the text file to skip formatting. gpiooutput.txt
Is there anything else connected to GPIO? It looks like none of the devices are acknowledging that they're there. This could happen if something else was connected and was pulling the pin low.
It might be worth trying the earlier build again. If that doesn't work anymore, then you'll know it's a hardware problem.
Just a few buttons. I followed the instructions provided at https://www.raspberrypi.org/learning/astro-pi-flight-case/worksheet2/, and after testing, the buttons and camera are all functional.
How do I revert to an older build of Raspian?
An archive of all the images can be found here: http://downloads.raspberrypi.org/raspbian/images/
Another possibility is that the HAT itself was damaged or the pin on the pi was damaged. That could've happened if there was a short, for example. If you have any other I2C devices you could test, that would be useful information, but I suspect you might not have anything suitable lying around.
Unfortunately, I don't have any other I2C devices. I've tried this on two SenseHats, on two separate RPi's, and I doubt the possibility that it's a hardware issue.
Nevertheless, I tried loading the library on an older version of Raspian, and the issue is still not resolved.
I have a multi-meter. Is there any guide for testing the pins with a regular multimeter?
Just saw your edit. Here's the output of the two commands you wanted to see. uname.txt vcgencmd.txt
If we've ruled out software (by returning to your previous setup), and you're saying it couldn't possibly be hardware, what does that leave?
If you start with a fresh, untouched card with only power and the HAT connected, you should see the rainbow pattern go on and then turn off when the kernel loads the relevant module. If that doesn't happen, that certainly points to a hardware issue.
Using the multimeter, you could arm yourself with the datasheet of one of the i2c devices and the sense hat schematic (https://www.raspberrypi.org/wp-content/uploads/2015/08/Sense-HAT-V1_0.pdf), you could do some basic troubleshooting. While it's running, carefully check the main voltage rails. When it's disconnected, check the connections and that there are no shorts to ground on the sda/scl lines. To check what's really happening, you'd want to use a scope and/or a logic analyzer.
You were right, it was a hardware issue. Except not with the boards.
It was with the extended 23-way pin header that I was using. It must not have been establishing a solid electrical connection, because I swapped it out with a more sturdy extended header from Adafruit, and now the SenseHat is working just fine. Thanks for helping me find the problem!
I got the Raspberry Pi Sense-Hat to work on an earlier build of Raspian, and was even able to program some simple programs using it. Now, the LED Matrix remains on, permanently showing the rainbow test pattern.
I try to clear it in Python 3, and I get the following when I try to instantiate the object:
Traceback (most recent call last): File "", line 1, in
File "/usr/lib/python3/dist-packages/sense_hat/sense_hat.py", line 39, in init
raise OSError('Cannot detect %s device' % self.SENSE_HAT_FB_NAME)
OSError: Cannot detect RPi-Sense FB device
I've checked the connections to the RPi and Sense-Hat, and they seem secure. This is in fact been an ongoing problem, as I ended up exchanging both a perfectly good RPi3 and Sense-Hat for new ones, only to have the same issue.
I have also tried a fresh install with a microSD with only Raspian installed, to avoid any possibility of a misconfiguration on the part of the OS. The issue did not resolve.
Any input would be appreciated.