Closed sonelu closed 5 years ago
Ignore the issue. I will close it. Seems to be a hardware problem on the bus with the new devices that I have installed.
Thanks.
I was going to ask whether the NanoPi core 2 has built-in pull-up resistors on the I2C data and clock lines. If not, you may want to add a 10K pull-up resistor on each line.
The NanoPi doesn't but the display is connected through an add-on board that has the pull ups. As a matter of fact both the screen and the other GPIO extender boards have their own pull ups. So I removed the pair from the screen but that did not solve the problem. In the end I have separated the GPIO and the screen and I have tested only with the screen. That works fine.
So I will continue to see where the problem is. I have another GPIO board that I can test separately independent on the screen and then try again all of them on the same bus. There are a few other hacks that I did on the boards - I might have screwed up something - although I've triple checked and nothing seems to be a problem.
Thing is, the luma.oled
is working fine.
Thanks for the work, and for sharing it by the way.
Type of Raspberry Pi
NanoPi Core2
Linux Kernel version
Linux PD2 4.14.111 #2 SMP Tue Apr 30 16:04:14 CST 2019 aarch64 aarch64 aarch64 GNU/Linux
Expected behaviour
I've been using an SSD1306 without any problems and I have changed to an SSD1327. The device is recognised by the kernel:
The display is at address 0x3c as the previous one. 0x1e and 0x6a are a gyro/accelerometer and 0x70 a GPIO expander.
I've updated the
luma.core
to 1.10.1:When trying to initialise the screen I get this:
Thanks.