03-28-2013 01:57 PM - edited 03-18-2019 12:51 AM
Hello,
I was wondering if anyone has come across this issue with the SX20 QuickSet:
- SX20 goes to standby and CEC works normally, so that the screen goes in standby
- The SX20 is restarted from the GUI
- The SX20 restarts and the CEC functionality renders non operational; the codec does not wake up the screen anymore, it stays in standby although the codec is active - even more, this appears so only on HMDI output 1, HDMI output 2 works well and as expected
Software version is the newest TC6.0.1
Cheers,
Mihail
03-28-2013 03:28 PM
I would recommend to turn on some debugs and repeat the test where you put the screen/codec in standby and then in active mode.
Logon to the SX20 via ssh with admin and execute following commands :
sys-fsm
s-t 0x13ff cecctrl
s-t 0x13ff cec_fsm
trace-output on
Then put the codec in standby mode and active mode whilst logging the data in the "ssh" screen window.
Replace the IP address above with your IP address.
Then stop the debugging in the ssh window.
trace-output off
s-t 0x0 cecctrl
s-t 0x0 cec_fsm
quit
And you are back in the admin tandberg shell.
03-28-2013 10:13 PM
Hello Danny,
It looks like a very interesting procedure that could provide a very useful insight, but the codec does not accept the commands
sys-fsm
s-t 0x13ff cecctrl
s-t 0x13ff cec_fsm
trace-output on
in admin nor in root mode.
Where should these be entered please ?
Thanks,
Mihail
03-28-2013 10:46 PM
sweet-brew-7:/home/dderidde # ssh root@10.60.142.199
Welcome to my home EX90!
Password:
[dderidde-ex90-home:~] $ tsh
Welcome to dderidde.ex90.home
TANDBERG Codec Release TC6.0.1.65adebe
SW Release Date: 2013-02-21
OK
sys-fsm
OK
s-t 0x13ff cecctrl
Bits set to 0x13ff
OK
s-t 0x13ff cec_fsm
Bits set to 0x13ff
OK
trace-output on
OK
03-28-2013 11:45 PM
Hi Danny,
Here is the CEC trace output when everything works as it should, system in standby, both HDMI 1 and HDMI 2 wake up to active works:
Cisco Codec Release TC6.0.1.65adebe
SW Release Date: 2013-02-21
OK
sys-fsm
OK
s-t 0x13ff cecctrl
Bits set to 0x13ff
OK
s-t 0x13ff cec_fsm
Bits set to 0x13ff
OK
trace-output on
OK
1465197.634 fsm-R: CECCTRL 000 <- VIDEOLC 000 CECCTRL_DisplayPowerState Ready
CECCTRL_Common_doCECCTRLDisplayPowerState: id 1, powersave off
CECCTRL_sendConfig
flags : 0x2
enabled : yes
powersave : no
display : 1
addr : 1.0.0.0
OSDname : SX20-HDMI-1
1465197.640 fsm-S: CECCTRL 000 -> CEC_FSM 000 CECCTRL_Config
1465197.640 fsm-R: CEC_FSM 000 <- CECCTRL 000 CECCTRL_Config Ready
CEC_Common_doCECCTRLConfig:
1465197.642 fsm-S: CEC_FSM 000 -> CEC_FSM 000 CEC_DisplayPowerManagement
1465197.642 fsm-R: CEC_FSM 000 <- CEC_FSM 000 CEC_DisplayPowerManagement Ready
CEC_Ready_doCECDisplayPowerManagement: display 1, powersave off
CEC_send_give_power_status
buildCecTxGiveDevicePowerStatus initiator: 4 destination: 0
CEC_post_tx_msg
CEC_send_cec_msg, cecId 0, len 2
1465197.660 fsm-R: CECCTRL 000 <- VIDEOLC 000 CECCTRL_DisplayPowerState Ready
CECCTRL_Common_doCECCTRLDisplayPowerState: id 2, powersave off
CECCTRL_sendConfig
flags : 0x2
enabled : yes
powersave : no
display : 0
addr : 1.0.0.0
OSDname : SX20-HDMI-2
1465197.662 fsm-S: CECCTRL 000 -> CEC_FSM 001 CECCTRL_Config
1465197.662 fsm-R: CEC_FSM 001 <- CECCTRL 000 CECCTRL_Config Ready
CEC_Common_doCECCTRLConfig:
1465197.663 fsm-S: CEC_FSM 001 -> CEC_FSM 001 CEC_DisplayPowerManagement
1465197.663 fsm-R: CEC_FSM 001 <- CEC_FSM 001 CEC_DisplayPowerManagement Ready
CEC_Ready_doCECDisplayPowerManagement: display 0, powersave off
CEC_send_give_power_status
CEC_post_tx_msg
CEC_send_cec_msg, cecId 1, len 2
Now here is the example I already explained. The system is in standby, and it is then restarted.
After the restart CEC is operational on HDMI 2 but not on HDMI 1.
SW Release Date: 2013-02-21
OK
sys-fsm
OK
s-t 0x13ff cecctrl
Bits set to 0x13ff
OK
s-t 0x13ff cec_fsm
Bits set to 0x13ff
OK
trace-output on
OK
204.452 fsm-R: CECCTRL 000 <- VIDEOLC 000 CECCTRL_DisplayPowerState Ready
CECCTRL_Common_doCECCTRLDisplayPowerState: id 1, powersave off
CECCTRL_sendConfig
I guess here something out of the ordinary happened I do not see the message with OSDname : SX20-HDMI-1, display 1
204.465 fsm-R: CECCTRL 000 <- VIDEOLC 000 CECCTRL_DisplayPowerState Ready
CECCTRL_Common_doCECCTRLDisplayPowerState: id 2, powersave off
CECCTRL_sendConfig
flags : 0x2
enabled : yes
powersave : no
display : 0
addr : 1.0.0.0
OSDname : SX20-HDMI-2
204.479 fsm-S: CECCTRL 000 -> CEC_FSM 001 CECCTRL_Config
204.479 fsm-R: CEC_FSM 001 <- CECCTRL 000 CECCTRL_Config Ready
CEC_Common_doCECCTRLConfig:
204.479 fsm-S: CEC_FSM 001 -> CEC_FSM 001 CEC_DisplayPowerManagement
204.479 fsm-R: CEC_FSM 001 <- CEC_FSM 001 CEC_DisplayPowerManagement Ready
CEC_Ready_doCECDisplayPowerManagement: display 0, powersave off
CEC_send_give_power_status
buildCecTxGiveDevicePowerStatus initiator: 4 destination: 0
CEC_post_tx_msg
CEC_send_cec_msg, cecId 1, len 2
204.544 fsm-S: CEC_FSM 001 -> CEC_FSM 001 CEC_TxOk
204.545 fsm-S: CEC_FSM 001 -> CEC_FSM 001 CEC_RxMsg
204.546 fsm-R: CEC_FSM 001 <- CEC_FSM 001 CEC_TxOk Ready
CEC_Ready_doCECTxOk
CEC_tx_ok, msg count 1
204.546 fsm-R: CEC_FSM 001 <- CEC_FSM 001 CEC_RxMsg Ready
CEC_Common_doCECRxMsg: (3): 4 90 1
cec: initiator: 0 destination: 4
cec: 0x90 Report Power Status
cec: PowerStatus: Power Standby 0x1
handleCecRxMsg: initiator 0, destination 4, receiver yes, broadcast no, opcode 0x90, polling 0
204.737 fsm-R: CECCTRL 000 <- VIDEOLC 000 CECCTRL_DisplayInfo Ready
CECCTRL_Common_doCECCTRLDisplayInfo: id 2, gw_ind 0, display 0, edid segment 0
CECCTRL_parseEdid
CECCTRL_sendConfig
flags : 0x10
enabled : yes
powersave : no
display : 0
addr : 1.0.0.0
OSDname : SX20-HDMI-2
204.740 fsm-S: CECCTRL 000 -> CEC_FSM 001 CECCTRL_Config
204.741 fsm-R: CEC_FSM 001 <- CECCTRL 000 CECCTRL_Config Ready
CEC_Common_doCECCTRLConfig:
CEC_Common_doCECCTRLConfig: same monitor re-plugged or powered up
205.480 fsm-R: CEC_FSM 001 <- FSM_TIMER 000 CEC_DisplayPowerTimer Ready
CEC_Ready_doCECDisplayPowerTimer
device(0) present: dest 0, src 4
CEC_send_image_view_on
buildCecTxImageViewOn initiator: 4 destination: 0
CEC_post_tx_msg
CEC_send_cec_msg, cecId 1, len 2
CEC_send_active_source
buildCecTxActiveSource initiator: 4 destination: 15
CEC_post_tx_msg
CEC_send_give_power_status
buildCecTxGiveDevicePowerStatus initiator: 4 destination: 0
CEC_post_tx_msg
205.546 fsm-S: CEC_FSM 001 -> CEC_FSM 001 CEC_TxOk
205.546 fsm-S: CEC_FSM 001 -> CEC_FSM 001 CEC_RxMsg
205.547 fsm-R: CEC_FSM 001 <- CEC_FSM 001 CEC_TxOk Ready
CEC_Ready_doCECTxOk
CEC_tx_ok, msg count 3
CEC_send_cec_msg, cecId 1, len 4
Any additional thoughts ? As you can see, it is apparent that display 1 does not wake from standby by CEC, so we have to use the LCD remote to wake it up.
Thank you very much for this wonderful insight on the debugging.
Cheers,
M.
03-29-2013 01:13 AM
Hello,
so the trigger for the failure is to have a system in standby mode, reload the SX20, and when it comes up, HDMI 1 connected display never wakes up.
We do see the message :
CECCTRL_sendConfig
But afterwards we are missing the subsequent messages :
flags : 0x2
enabled : yes
powersave : no
display : 1
addr : 1.0.0.0
OSDname : SX20-HDMI-1
I am unaware of any ddts-es being reported against this,so I opened one.
CSCuf93352 - CEC fails to bring HDMI1 out of standby when SX20 is reloaded
Thanks for providing the debugs!
Engineering in Oslo is out for Easter, so please allow some time before the ddts gets worked upon.
Regards,
Danny.
03-29-2013 01:19 AM
Thanks for this Danny.
I would just add an additional comment for the ddts,
CEC fails to bring HDMI1 out of standby when SX20 is reloaded whilst in standby
because if it is active and reloaded, then everything works as expected.
Regards,
Mihail
03-29-2013 01:31 AM
Hello,
yes, that's understood. I could not squeeze it into the title line of the ddts, but the release note clarifies this.
Symptom:
SX20 does not wake up display on HDMI1, even when CEC is set correctly.
Conditions:
Issue occurs after reloading SX20 from GUI when it is in standby mode.
Workaround:
Use remote control of display connected to HDM1 to wakeup the screen.
04-04-2013 12:57 AM
Hello,
I got feedback from engineering on this bug and they say :
My suspicion is that this is a monitor problem. Do you have the same make and model for both HDMI1
and HDMI2? On a BENQ monitor I have there is a difference in the LCDs wake-up behaviour depending
on whether a single or multiple input sources are connected.
If it is a monitor issue, the problem would move with the monitor if we swap the monitor on HDMI2 to HDMI1 and vice versa, right?
Could you do such a test?
Also, to get the make of your monitors, could you send me the current logbundle from your system so I can decode the
EDID data which is normally in all.log ?
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: Edid segment 0 for display HDMI 1:
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x00, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x4c, 0x2d, 0xa7, 0x07, 0x00, 0x00, 0x00, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x30, 0x14, 0x01, 0x03, 0x80, 0x30, 0x1b, 0x78,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x0a, 0xee, 0x91, 0xa3, 0x54, 0x4c, 0x99, 0x26,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x0f, 0x50, 0x54, 0xbf, 0xef, 0x80, 0x71, 0x4f,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x81, 0x00, 0x81, 0x40, 0x81, 0x80, 0x95, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x95, 0x0f, 0xb3, 0x00, 0x01, 0x01, 0x02, 0x3a,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x80, 0x18, 0x71, 0x38, 0x2d, 0x40, 0x58, 0x2c,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x45, 0x00, 0xdd, 0x0c, 0x11, 0x00, 0x00, 0x1e,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x66, 0x21, 0x50, 0xb0, 0x51, 0x00, 0x1b, 0x30,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x40, 0x70, 0x36, 0x00, 0xdd, 0x0c, 0x11, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x00, 0x1e, 0x00, 0x00, 0x00, 0xfd, 0x00, 0x18,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x4b, 0x1a, 0x51, 0x17, 0x00, 0x0a, 0x20, 0x20,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xfc,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x00, 0x53, 0x4d, 0x54, 0x32, 0x32, 0x41, 0x33,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x35, 0x30, 0x0a, 0x20, 0x20, 0x20, 0x01, 0xc7,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x02, 0x03, 0x23, 0xf1, 0x4b, 0x90, 0x1f, 0x04,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x13, 0x05, 0x14, 0x03, 0x12, 0x20, 0x21, 0x22,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x23, 0x09, 0x07, 0x07, 0x83, 0x01, 0x00, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0xe2, 0x00, 0x0f, 0x67, 0x03, 0x0c, 0x00, 0x10,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x00, 0xb8, 0x2d, 0x01, 0x1d, 0x00, 0x72, 0x51,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0xd0, 0x1e, 0x20, 0x6e, 0x28, 0x55, 0x00, 0xa0,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x5a, 0x00, 0x00, 0x00, 0x1e, 0x01, 0x1d, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0xbc, 0x52, 0xd0, 0x1e, 0x20, 0xb8, 0x28, 0x55,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x40, 0xa0, 0x5a, 0x00, 0x00, 0x00, 0x1e, 0x01,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x1d, 0x80, 0x18, 0x71, 0x1c, 0x16, 0x20, 0x58,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x2c, 0x25, 0x00, 0xa0, 0x5a, 0x00, 0x00, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x9e, 0x01, 0x1d, 0x80, 0xd0, 0x72, 0x1c, 0x16,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x20, 0x10, 0x2c, 0x25, 0x80, 0xa0, 0x5a, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x00, 0x00, 0x9e, 0x00, 0x00, 0x00, 0x00, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0d,
Apr 3 21:52:19 a8 appl: 20333.56 VIDEOLC-0 I: Edid event received, new timing list made for output HDMI 1
Thanks!
Danny.
04-04-2013 03:14 AM
Hello Danny,
The monitors are not the issue. I already swapped the HDMI cables, issue pertains on HDMI 1.
Even more, both LCD monitors are completely the same, make and model, Sony KDL-55HX750
Thanks,
Mihail
04-04-2013 08:57 AM
Hello,
engineering had some extra questions.
1: sx20 in standby.
2: both monitors off via CEC.
3: System restarted via web-interface
4: How do you manage to catch the trace during start-up ?
(I guess you did the debug when the system was started up, and then you woke up screens using Web or remote control or touch panel? )
There are Hardware differences between HDMI-1 and HDMI-2.
HDMI-2 is the built-in HDMI/CEC transmitter in the Netra-chip while
HDMI-1 uses HDMI transmitter ad9389b together with the spare CEC-device in the DVI-I receiver. But they should behave in the same way.
Engineering tested with a Samsung monitor here and it wakes up while it boots and shows splash screen.
Do you get to see the splash screen on any display, i.e. the Cisco logo when the codec boots up?
04-04-2013 01:44 PM
1: sx20 in standby.
2: both monitors off via CEC.
3: System restarted via web-interface
4: How do you manage to catch the trace during start-up ?
I guess you did the debug when the system was started up, and then you woke up screens using Web or remote control or touch panel?
Exactly.
Do you get to see the splash screen on any display, i.e. the Cisco logo when the codec boots up?
Yes, everything works as it should on HDMI 2, but HDMI 1 CEC is dead after a boot from standby.
04-05-2013 01:04 AM
Hello,
engineering explained following differences between both HDMIs.
A main difference between the two HDMI outputs is that HDMI-1 will require Hotplug from the monitor to be able to activate the TMDS-links, while HDMI-2 is able to send video-data regardless of Hotplug-state. And will do so.
When you have this situation, which I assume is after a re-boot of the codec could you look at the status of the HDMI-1 transmitter.
On the linux prompt
v4l2-ctl -d 2 --log-status
For comparison do also HDMI-2
v4l2-ctl -d 3 --log-status
Thanks!
Danny.
04-05-2013 01:17 AM
Hi Danny,
I will do the logging for you during the weekend, when the system is not utilized, but the fundamental issue still sticks.
Having two identical LCD screens, the HDMI outputs of the SX20 do not behave the same.
I still think this is a bug problem on the codec.
Thanks.
Mihail
04-05-2013 01:23 AM
I do not disagree this is issue on the codec, that's why I opened CSCuf93352.
I will update the ddts if/when I get the log-status info from you.
Thanks for the help,
Danny.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide