Connecting LCD to Dev board for Windows IOT

[DavidCCC]

I have a Raspberry Pi 3 Dev board and Compute Module with a New 7" Official LCD Display.

I would like to connect my 7" Official Raspberry Pi Screen to my Dev board to allow me to use it with Windows IOT core. I am struggling to work out the correct pins to connect on between the screen and the dev board (or dev board to dev board) to allow the system to work. There seems to be little to no information about doing this (Or I am failing to be able to find it)

I have tested the screen with Raspbian and the LCD screen starts on boot and Touch and Display function. This shows me that the board is in working condition.

However when I switch the SD card for the Windows IOT Version (Version 10.0.15063.0) The Dev board will not boot to the LCD screen only the HDMI port (when I connect it to see if I am actually getting a boot)

The Ribbon cable of the Screen is connected to DISP1 on the Dev Board

On the back of the screen we have the 5 GPIO connectors;

For use with Raspbian I just have the following pins linked:
CD1_SDA (J6:37) -> GPIO 0 (J5:1)
CD1_SCL (J6:39) -> GPIO 1 (J5:3)
On Screen:
5V -> Pin 4 on J6 header (next to GPIO29)
GND -> PIN 2 on J6 Header (Next to GPIO28)

As stated, this appears to fully work

I am strugglign to work out the correct pin connections the LCD when used with Wondows IOT
I have the 5V and GND connected because they are logical, but what about the INT, SDA and SCL pins? Where do they connect on the Dev Board?

5V -> Pin 4 on J6 header (next to GPIO29)
INT -> ???
SDA -> ???
SCL -> ???
GND -> PIN 2 on J6 Header (Next to GPIO28)

Please forgive my terminology if I have got it wrong, I am still trying to get my head around the Raspberry Pi boards having used Arduinos many years ago and then had a 5 year break from them completely.

[6by9]

https://www.raspberrypi.org/documentati ... display.md

The 7" display is almost solely a function of the firmware, not the ARM OS. The ARM OS hasn't been started at the point when things like the rainbow screen are displayed.
Having said that the APIs for displaying stuff on screen do allow for sending stuff to a particular display rather than the default. It may be that the Windows IOT core does that to force output to HDMI - I don't know on that front.
Confirm you can get the rainbow screen on the 7" display first. That should solely be a function of dt-blob.bin.

[fruitoftheloom]

I have a Raspberry Pi 3 Dev board and Compute Module with a New 7" Official LCD Display.

I would like to connect my 7" Official Raspberry Pi Screen to my Dev board to allow me to use it with Windows IOT core. I am struggling to work out the correct pins to connect on between the screen and the dev board (or dev board to dev board) to allow the system to work. There seems to be little to no information about doing this (Or I am failing to be able to find it)

I have tested the screen with Raspbian and the LCD screen starts on boot and Touch and Display function. This shows me that the board is in working condition.

However when I switch the SD card for the Windows IOT Version (Version 10.0.15063.0) The Dev board will not boot to the LCD screen only the HDMI port (when I connect it to see if I am actually getting a boot)

The Ribbon cable of the Screen is connected to DISP1 on the Dev Board

On the back of the screen we have the 5 GPIO connectors;

For use with Raspbian I just have the following pins linked:
CD1_SDA (J6:37) -> GPIO 0 (J5:1)
CD1_SCL (J6:39) -> GPIO 1 (J5:3)
On Screen:
5V -> Pin 4 on J6 header (next to GPIO29)
GND -> PIN 2 on J6 Header (Next to GPIO28)

As stated, this appears to fully work

I am strugglign to work out the correct pin connections the LCD when used with Wondows IOT
I have the 5V and GND connected because they are logical, but what about the INT, SDA and SCL pins? Where do they connect on the Dev Board?

5V -> Pin 4 on J6 header (next to GPIO29)
INT -> ???
SDA -> ???
SCL -> ???
GND -> PIN 2 on J6 Header (Next to GPIO28)

Please forgive my terminology if I have got it wrong, I am still trying to get my head around the Raspberry Pi boards having used Arduinos many years ago and then had a 5 year break from them completely.

Microsoft do not list the CM3 as a supported device:

https://developer.microsoft.com/en-us/w ... iceoptions

[DavidCCC]

https://www.raspberrypi.org/documentati ... display.md

The 7" display is almost solely a function of the firmware, not the ARM OS. The ARM OS hasn't been started at the point when things like the rainbow screen are displayed.
Having said that the APIs for displaying stuff on screen do allow for sending stuff to a particular display rather than the default. It may be that the Windows IOT core does that to force output to HDMI - I don't know on that front.
Confirm you can get the rainbow screen on the 7" display first. That should solely be a function of dt-blob.bin.

I get the rainbow screen when I boot with the Raspbian SD Card but I do not get this when I boot with the Windows IOT sd card. Is it a simple case of copying the dt-blob.bin to a location on the IOT SD card? if so, where?

The interesting thing is that people make this work with a standard Raspberry Pi 3 board so theoretically it should work with the Dev board and compute module.

[fruitoftheloom]

https://www.raspberrypi.org/documentati ... display.md

The 7" display is almost solely a function of the firmware, not the ARM OS. The ARM OS hasn't been started at the point when things like the rainbow screen are displayed.
Having said that the APIs for displaying stuff on screen do allow for sending stuff to a particular display rather than the default. It may be that the Windows IOT core does that to force output to HDMI - I don't know on that front.
Confirm you can get the rainbow screen on the 7" display first. That should solely be a function of dt-blob.bin.

I get the rainbow screen when I boot with the Raspbian SD Card but I do not get this when I boot with the Windows IOT sd card. Is it a simple case of copying the dt-blob.bin to a location on the IOT SD card? if so, where?

The interesting thing is that people make this work with a standard Raspberry Pi 3 board so theoretically it should work with the Dev board and compute module.

You should be asking Microsoft if their kernel / firmware / eufi boot has been updated to support the CM3.......