Uncategorized

hdmi mon special connect notes

Asked 
Viewed 29 times
0

I have a raspberry pi 4 using the latest Os but I cant get anything to display on my monitor the monitor I am using is MCT101HDMI-A I have tried another monitor and it display works so I know nothing wrong with the Pi or the SD card as i can also SSH into it.

My config.txt setting are currently:

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=87

hdmi_cvt=1280 800 60 5 0 0 0

#hdmi_timings=1280 0 16 44 100 800 0 10 3 10 0 0 0 60 0 71000000 7

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=7

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
start_x=1
gpu_mem=128

migrated from superuser.com 17 hours ago

This question came from our site for computer enthusiasts and power users.

  • Try with another cable .Then tell us the result – Sohan Arafat 10 hours ago
  • @user3298095, Ah, let me see. Is your MCT101HDMI-A direct Rpi 40 pin plug in (no cable) ? You might like to read the user guide farnell.com/datasheets/2622303.pdf, and use a multi-meter to open short test CON 4/5/6. WARNING: unplug power first! Good luck and cheers! 🙂 Con4 / Con5 /Con6 – tlfong01 6 hours ago    
  • @user3298095, And if open/short tests seems OK, ie,no poor contact problem. Then you can test the power points, ie, 5V/3v3, relative to every ground point. WARNING: this time you need to plug in power, but there is no guarantee your mon won’t explode into 5 pieces! Two more comments: (1) Blank screen usually means back lit LED which is independently powered, is OK, ie, not total loss! (2) Use a 40 pin 30+ cm extension ribbon COLOUR cable for easy access to everything. – tlfong01 6 hours ago    
  • @SohanArafat I have tried a different cable same result and I have the screen working with a pi 3 but have changed over to a pi 4 and having this issue. – FXUDarkNova 2 hours ago
  • @tlfong01 I don’t have the pi plugged directly into the screen just using a hdmi cable. It works fine with a pi 3 but i have swapped over to a pi 4 as i need more powerful device with more memory – FXUDarkNova 2 hours ago
  • @FXUDarkNova, Ah, perhaps I misunderstood your situation. Now let me start all over again. (1) Rpi3 + stretch + mini HDMI connector cable + MCT101HDMI-A mon = Good, (2) Rpi4 + buster + micro HDMI connector cable + MCT101HDMI-A mon = Bad, (3) Rpi4 + buster + micro HDMI connector cable,+ “another” mon = Good. Now let me see: (1) impiies MCT10HDMI mon is OK, at least for Rpi3. (3) implies Rpi4 + cable are OK, at least for “another” mon, (2) and (3) together imply (4) MCT mon does not like Rpi4B buster (cable should be OK though). Other comments and counter conclusion welcome! – tlfong01 56 mins ago   
  • @tlfong01 Yes you are correct seems to be an issue with pi4 buster and monitor I have been playing around with the config file and tvservice commands and the pi can see a monitor just getting nothing from the display any suggested to try something would be great. – FXUDarkNova 53 mins ago
  • @FXUDarkNova, I am still confused. Can you please confirm that the following video makes sense? 4 Easy Steps To Raspberry Pi Connection – Midas Displays – youtube.com/watch?v=9jDRPCYfqhw. – tlfong01 43 mins ago   
  • @tlfong01 the following video makes sense screen is still blank. – FXUDarkNova 40 mins ago
  • @FXUDarkNova, Now, look at the video capture below and please confirm the following: (1) You plug the Rpi’s 40 pin connector to the HDMI monitor. In other words, the monitor looks like a HAT to Rpi. imgur.com/gallery/4WYmUqA. This is what confuses me. – tlfong01 20 mins ago   
  • @tlfong01 yes that is how I have the pi set up with the monitor. – FXUDarkNova 18 mins ago
  • @FXUDarkNova, Ha, now I can make a not so quick and dirty conclusion. (1) When your huge HAT (I mean the mon) plugs into the tiny Rpi (40 pin connector) and boots, OS (stretch) detects there is a HAT and reads the EEPROM in the HAT (the mon!) using I2C and sets some parameters (perhaps mon config, touch screen config etc) into the stretch OS SD card image. I still have some other minor confusions, but my conclusion is that the mon is NOT compatible to Rpi4B. Anyway, I need to leave now. So you can carry on guessing. Good luck and cheers. – tlfong01 7 mins ago    
  • PS – Is your Rpi3 using stretch? If yes, you can change it to buster and try your luck. But I guess not much hope for any luck: either Rpi3 also gets a blank screen, or the mon explodes into 5 pieces! 🙂 – tlfong01 49 secs ago   Edit   

Categories: Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: