TV doesn't recognize Pi if TV is turned on after PI
#16
Have you tried hdmi_edid_file as explained in previous posts? You also need to create the edid.dat file using tvservice.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#17
(2014-02-18, 15:29)koze Wrote: Thanks for your info.
I have config.txt file already on my Pi. As I mentioned in my first post hdmi_force_hotplug=1 is already set in config.txt file.
But still have the same issue.
When I start my RPi with TV on all works great. Even if I later turn off Tv with RPi working I can turn on tv and all is working fine.
The only problem I have when I start my RPi with TV turn off and after that I turn my TV, TV doesn't recognize RPI.

Thanks,

koze



Sorry, I misread your first post and thought you were looking for help editing your config.txt, a process which is not intuitive.

You definitely did it correctly with the remount command and everything (as outlined in those steps)? And the line that you added is not commented out with a "#" in front of it? I'm only asking because I encounter this exact problem every time I spin up a Raspberry Pi, and the hdmi_force_hotplug=1 setting fixes it each time.
Reply
#18
(2014-02-18, 15:52)MilhouseVH Wrote: Have you tried hdmi_edid_file as explained in previous posts? You also need to create the edid.dat file using tvservice.

should I follow those steps?

1. Delete 'hdmi_edid_file=1' from config.txt. If you have an empty edid.dat delete that as well.
2. Reboot with the tv on.
2. Run 'tvservice -m CEA' to see if it reads edid from TV correct and what is reported.
3. If everything seems ok, run 'tvservice -d'. Edid.dat will be placed in your home directory.
4. Move edid.dat from there to the correct location (not /boot on OE, probably /flash or something, cannot remember exactly).
5. After that, add 'hdmi_edid_file=1' to config.txt and reboot.

I wasn't sure if those steps are to help me with my issue?

Thanks,

koze
Reply
#19
@koze, yes sounds about right.

If you're using OpenELEC you'll need to move the file to /flash/edid.dat. Since /flash will be mounted read-only, you'll also need to remount the partition read-write, so step 4 should be:
Code:
mount -o remount,rw /flash
mv edid.dat /flash
sync
mount -o remount,ro /flash

I don't know if the above steps will help fix your problem, but it's probably worth a shot.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#20
Run 'tvservice -m CEA' to see if it reads edid from TV correct and what is reported.

What should be returned to me to be sure that everthing seems to be ok?

That edit.dat file is located on my sd card. Am I right?

Thanks avp0 and MilhouseVH for your help.
Reply
#21
(2014-02-18, 17:40)koze Wrote: Run 'tvservice -m CEA' to see if it reads edid from TV correct and what is reported.

What should be returned to me to be sure that everthing seems to be ok?

You should get a list of modes supported by your display, with the preferred mode highlighted.

(2014-02-18, 17:40)koze Wrote: That edit.dat file is located on my sd card. Am I right?

That's where it needs to go, yes. Initially with "tvservice -d edid.dat" it will be written to your current directory, which is probably /storage.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#22
After running following command:
Quote:tvservice -m CEA

I got following info:
Quote:Group CEA has 5 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
(native) mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
So it's look like RPi reads edid from TV correct. What above information means? Currently I am using mode 4 but I can switch to mode 5? Am I right?


After running following command:
Quote:tvservice -d
I got following info:
Quote:OpenELEC:~ # tvservice -d
tvservice: option requires an argument -- 'd'
Usage: tvservice [OPTION]...
-p, --preferred Power on HDMI with preferred settings
-e, --explicit="GROUP MODE DRIVE" Power on HDMI with explicit GROUP (CEA, DMT, CEA_3D_SBS, CEA_3D_TB)
MODE (see --modes) and DRIVE (HDMI, DVI)
-c, --sdtvon="MODE ASPECT" Power on SDTV with MODE (PAL or NTSC) and ASPECT (4:3 14:9 or 16:9)
-o, --off Power off the display
-m, --modes=GROUP Get supported modes for GROUP (CEA, DMT)
-M, --monitor Monitor HDMI events
-s, --status Get HDMI status
-a, --audio Get supported audio information
-d, --dumpedid <filename> Dump EDID information to file
-j, --json Use JSON format for --modes output
-n, --name Print the device ID from EDID
-h, --help Print this information

I still couldn't locate edit.dat file on my RPi.


Do I need to run this commend to get edit.dat file :
Quote:tvservice -d edid.dat
?

Thank you,

koze
Reply
#23
Yes, sorry about that...
Reply
#24
(2014-02-19, 13:45)koze Wrote: After running following command:
Quote:tvservice -m CEA

I got following info:
Quote:Group CEA has 5 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
(native) mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
So it's look like RPi reads edid from TV correct. What above information means? Currently I am using mode 4 but I can switch to mode 5? Am I right?

My guess from the above information is that your display has only a 1280x720 panel, which is its "native" resolution and what you should be using for XBMC. It appears your display may support 1920x1080 as an input resolution but the display will most likely re-scale it to 1280x720 to fit the native panel resolution, so 1920x1080 probably isn't a resolution/mode you want to use - stick with the native resolution (mode 4).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#25
Thank you. What about edit.dat file:

After running following command:
Quote:
tvservice -d
I got following info:

Quote:
OpenELEC:~ # tvservice -d
tvservice: option requires an argument -- 'd'
Usage: tvservice [OPTION]...
-p, --preferred Power on HDMI with preferred settings
-e, --explicit="GROUP MODE DRIVE" Power on HDMI with explicit GROUP (CEA, DMT, CEA_3D_SBS, CEA_3D_TB)
MODE (see --modes) and DRIVE (HDMI, DVI)
-c, --sdtvon="MODE ASPECT" Power on SDTV with MODE (PAL or NTSC) and ASPECT (4:3 14:9 or 16:9)
-o, --off Power off the display
-m, --modes=GROUP Get supported modes for GROUP (CEA, DMT)
-M, --monitor Monitor HDMI events
-s, --status Get HDMI status
-a, --audio Get supported audio information
-d, --dumpedid <filename> Dump EDID information to file
-j, --json Use JSON format for --modes output
-n, --name Print the device ID from EDID
-h, --help Print this information

I still couldn't locate edit.dat file on my RPi.


Do I need to run this commend to get edit.dat file :
Quote:
tvservice -d edid.dat
?
Reply
#26
Yes, you need to do tvservice -d edid.dat, and place the file in /boot (for raspbmc).

You can analyse the result with edidparser edid.dat
Derek
Reply
#27
(2014-02-19, 15:30)koze Wrote: Thank you. What about edit.dat file:

Yes, the command is:
Code:
tvservice -d edid.dat
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#28
Here is what I've got:
Image

I have checked and edit.dat was moved from my storage area to flash folder.

Analize command returned:
Image

Can you please let me know if it was done correctly?



If everything is ok I will continue with:

5. After that, add 'hdmi_edid_file=1' to config.txt and reboot.



Thank you in advance,

koze
Reply
#29
(2014-02-21, 02:08)koze Wrote: Can you please let me know if it was done correctly?

Looks fine to me.

(2014-02-21, 02:08)koze Wrote: Analize command returned:

As you've now moved the edid.dat file to /flash, the analyse command is:
Code:
edidparser /flash/edid.dat

Anyway try updating your config.txt and see if it has any effect.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#30
works great,
thank you for your help.
Here is the code I have received back:
Quote:OpenELEC:~ # edidparser /flash/edid.dat
Enabling fuzzy format match...
Parsing /flash/edid.dat...
HDMI:EDID version 1.3, 1 extensions, screen size 115x65 cm
HDMI:EDID features - videodef 0x80 !standby !suspend !active off; colour encodin g:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 56-85 Hz, horizontal is 31-60 kHz, max pixe l clock is 80 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is LG_TV
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is PDP
HDMI:EDID found preferred DMT detail timing format: 1024x768p @ 60 Hz (16)
HDMI:EDID established timing I/II bytes are 2F CE 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 5, 640x480p @ 72 Hz in established timing I/II
HDMI:EDID found DMT format: code 6, 640x480p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 8, 800x600p @ 56 Hz in established timing I/II
HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 10, 800x600p @ 72 Hz in established timing I/II
HDMI:EDID found DMT format: code 11, 800x600p @ 75 Hz in established timing I/II
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/I I
HDMI:EDID found DMT format: code 17, 1024x768p @ 70 Hz in established timing I/I I
HDMI:EDID found DMT format: code 18, 1024x768p @ 75 Hz in established timing I/I I
HDMI:EDID standard timings block x 8: 0x3140 4540 6140 0101 0101 0101 0101 0101
HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz (4:3) in standard timing 0
HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz (4:3) in standard timing 1
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz (4:3) in standard timing 2
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:yes, basic audio:yes, yuv444:ye s, yuv422:yes, #native DTD:1
HDMI:EDID found CEA detail timing format: 1280x720p @ 60 Hz (4)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2)
HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2)
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz (native)
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz
HDMI:EDID found CEA format: code 2, 720x480p @ 60Hz
HDMI:EDID found audio format 6 channels AC3, sample rate: 32|44|48 kHz, bitrate: 640 kbps
HDMI:EDID found HDMI VSDB length 5
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB has no extension fields
HDMI:EDID adding mandatory support for CEA (1) 640x480p @ 60Hz
HDMI:Warning EDID must support pcm or no audio
HDMI:EDID filtering formats with pixel clock > 162 MHz or h. blanking > 1023
HDMI:EDID best score mode initialised to DMT (4) 640x480p @ 60 Hz with pixel clo ck 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MH z (score 43432)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MH z (score 3545736)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 4 5736
HDMI:EDID best score mode is now CEA (4) 1280x720p @ 60 Hz with pixel clock 74 M Hz (score 4607944)
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 6 1864
HDMI:EDID CEA mode (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz has a score of 4149416
HDMI:EDID DMT mode (5) 640x480p @ 72 Hz with pixel clock 31 MHz has a score of 4 4236
HDMI:EDID DMT mode (6) 640x480p @ 75 Hz with pixel clock 31 MHz has a score of 4 6080
HDMI:EDID DMT mode (8) 800x600p @ 56 Hz with pixel clock 36 MHz has a score of 5 3760
HDMI:EDID DMT mode (9) 800x600p @ 60 Hz with pixel clock 40 MHz has a score of 8 2600
HDMI:EDID DMT mode (10) 800x600p @ 72 Hz with pixel clock 50 MHz has a score of 69120
HDMI:EDID DMT mode (11) 800x600p @ 75 Hz with pixel clock 49 MHz has a score of 72000
HDMI:EDID best score mode is now DMT (16) 1024x768p @ 60 Hz with pixel clock 65 MHz (score 5166555)
HDMI:EDID DMT mode (17) 1024x768p @ 70 Hz with pixel clock 75 MHz has a score of 110100
HDMI:EDID DMT mode (18) 1024x768p @ 75 Hz with pixel clock 78 MHz has a score of 117964
HDMI:EDID preferred mode remained as DMT (16) 1024x768p @ 60 Hz with pixel clock 65 MHz
HDMI:EDID has HDMI support and audio support
edid_parser exited with code 0
Reply

Logout Mark Read Team Forum Stats Members Help
TV doesn't recognize Pi if TV is turned on after PI0