RPi2 Red Screen Issue - RMA?

[Pedrox64]

I had been using my new RPi2 for a week without problems: installed Raspbian from a pre-loaded SD card, HDMI connected straight to TV, plugged in to router and updated OS and programmes and was able to surf the web straight away and got the GPIO controlling LEDs. I was impressed with how easy all of this was done, then...

last night when the Pi was powered up, the background on the rainbow splash screen was red, the background behind the boot-up text is red and the desktop is heavily tinted red: I have gone through various options on forums including config changes, different power supplies, different HDMI cable and connecting to different HDMI ports in TV, but cannot get rid of the red display issue. I reinstalled Raspbian from NOOBS, but the problem persists. I have also added avoid_warnings=1 to config to see if the red is a warning, but the screen remained red.

Any last tips before sending the Pi back as faulty?

[Burngate]

I'm not convinced it's your Pi that's at fault. The HDMI uses serial data, and it would be quite difficult to just change the right bits to make the blacks red.

Could it be that the TV is selecting the wrong encoding?
In the config.txt file, can you put in (or change it if it's already in there) one of

Code: Select all

hdmi_pixel_encoding=0 default       (limited for CEA, full for DMT)
hdmi_pixel_encoding=1 RGB limited   (16-235)
hdmi_pixel_encoding=2 RGB full      ( 0-255)
hdmi_pixel_encoding=3 YCbCr limited (16-235)
hdmi_pixel_encoding=4 YCbCr full    ( 0-255)

For more information, look at http://elinux.org/RPiconfig

[Douglas6]

And test the TV itself with a different source. Could be one of the electron guns went bad (I know, I know, showing my age....)

[plugwash]

I would try adding config_hdmi_boost=4 toconfig.txt

I'm not convinced it's your Pi that's at fault. The HDMI uses serial data, and it would be quite difficult to just change the right bits to make the blacks red.

AIUI while it is serial it uses seperate links for each colour component and the sync signals are carried on the blue component. So a signal integrity issue on the red component could easilly cause a red tint. Especially when running in non-HDCP mode*.

* AIUI there are no HDCP keys on the Pi so it always runs in non-hdcp mode.

[Burngate]

As ever, I was wrong. plugwash pointed me in the right direction - thanks.
The red data is carried on TDMS data2, pins 1, 2 & 3, which happen to be right at one end of the connector.

So, is the plug fully home in the Pi? Or is it in a case that's preventing that?

[Pedrox64]

I have tried the suggested permutations of hdmi_pixel_encoding: options 0, 1 & 2 still red; options 3 & 4 still a colour fault but red appears more pinky (?).

TV tested with a different source: PVR in a different HDMI port works properly, Pi connected to same port using same cable PVR was attached to has red error.

config_hdmi_boost=4 made no difference, upped to 7 no change and even at 10 no difference.

All plugs pushed in fully, waggling of HDMI makes no difference.

Tried a different 5V 2A power supply, no change.

Installed OS on a different disc and still have red error.

I can't think of anything else to try, I guess I need to contact the supplier...

[paulie]

I had the same problem using an el cheapo HDMI to DVI cable: wiggling the cable would fix matters temporarily - eventually I replaced the cable & all is well (so far).
Try the cable on another device.
I think my cheap cable had broken/intermittent wires. There must be a price/quality tradeoff with an optimal range: stupidly cheap,( you just junk & replace), , great vfm, and then overpriced for the build quality/dodgy technology/branded (oxygen-free copper anyone?)

[Burngate]

I have tried ...
I can't think of anything else to try, I guess I need to contact the supplier...

My guess also.

Without seeing the offending item, it's difficult to diagnose, but if it had landed on my bench with those symptoms, I'd have:
Stage 1 - looked inside the HDMI socket for broken pins or foreign objects (it's surprising what people manage to force into small places)
Stage 2 - if there wasn't anything obvious, swapped out the HDMI socket for one from the spares bin
Stage 3 - if that didn't cure it, bin it.
- move onto the next problem.

Stage 2 isn't really possible for the average user.

[MaxK1]

Way back when I got my first Pi, it wouldn't work with the HDMI cable until I swapped ends. After I did that, no problems. Maybe you have a similar issue?

[Pedrox64]

Thanks for the input. None of the above worked, so Pi returned. After some testing I was sent a new Pi and HDMI cable: new Pi connected to TV normally, all colours correct.

[Nickthegeek]

Way back when I got my first Pi, it wouldn't work with the HDMI cable until I swapped ends. After I did that, no problems. Maybe you have a similar issue?

Just did the exact same thing and it worked, no more red screen. F_ knows why.