User Tools

Site Tools


test_decoder_card

This is an old revision of the document!


Test Decoder Card

Oct 2018


Introduction

When testing the MFCP decode, it is possible that the decoder card may have failed, and that the MFCP has dropped to SW decoding. In 4K this my not be obvious if you are decoding some very simple content.

There are however a couple of tests that can be made to ensure that the decoder card is working (as much as we can tell).


Is the Decoder Card detected by the Driver?


Each time the MFCP is started, the driver communicates with the decoder card, we can see if the decoder was detected by looking for the driver in CentOs.

  Run the command:
  
  ls /dev
  
  
  Among the listed files/folders you should see the following:
  
  decoder0
  sdi0



If these are missing, the card may have failed (or just failed to boot) if you restart the unit and still don't see these two entries then you may have a decoder card failure.

If these are not listed then there is a hardware or driver issue with the card. First step would be to try reinstalling.


When the Decoder is in use


lsmod | grep decoder

decoder                22463  1    <-- last number is number of instances using driver. 0 means the device isn't used.

For the SDI:

lsmod | grep sdi

sdi                    17706  1   <-- last number is number of instances using driver. 0 means the device isn't used.



test_decoder_card.1538560080.txt.gz · Last modified: 2023/03/09 22:35 (external edit)