Posts by pepesuriano

    Update in #1.

    It works like a charm! crazycat your tuner improvement solved the issue.

    We are not competing! I am only following kszaq's main line adding capabilities to support internal driver.

    afl1  kszaq have you tried to mirror the work with KII Pro using S912 based image and implement same base (onboard tuner support) for KIII Pro?

    It seems that r848 is trying to tune dvbs or i'm reading useless info?

    Special test build for pepesuriano with the latest crazycat69 ''Improve DVB-C annex A and B support''

    Try to use DVB-C Annex B as DVB-.C. Driver is trying detect annex B.

    Tested. With dvbc anx b (using dvbc option) and atscc it has the same behaviour


    1. LibreELEC (community) Version: 8.0.0f-annexB
    2. LibreELEC git: c3df916ccd7b06fb923e473f7b2c308501498ada
    3. HTS Tvheadend 4.1.2459 ~ LibreELEC Tvh-addon v8.1.11

    SSH output

    Tvheadend output

    Is it also returning infinite times this error only when either atsc or dvbc tuner gets enabled

    1. [  [email protected]] R848: r848_init:
    2. [  [email protected]] AVL: avl6862_read_status: Level=32
    3. [  [email protected]] AVL: avl6862_read_status: Level=32
    4. [  [email protected]] AVL: avl6862_read_status: Level=32
    5. [  [email protected]] AVL: avl6862_read_status: Level=32
    6. [  [email protected]] AVL: avl6862_read_status: Level=32
    7. [  [email protected]] AVL: avl6862_read_status: Level=32
    8. [  [email protected]] AVL: avl6862_read_status: Level=32
    9. [  [email protected]] AVL: avl6862_read_status: Level=32

    Provide also driver debug log.

    Tuner does not lock with atsc, with dvbc it does

    For annex B you have to create ATSC-C network and connect it to ATSC-C adapter.

    New tvheadend42 version:
    Adding standard sharing damaged some other features. In this version it is fixed.

    When creating muxes the combo box only shows “DVB_C" and “DVB_C Annex c" B is not an option un this version of tvheadend :/

    From interactive log:

    What are those PID?

    From ssh console:
    [ [email protected]] R848: r848_init:
    [ [email protected]] AVL: avl6862_set_dvbmode: initing demod for delsys=1
    [ [email protected]] i2c i2c-1: Load avl6862 firmware patch for DVB-C size=47928
    [ [email protected]] AVL: avl6862_wait_demod_boot: status:1 ready_code:0x5aa57ff7
    [ [email protected]] AVL: avl6862_wait_demod_boot: status:0 ready_code:0x5aa57ff7
    [ [email protected]] i2c i2c-1: avl6862 patch ver 2.0 build 20559
    [ [email protected]] R848: r848_set_params: delivery_system=1 frequency=507000000 symbol_rate=5360000 bandwidth_hz=6164000
    [ [email protected]] R848: R848_GetLockStatus: R848_GETLOCKSTATUS=0x72
    [ [email protected]] R848: r848_set_params: Tuner Locked.
    [ [email protected]] AVL: avl6862_set_dvbc: Freq:507000000 Mhz,sym:5360000

    This was with HTS Tvheadend 4.1.2459 and OTA EPG disabled in dvbc tuner in tvheadend

    Hi, I guess that there are not annex B news, but I would like to help debugging, is there any guide to a good debugging of drivers in tvheadend? I see you put linuxdvb in debug console but info at web is a bit confusing and I am not sure of where extract the info, could you provide any tips to research some interesting info?

    Sorry if that sounds like kinder garden, we are doing out first steps in that

    Edit: maybe having those tips sticked in #1 would avoid a lot of questions

    registering mux for OTA EPG >>" For test is necessary disable OTA EPG in adapter settings "

    Sorry, config didnt get applied

    2017-03-13 15:01:45.041 mpegts: 507MHz in my dvbc - tuning on Availink avl6862 : DVB-C #0
    2017-03-13 15:01:45.042 subscription: 0004: "scan" subscribing to mux "507MHz", weight: 6, adapter: "Availink avl6862 : DVB-C #0", network: "my dvbc", service: "Raw PID Subscription"
    2017-03-13 15:01:50.042 mpegts: 507MHz in my dvbc - scan no data, failed
    2017-03-13 15:01:50.042 subscription: 0004: "scan" unsubscribing

    Not working here

    2017-03-13 14:27:38.364 htsp: Got connection from
    2017-03-13 14:27:38.364 htsp: Welcomed client software: Kodi Media Center (HTSPv25)
    2017-03-13 14:27:38.365 htsp: [ Kodi Media Center ]: Identified as user ''
    2017-03-13 14:28:18.656 mpegts: 507MHz in dvbc - tuning on Availink avl6862 : DVB-C #0
    2017-03-13 14:28:19.762 epggrab: 507MHz in dvbc - registering mux for OTA EPG
    2017-03-13 14:28:19.777 subscription: 0001: "scan" subscribing to mux "507MHz", weight: 6, adapter: "Availink avl6862 : DVB-C #0", network: "dvbc", service: "Raw PID Subscription"
    2017-03-13 14:28:24.746 mpegts: 507MHz in dvbc - scan no data, failed
    2017-03-13 14:28:24.747 subscription: 0001: "scan" unsubscribing

    As I know there are no GPIOs for common use. I don't know nothing about internal connector pinouts.
    In S905_Public_Datasheet is following:
    "The SOC has a number of multi-function digital I/O pads that can be multiplexed to a number of internal resources (e.g. PWM generators, SDIO controllers …). When a digital I/O is not being used for any specific purpose, it is converted to a general purpose GPIO pin. A GPIO pin can be statically set to high/low logical levels."

    Thinking in the reversed way, how difficult could it be to use a rpi3 GPIO's to connect KII tuner board for example?