Odroid N2 - HDMI Stopped Working

Do you see the boot logos at all?

nope … nothing :frowning:

Seems like the death symptoms like my N2 failure.

yes, you may be right.
I found this link yesterday HDMI Hardware Test - OhmMeter
My test suggested there “may” be a hardware error (~1-5kOhm resistance with my dodgy meter)… but that seems odd if the edid is read and the CEC signal is transmitted ok … why would some pins work and not others - without some kind of mechanical or heat stress (and there’s been none)

If yours has failed what are you doing with it now ? Any use as a server ? I suppose I could use it as jump box or container host but setup might be challenging without a screen - just have to hope ssh works out of the box

I returned it in Good Faith that my term of use was so ridiculously short that Hardkernel may honour a return or at least a partial discount for a new one.

Unfortunately that is not the Hardkernel business model.


How to use AV / CVBS Video Output You do need an AV composite cable and it works surprisingly well

thanks - I had completely overlooked the CVBS output.
Not great for a media player attached to a 1080P TV … but at least it provides some kind of window into what’s happening :slight_smile:

In the meantime I’ve restored the trusty old Mini M8s+ … the most reliable player I currently own. I think I’ll go back to the “cheap” chinese units - I’ve found them to be more reliable generally.

1 Like

EDID & CEC have seperate signals with different circuit design, therefore still working.
The components you measured on the LVDS lines are Common-Mode filters with builtin ESD protection. If resistance from signal to GND is only kOhms, there was likely an ESD incident. The good thing is that you can replace them (or bypass, although not the best idea…) more easily than the CPU (if HDMI port not also damaged by that incident).

I believe they made a new revision N2 to combat these issues but it does sound like the N2 death issue if you do not even see the boot logos, I believe there is a guide on their forum for fixing them but it requires soldering and changing some component.

For the fix, are you talking about the resistor change to increase the LVDS voltage swing?
You have some details of new N2 pcb rev? Is this ODROID-N2plus - pcb rev. 2019-11-20)?

IMO they have to refine their ESD strategy. The main issue is likely that they use CM filters with TVS on both ends. The one to connector side is fully exposed to the transient, and maybe too weak, so just fails after first shot, while the other one is quite useless.
Would be state-of-art to use a dedicated device with stronger TVS only on one side (e.g. this or this, designed even for HDMI2.0)

I’m seeing to many reports of this hdmi issue,there was a guy last week on freektab.com with the same problem,I’d be really pissed off if this happened to me as these boxes are not cheap,cost me £124 so to hear these boxes failing within such a short time is worrying,7 bought mine from odroid uk Thinking I’d be OK cause anything electrical must have atleast 1y warranty,by law it’s a actually 5y warranty in the uk but trying to get them to honour that is another story,but they usually honour a 1y,but odroid uk seem to be pulling a fast one with a 4 week warranty which totally illegal

thanks for the comments and suggestions
not sounding good really is it
I’m not really brave enough to take a soldering iron to somethinng like this … for all sorts of reasons :slight_smile:
looks like I now have an ARM mini-server. Maybe. If I can make Arch or Ubuntu work ie. if the build has SSH support out of the box

Pretty disappointing to be on the wrong end of such a quality issue :frowning:
It has encouraged me to make Kodi work from an LXC container on my J4015 box (USB IR passthrough had me foxed for a while) … so am using that for the moment and holding the Mini M8S+ in reserve - it has been rock solid ever since I first received it in 2016 (?), shame they don’t make them any more

One last question regarding the N2 failure:
Did you see the 1-5kOhms on all of the LVDS lines, or only on one of them (or only on L8 or L9)?
It would be really interesting to find out if it’s the SOC or the ESD protection failing, as you wrote you didn’t change any cabling…

I have a mixed relationship with my multimeter :slight_smile:
Just placed on probe on L9 and the rightmost line into the HDMI connector - which showed ~1k Ohm based on diagram here Hardkernel - No HDMI After Using Adapter and here Hardkernel - N2 Received & No HDMI Output
What should I test for more insight ?

Please measure each signal line separately against GND:
Blue marked contacts are all the same GND signal, so doesn’t matter which one you use.
Blue vs L8.1, Blue vs L8.2…
Blue vs L9.1, Blue vs L9.2…

Not sure I believe my own data (poor eyesight and dodgy meter). Ground used was the body of the Ethernet adapter housing (I stuck the probe to it with tape and verified measurement was largely unchanged from manual against #9). Here it is
L8 01 5k
L8 02 4k
L8 03 4k
L8 04 3k

L9 01 15k
L9 02 15k
L9 03 13k
L9 04 13k

Index numbers are counted from left as per the diagram you posted. The numbers all seem way too low
Does this seem reasonable to you, given that CEC works ?

Hi, I seem to be in the same situation with the N2. No HDMI signal at all and I’m not able to get far with the Android install since I cant turn on SSH. Did you find a way to do a headless Ubuntu or Arch install to keep this box useful? I was thinking use it as a media server possibly…

I dont have access to meter or the composite cable as yet. Any help appreciated. Thanks!

You should be able to just flash the Ubuntu or Arch img (the minimal or server img being the best option since it doesn’t have the added gui packages) to an sd card or eMMC module, then log in via ssh to be able to do a headless install.

Hi, thanks for your input. I tried flashing Ubuntu ‘ubuntu-18.04.4-4.9-minimal-odroid-n2-20200229.img’. The unit boots up and I see blue led light up twice every few seconds. Unable to ssh in to the box, get a connection refused msg on putty.

I will download the ubuntu img and try. It’s possibly just a matter of the sshd not being enabled by default on that img. If that is the case I will post some instructions on how to enable it when you don’t have a display.