It seems like an issue with your particular setup. Are you using gpio for anything else? Does this happen every time you boot? Are you running anything that might be trying to use gpio? As a test, try running 'raspi-gpio set 2 a0' as a temporary workaround. If that works, we can try to figure out w...

ShiftPlusOne wrote:yes, I should've set gpio 2 and 3, not 1 and 2.

gpio 2 should be SDA1, so something is hijacking that pin.

Solution?

ShiftPlusOne wrote:What do you get if you run 'raspi-gpio get'? You should see gpio 1 and 2 set up as SDA1/SCL1. You should also not see SDA1/SCL1 on any other pins.

Not what I get. 1 and 2 are func=INPUT, and 3 is SCL1. I don't see SDA1 anywhere.

NO!!!! I missed the one exception!

I have UU in place of 46

That's exactly what I'm seeing - but with each -- replaced by 03 04 05 ..... all the way up to 77.

Sorry I'm new to this and unfamiliar with code tags.

ok, that got a result:

a grid, 0 to f along top, 00: to 70: on side -

all elements from 03 to 77 filled in.

ShiftPlusOne wrote:In a terminal window, what's the output if you run the command 'i2cdetect -y 1'?

bash: i2cdetect: command not found
and
Sudo: i2cdetect: command not found

maybe I'm doing the wrong thing?

ShiftPlusOne wrote:The output of dmesg and i2cdetect -y 1 could be helpful. Do the lights remain on after the pi boots?

No, the lights go off after about 20s. Sorry, I didn't understand the first bit?

I’ve had my Sense HAT working before, then I removed it from the Pi a few months ago to use the Pi for something else. Now I’ve got a problem getting the Sense HAT to work. When I power up, all the LEDs came on in the rainbow pattern. But when I try the simplest Python scripts (which used to work OK...