CMIO4&rpi-5.10.y - DSI1(2lanes) cannot display

Open
#3,987 25 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux, raspberry-pi

Research direction

Start by reproducing the reported setup with the rpi-5.10.y and mipi_dsi commits, using the /boot/config.txt settings and the supplied dts.txt and raspinfo.txt files. Compare the kernel and overlay behavior for the ST7701s two-lane DSI connection; done means the LCD displays the GUI rather than only the initialization or test screen.

Written by the indexing model from the issue text.

Description

Describe the bug

  1. Problem description:
    CMIO4 runs the latest rpi-5.10.y. The initialization code can be sent to MIPI LCD(ST7701s 2lanes) through lane0, but the GUI cannot be displayed.

  2. Raspberrypi kernel:
    https://github.com/raspberrypi/linux.git
    branch: rpi-5.10.y
    commit: 4f86a599b4cd07e635f289451d6460b1fd6d78ed

  3. Test code:
    https://github.com/Seeed-Studio/seeed-linux-dtoverlays.git
    branch: mipi_dsi
    commit: 668fdb0780c2e9685b9a6c96f15909d398398ada

  4. Test Method:

Config /boot/config.txt
dtparam=i2c_arm=on
dtparam=i2c_vc=on
ignore_lcd=1
dtoverlay=vc4-kms-v3d-pi4
dtoverlay=mipi_dsi-i2c10

Compile the code:
cd seeed-linux-dtoverlays
make all_rpi
sudo make install_rpi
sudo reboot

  1. Hardware:
    I have a bridge board, an MCU on the board controls the RESET and PWM backlight of the LCD, I2C connected to I2C1 of CMIO4, and the LCD MIPI pin is directly connected between the CMIO4.

  2. What I tried so far:
    I can send test commands to the LCD, and the LCD can display the test screen, as shown in the picture below.
    And I can see the correct display configuration through VNC.
    IMG_20201203_090824
    无标题

Logs
raspinfo.txt
dts.txt

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.