[mythtv-users] CEC support on Raspberry Pi 3
Mike Bibbings
mike.bibbings at gmail.com
Sat Jul 9 16:15:27 UTC 2016
On 09/07/16 16:47, Matthew Zimmerman wrote:
> Well I feel a like a goat. Turns out that my TV (maybe this is
> standard?) only supports 3 CEC playback devices, so when mythtv would
> try to register itself, there were no more addresses available for
> playback devices which is I guess why cec-client registered itself as
> a recording device. Turning off one of the device's CEC support has
> given room for mythtv and the CEC support is working great now.
>
> My natural "enter" key on the remote does not map to anything, but
> that's for another day. Thanks so much for your help!
>
> On Sat, Jul 9, 2016 at 10:47 AM Matthew Zimmerman
> <mzimmerman at gmail.com <mailto:mzimmerman at gmail.com>> wrote:
>
> Peter, thank you, great job on this already again, it was
> fantastically easy to get this far.
>
> Mike, good catch. I had somehow never stumbled upon Peter's apt
> source but instead loaded the package using dpkg manually as
> instructed at https://github.com/bennettpeter/mythtv/releases
>
> Peter, you're right, it's something with the "playback device" --
> cec-utils now reproduces the problem. I will play around with
> this some more and figure out what the difference is. Thank you!
>
> pi at raspliving:~ $ cec-client -t p
> == using device type 'playback device'
> CEC Parser created - libCEC version 3.0.1
> no serial port given. trying autodetect:
>
> path: Raspberry Pi
> com port: RPI
>
> opening a connection to the CEC adapter...
> DEBUG: [ 57] Broadcast (F): osd name set to
> 'Broadcast'
> DEBUG: [ 58] InitHostCEC - vchiq_initialise
> succeeded
> DEBUG: [ 58] InitHostCEC - vchi_initialise
> succeeded
> DEBUG: [ 58] InitHostCEC - vchi_connect succeeded
> DEBUG: [ 59] Open - vc_cec initialised
> DEBUG: [ 59] logical address changed to Free
> use (e)
> NOTICE: [ 60] connection opened
> DEBUG: [ 60] processor thread started
> DEBUG: [ 60] << Broadcast (F) -> TV (0): POLL
> DEBUG: [ 60] initiator 'Broadcast' is not
> supported by the CEC adapter. using 'Free use' instead
> TRAFFIC: [ 60] << e0
> DEBUG: [ 120] >> POLL sent
> DEBUG: [ 120] TV (0): device status changed into
> 'present'
> DEBUG: [ 120] << requesting vendor ID of 'TV' (0)
> TRAFFIC: [ 120] << e0:8c
> TRAFFIC: [ 313] >> 0f:87:00:00:39
> DEBUG: [ 313] TV (0): vendor = Toshiba (000039)
> DEBUG: [ 313] expected response received (87:
> device vendor id)
> DEBUG: [ 313] replacing the command handler for
> device 'TV' (0)
> NOTICE: [ 313] registering new CEC client - v3.0.1
> DEBUG: [ 313] detecting logical address for type
> 'playback device'
> DEBUG: [ 313] >> TV (0) -> Broadcast (F): device
> vendor id (87)
> DEBUG: [ 313] trying logical address 'Playback 1'
> DEBUG: [ 313] << Playback 1 (4) -> Playback 1
> (4): POLL
> TRAFFIC: [ 313] << 44
> DEBUG: [ 553] >> POLL sent
> DEBUG: [ 553] logical address 'Playback 1'
> already taken
> DEBUG: [ 553] Playback 1 (4): device status
> changed into 'present'
> DEBUG: [ 553] trying logical address 'Playback 2'
> DEBUG: [ 553] << Playback 2 (8) -> Playback 2
> (8): POLL
> TRAFFIC: [ 553] << 88
> DEBUG: [ 733] >> POLL sent
> DEBUG: [ 733] logical address 'Playback 2'
> already taken
> DEBUG: [ 733] Playback 2 (8): device status
> changed into 'present'
> DEBUG: [ 733] trying logical address 'Playback 3'
> DEBUG: [ 733] << Playback 3 (B) -> Playback 3
> (B): POLL
> TRAFFIC: [ 733] << bb
> DEBUG: [ 914] >> POLL sent
> unable to open the device on port RPI
> DEBUG: [ 914] logical address 'Playback 3'
> already taken
> DEBUG: [ 914] Playback 3 (B): device status
> changed into 'present'
> ERROR: [ 914] AllocateLogicalAddresses - failed
> to allocate device '0', type 'playback device'
> ERROR: [ 914] failed to find a free logical
> address for the client
> ERROR: [ 914] failed to register the new CEC
> client - cannot allocate the requested device types
> ERROR: [ 914] failed to register a CEC client
> DEBUG: [ 914] unregistering all CEC clients
>
>
> On Sat, Jul 9, 2016 at 9:48 AM Mike Bibbings
> <mike.bibbings at gmail.com <mailto:mike.bibbings at gmail.com>> wrote:
>
> On 09/07/16 13:57, Matthew Zimmerman wrote:
>> So I have a Raspberry Pi 3 running mythfrontend 0.28
>> on raspbian jessie with which overall works beautifully, but
>> the icing on the cake would be to get CEC functionality
>> working so I can control mythfrontend with the TV remote
>> (definitely a wife-acceptance-factor!)
>>
>> 2016-07-09 08:38:06.693291 C mythfrontend version:
>> fixes/0.28 [v0.28-32-g6eff083] www.mythtv.org
>> <http://www.mythtv.org>
>> ---- SNIP ------
>> 2016-07-09 08:38:08.833406 I CECAdapter: Found 1 CEC
>> devices(s).
>> 2016-07-09 08:38:08.833503 I CECAdapter: Device 1: path
>> 'Raspberry Pi' com port 'RPI' SELECTED
>> 2016-07-09 08:38:08.833522 I CECAdapter: Trying to open
>> device Raspberry Pi (RPI).
>> 2016-07-09 08:38:08.834810 I CECAdapter: connection opened
>> 2016-07-09 08:38:09.158714 I CECAdapter: registering new CEC
>> client - v3.0.1
>> 2016-07-09 08:38:09.910458 E CECAdapter:
>> AllocateLogicalAddresses - failed to allocate device '0',
>> type 'playback device'
>> 2016-07-09 08:38:09.910497 E CECAdapter: failed to find a
>> free logical address for the client
>> 2016-07-09 08:38:09.910608 E CECAdapter: failed to register
>> the new CEC client - cannot allocate the requested device types
>> 2016-07-09 08:38:09.910679 E CECAdapter: Failed to open device.
>> 2016-07-09 08:38:09.910695 E CECAdapter: failed to register
>> a CEC client
>> 2016-07-09 08:38:11.336293 I CECAdapter: Closing down CEC.
>>
>> https://www.mythtv.org/wiki/Raspberry_Pi states that CEC
>> support should work in this case. This isn't a hardware thing
>> because cec-util works beautifully.
>>
>> How can I debug this further? I'm not shy of writing some
>> code to fix it, although my C is not great.
>>
>> Thanks for this working as well as it does!
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums:https://forum.mythtv.org
> A few things to try:
>
> Upgrade your version of mythtv-light, as of writing I have
> v0.28-40-g7a4e9ab, which is later than the version you have
> see https://www.mythtv.org/wiki/MythTV_Light
>
> I had to install libcec3 (sudo apt-get install libcec3)
>
> Mike
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
For your natural "enter", assuming it does not have a dedicated function
on the TV and is thus not passed to mythfrontend.
You will probably need a keyboard attached to the Pi.
You can map any available remote button to a mythtv action e.g. "SELECT"
Setup>Edit Keys>Global>SELECT . Up to 4 keys/buttons can be mapped, pick
a blank box, (or one of the used ones).
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160709/f9933de6/attachment-0001.html>
More information about the mythtv-users
mailing list