Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

On-chip DDC controller is unreliable on this board so override DDC

Featured Replies

From: Joachim Eastwood <joachim.eastwood@gmail.com>

On-chip DDC controller is unreliable on this board so override DDC on
the HDMI connector with i2c-gpio. The root cause of breakage is not
known but on-chip DDC controller refuses to read the EDID.

Signed-off-by: Joachim Eastwood <joachim.eastwood@gmail.com>

@igorpecovnik

Maybe we can find the root.

Claudes first gut reaction.

"H96 MAX V58 HDMI puzzle

His facts: the built-in DDC controller never reads the EDID, while bit-banging the same two pins works. Pull-ups and slower speeds changed nothing, and the NanoPi M6 with the same pins is fine.

  1. Most likely: the controller's DDC inputs are masked. The RK3588 manual (Part 1, p.789–790) has two bits in the VO1 GRF that connect the controller's SCL and SDA inputs to the pins. Their reset value is "masked": the input is tied to 1, so the controller reads every acknowledge as a NACK, whatever happens on the wire. That fits "nothing I changed on the pins helped". Mainline sets both bits once at startup and again only after a system resume. Something on that board may leave them unset or reset them. One register read on an H96 after a failed EDID read would settle it.

  2. The pad settings, which he never tried. SDA runs at the weakest drive strength with the Schmitt trigger on. The working workaround uses plain settings, so a two-line device-tree override would test this.

  3. A long shot: the IR receiver. It sits on GPIO0_D4, which is also the SDA pin of the controller's alternate pin pair. It's muxed as a GPIO, so it probably doesn't matter, but it's cheap to rule out.

If either of the first two is the cause, the fix is a few device-tree lines or a small driver change, not his two AI-assisted bridge patches.

The initial reaction.. I will reengage tomorrow with my REA Agents.



defcom5-rockchip

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.