6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5805
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Compute Module IO board and official 7in LCD?

Tue Dec 01, 2015 11:41 pm

There's an update to the docs pending at https://github.com/raspberrypi/documentation/pull/279 which includes full details of how to hook up the display and 2 cameras.

Do NOT include display_default_lcd=1 in config.txt - that is only relevant for DPI and VGA666 screens.

If you're going to define your own dt-blob.bin, then you need to add
[email protected]_SDA {
type = "internal";
number = <28>;
};
[email protected]_SCL {
type = "internal";
number = <29>;
};
[email protected]_I2C_PORT {
type="internal";
number=<0>;
};
and connect the display I2C to GPIOs 28&29, in parallel with one of the cameras.
If you don't want to parallel up a camera with the display, you should be able to amend the above and use pins 44&45 off either i2c-0 or i2c-1. It makes the wiring simpler, but actually has no gain in performance.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

kzmo
Posts: 3
Joined: Tue Dec 01, 2015 7:53 pm

Re: Compute Module IO board and official 7in LCD?

Wed Dec 02, 2015 9:15 am

Thank you very much 6by9, using the information you provided I managed to have run 2 cameras and 1 LCD display!
6by9 wrote:There's an update to the docs pending at https://github.com/raspberrypi/documentation/pull/279 which includes full details of how to hook up the display and 2 cameras.

Do NOT include display_default_lcd=1 in config.txt - that is only relevant for DPI and VGA666 screens.
In the docs update you mentioned, there is a line to add display_default_lcd=1 in config.txt - so I guess this is a bug in docs.
6by9 wrote: If you're going to define your own dt-blob.bin, then you need to add
[email protected]_SDA {
type = "internal";
number = <28>;
};
[email protected]_SCL {
type = "internal";
number = <29>;
};
[email protected]_I2C_PORT {
type="internal";
number=<0>;
};
and connect the display I2C to GPIOs 28&29, in parallel with one of the cameras.
If you don't want to parallel up a camera with the display, you should be able to amend the above and use pins 44&45 off either i2c-0 or i2c-1. It makes the wiring simpler, but actually has no gain in performance.
That was it: I connected GPIOs 44 & 45 to LCD's SDA and SCL and added proper pin_defines to dt-blob file and everything worked like a charm. Right now I'm powering LCD using external power adapter, I'll try however to power the LCD using 5V0 and GND pins available at J5 CMIO board. I guess it should work.

So to summarize it all.
My dt-blob.dts file for 2 cameras and 1 LCD display is:

Code: Select all

/dts-v1/;

/ {

	videocore {

		pins_cm {

			pin_config {

				[email protected] {
					polarity = "active_high";
					termination = "pull_down";
					startup_state = "inactive";
					function = "input";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "output";
					termination = "no_pulling";
				};

				[email protected] {
					function = "output";
					termination = "no_pulling";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "uart0";
					termination = "no_pulling";
				};

				[email protected] {
					function = "uart0";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "output";
					termination = "no_pulling";
				};

				[email protected] {
					function = "output";
					termination = "no_pulling";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_up";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "pull_down";
				};

				[email protected] {
					function = "input";
					termination = "no_pulling";
					drive_strength_mA = <0x8>;
					polarity = "active_high";
				};

				[email protected] {
					function = "output";
					termination = "no_pulling";
					drive_strength_mA = <0x8>;
					polarity = "active_low";
					startup_state = "active";
				};

				[email protected] {
					function = "sdcard";
					termination = "pull_up";
					drive_strength_mA = <0x8>;
				};

				[email protected] {
					function = "sdcard";
					termination = "pull_up";
					drive_strength_mA = <0x8>;
				};

				[email protected] {
					function = "sdcard";
					termination = "pull_up";
					drive_strength_mA = <0x8>;
				};

				[email protected] {
					function = "sdcard";
					termination = "pull_up";
					drive_strength_mA = <0x8>;
				};

				[email protected] {
					function = "sdcard";
					termination = "pull_up";
					drive_strength_mA = <0x8>;
				};

				[email protected] {
					function = "sdcard";
					termination = "pull_up";
					drive_strength_mA = <0x8>;
				};
			};

			pin_defines {

				[email protected]_CAMERAS {
					type = "internal";
					number = <0x2>;
				};

				[email protected]_0_LED {
					type = "internal";
					number = <0x2>;
				};

				[email protected]_0_SHUTDOWN {
					type = "internal";
					number = <0x3>;
				};

				[email protected]_0_UNICAM_PORT {
					type = "internal";
					number = <0x1>;
				};

				[email protected]_0_I2C_PORT {
					type = "internal";
					number = <0x0>;
				};

				[email protected]_0_SDA_PIN {
					type = "internal";
					number = <0x0>;
				};

				[email protected]_0_SCL_PIN {
					type = "internal";
					number = <0x1>;
				};

				[email protected]_1_LED {
					type = "internal";
					number = <0x1e>;
				};

				[email protected]_1_SHUTDOWN {
					type = "internal";
					number = <0x1f>;
				};

				[email protected]_1_UNICAM_PORT {
					type = "internal";
					number = <0x0>;
				};

				[email protected]_1_I2C_PORT {
					type = "internal";
					number = <0x0>;
				};

				[email protected]_1_SDA_PIN {
					type = "internal";
					number = <0x1c>;
				};

				[email protected]_1_SCL_PIN {
					type = "internal";
					number = <0x1d>;
				};
				
				[email protected]_SDA {
					type="internal";
					number=<44>;
				};
				
				[email protected]_SCL {
					type="internal";
					number=<45>;
				};

				[email protected]_I2C_PORT {
					type="internal";
					number=<0>;
				};
			};
		};
	};
};
My config.txt does NOT include display_default_lcd=1 - as 6by9 said.

The wiring is:
J5:
GPIO0 -> CD1_SDA
GPIO1 -> CD1_SCL
GPIO2 -> CAM1_IO1
GPIO3 -> CAM1_IO0

J6:
GPIO28 -> CD0_SDA
GPIO29 -> CD0_SCL
GPIO30 -> CAM0_IO1
GPIO31 -> CAM0_IO0
GPIO44 -> SDA on LCD board
GPIO45 -> SCL on LCD board

LCD itself is powered from external adapter. LCD is connected to DISP1.

One note: it looks that, after applying changed dt-blob, when I disconnect LCD and connect HDMI, then CAM1 is not available and I get error that "cannot load camera module". CAM0 works OK. The CAM1 works OK when I connect GPIOs 44&45 do LCD and power LCD up. Why's that? That's not a problem for me, but I'm wondering what the reason might be.

Anyway, thanks again 6by9 for help.

best regards,
Chris

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5805
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Compute Module IO board and official 7in LCD?

Wed Dec 02, 2015 10:39 am

kzmo wrote:In the docs update you mentioned, there is a line to add display_default_lcd=1 in config.txt - so I guess this is a bug in docs.
I thought the change had been merged, but it hasn't. Any pull request can be commented on by anyone with a github account (signup is free), so make corrections. There are 4 commits there, so do double check it hasn't been fixed in a later commit (ideally all the commits should be squashed into one before they will get merged).
kzmo wrote:One note: it looks that, after applying changed dt-blob, when I disconnect LCD and connect HDMI, then CAM1 is not available and I get error that "cannot load camera module". CAM0 works OK. The CAM1 works OK when I connect GPIOs 44&45 do LCD and power LCD up. Why's that? That's not a problem for me, but I'm wondering what the reason might be.
Pass. If you've got them wired to different GPIOs, then nothing springs to mind. If they were both on the same GPIO, then unpowered I2C pull-ups could interfere (I was just looking at that on a Pi2 the other day).

"vcgencmd get_camera" should confirm what the GPU has found.
I don't have a CM display board, so can't hook my display up to the CMIO. Might have to scrounge one from Pi Towers, or buy my own and wait ages for the Swag Store to ship them.

You could try to debug with raspi-gpio, enabling i2c_vc=on, setting disable_touchscreen=1 (requires absolute latest firmware - I added it at the weekend), and then manually pinmux and use i2c-detect -y 0 to find the devices. Do note that you setting two sets of pins to the same I2C peripheral at the same time will cause all I2C comms for that peripheral to fail - it does not combine the input signals.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

kzmo
Posts: 3
Joined: Tue Dec 01, 2015 7:53 pm

Re: Compute Module IO board and official 7in LCD?

Tue Dec 08, 2015 8:06 am

6by9 wrote: I thought the change had been merged, but it hasn't. Any pull request can be commented on by anyone with a github account (signup is free), so make corrections. There are 4 commits there, so do double check it hasn't been fixed in a later commit (ideally all the commits should be squashed into one before they will get merged).
Ok, will try to do that in the nearest feature.
6by9 wrote:"vcgencmd get_camera" should confirm what the GPU has found.
Will check that again, but AFAIR it returned Supported = 2, Detected = 1.
6by9 wrote: You could try to debug with raspi-gpio, enabling i2c_vc=on, setting disable_touchscreen=1 (requires absolute latest firmware - I added it at the weekend), and then manually pinmux and use i2c-detect -y 0 to find the devices. Do note that you setting two sets of pins to the same I2C peripheral at the same time will cause all I2C comms for that peripheral to fail - it does not combine the input signals.
Thank you, I'll try to check it when I have some time, since this matter is not the big issue.

b1gtuna
Posts: 23
Joined: Wed Oct 21, 2015 12:17 am

Re: Compute Module IO board and official 7in LCD?

Tue Jan 26, 2016 9:33 pm

Ok, haven't checked this thread past weeks. I removed `default_display_lcd` from the instruction.
The original commit I submitted still hasn't been merged btw =(.
Anyone has an idea what's the hold up?

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5805
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Compute Module IO board and official 7in LCD?

Tue Jan 26, 2016 11:41 pm

b1gtuna wrote:Ok, haven't checked this thread past weeks. I removed `default_display_lcd` from the instruction.
The original commit I submitted still hasn't been merged btw =(.
Anyone has an idea what's the hold up?
I've just pinged my main contact at Pi Towers with the question of who handles doc PRs. There are a fair few commits to the docs in the last few days so it's not that nothing is happening, just no one seems to be monitoring it.

One request you may get is to squash all your changes into one. There's no need for the main commit history to include the details over all your little edits. Wait and see if it gets queried on the PR first though.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

satya_2017
Posts: 1
Joined: Mon Feb 20, 2017 12:29 pm

Re: Compute Module IO board and official 7in LCD?

Mon Feb 20, 2017 12:43 pm

Unable to connect the seven inch touchscreen display to compute module 3 IO board

Purpose: - Just to use Official 7-inch screen as display

Using the following hardware:-

Compute Module 3 Lite
Compute module IO board V3.0
Official 7-inch touchscreen display
22 way to 15 way DSI display adapter
Official 5v power adapter
Software Info:-
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian

Followed the following process to connect:-

After running vcgencmd version, received the following output:-
Dec 9 2016 15:11:26
Copyright (c) 2012 Broadcom
version 2e557d8dac70add28597c3b449cb52c34588d818 (clean) (release)

Connected the display to the DISP1 port on the Compute Module IO Board through the 22W to 15W display adaptor.
Connected these pins together with jumper wires:
GPIO0 - CD1_SDA
GPIO1 - CD1_SCL
Executed the following command on the Compute Module 3 Lite:-

sudo wget https://goo.gl/Ah6XD5 -O /boot/dt-blob.bin

Rebooted for the dt-blob.bin file to be read, but the screen is blank.
Also supplied 5V extra power supply to PWR IN port of the touch screen.
But still, the screen is blank.

Image

Moscity
Posts: 5
Joined: Wed Oct 03, 2018 9:29 am
Location: Windisch, CH

Re: Compute Module IO board and official 7in LCD?

Fri Oct 05, 2018 9:55 am

Hello

I'm fighting with the same problem as mentioned here and I can't get it away.
I tried all the possibilities you wrote here and it still doesn't want to.

I posted my problem already here, so I don't want to rewrite it here. Please take a look.


I will update this post with pictures and log-files this afternoon.


If you need any more information, please tell.
M. Oscity

Moscity
Posts: 5
Joined: Wed Oct 03, 2018 9:29 am
Location: Windisch, CH

Re: Compute Module IO board and official 7in LCD?

Fri Oct 05, 2018 11:14 am

Hey, I am struggling with similar problems as described here.

I try to attach 2 Cams + 1 Display (in the end), but even only the display doesnt work.

I tried all possibilities described here, but couldn't get further after 4 days.
I wrote already post on stackexchange.

Please take a look there first, if you miss any information here.


So I connected it like this:

GPIO 0 -> CD1_SDA
GPIO 1 -> CD1_SCL
GPIO 4 -> CAM1_IO1
GPIO 5 -> CAM1_IO0

GPIO 28 -> CD0_SDA
GPIO 29 -> CD0_SCL
GPIO 30 -> CAM0_IO1
GPIO 31 -> CAM0_IO0

and also tried the version with
GPIO 44 -> Display's SDA
GPIO 45 -> Display's SCL
and edited the dt-blob.bin correspondingly (DISPLAY_SDA to 44, DISPLAY_SCL to 45, both pins as "input" with "pull_up")

I also tried DISPLAY_I2C_PORT set to number = <1> (and of course the default <0>), but that didn't help and is possibly the wrong way.

Can anyone help me out?


Thanks!


Here are my settings:

cat /proc/cpuinfo

Code: Select all

processor	: 0
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 76.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 1
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 76.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 2
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 76.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

processor	: 3
model name	: ARMv7 Processor rev 4 (v7l)
BogoMIPS	: 76.80
Features	: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4

Hardware	: BCM2835
Revision	: a220a0
Serial		: 000000000cf7740f

vcdbg log msg

Code: Select all

001533.245: brfs: File read: /mfs/sd/config.txt
001534.218: brfs: File read: 1694 bytes
001537.550: brfs: File read: /mfs/sd/dt-blob.bin
001558.634: HDMI:EDID version 1.3, 0 extensions, screen size 51x29 cm
001558.740: HDMI:EDID features - videodef 0x80 standby suspend active off; colour encoding:RGB444|YCbCr444|YCbCr422; sRGB is default colourspace; preferred format is native; does not support GTF
001558.860: HDMI:EDID found preferred CEA detail timing format: 1920x1080p @ 60 Hz (16)
001558.947: HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
001559.023: HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II
001559.108: HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
001559.187: HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II
001559.272: HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II
001559.358: HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II
001559.440: HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II
001559.574: HDMI:EDID standard timings block x 8: 0x714F 8180 D1C0 0101 0101 0101 0101 0101 
001559.672: HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 0
001559.771: HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 1
001559.872: HDMI:EDID found DMT format: code 82, 1920x1080p @ 60 Hz (16:9) in standard timing 2
001559.945: HDMI:EDID moving support for CEA mode 16 to DMT mode 82 because sink does not support HDMI
001560.027: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
001560.200: HDMI:EDID preferred mode is updated to DMT (82) 1920x1080p @ 60 Hz with pixel clock 148500000 Hz
001570.811: brfs: File read: 42266 bytes
001574.989: brfs: File read: /mfs/sd/config.txt
001575.837: HDMI:Setting property pixel encoding to Default
001575.896: HDMI:Setting property pixel clock type to PAL
001575.958: HDMI:Setting property content type flag to No data
001576.015: HDMI:Setting property fuzzy format match to enabled
001576.168: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001584.308: gpioman: gpioman_get_pin_num: pin BT_ON not defined
001584.371: gpioman: gpioman_get_pin_num: pin WL_ON not defined
001617.059: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
001679.908: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001679.994: hdmi: HDMI:>>>>>>>>>>>>>Rx sensed, reading EDID<<<<<<<<<<<<<
001692.095: hdmi: HDMI:EDID version 1.3, 0 extensions, screen size 51x29 cm
001692.209: hdmi: HDMI:EDID features - videodef 0x80 standby suspend active off; colour encoding:RGB444|YCbCr444|YCbCr422; sRGB is default colourspace; preferred format is native; does not support GTF
001692.322: hdmi: HDMI:EDID found preferred CEA detail timing format: 1920x1080p @ 60 Hz (16)
001692.409: hdmi: HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
001692.498: hdmi: HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II
001692.578: hdmi: HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
001692.667: hdmi: HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II
001692.751: hdmi: HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II
001692.832: hdmi: HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/II
001692.924: hdmi: HDMI:EDID found DMT format: code 36, 1280x1024p @ 75 Hz in established timing I/II
001693.059: hdmi: HDMI:EDID standard timings block x 8: 0x714F 8180 D1C0 0101 0101 0101 0101 0101 
001693.156: hdmi: HDMI:EDID found DMT format: code 21, 1152x864p @ 75 Hz (4:3) in standard timing 0
001693.251: hdmi: HDMI:EDID found DMT format: code 35, 1280x1024p @ 60 Hz (5:4) in standard timing 1
001693.362: hdmi: HDMI:EDID found DMT format: code 82, 1920x1080p @ 60 Hz (16:9) in standard timing 2
001693.448: hdmi: HDMI:EDID moving support for CEA mode 16 to DMT mode 82 because sink does not support HDMI
001693.524: hdmi: HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
001693.693: hdmi: HDMI:EDID preferred mode is updated to DMT (82) 1920x1080p @ 60 Hz with pixel clock 148500000 Hz
001693.755: hdmi: HDMI: hotplug attached with DVI support
001693.827: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
001696.283: hdmi: HDMI: power_on to DMT mode 1080p60
001699.500: hdmi: HDMI: Action callback added to queue to happen at frame 0
001716.213: *** Restart logging
001716.278: brfs: File read: 1694 bytes
001719.532: brfs: File read: /mfs/sd/cmdline.txt
001719.636: Read command line from file 'cmdline.txt':
001719.702: 'dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p7 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait splash plymouth.ignore-serial-consoles'
001720.027: brfs: File read: 175 bytes
002064.321: brfs: File read: /mfs/sd/kernel7.img
002064.387: Loading 'kernel7.img' to 0x8000 size 0x4b5338
002064.479: No kernel trailer - assuming DT-capable
002064.551: Trying Device Tree file 'bcm2710-rpi-cm3.dtb'
002064.618: brfs: File read: 4936504 bytes
002068.757: brfs: File read: /mfs/sd/bcm2710-rpi-cm3.dtb
002068.818: Loading 'bcm2710-rpi-cm3.dtb' to 0x4bd338 size 0x5e17
002085.947: dtdebug: delete_node(/__local_fixups__)
002095.527: dtdebug: /aliases:i2c_vc=i2c0
002105.096: dtdebug: /__symbols__:i2c_vc=i2c0
002112.256: dtdebug: /__overrides__:i2c_vc=i2c0
002126.063: dtdebug: /__overrides__:i2c_vc_baudrate=i2c0_baudrate
002130.401: dtdebug: /aliases:i2c=i2c1
002140.216: dtdebug: /__symbols__:i2c=i2c1
002147.446: dtdebug: /__overrides__:i2c=i2c1
002151.834: dtdebug: /aliases:i2c_arm=i2c1
002161.637: dtdebug: /__symbols__:i2c_arm=i2c1
002168.949: dtdebug: /__overrides__:i2c_arm=i2c1
002182.924: dtdebug: /__overrides__:i2c_baudrate=i2c1_baudrate
002196.921: dtdebug: /__overrides__:i2c_arm_baudrate=i2c1_baudrate
002196.952: dtparam: uart0_clkrate=48000000
002202.261: dtdebug: /__overrides__ has no uart0_clkrate property
002202.276: Unknown dtparam 'uart0_clkrate' - ignored
002202.339: brfs: File read: 24087 bytes
002206.774: brfs: File read: /mfs/sd/config.txt
002207.316: dtparam: i2c_arm=on
002212.318: dtdebug: Found override i2c_arm
002212.355: dtdebug:   override i2c_arm: string target 'status'
002223.642: dtparam: i2c_vc=on
002228.666: dtdebug: Found override i2c_vc
002228.701: dtdebug:   override i2c_vc: string target 'status'
002237.877: dtparam: audio=on
002243.056: dtdebug: Found override audio
002243.091: dtdebug:   override audio: string target 'status'
003140.789: dtparam: cam0-pwdn=5
003145.921: dtdebug: Found override cam0-pwdn
003145.949: dtparam: cam0-led=4
003151.091: dtdebug: Found override cam0-led
003151.119: dtparam: cam1-pwdn=31
003156.520: dtdebug: /__overrides__ has no cam1-pwdn property
003156.534: Unknown dtparam 'cam1-pwdn' - ignored
003156.601: dtparam: cam1-led=30
003161.996: dtdebug: /__overrides__ has no cam1-led property
003162.010: Unknown dtparam 'cam1-led' - ignored
003162.100: dtparam: arm_freq=1200000000
003167.472: dtdebug: Found override arm_freq
003167.523: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003182.095: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003196.777: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003211.574: dtdebug:   override arm_freq: cell target clock-frequency @ offset 0 (size 4)
003226.370: dtparam: core_freq=400000000
003231.767: dtdebug: /__overrides__ has no core_freq property
003231.782: Unknown dtparam 'core_freq' - ignored
003236.457: dtparam: cache_line_size=64
003241.622: dtdebug: Found override cache_line_size
003241.669: dtdebug:   override cache_line_size: cell target cache-line-size @ offset 0 (size 4)
003261.139: dtdebug: delete_node(/hat)
003272.479: Device tree loaded to 0x2eff9d00 (size 0x6244)
003274.304: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
004722.802: vchiq_core: vchiq_init_state: slot_zero = 0xf7980000, is_master = 1
004727.834: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
004733.877: TV service:host side not connected, dropping notification 0x00000002, 0x00000002, 0x00000052
056822.133: camsubs: Looking for camera 0: i2c_port = 0, led gpio = 4, power enable gpio = 5
057153.726: camsubs: Camera not found
057153.778: camsubs: Looking for camera 0: i2c_port = 0, led gpio = 4, power enable gpio = 5
057485.360: camsubs: Camera not found
057485.407: camsubs: Looking for camera 0: i2c_port = 0, led gpio = 4, power enable gpio = 5
057516.991: camsubs: Camera not found
057517.048: camsubs: Looking for camera 0: i2c_port = 0, led gpio = 4, power enable gpio = 5
057548.624: camsubs: Camera not found
057548.674: camsubs: Looking for camera 0: i2c_port = 0, led gpio = 4, power enable gpio = 5
057580.254: camsubs: Camera not found
057587.316: camsubs: Looking for camera 1: i2c_port = 0, led gpio = 30, power enable gpio = 31
057888.055: camsubs: Camera not found
057888.105: camsubs: Looking for camera 1: i2c_port = 0, led gpio = 30, power enable gpio = 31
058188.852: camsubs: Camera not found
058188.902: camsubs: Looking for camera 1: i2c_port = 0, led gpio = 30, power enable gpio = 31
058189.637: camsubs: Camera not found
058189.684: camsubs: Looking for camera 1: i2c_port = 0, led gpio = 30, power enable gpio = 31
058191.335: camsubs: Camera found OK
058193.401: gpioman: gpioman_get_pin_num: pin FLASH_0_ENABLE not defined
058193.452: gpioman: gpioman_get_pin_num: pin FLASH_0_INDICATOR not defined
058193.521: gpioman: gpioman_get_pin_num: pin FLASH_0_ENABLE not defined
058193.566: gpioman: gpioman_get_pin_num: pin FLASH_0_INDICATOR not defined
058193.627: gpioman: gpioman_get_pin_num: pin CAMERA_LED not defined
058193.672: gpioman: gpioman_get_pin_num: pin CAMERA_LED not defined

I wondered if these lines are alright: ?

Code: Select all

003140.789: dtparam: cam0-pwdn=5
003145.921: dtdebug: Found override cam0-pwdn
003145.949: dtparam: cam0-led=4
003151.091: dtdebug: Found override cam0-led
003151.119: dtparam: cam1-pwdn=31
003156.520: dtdebug: /__overrides__ has no cam1-pwdn property
003156.534: Unknown dtparam 'cam1-pwdn' - ignored
003156.601: dtparam: cam1-led=30
003161.996: dtdebug: /__overrides__ has no cam1-led property
003162.010: Unknown dtparam 'cam1-led' - ignored
vcgencmd version

Code: Select all

Sep 21 2018 15:48:28 
Copyright (c) 2012 Broadcom
version 07f57128b8491ffdefcdfd13f7b4961b3006d9a9 (clean) (release)
vcgencmd get_camera

Code: Select all

supported=2 detected=1
uname -a

Code: Select all

Linux raspberrypi 4.14.73-v7+ #1148 SMP Mon Oct 1 16:57:50 BST 2018 armv7l GNU/Linux
mount

Code: Select all

/dev/mmcblk0p7 on / type ext4 (rw,noatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=443728k,nr_inodes=110932,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mmcblk0p6 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=89664k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/mmcblk0p5 on /media/pi/SETTINGS1 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)

ls -la /boot

Code: Select all

insgesamt 22157
drwxr-xr-x  3 root root    2560 Jan  1  1970 .
drwxr-xr-x 23 root root    4096 Okt  5 10:11 ..
-rwxr-xr-x  1 root root   23315 Okt  5 10:14 bcm2708-rpi-0-w.dtb
-rwxr-xr-x  1 root root   22812 Okt  5 10:14 bcm2708-rpi-b.dtb
-rwxr-xr-x  1 root root   23071 Okt  5 10:14 bcm2708-rpi-b-plus.dtb
-rwxr-xr-x  1 root root   22589 Okt  5 10:14 bcm2708-rpi-cm.dtb
-rwxr-xr-x  1 root root   24115 Okt  5 10:14 bcm2709-rpi-2-b.dtb
-rwxr-xr-x  1 root root   25311 Okt  5 10:14 bcm2710-rpi-3-b.dtb
-rwxr-xr-x  1 root root   25574 Okt  5 10:14 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x  1 root root   24087 Okt  5 10:14 bcm2710-rpi-cm3.dtb
-rwxr-xr-x  1 root root   52116 Okt  5 10:14 bootcode.bin
-rwxr-xr-x  1 root root     175 Jan  1  1980 cmdline.txt
-rwxr-xr-x  1 root root    1694 Okt  5 11:33 config.txt
-rwxr-xr-x  1 root root   18693 Mär  9  2018 COPYING.linux
-rwxr-xr-x  1 root root   42266 Okt  5 13:03 dt-blob.bin
-rwxr-xr-x  1 root root      41 Okt  5 10:14 .firmware_revision
-rwxr-xr-x  1 root root    2618 Okt  5 10:14 fixup_cd.dat
-rwxr-xr-x  1 root root    6660 Okt  5 10:14 fixup.dat
-rwxr-xr-x  1 root root    9893 Okt  5 10:14 fixup_db.dat
-rwxr-xr-x  1 root root    9889 Okt  5 10:14 fixup_x.dat
-rwxr-xr-x  1 root root     145 Jun 27 03:22 issue.txt
-rwxr-xr-x  1 root root 4936504 Okt  5 10:14 kernel7.img
-rwxr-xr-x  1 root root 4686920 Okt  5 10:14 kernel.img
-rwxr-xr-x  1 root root    1494 Mär  9  2018 LICENCE.broadcom
-rwxr-xr-x  1 root root   18974 Jun 27 03:22 LICENSE.oracle
-rwxr-xr-x  1 root root     300 Jan  1  1980 os_config.json
drwxr-xr-x  2 root root   12288 Okt  5 10:14 overlays
-rwxr-xr-x  1 root root  677764 Okt  5 10:14 start_cd.elf
-rwxr-xr-x  1 root root 5108996 Okt  5 10:14 start_db.elf
-rwxr-xr-x  1 root root 2847044 Okt  5 10:14 start.elf
-rwxr-xr-x  1 root root 4047876 Okt  5 10:14 start_x.elf

IMG_6799.jpg
IMG_6799.jpg (105.84 KiB) Viewed 555 times
IMG_6799.jpg
IMG_6799.jpg (105.84 KiB) Viewed 555 times
Attachments
IMG_6800.jpg
IMG_6800.jpg (106.16 KiB) Viewed 542 times
Last edited by Moscity on Fri Oct 05, 2018 1:02 pm, edited 1 time in total.
M. Oscity

aBUGSworstnightmare
Posts: 1077
Joined: Tue Jun 30, 2015 1:35 pm

Re: Compute Module IO board and official 7in LCD?

Fri Oct 05, 2018 12:41 pm

Sorry, but which cable do you use for DSI interface (display -> DSI1 connector)?

There is a how-to available in the compute module documentation https://www.raspberrypi.org/documentati ... display.md

Connect everything as described and use this dt-blob.dts file https://www.raspberrypi.org/documentati ... 1-cam2.dts

this is the source --> you need to compile it into dt-blob.bin as described here https://www.raspberrypi.org/documentati ... uration.md

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5805
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Compute Module IO board and official 7in LCD?

Fri Oct 05, 2018 1:15 pm

If that is a Pi Zero camera cable then it is NOT compatible with hooking up the display to a CMIO.

Check the schematics at https://www.raspberrypi.org/documentati ... gnfiles.md and you'll see that routing of pins 11-14 differ.
Your CMIO should have been supplied with one adapter saying RPI-CAMERA, and one saying RPI-DISPLAY. Please use the display one.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

Moscity
Posts: 5
Joined: Wed Oct 03, 2018 9:29 am
Location: Windisch, CH

Re: Compute Module IO board and official 7in LCD?

Fri Oct 05, 2018 2:11 pm

Well, could explain my problems... haha.

I received the stuff from my prof and he just gave me the devices, but since our institute was moving (changed all rooms to the next building), he probably forgot to give me everything.

Next time I just order the stuff myself and then I know what's inside the package.


I will update you if it works with the right cable.

Thanks for the fast reply!
M. Oscity

Moscity
Posts: 5
Joined: Wed Oct 03, 2018 9:29 am
Location: Windisch, CH

Re: Compute Module IO board and official 7in LCD?

Fri Oct 05, 2018 4:17 pm

So did I understand it correctly this way:

1. ) I take the TouchScreen Display and use the 22-pin FFC cable, which is provided with the TouchDisplay:
The blue/white cable seen on this page.

I have one, it is as broad as the broad end of the Raspberry Pi Zero Camera Cable.
BUT I MAY NOT use the Raspberry Pi Zero Camera Cable.
I will just use the pi zero cable for my two SpyCams attached to CAM0 and CAM1 (which worked fine without display).

2.) Then I plug the other end of that 22-pin FFC cable into a DISPLAY ADAPTOR 22W to 15W . (need to order one)

EDIT: AND NOT CSI/DVI Cable Extender

3.) At the other end of the extender I use a 15-pin cable like this.


4.) And finally the other end of the 15-pin cable to the CM I/O Extension Board to DISP1.

Right?

And so I should get the image seen in your cmio-display.md - documentation.

I can try it next tuesday, when I'm back at work. (sadly, I would like to try earlier...)
EDIT: I can't, need to wait for delivery.
M. Oscity

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5805
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Compute Module IO board and official 7in LCD?

Mon Oct 08, 2018 8:39 am

Moscity wrote:
Fri Oct 05, 2018 4:17 pm
So did I understand it correctly this way:

1. ) I take the TouchScreen Display and use the 22-pin FFC cable, which is provided with the TouchDisplay:
The blue/white cable seen on this page.
That's a 15 way FFC, but yes it connects to the screen
Moscity wrote:I have one, it is as broad as the broad end of the Raspberry Pi Zero Camera Cable.
BUT I MAY NOT use the Raspberry Pi Zero Camera Cable.
I will just use the pi zero cable for my two SpyCams attached to CAM0 and CAM1 (which worked fine without display).
Correct.
Moscity wrote:2.) Then I plug the other end of that 22-pin FFC cable into a DISPLAY ADAPTOR 22W to 15W . (need to order one)

EDIT: AND NOT CSI/DVI Cable Extender
(Still a 15 way FFC) Correct, you want the RS part and not the Pi-shop one. The Pi-shop one connects two 15way FFC's together should you only want extra length to the cable.
Moscity wrote:3.) At the other end of the extender I use a 15-pin cable like this.
22way FFC :-)

Moscity wrote:4.) And finally the other end of the 15-pin cable to the CM I/O Extension Board to DISP1.
22-way FFC from the CMCDA board to DISP1 on the CMIO board.
Moscity wrote:Right?
Other than getting your 15 and 22 way FFC's swapped, yes.
It is a little confusing as they've used a narrower 0.5mm pitch on the 22way connector, therefore it is physically narrower than the 15way 1.0mm pitch used elsewhere.

CMIO board DISP1
22way FFC
CMCDA RPI-DISPLAY board
15way FFC
Screen.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

Moscity
Posts: 5
Joined: Wed Oct 03, 2018 9:29 am
Location: Windisch, CH

Re: Compute Module IO board and official 7in LCD?

Fri Oct 12, 2018 1:54 pm

Parts arrived: Now it works (two cams and one display). Poblem solved.

It was the Display Adaptor, as you said.
I wasn't aware of the Pin Switching.

Thank you very much!! :)


Might I suggest to add the following on the documentation page ?
  • Add a link to the display adaptor, maybe one of these links: your link, the RS link, or the Element14 Link (I used the swiss page, but maybe there is a generic link?)
  • OR highlight the display adaptor on the second picture in your documentation a bit more.
  • Comment out that the pins for the display are switched (Pin 11 - 14 as you mentioned 6by9)
because in the pi-shop.ch version of the development kit is the display adaptor not (yet) included, and probably in other kits from other sellers too.
M. Oscity

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5805
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Compute Module IO board and official 7in LCD?

Fri Oct 12, 2018 2:12 pm

Moscity wrote:
Fri Oct 12, 2018 1:54 pm
Parts arrived: Now it works (two cams and one display). Poblem solved.
Good news.
Moscity wrote:because in the pi-shop.ch version of the development kit is the display adaptor not (yet) included, and probably in other kits from other sellers too.
It looks like RS have dropped them from their bundle which I wasn't aware of.
https://uk.farnell.com/raspberry-pi/rpi ... dp/2675719 - "RPi Compute Module 3 & IO Board, Camera & Display Adaptor Board, FFC & USB cables, jumper wires"
https://uk.rs-online.com/web/p/processo ... s/1270226/ - "Compute Module 3, I/O Board V3, White Power Supply" (and £48exVAT more expensive!)

At least RS are selling the camera and display boards (Farnell had been not stocking them separately), but I certainly had always been making the assumption they had shipped with the CMIO. I'll query with sales.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

aBUGSworstnightmare
Posts: 1077
Joined: Tue Jun 30, 2015 1:35 pm

Re: Compute Module IO board and official 7in LCD?

Fri Oct 12, 2018 2:42 pm

6by9 wrote: At least RS are selling the camera and display boards (Farnell had been not stocking them separately), but I certainly had always been making the assumption they had shipped with the CMIO. I'll query with sales
mine came without any adapters; CMIO only in a white box with yellow label

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5805
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Compute Module IO board and official 7in LCD?

Fri Oct 12, 2018 2:58 pm

aBUGSworstnightmare wrote:
Fri Oct 12, 2018 2:42 pm
6by9 wrote: At least RS are selling the camera and display boards (Farnell had been not stocking them separately), but I certainly had always been making the assumption they had shipped with the CMIO. I'll query with sales
mine came without any adapters; CMIO only in a white box with yellow label
That sounds like you bought the CMIO alone, not the kit.

Anyway I've had confirmation from sales. The intent was that the two kits would be consistent, but something has gone wrong. It's on their list of things to resolve and realign the contents, so hopefully it will get resolved at some point.
I'll create an issue for the docs to get updated. If nothing else stating in big friendly letters that the two adapters are not the same would be sensible.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
Please don't send PMs asking for support - use the forum.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

Return to “Compute Module”