Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discrepancy on CrowPi2 specific statements in the config.txt file #38

Open
Pearl-852 opened this issue Feb 23, 2021 · 1 comment
Open

Comments

@Pearl-852
Copy link
Contributor

Pearl-852 commented Feb 23, 2021

I have found discrepancy on the CrowPi2 specific statements in the config.txt file.

hdmi_force_hotplug=1
max_usb_current=1    <-- This is now deprecated, see note 1 below
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1920 1080 60 6 0 0 0    <-- This specify the aspect ratio = 15:9
hdmi_drive=2
enable_uart=1
gpio=0=op,dl

Note 1: max_usb_current command reference is here.

In addition, I would recommend to add a conditional filter [EDID=*] to keep the CrowPi2 specific statements effective only when using in the CrowPi2.

  1. Open a terminal and run tvservice -n to view the EDID name of the CrowPi2 Display
$ tvservice -n
device_name=RTK-RTK_FHD
  1. Revise the config.txt file content adding the [EDID=*] filter as shown below
[EDID=RTK-RTK_FHD]
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt=1920 1080 60 3 0 0 0
hdmi_drive=2
enable_uart=1
gpio=0=op,dl
[all]

Note 2: The max_usb_current and hdmi_cvt statements are removed and revised respectively.

  1. Should you (Elecrow) choose to accept my recommended changes, please update your instructions here also.
@Pearl-852
Copy link
Contributor Author

Further checking on the supported video modes for the CrowPi2 Display as shown below

$ tvservice -m CEA
Group CEA has 16 modes:
           mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive 
           mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive 
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive 
           mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced 
           mode 6: 720x480 @ 60Hz 4:3, clock:27MHz x2 interlaced 
           mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced 
  (native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 
           mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive 
           mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive 
           mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive 
           mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced 
           mode 21: 720x576 @ 50Hz 4:3, clock:27MHz x2 interlaced 
           mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced 
           mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive 
           mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive 
$ tvservice -m DMT
Group DMT has 11 modes:
           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive 
           mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive 
           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive 
           mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive 
           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive 
           mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive 
           mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive 
           mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive 
           mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive 
           mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive 
  (prefer) mode 82: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive 

It would be safe to define hdmi_group=2 and hdmi_mode=82 in the config.txt file, as it is being reported as the preferred video mode. Rather than to define a custom CVT mode.

Revised config.txt file content:

[EDID=RTK-RTK_FHD]
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=82
hdmi_drive=2
enable_uart=1
gpio=0=op,dl
[all]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant