ROC RK3328/RK3399 No Video on Monitor

Hardware
1

Please use this thread to report no video issues on boards with the ROC- model prefix.

  • ROC-RK3328-CC Renegade
  • ROC-RK3399-PC Renegade Elite

This device was designed for most standard resolution HDTVs and monitors. HDMI supports two modes:

  • CEA Consumer Electronics Association
  • DMI Digital Media Interface

Different video modes require proper clock generator and setup to create the appropriate synchronization frequencies with the display. This is a very complex topic beyond the scope of this post.

If you have a monitor that is not showing video, please post on this thread with the following information if possible:

  1. Monitor/TV Make and Model
  2. Native Resolution
  3. EDID Dump

It is not guaranteed that every monitor resolution is supported due to the limitations on the onboard clock generator. By reporting the issue, we can identify target clocks and resolutions to debug over time.

2
  1. Samsung SyncMaster 2443BWX with HDMI/DVI adapter
  2. 1920 x 1200

xxd edid
00000000: 00ff ffff ffff ff00 4c2d 3f04 3432 594d …L-?.42YM
00000010: 1912 0103 8034 2078 2aee 91a3 544c 9926 …4 x*…TL.&
00000020: 0f50 5423 0800 a940 8180 8140 0101 0101 .PT#…@…@…
00000030: 0101 0101 0101 283c 80a0 70b0 2340 3020 …(<…p.#@0
00000040: 3600 0644 2100 001a 0000 00fd 0038 3c1e 6…D!..8<.
00000050: 5111 000a 2020 2020 2020 0000 00fc 0053 Q… …S
00000060: 796e 634d 6173 7465 720a 2020 0000 00ff yncMaster. …
00000070: 0048 564d 5136 3030 3334 360a 2020 00b1 .HVMQ600346. …

3

Samsung SyncMaster P2770HD with HDMI->DVI adapter
1920 x 1080 @60Hz

00000000: 00ff ffff ffff ff00 4c2d ec05 0000 0000 ........L-......
00000010: 1913 0103 803c 2278 2a34 81a6 5648 9a24 .....<"x*4..VH.$
00000020: 1250 54bf ef80 714f 8100 8140 8180 9500 .PT...qO...@....
00000030: 950f a940 b300 1a36 80a0 7038 1f40 3020 ...@...6..p8.@0
00000040: 3500 5550 2100 001a 0000 00fd 0038 4b1e 5.UP!........8K.
00000050: 5111 000a 2020 2020 2020 0000 00fc 0053 Q... .....S
00000060: 796e 634d 6173 7465 720a 2020 0000 00ff yncMaster. ....
00000070: 0048 3141 4b35 3030 3030 300a 2020 0011 .H1AK500000. ..

4
  1. Vilros Maker Shack 10 Inch LCD Screen Flip-Back Case for Raspberry Pi 4 with HDMI
  2. 1280 X 800

xxd edid
00000000: 00ff ffff ffff ff00 5304 2578 4554 0000 …S.%xET…
00000010: 241d 0103 8029 1778 2e60 81a6 564a 9c25 $…).x...VJ.% 00000020: 1250 54a5 6000 0101 0101 0101 0101 0101 .PT.…
00000030: 0101 0101 0101 9e20 0090 5120 1f30 4880 … …Q .0H.
00000040: 3600 99e6 1000 001a 011d 0072 51d0 1e20 6…rQ…
00000050: 6e28 5500 c48e 2100 0020 0000 00fd 0032 n(U…!.. …2
00000060: 4c18 530f 000a 2020 2020 2020 0000 00fc L.S… …
00000070: 0056 494c 524f 530a 2020 2020 2020 0194 .VILROS. …
00000080: 0203 17f1 4403 0201 1123 097f 0765 030c …D…#…e…
00000090: 0010 0083 0100 0064 1900 4041 5826 2018 …d…@AX& .
000000a0: 8836 0099 e610 0000 1e00 0000 1000 1c16 .6…
000000b0: 2058 2c25 0013 2b21 0000 9f00 0000 1000 X,%…+!..
000000c0: d01e 206e 2855 0013 2b21 0000 1e8c 0ad0 … n(U…+!..
000000d0: 8a20 e02d 1010 3e96 0013 2b21 0000 1800 . .-…>…+!..
000000e0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000000f0: 0000 0000 0000 0000 0000 0000 0000 00a8 …

side note: display works fine connected to a blu-ray player

5

Got the Renegade loaded up – tried LibreELEC, but even for Kodi I don’t believe in root-only systems, so it’s currently booting your Raspbian image.

Came up happily (if slowly) when connected to a PC monitor. Finished initial configuration of the system and ran the update/upgrade cycle.

Moved it to output to HDMI3 of my Samsung Frame’s controller box… and the Frame says it’s never seeing any HDMI signal on that port. The system also apparently isn’t getting far enough to start the Bluetooth dongle for my small keyboard; it blinks the “dongle powered but not communicating” signal.

Moved the system back to the PC monitor (an old Lenovo, with HDMI-to-DVI adapter), and it’s working fine.

Repeated that a few times, trying to isolate the problem. It’s the same HDMI cable in both cases. Same micro-USB power cable and supply. So it looks like it doesn’t like the Samsung 4K TV set.

Which is frustrating given that, as I said, I want to use the Renegade as a media center…

TV: Samsung 43" “The Frame”, model QN43LS03BAFXZA
Firmware T-PTMAKVC-1622.4, BT-S
4K native resolution, but should be able to upconvert

EDID: Given that the machine doesn’t seem to actually be booting when connected to this TV, I’m not sure how to obtain the info for this set. Is it captured during the boot attempt even though the system doesn’t seem to be getting as far as initiating the keyboard dongle? Should I try finding a Linux PC which will talk to it and see if I can fetch it that way?

Is there any other info I can try to retrieve which might help diagnose the problem?

6

Guess I can try booting headless, then connect, and see what happens…

7

For some reason, this machine isn’t actually booting until I swat the keyboard.

Tried bringing it up with no display plugged in, gave it plenty of time, connected PC display which I know works, it said no signal. Only when I hit Enter on the keyboard did the RK3328 actually start its boot process.

That is unacceptable for an appliance machine. What do I need to change to fix that? Use a different boot image? Reconfigure this one?

Yes, I know this is a digression from the video issue. I’ll get back to that shortly.

8

It sounds like you have a keyboard that is sending a keystroke on enumeration that causes GRUB to be interrupted. What make and model is the keyboard? You can try to configure GRUB to disable the menu and boot the first choice to prevent your keyboard from interrupting the GRUB timer.

9

The keyboard is an el-cheapo left over from a Kano package – labelled as their model kbr101. I wouldn’t be at all surprised if it does something weird. I can try another bluetooth-dongle-connected keyboard…

On the other hand… If I load up the Renegade with Armbian rather than Raspbian, it has no trouble starting without manual intervention even with the Kano chicklet keyboard, and is running much faster. Which makes me wonder whether it’s worth continuing down the Raspbian path.

If nothing else, I can hopefully use the Armbian image to query the TV set. Details to follow on that.

At least I can use Armbian to try to get the display description for you…

10

OK. Armbian boots when connected to the Samsung TV. But they do not negotiate resolution correctly – I’m seeing low-res raster lines, though most or all of the display area seems to be covered.

TV: Samsung 43" “The Frame”, model QN43LS03BAFXZA
Firmware T-PTMAKVC-1622.4, BT-S
4K native resolution, but should be able to upconvert

/sys/devices/platform/display-subsystem/drm/card0/card0-HDMI-A-1/edid

keshlam@Medea:~$ edid-decode samsung_frame_edid
edid-decode (hex):

00 ff ff ff ff ff ff 00 4c 2d 7f 72 00 0e 00 01
01 20 01 03 80 5f 36 78 0a b3 61 ab 4f 46 a8 27
0b 50 54 bd ef 80 71 4f 81 c0 81 00 81 80 95 00
a9 c0 b3 00 d1 c0 04 74 00 30 f2 70 5a 80 b0 58
8a 00 50 1d 74 00 00 1e 56 5e 00 a0 a0 a0 29 50
30 20 35 00 50 1d 74 00 00 1a 00 00 00 fd 00 18
4b 0f 51 1e 00 0a 20 20 20 20 20 20 00 00 00 fc
00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 9f

02 03 51 f0 52 5f 10 1f 04 13 05 14 20 21 22 5d
5e 62 64 07 16 03 12 2f 0d 57 07 09 07 07 15 07
50 57 07 01 67 54 03 83 0f 00 00 e2 00 4f e3 05
c3 01 6e 03 0c 00 30 00 b8 44 20 00 80 01 02 03
04 e3 06 0d 01 e5 0e 60 61 65 66 e5 01 8b 84 90
01 02 3a 80 18 71 38 2d 40 58 2c 45 00 50 1d 74
00 00 1e 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ea

Block 0, Base EDID:
EDID Structure Version & Revision: 1.3
Vendor & Product Identification:
Manufacturer: SAM
Model: 29311
Serial Number: 16780800
Made in: week 1 of 2022
Basic Display Parameters & Features:
Digital display
Maximum image size: 95 cm x 54 cm
Gamma: 2.20
RGB color display
First detailed timing is the preferred timing
Color Characteristics:
Red : 0.6699, 0.3115
Green: 0.2734, 0.6591
Blue : 0.1533, 0.0449
White: 0.3125, 0.3291
Established Timings I & II:
IBM : 720x400 70.081663 Hz 9:5 31.467 kHz 28.320000 MHz
DMT 0x04: 640x480 59.940476 Hz 4:3 31.469 kHz 25.175000 MHz
Apple : 640x480 66.666667 Hz 4:3 35.000 kHz 30.240000 MHz
DMT 0x05: 640x480 72.808802 Hz 4:3 37.861 kHz 31.500000 MHz
DMT 0x06: 640x480 75.000000 Hz 4:3 37.500 kHz 31.500000 MHz
DMT 0x09: 800x600 60.316541 Hz 4:3 37.879 kHz 40.000000 MHz
DMT 0x0a: 800x600 72.187572 Hz 4:3 48.077 kHz 50.000000 MHz
DMT 0x0b: 800x600 75.000000 Hz 4:3 46.875 kHz 49.500000 MHz
Apple : 832x624 74.551266 Hz 4:3 49.726 kHz 57.284000 MHz
DMT 0x10: 1024x768 60.003840 Hz 4:3 48.363 kHz 65.000000 MHz
DMT 0x11: 1024x768 70.069359 Hz 4:3 56.476 kHz 75.000000 MHz
DMT 0x12: 1024x768 75.028582 Hz 4:3 60.023 kHz 78.750000 MHz
DMT 0x24: 1280x1024 75.024675 Hz 5:4 79.976 kHz 135.000000 MHz
Apple : 1152x870 75.061550 Hz 192:145 68.681 kHz 100.000000 MHz
Standard Timings:
DMT 0x15: 1152x864 75.000000 Hz 4:3 67.500 kHz 108.000000 MHz
DMT 0x55: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
DMT 0x1c: 1280x800 59.810326 Hz 16:10 49.702 kHz 83.500000 MHz
DMT 0x23: 1280x1024 60.019740 Hz 5:4 63.981 kHz 108.000000 MHz
DMT 0x2f: 1440x900 59.887445 Hz 16:10 55.935 kHz 106.500000 MHz
DMT 0x53: 1600x900 60.000000 Hz 16:9 60.000 kHz 108.000000 MHz (RB)
DMT 0x3a: 1680x1050 59.954250 Hz 16:10 65.290 kHz 146.250000 MHz
DMT 0x52: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz
Detailed Timing Descriptors:
DTD 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz (1872 mm x 1053 mm)
Hfront 176 Hsync 88 Hback 296 Hpol P
Vfront 8 Vsync 10 Vback 72 Vpol P
DTD 2: 2560x1440 59.950550 Hz 16:9 88.787 kHz 241.500000 MHz (1872 mm x 1053 mm)
Hfront 48 Hsync 32 Hback 80 Hpol P
Vfront 3 Vsync 5 Vback 33 Vpol N
Display Range Limits:
Monitor ranges (GTF): 24-75 Hz V, 15-81 kHz H, max dotclock 300 MHz
Display Product Name: ‘SAMSUNG’
Extension blocks: 1
Checksum: 0x9f

Block 1, CTA-861 Extension Block:
Revision: 3
Underscans IT Video Formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
Native detailed modes: 0
Video Data Block:
VIC 95: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz
VIC 16: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz
VIC 31: 1920x1080 50.000000 Hz 16:9 56.250 kHz 148.500000 MHz
VIC 4: 1280x720 60.000000 Hz 16:9 45.000 kHz 74.250000 MHz
VIC 19: 1280x720 50.000000 Hz 16:9 37.500 kHz 74.250000 MHz
VIC 5: 1920x1080i 60.000000 Hz 16:9 33.750 kHz 74.250000 MHz
VIC 20: 1920x1080i 50.000000 Hz 16:9 28.125 kHz 74.250000 MHz
VIC 32: 1920x1080 24.000000 Hz 16:9 27.000 kHz 74.250000 MHz
VIC 33: 1920x1080 25.000000 Hz 16:9 28.125 kHz 74.250000 MHz
VIC 34: 1920x1080 30.000000 Hz 16:9 33.750 kHz 74.250000 MHz
VIC 93: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz
VIC 94: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz
VIC 98: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz
VIC 100: 4096x2160 30.000000 Hz 256:135 67.500 kHz 297.000000 MHz
VIC 7: 1440x480i 59.940060 Hz 16:9 15.734 kHz 27.000000 MHz
VIC 22: 1440x576i 50.000000 Hz 16:9 15.625 kHz 27.000000 MHz
VIC 3: 720x480 59.940060 Hz 16:9 31.469 kHz 27.000000 MHz
VIC 18: 720x576 50.000000 Hz 16:9 31.250 kHz 27.000000 MHz
Audio Data Block:
Linear PCM:
Max channels: 6
Supported sample rates (kHz): 192 96 48 44.1 32
Supported sample sizes (bits): 24 20 16
Linear PCM:
Max channels: 2
Supported sample rates (kHz): 48 44.1 32
Supported sample sizes (bits): 24 20 16
AC-3:
Max channels: 6
Supported sample rates (kHz): 48 44.1 32
Maximum bit rate: 640 kb/s
Enhanced AC-3 (DD+):
Max channels: 8
Supported sample rates (kHz): 48 44.1 32
Supports Joint Object Coding
MAT (MLP):
Max channels: 8
Supported sample rates (kHz): 192 96 48
Supports Dolby TrueHD, object audio PCM and channel-based PCM
Hash calculation not required for object audio PCM or channel-based PCM
Speaker Allocation Data Block:
FL/FR - Front Left/Right
LFE1 - Low Frequency Effects 1
FC - Front Center
BL/BR - Back Left/Right
Video Capability Data Block:
YCbCr quantization: No Data
RGB quantization: Selectable (via AVI Q)
PT scan behavior: No Data
IT scan behavior: Supports both over- and underscan
CE scan behavior: Supports both over- and underscan
Colorimetry Data Block:
xvYCC601
xvYCC709
BT2020YCC
BT2020RGB
Reserved MD0
Vendor-Specific Data Block (HDMI), OUI 00-0C-03:
Source physical address: 3.0.0.0
Supports_AI
DC_36bit
DC_30bit
DC_Y444
Maximum TMDS clock: 340 MHz
Extended HDMI video details:
HDMI VICs:
HDMI VIC 1: 3840x2160 30.000000 Hz 16:9 67.500 kHz 297.000000 MHz
HDMI VIC 2: 3840x2160 25.000000 Hz 16:9 56.250 kHz 297.000000 MHz
HDMI VIC 3: 3840x2160 24.000000 Hz 16:9 54.000 kHz 297.000000 MHz
HDMI VIC 4: 4096x2160 24.000000 Hz 256:135 54.000 kHz 297.000000 MHz
HDR Static Metadata Data Block:
Electro optical transfer functions:
Traditional gamma - SDR luminance range
SMPTE ST2084
Hybrid Log-Gamma
Supported static metadata descriptors:
Static metadata type 1
YCbCr 4:2:0 Video Data Block:
VIC 96: 3840x2160 50.000000 Hz 16:9 112.500 kHz 594.000000 MHz
VIC 97: 3840x2160 60.000000 Hz 16:9 135.000 kHz 594.000000 MHz
VIC 101: 4096x2160 50.000000 Hz 256:135 112.500 kHz 594.000000 MHz
VIC 102: 4096x2160 60.000000 Hz 256:135 135.000 kHz 594.000000 MHz
Vendor-Specific Video Data Block (HDR10+), OUI 90-84-8B:
Application Version: 1
Detailed Timing Descriptors:
DTD 3: 1920x1080 60.000000 Hz 16:9 67.500 kHz 148.500000 MHz (1872 mm x 1053 mm)
Hfront 88 Hsync 44 Hback 148 Hpol P
Vfront 4 Vsync 5 Vback 36 Vpol P
Checksum: 0xea

I presume/hope there’s a way to ask the Renegade what display mode it thinks it’s using, and/or to hint which mode to try if it isn’t automatically matching one?

I understand the Renegade is an experimental device, so I’m not very surprised that we have to struggle with it a bit for this application. Just disappointed; I would have hoped that something in that list of supported resolutions would match, even if it was just 1K mode.

Please let me know if there’s anything I can do to further help diagnose and test. If there’s any tool that would let me try alternative parameters and report back to you, I’d be glad to do that.

Running Armbian (but not Raspbian?), I’m impressed with the system’s responsiveness. If we can just overcome the video problem, I think I’ll be very happy with it. If not… sigh, it can go into the parts box for a future project.

(Minor wishlist item, for Armbian rather than you folks: It’d be nice if the network config gave us the option of continuing to use DHCP for most parameters but add the “inform” line to the configuration to lock in a stable address. Can do that manually, but I am guessing it’s not an uncommon mode of operation.)

11

Do you have a picture of what is being displayed?

Regarding network configuration, we only use what upstream uses. We do not modify the network configuration from the distro defaults.

12

Images attached. There will also occasionally be a momentary screen blanking, perhaps as something tries to find a better compromise.

FWIW, I am running fully updated Armbian 24.2.1 Bookworm Cinnamon.

And THANK YOU for your responsiveness!!

IMG_20240404_155534123
IMG_20240404_1555341231920×1080 201 KB

13

Longer view. with moire interference patterns between screen and camera rasters:

IMG_20240404_155545149
IMG_20240404_1555451491920×1080 265 KB

14

Armbian uses a bunch of patches. We don’t exactly support. What happens when you plug in the display after giving the board a few seconds to boot with our software?

15

Ah. Is there someplace I should be posting this against upstream too?

Booting without the display, confirming it’s up with SSH, then connecting the TV: Black screen with blinking white dot (single pixel?) in upper left corner. Tapping on keyboard has no effect. So that isn’t a workaround.

Note that bad display config starts right at the bootup splash screen with the Armbian chip logo.

You say Armbian isn’t exactly supported. That’s fair, I guess. The question is, what would my best bet be for media-center-suitable video drivers that would handle my TV?

The LibreELEC build is out because it pushes us to run everything as root; it doesn’t even have adduser installed. Not acceptable.

Raspbian was running much, much more slowly than Armbian. Not Preferred unless that can be solved.

Fedora: Haven’t tried it yet. Requires a bootloader installed via libretech-flash-tool, which runs only on Linux. I have Linux machines I can try that from if I must (Pi’s and an ancient laptop) but I was hoping to do the setup from my main development workstations, which are still Windows-with-WSL.

Debian: Haven’t tried it yet.

Ubuntu: Haven’t tried it yet.

Open SUSE: Haven’t tried, it but it seems even less supported than Armbian, given the placeholder page on your website.

I assume that there’s some Linux build for this board that has support, speed, better HDMI compatibility and that runs multiuser…?

(“NOBODY expects the Spanish Inquisition! Our chief weapon is fear. And surprise. Fear and surprise. Surprise and fear. Our two chief weapons…” – Monty Python)

16

The Armbian folks say that they’ve had bad experiences synching up with Samsung TVs generally.

With Debian, booting the Renegade while connected to the TV still results in the TV saying HDMI device connected but not producing recognizable signal.

Leaving it running but unplugging/replugging HDMI – no change.

Booting disconnected and then plugging in – This has worked ONCE, and I’m trying to figure out why. Something caused the set to ask me “is this a PC”, and when I said yes I got the screen. But I’ve been having trouble getting back to that state.

Best thought I’ve got: Figure out how to get it to synch up once (again), then ask the Renegade what video mode it’s running in and try to lock it into that mode. I expect I still won’t be able to see the boot-up sequence, which is a nuisance but one I can mostly live with.

17

1920x1200 lcd screen:

$ xxd edid
00000000: 00ff ffff ffff ff00 632b 0012 0300 0000  ........c+......
00000010: 0821 0103 801e 1378 2aee 95a3 544c 9926  .!.....x*...TL.&
00000020: 0f50 5400 0000 0101 0101 0101 0101 0101  .PT.............
00000030: 0101 0101 0101 423c 80a0 70b0 2440 3020  ......B<..p.$@0
00000040: 2500 2dbc 1000 001a 0000 00fc 0044 6973  %.-..........Dis
00000050: 706c 6179 0a20 2020 2020 0000 00ff 000a  play.     ......
00000060: 2020 2020 2020 2020 2020 2020 0000 00fd              ....
00000070: 0030 3c1e 5414 000a 2020 2020 2020 0132  .0<.T...      .2
00000080: 0203 2df2 4110 e200 d5e3 05c0 0023 091f  ..-.A........#..
00000090: 0783 0100 0067 030c 0010 0018 28e6 0605  .....g......(...
000000a0: 0162 6200 681a 0000 0101 303c e642 3c80  .bb.h.....0<.B<.
000000b0: a070 b024 4030 2045 002d bc10 0000 1a00  .p.$@0 E.-......
000000c0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
000000d0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
000000e0: 0000 0000 0000 0000 0000 0000 0000 0000  ................
000000f0: 0000 0000 0000 0000 0000 0000 0000 003a  ...............: