Samsung Q90 + ODroid N2. Not detected

[gmerrall]

Had my ODroid N2 in storage for a year and finally hooked up up to my new Samsung Q90 TV with a fresh copy of CE. Unfortunately the TV is not getting signal from the N2. There’s definitely comms as powering on the N2 will turn on the TV and vice versa when I turn the TV off.

CoreELEC (official): 20.2-Nexus (Amlogic-ng.arm)
Machine model: Hardkernel ODROID-N2
CoreELEC dt-id: g12b_s922x_odroid_n2
Amlogic dt-id: g12b_w400_a

So far tried:

1. Changing HDMI cables as seems to be a common issue
2. Set color sampling to 4:2:2 as this seems to show up on various threads
3. Updated petitboot due to some current silliness regarding
4. Tried the “Input Signal Plus” setting on the Samsung TV. Basically a hail Mary

Can’t try

1. Using fw_setenv as per this thread as it produces an error related to /etc/fw_env.config

Cannot parse config file '/etc/fw_env.config': Invalid argument

At this point I’m basically stuck. Any additional pointers gratefully accepted.

Log captured from dmesg since I can only access via SSH: http://ix.io/4BEg

[Portisch]

There is no env exist on N2.

How you set 4:2:2 when you have nothing on screen?
And 4:2:2 is wrong, leave it at auto.
Limit colour bit depth to 10 or 8 bits instead.

[gmerrall]

How you set 4:2:2 when you have nothing on screen?

Will do. I was trying to solve my problems by searching previous posts and people seemed to have success when directed to make that change.

In order to access the UI I’d plug the N2 into my computer monitor, make changes in the UI then move it back to the TV. I shut down the N2 via ‘halt’ command in terminal prior to changing plugs.

Limit colour bit depth to 10 or 8 bits instead.

Have changed to 10 and then 8 bit. Issue persists.

Dropped a new output from dmesg at http://ix.io/4BGO
Since I had the monitor plugged in I also enabled debug logging. Once it was back on the TV I used ‘cat temp/kodi.log | paste’. Output at http://ix.io/4BGN