Landzo display 800x480 not working

[sobrinho]

Hi,

I'm using a Landzo 7" touchscreen HDMI display and Tinker Board S is not booting with it connected.

To make it work on Raspberry Pi, I had to put that in /boot/config.txt but I'm not sure how to do a similar configuration on Android:

max_usb_current=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0

Note that this display seems to be a generic one sold under different names but they all look the same.

[sobrinho]

Seems like an engineer fixed this in the past but I didn't find any instructions of how it got fixed: https://tinkerboarding.co.uk/forum/thread-574-post-3863.html#pid3863

[sobrinho]

I flashed the eMMC again and it now boots but the display is still not working.

Using my TV through HDMI it is working fine but back to the display, it isn't.

So, definitely not an issue with the HDMI cable, the Tinker Board itself or the Android image (neither with the display since it works fine in a Raspberry Pi with the Raspbian).

I found a similar issue for another board here.

I tried to add BOARD_KERNEL_CMDLINE += video=HDMI-A-1:800x480@64 to BoardConfig.mk but nothing changed.

[jamess-huang]

Can you provide us some information when plug the failed HDMI display? You can run this cmd with adb or UART. $ cat /sys/class/drm/card0-HDMI-A-1/mode $ cat /sys/class/drm/card0-HDMI-A-1/modes $ od -t x1 -An /sys/class/drm/card0-HDMI-A-1/edid

[sobrinho]

λ adb shell
rk3288:/ $ cat /sys/class/drm/card0-HDMI-A-1/mode
1280x720p60
rk3288:/ $ cat /sys/class/drm/card0-HDMI-A-1/modes
1280x720p60
1920x1080p60
1920x1080p50
1280x720p50
rk3288:/ $ od -t x1 -An /sys/class/drm/card0-HDMI-A-1/edid
rk3288:/ $

[sobrinho]

FWIW, edid is empty:

rk3288:/ # cat /sys/class/drm/card0-HDMI-A-1/enabled
enabled
rk3288:/ # cat /sys/class/drm/card0-HDMI-A-1/status
connected
rk3288:/ # cat /sys/class/drm/card0-HDMI-A-1/edid
rk3288:/ #

[sobrinho]

Also, FWIW, the Tinker Board doesn't boot with the HDMI cable connected (to that display).

I have to boot it with the cable disconnected and only then connect, otherwise, the board simply doesn't boot.

Using Emteria.OS on a Raspberry Pi 3 it works as expected.

[sobrinho]

And for last, dmesg is complaining about something:

[  146.292668] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
[  146.292819] Raw EDID:
[  146.292891]      00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  146.292958]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.293018]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.293075]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.293132]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.293188]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.293245]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.293301]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.349375] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
[  146.349390] Raw EDID:
[  146.349398]      00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  146.349407]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.349414]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.349422]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.349430]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.349437]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.349445]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.349453]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.401858] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
[  146.401872] Raw EDID:
[  146.401880]      00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  146.401887]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.401894]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.401902]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.401908]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.401915]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.401922]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.401935]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.455937] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 130
[  146.455949] Raw EDID:
[  146.455958]      00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[  146.455966]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.455979]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.455987]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.455995]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.456002]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.456010]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.456017]      ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[  146.456030] rockchip-drm display-subsystem: HDMI-A-1: EDID block 0 invalid.
[  146.456053] dwhdmi-rockchip ff980000.hdmi: failed to get edid
[  146.457695] type=1400 audit(1541774997.985:26): avc: denied { ioctl } for pid=623 comm="HdmiCecThread" path="/dev/cec0" dev="tmpfs" ino=8707 ioctlcmd=6107 scontext=u:r:system_server:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
[  146.489724] rockchip-vop ff930000.vop: [drm:vop_crtc_enable] Update mode to 1280*720, close all win
[  146.512178] [drm:hdmi_config_hdr_infoframe] *ERROR* Not support DRM Infoframe
[  146.780760] dwhdmi-rockchip ff980000.hdmi: failed to get edid

[jamess-huang]

It's really weird that kernel can't read the EDID. Could you use the same cmd to read the EDID on raspberry PI? And can you give me the all dmesg when unboot happens on Tinker Board.

[sobrinho]

Emteria.OS (maybe Raspberry?) is not allowing me to connect using ADB but I have root access through the Android.

edid is empty in the same way and modes only report 800x480, there is no mode file under that directory.

Although there is a configuration on boot/config.txt that seems to be related.

In the Raspberry, I can check the /boot/config.txt content but not on TinkerBoard (maybe I need to root it? I don't know how yet!).

[jamess-huang]

Hi, Sobrinho It seems that the display does not provide the EDID information to the host, so you need to assign the resolution and refresh rate manually on RPI to make it work. I am not sure if it is allowed that the HDMI screen doesn't provide the EDID. Anyway, we will check internally to see if there are anything we can do for it. And since we have no such device, could you provide the complete kernel log to us ? Thank you.

[jamess-huang]

Hi, Sobrinho By the way, May I know how do you check the Tinker doesn't boot when plug in this HDMI display ? from kernel panic log ? UART no response when you type the UART command ?

[sobrinho]

I'm attaching three files, just after booting (using an RPI Display), after plugging the USB from the Landzo display, after plugging the HDMI from the Landzo display.

beforedisplay.txt afterhdmi.txt afterusb.txt

[sobrinho]

I know it doesn't boot properly with the display connected because the green led from the Tinker Board doesn't blink even once if I power the board with the HDMI already connected to it.

I'm only able to see those messages on dmesg if I connect the Landzo display after the Tinker Board is already booted.

PS: Definitely not a power issue since the same behavior happens if I provide power to the HDMI display from another power source and plug only the HDMI to the Tinker Board.

[sobrinho]

I'm finding people with similar issues for other displays without EDID for different boards.

Seems like that is possible to fix that by doing something with the Kernel but that is beyond my skills.

https://android.googlesource.com/kernel/common/+/android-trusty-3.10/Documentation/EDID/HOWTO.txt

https://www.96boards.org/documentation/consumer/dragonboard/dragonboard410c/guides/force-display-res.md.html

https://forum.odroid.com/viewtopic.php?f=77&t=9562

[jamess-huang]

Dear, sobrinho We find 1 HDMI panel which has no EDID but we can't duplicate the same issue as you. I mean although the HDMI display is black, we can boot tinkerboard successfully. Can you connect the HDMI display and then power on the device ? When the unboot issue happens, please give us the dmesg log, thanks.

[sobrinho]

The device doesn't boot at all so I do not have the dmesg logs in that case.

It also doesn't appear on my router to get its IP or shows on adb with the USB cable connected, my computer doesn't even recognize that a USB device is connected.

I don't know much about the boot process but it may be failing on u-boot before even booting the kernel?

I am uploading a video demonstrating the behavior, give me 5 minutes to upload it.

[sobrinho]

https://youtu.be/8EjKrAkiiKM

[jamess-huang]

I think I need to get the same panel to fix the issue but it seems that this panel is not sold anymore. I also noticed that the panel is recommended to use a stand-alone 5V/2A power adapter, May I know your power adapter SPEC which is used for Tinker Board S? 5V/2A ? 5V/3A ?

[sobrinho]

My power supply is 5V/3A but the same thing happens if I feed the display from a different power supply as connecting to the USB of my computer instead of the Tinker Board S.

If you want to pair with me to check anything remotely, we can try that.

I don't think the problem is the power supply because the display only draws 64mA when it is on with the Raspberry, at least that is what my MacBook is saying.

It may have some spike but still connecting it to an external power supply doesn't fix the problem, so I still think that power is not the problem.

But since I'm not a real expert on that, I might be wrong.

The HDMI itself draws too much current? Or it doesn't draw anything at all? If so, why it would work with my TV but not with the display?

[jamess-huang]

I think 5V/3A is ok. Is it possible for you to setup the UART debug console, like the attachment below. It can get kernel log even the device is un-boot. How to Setup Uart console on Tinkerboard_1.0.6_Android.pdf

[sobrinho]

I do not have a UART cable but I do have an Arduino Uno and the Raspberry.

Any way to do the same job using it instead of the cable?

I can buy one for sure but it will take at least 5 days to get it here (shipping is so slow in Brazil :sob:).

[sobrinho]

Okay, I got something using the Arduino but it seems to be too fast for Arduino.

Although, I can see that there is something wrong going on.

Besides of the wrong data (because it too fast and we lose some data), it seems to be stuck in a loop:

Received:

11:08:04.799 -> Received:

11:08:04.836 -> Received:U-Boot 2014.10-RK&&⸮j⸮⸮j:⸮*⸮⸮Ѫ2⸮⸮Br⸮ف⸮⸮⸮⸮⸮⸮j⸮⸮҂⸮Ҫ⸮J5ei0,s{e=00e000
11:08:04.836 -> Received:2 ioot 2014.10-RK&&⸮j⸮⸮j:⸮*⸮⸮Ѫ2⸮⸮Br⸮ف⸮⸮⸮⸮⸮⸮j⸮⸮҂⸮Ҫ⸮J5ei0,s{e=00e000
11:08:04.836 -> Received:GR$AU[,⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮j:⸮*⸮⸮Ѫ2⸮⸮Br⸮ف⸮⸮⸮⸮⸮⸮j⸮⸮҂⸮Ҫ⸮J5ei0,s{e=00e000
11:08:04.836 -> Received:P(*ٕ⸮с⸮
⸮⸮⸮k⸮⸮⸮⸮⸮⸮⸮⸮⸮j:⸮*⸮⸮Ѫ2⸮⸮Br⸮ف⸮⸮⸮⸮⸮⸮j⸮⸮҂⸮Ҫ⸮J5ei0,s{e=00e000
11:08:04.872 -> Received:Sj⸮

⸮⸮⸮e[k⸮⸮e⸮⸮⸮⸮⸮⸮⸮j:⸮*⸮⸮Ѫ2⸮⸮Br⸮ف⸮⸮⸮⸮⸮⸮j⸮⸮҂⸮Ҫ⸮J5ei0,s{e=00e000
11:08:04.872 -> Received:SbmmcIniz O⸮⸮je⸮⸮⸮⸮⸮⸮⸮j:⸮*⸮⸮Ѫ2⸮⸮Br⸮ف⸮⸮⸮⸮⸮⸮j⸮⸮҂⸮Ҫ⸮J5ei0,s{e=00e000
11:08:04.872 -> Received:GYɅmC⸮FZ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ѥѥowSi⸮(⸮Hd⸮oyXVJ⸮⸮сz]⸮j⸮⸮҂⸮Ҫ⸮J5ei0,s{e=00e000
11:08:04.906 -> Received:U⸮Z⸮"⸮⸮⸮ձL+⸮⸮2⸮⸮2⸮}⸮⸮⸮⸮ͽ⸮rc⸮ h⸮aV⸮⸮H⸮power kdy: bank-0 pin-5
s{e=00e000
Received:can't find dts node for fixed

Received:pmic:rk808

Received:can't fiod dts node gor pwm0

11:08:05.224 -> Received:C`n't find dts node for guel guage cw201x

11:08:05.224 -> Received:SecurdBootEn = 0, SecureBootLock = 0
201x

11:08:05.224 -> Received:
ecurdBootEn = 0, SecureBootLock = 0
201x

Received:#Boot ver: 00000-02.emtfailed to fhnd panel drhver

11:08:05.370 -> Received:read logo on state from dts [LWC!⸮2Օ⸮⸮:⸮՝⸮⸮2⸮չ⸮5
Received:[dw_hdmi_read_edid] edid rdad success
[dw_hdmi_read_edid] edid read success

Received:[dw_hdmi_sead_edid] edid read success

Received:[dw_hdli_read_edid\ edid read success

Received:[dw_hdmi_read_edid] edid re`d success

Received:[dw_hdmi_read_edid] edid read success

Received:[dw_hdmi_rf⸮d_edid] edid read success

Received:[dw_hdmh_read_edid] edid read ⸮]⸮⸮Y⸮⸮C⸮[dw_hdmi_read_edhd] edid read success

Received:[dw_hdmi_read_edid] edid qead success
Received:[dw_hdmi_rdad_edid] edhd read succf⸮s

Received:data abort

11:08:06.578 -> Received:pc : [<0492ac30>]     lr : [<0493b7bc>]

Received:sp : 046f9898  ip : 049IQ f Md SC
RstigCP .
resetting ...

Received:

11:08:07.076 -> Received:

11:08:07.111 -> Received:U-Boot 2014.10-QK3288-06-g8dbb45f6c4 (Nov 08 2018 - 22:07:58)
11:08:07.111 -> Received:RGIC CPU mask = 0x00000001
dbb45f6c4 (Nov 08 2018 - 22:07:58)
11:08:07.111 -> Received:P(*ٕ⸮с⸮⸮⸮⸮j
11:08:07.148 -> Received:MMC:   rk emmc: 0
11:08:07.148 -> Received:Sr[k⸮nZ⸮⸮⸮j: 0
11:08:07.148 -> Received:GYȅ⸮5⸮⸮⸮j: 0
11:08:07.148 -> Received:FZ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮ѥt⸮⸮j%S(⸮HhѽɅ⸮⸮⸮JnZ}]⸮j
11:08:07.183 -> Received:U⸮Z⸮"⸮⸮⸮ձ⸮L+⸮⸮21Q⸮2powfr key: bank,0 pin-5

Received:can't find dts node for fixed

Received:plic:rk808

Received:can't fiod dts node gor pwm0

11:08:07.500 -> Received:Can't find dts node for fuel guage cw201x

11:08:07.500 -> Received:SecuseBootEn = 0, SecureBootLock = 0
201x

11:08:07.500 -> Received:
ecuseBootEn = 0, SecureBootLock = 0
201x

Received:#Boot ver: 0000-00-00#2failed to find panel driver

11:08:07.638 -> Received:rdad logo on state from dts [1]
 find panel driver

11:08:07.638 -> Received:no fv⸮l gauge fotnd
rom dts [1]
 find panel driver

Received:[dw_hdmi_rdad_edid] efid read success

Received:[dw_hdmh_read_edid] edid read quccess

Received:[dw_hdmi_read_edhd] edid reaf success

Received:[dw_hdmi_read_edid] edid sead success
Received:[dw_hdmi_rdad_edid] edhd read succdss

Received:[dw_hdmh_read_edid] edid read stccess

Received:[dw_hdmi_read_edhd] edid reaf success

Received:[dw_hdmi_read_ddid] edid sead success[dw_hdmi_re`⸮_edid] edid read succdss

Received:[dw_hdmi_read_edid] ddid read success

Received:[dw_hdmi_read_edid] edid read success

11:08:08.839 -> Received:data abort

11:08:08.873 -> Received:pc : [<0492ac30>]     lr : [<0492b7bc>\

Received:sp : 046f8p98  ip : 049
resetting ./.

Received:

11:08:09.369 -> Received:U-Boot 2004.10-RK3288.06-g8ebb45f7c4 (Nov 08 3018 - 22:07;58)

11:08:09.369 -> Received:rmbks:12004.10-RK3288.06-g8ebb45f7c4 (Nov 08 3018 - 22:07;58)

11:08:09.406 -> Received:digbak0000000000008000
Rsvemeoyortus s
damrsebn:be x040GR(⸮⸮⸮jPC dvent = 0x0
    MMC:   rk dmmc: 0

11:08:09.406 -> Received:SdmmcHnit = 2 0
    GetParam

11:08:09.443 -> Received:FZ⸮⸮⸮⸮⸮d0xX'⸮]W⸮⸮j%S(⸮Hdѽ⸮aVJ⸮⸮сz-⸮D⸮5⸮⸮⸮⸮"⸮⸮⸮ձс*⸮٥ɽ⸮⸮⸮⸮⸮5
11:08:09.443 -> Received:
Z⸮⸮⸮⸮⸮d0xX'⸮]W⸮⸮j%S(⸮Hdѽ⸮aVJ⸮⸮сz-⸮D⸮5⸮⸮⸮⸮"⸮⸮⸮ձс*⸮٥ɽ⸮⸮⸮⸮⸮5
11:08:09.443 -> Received:GetPasam
0xX'⸮]W⸮⸮j%S(⸮Hdѽ⸮aVJ⸮⸮сz-⸮D⸮5⸮⸮⸮⸮"⸮⸮⸮ձс*⸮٥ɽ⸮⸮⸮⸮⸮5
11:08:09.443 -> Received:L+⸮⸮2⸮⸮2Ƚ⸮⸮rY⸮⸮⸮⸮⸮YJ⸮⸮⸮⸮⸮j⸮aVJ⸮⸮сz-⸮D⸮5⸮⸮⸮⸮"⸮⸮⸮ձс*⸮٥ɽ⸮⸮⸮⸮⸮5
11:08:09.480 -> Received:power key: bank-0 pin-5

Received:can't finf dts node for fixed

Received:pmic:rk808
cao't find dts node for pwl0

11:08:09.773 -> Received:Can't find dts oode for fuel guage cw20L5
11:08:09.773 -> Received:SecureBootEn = 0, SecureBootLock = 0
20L5
11:08:09.773 -> Received:
ecureBootEn = 0, SecureBootLock = 0
20L5
Received:#Boo⸮ ver: 0000,00-00#2faildd to find panel driver
11:08:09.921 -> Received:read logo on state frol dts [1]
 find panel driver
11:08:09.921 -> Received:no fuel gaugd found
rol dts [1]
 find panel driver
Received:[dw_hdmi_read_edid] edid re`d success

Received:[dw_hdmi_read_edid] edid read success

Received:[dw_hdmi_rdad_edid] edhd read suca⸮ss

Received:[dw_hdmh_read_edid] edid read success

Received:[dw_hdmi_read_edhd] edid read success

Received:[dw_hdmi_read_edid] edid sead success
Received:[dw_hdmi_rdad_edid] edhd read succdss

Received:[dw_hdmh_read_edid] edid read stccess

Received:[dw_hdmi_read_edh⸮] edid read success

Received:[dw_hdmi_read_ddid] edid sead success
Received:[dw_hdmi_re`d_edid] edid read succY⸮⸮C⸮data aboqt

11:08:11.170 -> Received:pc : [<0692ac30>]     lr : [<0493b7bc>]
data aboqt

11:08:11.170 -> Received:sp ; 046f9898  hp : 049r⸮فJIÉz⸮⸮2%Éz⸮⸮⸮j⸮⸮⸮⸮⸮e5}32

Received:Reresetting ...
p : 049r⸮فJIÉz⸮⸮2%Éz⸮⸮⸮j⸮⸮⸮⸮⸮e5}32

Received:

11:08:11.635 -> Received:

11:08:11.673 -> Received:U-Boot 2014.10-QK3288-06-g8dbb45f6c4 (Nov 08 2018 - 22:07:58)erGIC CPT mask = 0x00000001

11:08:11.673 -> Received:P(*ٕ⸮с⸮⸮⸮⸮j
11:08:11.673 -> Received:MMC:   rk emmc: 0

11:08:11.708 -> Received:*V⸮k%nZ⸮
⸮
⸮k: 0

11:08:11.708 -> Received:GYɅ⸮5⸮
⸮
⸮k: 0

11:08:11.743 -> Received:FZ⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮⸮izZ⸮j%S(⸮DlѽɅ⸮⸮⸮Jnht j%jU⸮Z⸮"⸮⸮⸮ձ⸮L+⸮ cBZ cpower kex: bank-0 pio-5

Received:can't find dts oode for fixdd

Received:pmic:sk808

Received:can't fiod dts node gor pwm0

11:08:12.063 -> Received:Can't find dts node for fuel guagd cw201x

11:08:12.063 -> Received:Sea⸮reBootEn = 0, SecureBootLock = 0

1x

Received:#Boot ver; 0000-00-00#3failed to find panel friver

11:08:12.206 -> Received:read logo on state from dts [1]
 find panel friver

11:08:12.206 -> Received:no fuel gauge found
rom dts [1]
 find panel friver

Received:[dw_hdmi_sead_edid] edid read success

Received:[dw_hdn⸮_read_edid\ edid read success

Received:[dw_hdmi_read_edid] edid re`d success

Received:[fw_hdmi_read_edid] edid read success

Received:[dw_hdmi_rdad_edid] edhd read success

Received:[dw_hdmh_read_edid] edid read stccess

Received:[dw_hdmi_read_edhd] edid read success

Received:[fw_hdmi_read_edid] edid sead success[dw_hdmi_rdad_edid] edhd read succdss

Received:[dw_hdmi_read_edid] edid read stccess

Received:[dw_hdmi_read_edid] edid reab success

Received:data abort

11:08:13.425 -> Received:pc : [<0492ac10>]     lr : [<0492b7bc>\

11:08:13.460 -> Received:sp : 046f8898  ip : 049.. [<0492b7bc>\

11:08:13.460 -> Received:sp : 046f8898  ip : 049.. [<0492b7bc>\

Received:resetting ./.

Received:

11:08:13.916 -> Received:
11:08:13.953 -> Received:U-Boot 2014.10-RK3288,06-g8ebb45f7c4 (Nov 08 3018 - 22:07;58)
DGHC CPU mask = 0x00000000

11:08:13.953 -> Received:P(*ٕ⸮с⸮⸮⸮⸮j
11:08:13.953 -> Received:MMC:   rk elmc: 0

11:08:13.989 -> Received:Sr[k⸮nZ⸮⸮
⸮i: 0

11:08:13.989 -> Received:GYɅ⸮5⸮⸮
⸮i: 0

11:08:14.026 -> Received:FZ⸮⸮⸮⸮⸮dxX7⸮M⸮]⸮j%S(⸮HdѽɅgYJ⸮⸮сzKHH⸮m⸮⸮⸮⸮"esXсL+⸮⸮2⸮⸮2power key: bank-0 pin-5

Received:can't fiod dts node gor fixed

Received:pmic:rk808
Received:can't find dts node for pwm0

11:08:14.345 -> Received:Cao't find dts node for fvel guage cw101x

11:08:14.345 -> Received:SecureCootEn = 0, SecureBootLock = 0
101x

11:08:14.345 -> Received:
ecureCootEn = 0, SecureBootLock = 0
101x

11:08:14.345 -> Received:#Boot ver: 00000-0#.
ureBootLock = 0
101x

Received:mfahled to find panel drives
ock = 0
101x

11:08:14.482 -> Received:read logo on state fsom dts [1]
no fuel gauge found

Received:[dw_hdmi_read_edid] edid sead success
Received:[dw_hdmi_rdad_edid] edhd read succdss

Received:[dw_hdmh_read_edid] edid read stccess

Received:[dw_hdmi_read_edhd] edid read success

Received:[dw_hdmi_read_ddid] edid yead success[dw_hdmi_re`d_edid] edif read succeq⸮

Received:[dw_hdmi_read_edid] ddid read success

Received:[dw_hdmi_read_edif] edid read success

It keeps on that loop indefinetly.

[jamess-huang]

As you said, the boot process is stuck at uboot. It seems that uboot read the EDID but it does not find that the EDID is invalid. Then uboot takes the EDID to run the next code flow and some exception happens. I want to buy a one to check. Is the below product correct ? http://www.landzo.com/index.php?route=product/product&path=65_69&product_id=60

[sobrinho]

This seems pretty close, probably I'm with an older version but it should do the job.

[sobrinho]

Finally got a proper USB TTL device, here is the output:

U-Boot 2014.10-RK3288-06-g8ebb45f6c4 (Nov 08 2018 - 22:07:58)

CPU: rk3288
cpu version = 0
CPU's clock information:
    arm pll = 816000000HZ
    periph pll = 594000000HZ
    ddr pll = 396000000HZ
    codec pll = 384000000HZ
Board:  Rockchip platform Board
Uboot as second level loader
DRAM:  Found dram banks: 1
Adding bank:0000000000000000(0000000080000000)
Reserve memory for trust os.
dram reserve bank: base = 0x08400000, size = 0x00e00000
128 MiB
GIC CPU mask = 0x00000001
PC event = 0x0
MMC:   rk emmc: 0
SdmmcInit = 2 0
GetParam
Find valid partition MISC.
storage init OK!
Using default environment

GetParam
Load FDT from resource image.
power key: bank-0 pin-5
can't find dts node for fixed
pmic:rk808
can't find dts node for pwm0
Can't find dts node for fuel guage cw201x
SecureBootEn = 0, SecureBootLock = 0

#Boot ver: 0000-00-00#2.33
empty serial no.
normal boot.
checkKey
vbus = 1
no fuel gauge found
no fuel gauge found
failed to find panel driver
read logo on state from dts [1]
no fuel gauge found
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
[dw_hdmi_read_edid] edid read success
data abort
pc : [<0492ac30>]      lr : [<0492b7bc>]
sp : 046f9898  ip : 0492ac18     fp : 0471b72c
r10: 00000002  r9 : 0470aa28     r8 : 00000001
r7 : 0000000b  r6 : 00000006     r5 : 00000003  r4 : 0471b648
r3 : ff9800ff  r2 : 00000105     r1 : 00007e21  r0 : 0471b648
Flags: Nzcv  IRQs on  FIQs off  Mode SVC_32
Resetting CPU ...

resetting ...

[jamess-huang]

Thanks. We have already ordered one panel and we will start debugging after we receive the panel.

[jamess-huang]

Dear, sobrinho Could you take a picture of this panel for me ? I want to check the model name, H/W version ...etc

[sobrinho]

There isn't any information on the panel or in the box.

[sobrinho]

Searching around: https://gitlab.eurecom.fr/oai/odroid-linux-3.10.y-rt/commit/ae6d54f96a09df418a05f74cd0a3e0c1463a3db9

[jamess-huang]

Hi, We just got the same panel as yours, but it has the EDID info inside. So I cannot duplicate the un-boot issue, but when I entering the OS, we still cannot see the display content (all black). We will try to make it work. After we finish it, we want to exchange the panel with you. Because we want to check the un-boot issue, is it OK for you ?

[sobrinho]

@jamess-huang sure, no problems with that.

[sobrinho]

@jamess-huang happy new year!

Any news on that?