7" Display not working with Ropieee, must be something I'm doing wrong

Audio Gear Talk RoPieee
1

I have been trying to get my 7" display working with Ropieee for a couple of weeks now with no avail, and I’m assuming there is something I’m doing wrong.
My setup:

  • rPi5
  • Ropieee release 2025.08.02
  • Ian Canada stack: Shieldpi pro mkIII, Recieverpi DDC, FifoPi reclocker, MonitorPi Pro
  • Audio HAT is set to Raspberry Pi DAC (I2S Generic)
  • The name of my Roon zone device name, and default display zone are all identical
  • I’ve enabled the RoPieee extension in Roon
  • Playback is flawless, and the Monitor Pi Pro works fine as well
  • The screen is being fed by a separate 35w 5v SMPS in order to keep the load off the GPIO header.

The screen never comes on during boot up or during playback. I have two screens, neither of which are working with Ropieee, but both work with the standard Raspberry Pi OS. I also have a rPi4 which I tested and the results are identical. I think I’ve ruled out hardware issues.
There must be something really simple I’m doing wrong or a setting I’m missing. Any help would be appreciated.

2

I should have added that I’ve reflashed the SDCard twice, and restarted the Roon server.

3

So let’s start with the basics: is there anything to see on the screen when the unit is up and running?

4

Thanks for the prompt response.
Nothing showing at all. Nothing at boot up and nothing during playback.

5

That sounds like an hardware issue. Can you send me feedback? You can find that option on the ‘advanced’ tab.

6

Just sent with ID: add0d742ed22c873

7

It seems that the touchscreen is not (entirely) properly initialized…

Is it connected to DSI 0?
Can you also do a test with the HAT removed?

8

Yes, it’s connected to DSI0. I’ll test with the HAT removed later today and report back. Thanks for investigating this.

1 Like
9

It’s been a very busy week but I’ve finally had a chance to dig into this. I found that the issues with the pi4 were related to the cable. The original cable was fine, but the longer ones I was using didn’t work at all. With the pi5, I was able to get it to initialize on the Display1 connector but not the Display0 which seems strange. However, I’m not getting the correct display and I’ve attached the photo. I seem to recall a similar issue with another user, but I can’t seem to find that thread right now.

IMG_0204
IMG_02041920×1440 139 KB

10

On the Pi5 you need to use Display0.

So please put it back on Display1, make sure you configure again (by changing something in a menu, doesn’t matter what) and after the configure/reboot step send me feedback.

Thanks

11

Using Display0 there is no display at all and no boot up sequence showing. I’ve sent feedback with ID: 32a1ce5de98e842f.

12

Yeah. But have you tried with the HAT disabled, as I suggested earlier?

The screen is seen, but it has a failure during initial communication. I want to make sure that the HAT is not interfering somehow.

But keep it on Display0, that’s the only one that works.

13

Whoops apologies, I should have mentioned that. There is no display from Display0 and no HAT connected. I just tried again with no HAT and after reflashing the SD card. For what it’s worth, the Raspberry Pi OS works fine in this configuration, so it doesn’t seem to be an issue with the connector. Feedback ID is: 5553be7be9c69f58.

14

I’m confused…

The display must be connected to Disp0.

15

Oh. Can you also change to the beta channel? You can do that from the ‘advanced’ tab.

Thanks

16

Sorry if my previous post was confusing. The display is currently connected to Disp0, and nothing comes up on the display at all. There is no HAT connected. It’s just the rPi5 and the Display.
I’ve also switched to the beta update channel in the Advanced tab as requested, though it’s still running the stable version right now.

17

Yeah, that will take a few hours before the update notification shows up.
Please let me know when you’re running the latest beta.

Thanks

18

Running beta 2025.10 now. Here’s the latest feedback in case you want it: 93bc3676eba812c6.

19

Issue remains the same… something goes wrong with the initialization of the screen.
Just to be sure: this is the official screen from Raspberry Pi?

20

Yes its the official Raspberry Pi Display2 (7"), and I have two of them both of which do the same thing.