20250910榮品RD-RK3588-MID開發板在Android13系統下解決點卡迪的屏閃屏的問題
2025/9/5 15:44
緣起:榮品RD-RK3588-MID開發板在Android13系統下解決點卡迪的屏。
按 POWER按鍵 關機之后,2s之內再次短按 POWER按鍵,開機之后屏會抖動。
2s后短按 POWER按鍵,開機之后屏顯示正常。
解決步驟:屏蔽掉11 29后面的初始化代碼。
據說后面的代碼是控制端使用的?
最好還需要修改一下:de-active的極性為1。
請問 DTS中的 de-active 這個參數 ? 是干嘛用的呀?/配置啥的?
@2025?一般【我見過的屏都是 】 0x11 和 0x29命令之后 就沒有 命令了。
請問 一下命令是 必須的嗎?做什么用的?
// Video Mode Enable--------------------------------------------------
writecomm(0xB7);
writedata(0x59);
writedata(0x02);
//----------------------------------------------------------------------
writepattern(0xFF,0xFF,0xFF);
不需要
請問 這些 指令是 干嘛用的?
望文生義:看名字是 視頻模式使能的?感覺很重要的![破涕為笑][疑問]
RD-RK3588-MID開發板。
使用卡迪的屏。
關機之后。
串口打印:[ ? 49.896765][ ? ?T1] reboot: Power down
如果 2秒之內按 POWER按鍵開機。LCD屏會抖動。
2秒后 正常。上下電 時序 按照 規格書配置。
可能是啥原因?你們有碰到過嗎?
[ ?976.096472][ ? ?T1] **** wyb 2025/8/29 11:28 drivers/gpu/drm/panel/panel-simple.c panel_simple_shutdown 1084
[ ?976.106290][ ? ?T1] **** wyb 2025/8/29 11:28 drivers/gpu/drm/panel/panel-simple.c panel_simple_disable 485
[ ?976.115934][ ? ?T1] **** wyb 2025/8/29 11:28 drivers/gpu/drm/panel/panel-simple.c panel_simple_unprepare 516
[ ?976.125751][ ? ?T1] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown device
[ ?976.132188][ ? ?T1] mpp_rkvenc2 fdbe0000.rkvenc-core: shutdown success
[ ?976.138711][ ? ?T1] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown device
[ ?976.145141][ ? ?T1] mpp_rkvenc2 fdbd0000.rkvenc-core: shutdown success
[ ?976.172870][ ? ?T1] rk860-regulator 1-0042: rk860..... reset
[ ?976.179465][ ? ?T1] rk860-regulator 1-0042: force rk860x_reset ok!
[ ?976.185651][ ? ?T1] rk860-regulator 0-0043: rk860..... reset
[ ?976.192245][ ? ?T1] rk860-regulator 0-0043: force rk860x_reset ok!
[ ?976.198421][ ? ?T1] rk860-regulator 0-0042: rk860..... reset
[ ?976.205013][ ? ?T1] rk860-regulator 0-0042: force rk860x_reset ok!
[ ?976.211745][ ? ?T1] mpp_av1dec av1d-master: shutdown device
[ ?976.217327][ ? ?T1] mpp_av1dec av1d-master: shutdown success
[ ?976.223034][ ? ?T1] [WLAN_RFKILL]: Enter rfkill_wlan_shutdown
[ ?976.228777][ ? ?T1] [WLAN_RFKILL]: rockchip_wifi_power: 0
[ ?976.234172][ ? ?T1] [WLAN_RFKILL]: rockchip_wifi_power: toggle = false
[ ?976.240694][ ? ?T1] wifi power off
[ ?976.347593][ ? ?T1] [WLAN_RFKILL]: wifi shut off power [GPIO76-0]
[ ?976.353682][ ? ?T1] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 0
[ ?976.359573][ ? ?T1] xhci-hcd xhci-hcd.4.auto: remove, state 4
[ ?976.365312][ ? ?T1] usb usb6: USB disconnect, device number 1
[ ?976.371379][ ? ?T1] xhci-hcd xhci-hcd.4.auto: USB bus 6 deregistered
[ ?976.377908][ ? ?T1] xhci-hcd xhci-hcd.4.auto: remove, state 4
[ ?976.383655][ ? ?T1] usb usb5: USB disconnect, device number 1
[ ?976.389730][ ? ?T1] xhci-hcd xhci-hcd.4.auto: USB bus 5 deregistered
[ ?976.396516][ ? ?T1] rkisp_hw fdcc0000.rkisp: rkisp_hw_shutdown
[ ?976.402384][ ? ?T1] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown device
[ ?976.408826][ ? ?T1] mpp_rkvdec2 fdc48100.rkvdec-core: shutdown success
[ ?976.415379][ ? ?T1] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown device
[ ?976.421829][ ? ?T1] mpp_rkvdec2 fdc38100.rkvdec-core: shutdown success
[ ?976.428391][ ? ?T1] mpp-iep2 fdbb0000.iep: shutdown device
[ ?976.433866][ ? ?T1] mpp-iep2 fdbb0000.iep: shutdown success
[ ?976.439455][ ? ?T1] mpp_vepu2 fdbac000.jpege-core: shutdown device
[ ?976.445626][ ? ?T1] mpp_vepu2 fdbac000.jpege-core: shutdown success
[ ?976.451892][ ? ?T1] mpp_vepu2 fdba8000.jpege-core: shutdown device
[ ?976.458064][ ? ?T1] mpp_vepu2 fdba8000.jpege-core: shutdown success
[ ?976.464332][ ? ?T1] mpp_vepu2 fdba4000.jpege-core: shutdown device
[ ?976.470503][ ? ?T1] mpp_vepu2 fdba4000.jpege-core: shutdown success
[ ?976.476771][ ? ?T1] mpp_vepu2 fdba0000.jpege-core: shutdown device
[ ?976.482939][ ? ?T1] mpp_vepu2 fdba0000.jpege-core: shutdown success
[ ?976.489201][ ? ?T1] mpp_jpgdec fdb90000.jpegd: shutdown device
[ ?976.495030][ ? ?T1] mpp_jpgdec fdb90000.jpegd: shutdown success
[ ?976.500963][ ? ?T1] mpp_vdpu1 fdb51000.avsd-plus: shutdown device
[ ?976.507048][ ? ?T1] mpp_vdpu1 fdb51000.avsd-plus: shutdown success
[ ?976.513224][ ? ?T1] mpp_vepu2 fdb50000.vepu: shutdown device
[ ?976.518872][ ? ?T1] mpp_vepu2 fdb50000.vepu: shutdown success
[ ?976.524614][ ? ?T1] mpp_vdpu2 fdb50400.vdpu: shutdown device
[ ?976.530264][ ? ?T1] mpp_vdpu2 fdb50400.vdpu: shutdown success
[ ?976.536063][ ? ?T1] dwc3 fc000000.usb: Wakeup sysfs attributes not added
[ ?976.551215][ ? ?T1] reboot: Power down
Z:\rk-android13-20250818RD-RK3588-MID\kernel-5.10\arch\arm64\boot\dts\rockchip\rk3588\rp-lcd-mipi0-8-1200-1920.dtsi
?? ??? ??? ?03 78 01 11
03 0A 01 29
////------------- ?Display Initial Setting end -------------------------
//?
?? ??? ??? ?//// Video Mode Enable--------------------------------------------------
//03 00 01 B7
//03 00 01 59
//03 00 01 02
////----------------------------------------------------------------------
//
//23 00 03 FF FF FF
//
////Read From SD Card-----------------------------------------------------
////Dis_pic_from_SD(00
//
////Erase SD
////Erase_SD(
//
////BIST Enable GEN_WR(02 5A)---------------------------------------
//// ?GEN_WR(02 5A
//
////read register?
//// ?Readregister(80 10 01
//
//03 96 01 29
//03 FF 01 11
];
panel-exit-sequence = [
05 78 01 28
05 78 01 10
];
//HS10 ?VS12 VBP32 VFP34 HBP17 HFP16 PCLK149 Hactive1200 Vactive 1920
disp_timings0: display-timings {
native-mode = <&dsi0_timing0>;
dsi0_timing0: timing0 {
clock-frequency = <149000000>;
hactive ? ? ? ? = <1200>;
vactive ? ? ? ? = <1920>;
hback-porch ? ? = <17>;
hfront-porch ? ?= <16>;
vback-porch ? ? = <32>;
vfront-porch ? ?= <34>;
hsync-len ? ? ? = <10>;
vsync-len ? ? ? = <12>;
hsync-active ? ?= <0>;
vsync-active ? ?= <0>;
? ? ? ? ? ? ? ? de-active ? ? ? = <1>;
pixelclk-active = <0>;
};
百度:RK3588 電源不穩 MIPI 初始化代碼 下發 異常
Rockchip RK3588 MIPI-DSI2 詳解
RK3566 buildroot 拿掉 啟動界面
RK3588 休眠 喚醒 LCD初始化代碼
RK3588 關機之后 2秒之內開機 屏幕抖動
https://blog.51cto.com/u_15127674/4596055
https://blog.51cto.com/u_15284384/3060711
LCD之mipi DSI接口驅動調試流程
2.3.3、panel電荷無法釋放導致閃屏 --- 硬件設計
1.思路就是在lcd prepare期間判斷是dsi接口屏就給mipi控制器reset一下。
由于lcd不能直接調用mipi控制器接口,我就自己定義了一條特殊的mipi指令,在mipi控制器驅動那邊收到這條指令后進行reset操作。
https://blog.csdn.net/w504430863/article/details/140821572
rk3568和rk3588 ubuntu系統休眠喚醒后顯示異常
復位完成后,馬上寫入參數,可能會造成寫入不成功。
解決方案:
在dts文件里面加入init-delay-ms = <50>;
添加后的樣子
https://blog.csdn.net/Yongheng6/article/details/134557418
rk3588 mipi屏幕初始化參數下發失敗
https://blog.csdn.net/qq_45696114/article/details/140018559
rk3588驅動開發:休眠喚醒學習與分析1(個人理解)
https://zhuanlan.zhihu.com/p/9951119096
RK3588 Android12 假休眠 power鍵只關背光觸摸時喚醒亮屏
https://blog.csdn.net/weixin_49264216/article/details/140954266?spm=1001.2101.3001.6650.13&utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7ERate-13-140954266-blog-140954749.235%5Ev43%5Epc_blog_bottom_relevance_base5&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7ERate-13-140954266-blog-140954749.235%5Ev43%5Epc_blog_bottom_relevance_base5&utm_relevant_index=17
RK3568 花屏問題
https://blog.csdn.net/weixin_49264216/article/details/140954266
https://blog.csdn.net/weixin_49264216/article/details/140954749
RK3568 屏抖問題
https://blog.csdn.net/weixin_53757859/article/details/132034488?spm=1001.2101.3001.6650.12&utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7ERate-12-132034488-blog-52290815.235%5Ev43%5Epc_blog_bottom_relevance_base8&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7ERate-12-132034488-blog-52290815.235%5Ev43%5Epc_blog_bottom_relevance_base8&utm_relevant_index=21%E6%98%BE%E7%A4%BA%E6%A8%A1%E7%BB%84%E4%BD%BF%E7%94%A8%E8%BF%87%E7%A8%8B%E4%B8%AD%E5%87%BA%E7%8E%B0%E9%83%A8%E5%88%86%E9%97%AA%E5%B1%8F
顯示模組使用過程中出現部分閃屏
https://blog.csdn.net/weixin_53757859/article/details/132034488
步驟一:使用邏輯分析儀或示波器按驅動IC的上下電時序測試對應引腳,特別是電源、RST、D0+、D0-,若實測整機開關機及其Power鍵休眠喚醒的時序無法滿足驅動IC的要求則需按驅動IC的要求調整整機驅動更新時序;
https://blog.csdn.net/fantasyhujian/article/details/18522611?spm=1001.2101.3001.6650.2&utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7ERate-2-18522611-blog-52290815.235%5Ev43%5Epc_blog_bottom_relevance_base8&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7ERate-2-18522611-blog-52290815.235%5Ev43%5Epc_blog_bottom_relevance_base8&utm_relevant_index=5
https://blog.csdn.net/fantasyhujian/article/details/18522611
MIPI接口屏閃屏的分析及解決方法
https://2048ai.net/68244806a5baf817cf4bd059.html?spm=1001.2101.3001.6650.8&utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7Eactivity-8-85682485-blog-133706352.235%5Ev43%5Epc_blog_bottom_relevance_base8&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromBaidu%7Eactivity-8-85682485-blog-133706352.235%5Ev43%5Epc_blog_bottom_relevance_base8&utm_relevant_index=11
Rockchip之RK3288解決MIPI屏花屏
https://2048ai.net/68244806a5baf817cf4bd059.html
【很多調試步驟】
https://blog.csdn.net/qq_30624591/article/details/100137545
RK3288_Android7.1平臺基于DRM框架的LCD開發
https://cloud.tencent.com/developer/article/1867377
Linux MIPI DSI驅動調試筆記-LCD時序參數配置(三)
clock-frequency = (h_active + hfp + hbp + h_sync) * (v_active + vfp + vbp + v_sync) * fps
fps = 51200000 / (1024+160+160+70) * (600+23+12+10) = 51200000 / 912030 = 56Hz
https://developer.aliyun.com/article/1326364
Linux MIPI DSI LCD設備驅動開發調試細節學習筆記(一)
(h+hbp+hfp+hsa)*(v+vbp+vfp+vsa)*60