Author Topic: Raspberry pi 2 installation -> HDMI CEC problems  (Read 3982 times)

rebelkiller

  • Veteran
  • ***
  • Posts: 77
    • View Profile
Raspberry pi 2 installation -> HDMI CEC problems
« on: November 17, 2015, 08:20:59 pm »
Hello!

 did fresh installation of jessie on my rpi2. I want to use HDMI-CEC with my rpi2, Panasonic-Plasma and DENON AVR.

Testing with cec-client gives the right outputs (addresses, Vendors etc.). So basically I it is a working setup. (A further test with a another rpi2 and a recent KODI/Openelec installation HDMI works OOTB). So I assume that there are no incompatibilities between the devices.

I followed instructions in the wiki regarding pulse eight adaptor and give the right(?) address entries of those three devices in webadmin. COM port of the CEC-Adaptor is left blank. I set the Audio/Videos pipes and reloaded the core.

Now on the rpi2 MD my TV remote does not show any reaction on button presses.


Partially the log of CEC_Adaptor:

Code: [Select]
========== NEW LOG SECTION ==========
1       11/17/15 18:43:52       143 (spawning-device)   ^[[1;00mStarting... 1^[[1;00m
1       11/17/15 18:43:52       143 (spawning-device)   ^[[1;00mFound /usr/pluto/bin/CEC_Adaptor^[[1;00m
05      11/17/15 18:43:53.646           ^[[33;1mConnect() failed, Error Code 111 (Connection refused))^[[0m <0x76f64000>
05      11/17/15 18:43:54.648           ^[[33;1mConnect() failed, Error Code 111 (Connection refused))^[[0m <0x76f64000>
05      11/17/15 18:44:19.104           ^[[33;1mNo COM Port specified. Trying autodetect.  Please set a port in the Interfaces section of Web Admin, or re-detect device.^[[0m <0x76f64000>
01      11/17/15 18:44:21.298           ^[[31;1mCECCommand: CALLBACK! From: 0, To: 4, set=1, Opcode: 135/device vendor id, Parm1=0, sParms: ''^[[0m <0x7640d450>
01      11/17/15 18:44:21.299           ^[[31;1mCECCommand: CALLBACK! VendorID     : 0/Unknown^[[0m <0x7640d450>
05      11/17/15 18:44:27.624           ^[[33;1mCreating child 144^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2303 that this has no custom event handler for.  It will not fire events.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2303 that this has no custom handler for.  This is normal for IR.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mCreating child 146^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2304 that this has no custom event handler for.  It will not fire events.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2304 that this has no custom handler for.  This is normal for IR.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mCreating child 147^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2306 that this has no custom event handler for.  It will not fire events.^[[0m <0x76f64000>
05      11/17/15 18:44:27.625           ^[[33;1mNote: Device manager has attached a device of type 2306 that this has no custom handler for.  This is normal for IR.^[[0m <0x76f64000>
01      11/17/15 18:47:06.215           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:08.273           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:10.328           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:12.383           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:14.437           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:47:16.492           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
...
01      11/17/15 18:48:12.012           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:14.073           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:16.127           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:18.183           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:20.237           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:22.293           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:24.352           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
01      11/17/15 18:48:26.407           ^[[31;1mCECCommand: CALLBACK! Unhandled!^[[0m <0x7640d450>
05      11/17/15 18:56:21.696           ^[[33;1mlibCEC: unhandled response received: opcode=0 initiator=e destination=0 response=0^[[0m <0x7640d450>
05      11/17/15 18:56:21.792           ^[[33;1mlibCEC: unhandled response received: opcode=8c initiator=e destination=0 response=0^[[0m <0x7640d450>
05      11/17/15 18:56:22.604           ^[[33;1mlibCEC: unhandled response received: opcode=84 initiator=4 destination=f response=0^[[0m <0x7640d450>
05      11/17/15 18:56:22.904           ^[[33;1mlibCEC: unhandled response received: opcode=47 initiator=4 destination=0 response=0^[[0m <0x7640d450>
05      11/17/15 18:56:23.087           ^[[33;1mlibCEC: unhandled response received: opcode=8f initiator=4 destination=0 response=0^[[0m <0x7640d450>
01      11/17/15 18:56:23.638           ^[[31;1mCECCommand: CALLBACK! From: 0, To: 4, set=1, Opcode: 135/device vendor id, Parm1=0, sParms: ''^[[0m <0x7640d450>
01      11/17/15 18:56:23.639           ^[[31;1mCECCommand: CALLBACK! VendorID     : 0/Unknown^[[0m <0x7640d450>
05      11/17/15 18:56:23.791           ^[[33;1mlibCEC: unhandled response received: opcode=87 initiator=4 destination=f response=0^[[0m <0x7640d450>
05      11/17/15 18:56:24.280           ^[[33;1mlibCEC: unhandled response received: opcode=89 initiator=4 destination=0 response=0^[[0m <0x7640d450>


Some ideas?

Thank you!


Greets
Bernd

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1747
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #1 on: November 17, 2015, 09:22:39 pm »
I have a panasonic tv and a Denon AVR with a pulse-eight adaptor (I have tested rpi as well).  My panasonic remote presses have never been sent along the CEC bus.  Another TV I have (a Vizio) *does* send the remote button presses along the CEC bus.  I'm not sure if it's the TV or the CEC library or how we've configured the CEC library.

Do you see the button presses in cec-client?  If you do then the system will see them, if you don't then they're not being sent to the CEC adaptor on the CEC bus.  You should have control of your AVR and TV from lmce and you should see those commands go out on the CEC bus if you follow along with cec-client.

Beyond that it'll take some playing/troubleshooting with the source and with cec-client to see if it's something we can fix.  As I said, I have control from my vizio tv's remote, but not from my panny.

J.

rebelkiller

  • Veteran
  • ***
  • Posts: 77
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #2 on: November 18, 2015, 10:47:52 am »
Quote
I have a panasonic tv and a Denon AVR with a pulse-eight adaptor (I have tested rpi as well).  My panasonic remote presses have never been sent along the CEC bus.

Watching cec-client messages on the rpi2-MD I *can* see button presses from the Panasonic's TV remote .
I have another rpi2 with an OpenElec OS. Connecting it the same way as rpi2-MD to the Panasonic (tx-p50-gw30) and the Denon AVR 2310 it works ootb (Navigating through OpenElec menus, channel up, channel down, volume up volume down etc. is all working as expected).

It must be a LMCE-issue. I do not really know where to look at...



phenigma

  • LinuxMCE God
  • ****
  • Posts: 1747
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #3 on: November 18, 2015, 05:58:59 pm »
Create a defect ticket in our trac system at svn.linuxmce.org.    You can get a trac login by following this: http://forum.linuxmce.org/index.php?topic=13696.0

That will add that to my list of things to look at.

Thanks for testing and reporting!

J.

rebelkiller

  • Veteran
  • ***
  • Posts: 77
    • View Profile

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1747
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #5 on: November 21, 2015, 06:40:14 pm »
Thank you very much!  The detail you have provided is terrific!  I'll see what I can make of it.  :D

J.

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1747
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #6 on: November 22, 2015, 12:24:48 am »
The cec-client log you linked shows that you pressed the 'Exit' button 2x and released it.  Can you confirm that for me?

The next thing is is that libcec3 is more tightly tied to the cec specification and I need to implement some additional functionality for it to fully announce on the CEC bus.  Let me know about the above question and I'll work on the updates that are required.

Thanks for testing and reporting!  It's really appreciated.

J.
« Last Edit: November 22, 2015, 01:40:11 am by phenigma »

rebelkiller

  • Veteran
  • ***
  • Posts: 77
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #7 on: November 22, 2015, 07:16:37 pm »
 I randomly tapped on the remote.... Some buttons I pressed twice.

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1747
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #8 on: November 22, 2015, 08:48:33 pm »
Thank you.

J.

rebelkiller

  • Veteran
  • ***
  • Posts: 77
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #9 on: November 25, 2015, 07:49:52 pm »
I noticed package update to 31661 (core), the rpi2-packages are still 31597 (on the MD itself)... Correct?

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1747
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #10 on: November 25, 2015, 08:37:54 pm »
The packages for the various distribution releases do not all get built at the same time.  The arm builds are updated less frequently than the i386 builds for instance. 

J.

rebelkiller

  • Veteran
  • ***
  • Posts: 77
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #11 on: December 13, 2015, 03:20:03 pm »
okay. HDMI command are getting used by lmce now.

But using the Panasonic remote is not very responsive. Something is slowing down. About 0.5 - 1 second after a key is pressed the command will be executed on the on screen orbiter.

any ideas how to optimize this?

Greets

Bernd

phenigma

  • LinuxMCE God
  • ****
  • Posts: 1747
    • View Profile
Re: Raspberry pi 2 installation -> HDMI CEC problems
« Reply #12 on: December 14, 2015, 02:12:07 pm »
There are no pauses or delays in the software handling of the cec adaptor.  I have no apparent delays when I use mine here.  I'm not sure what could be interfering atm.

J.