07-03-2021, 12:07 PM
Hi Lucius
It is going to be difficult for me to help with this. If you know how to program on the Raspberry Pi with C++ then you could try to track down where the segfault is occuring in the mpd_oled code, and it might suggest a solution.
Is it possible that the Moode upgrade included some software that is also accessing your display (as it is part of a kit)?
Just to note, mpd_oled accesses the hardware SPI bus directly, rather than through the kernel driver (e.g. /dev/spidev0.0). However, if you get the same result after disabling the kernel driver (removing 'dtparam=spi=on') then the issue shouldn't be due to a conflict with this.
To anybody else using an SSD1306 (or SSD1309) SPI screen (-o 1) with mpd_oled on Moode 7.3, could you please confrm if it is working correctly?
Adrian.
It is going to be difficult for me to help with this. If you know how to program on the Raspberry Pi with C++ then you could try to track down where the segfault is occuring in the mpd_oled code, and it might suggest a solution.
Is it possible that the Moode upgrade included some software that is also accessing your display (as it is part of a kit)?
Just to note, mpd_oled accesses the hardware SPI bus directly, rather than through the kernel driver (e.g. /dev/spidev0.0). However, if you get the same result after disabling the kernel driver (removing 'dtparam=spi=on') then the issue shouldn't be due to a conflict with this.
To anybody else using an SSD1306 (or SSD1309) SPI screen (-o 1) with mpd_oled on Moode 7.3, could you please confrm if it is working correctly?
Adrian.
