Posts by edit4ever

Quote

Yeah, that was actually my fault. After I set things back up, and because tvheadend will not add the muxes automatically, I have to manually add each mux.

This is TVH issue for ATSC muxes was solved starting with the 2214 nightly release. There was an issue with the code for memory that messed it up. You can download one of CVH's nightlies index - powered by h5ai v0.29.0 (https://larsjung.de/h5ai/) for the RPi. For the other boxes, we need the LE repo to be updated (repo is still 1945) to a later release to get back the predefined ATSC muxes. I can compile a version later and upload a link if you need it for amlogic.

chewitt I wanted to make sure enough people had tested before submitting. It looks like things are pretty solid, so I'll take a look at updating my readme instructions and read the wiki on how to submit addons. (still learning)

Latest release links (also updated on first post):

Latest zap2xml addon release: Dropbox - script.module.zap2xml.zip
zap2xml addon source: GitHub - edit4ever/script.module.zap2xml

Latest schedules direct addon release: Dropbox - Link not found
Schedules Direct addon source: GitHub - astrilchuk/sd2xmltv: A Schedules Direct to xmltv converter

Quote from crazycat

Check open-source mn88436 driver from TBS
add the demod'mn88436'and tuner 'mxl603'
added support TBS6704

Thanks crazycat! I'll give that a try when I get back to my test unit tomorrow night.

Thought I'd ask here as a start...

I'm testing some new dual tuner ATSC hardware...but need to get the driver/kernel module developed/ported to work in LE. As of now, the tuner works in Android but since this is beyond the scope of my skills - so I'm looking for help. It's built on the Panasonic MN88436 hardware.

If I can't find volunteers, I'm open to hearing about places to post to find freelancers.

Thanks!

Quote

So either there's some setting I've missed or a dependency that required that I don't have, but for some reason it refuses to write the xmltv.xml file.

This is due to trying to grab too many channels/days - zap2it server times out. when first setting up - leave the default settings. Then you can add extra days and details a day or two at a time. until you get to the level you want (up to 14 days)...once you get the full amount of days to load, it will keep the epg updated as it will just need to grab a new day's data every day.

Quote

I had to first install Aeon Nox skin before it would actually install mechanize

Not sure why you're seeing this unless there is an issue with the Kodi repo it is pulling mechanize from.

Quote

Now with the default zap2xml settings it's writing the xmltv.xml file, but now tvheadend is not able to pull the data.

Have you setup the tvheadend channels to point to the proper zap2xml epg channel? They usually don't connect automatically, so you have to set the it up manually. It's on the CONFIGURATION>CHANNEL/EPG>CHANNELS tab. You select the epg source column for each channel and pick the correct zap2xml data for the channel you're setting up.

Sorry about the delay in responding - I've been travelling and haven't checked in. Let me know if you're still having issues.

Quote from kszaq

I also think I will make 7.0.2.008 build next week.

Would it be possible to add the following firmware to your build??

ATSC_firmware.zip

I'm starting to work on getting ATSC dvb working and these are generally not included in the kernel. I still have to work on figuring out the driver - but this would be a start. Thanks!

Quote from afl1

I published sources for KI Plus and KII Pro.
GitHub - afl1/LibreELEC.tv: 'Just enough OS' for Kodi

There is special rule: You cannot change config of linux build-in modules. Only changes possible in linux are modification of loadable modules and firmware files.

Thanks for this - based on what you said above, I should be able to add the following firmware to the build?

ATSC_firmware.zip

Unfortunately, these aren't currently in the kernel.

afl1 - I'm working to get my ATSC version of the K2Pro working under your build. I'm having trouble getting the wifi to function. My device tree needs to be different as the power and interrupt pins for wifi are 238 and 239 instead of 234 and 235 like on the standard boxes. Also I have a gigabit lan chip.

I've made the changes in the dtb file that should enable these to function.

wifi {
        compatible = "amlogic, aml_broadcm_wifi";
        dev_name = "aml_broadcm_wifi";
        status = "okay";
        interrupt_pin = <0x20 0x67 0x0>;
        interrupts = <0x0 0x44 0x4>;
        irq_trigger_type = "GPIO_IRQ_LOW";
        power_on_pin = <0x20 0x66 0x0>;
        pinctrl-names = "wifi_32k_pins";
        pinctrl-0 = <0x24>;
    };


    ethernet@0xc9410000 {
        compatible = "amlogic, gxbb-rgmii-dwmac";
        reg = <0x0 0xc9410000 0x0 0x10000 0x0 0xc8834540 0x0 0x8>;
        interrupts = <0x0 0x8 0x1>;
        phy-mode = "rgmii";
        pinctrl-names = "eth_pins";
        pinctrl-0 = <0x1f>;
        rst_pin-gpios = <0x20 0xe 0x0>;
        mc_val = <0x1621>;
        resets = <0xc 0x23>;
        reset-names = "ethpower";
        interrupt-names = "macirq";
        clocks = <0xc 0xa>;
        clock-names = "ethclk81";
    };

Lan is working - but wifi is having issues.

Here is the dmesg output: K2proATSC-dmesg.zip

This change worked on kszaq's builds...but I know that is a different kernel.

Thanks for any insight!

-- additional info:

Here is the dmesg output when I delete the dtb.img and let it boot: K2proATSC-orig-dmesg.zip

Quote from afl1

Sorry wrong versions. I fixed them.

Link shows file has been deleted.

My mistake - I needed to go back to the original post!
LibreELEC

Looking to merge the dvb-atsc device tree info that I extracted from a working android test build into the device tree that afl1 is using in his builds.

Besides the obvious dvb lines at the end of the file - are there other lines I need to try to merge? The tricky part may be that the pins are different on my custom build as it has dual ATSC tuners, bcm4335 wifi and gigabit ethernet. Not sure how this impacts all the lines in the device tree.

I've got wifi and gig lan working under kszaq's builds (thanks to his efforts!) now I'm looking to work on the dvb functions so I'm experimenting with afl1's builds.

Here is the device tree I pulled from the android test build: k2pro_atsc.zip

The wifi doesn't work on this device tree (or in android) - but not a big deal...as it was meant as a test build to make sure the hardware was functioning.
I'm guessing there may also be some firmware/drivers I need to pull out of the android build to bring into LE.

I'm happy to play and experiment, but if anyone has a little guidance on where to focus first I would appreciate it!

Quote from xtract

Is it possible to buy the KII Pro with gigabit? I think that this is the best solution for what I want but I would miss a gigabit port...

Not sure...Videostrong custom built my sample boxes as we are looking to build a dvr for the US market. I didn't expect the gigabit ethernet as we didn't specify it, but have no issues with it. The biggest challenge is there is no software support for this type of hardware build - but the goal is to build only for LE and not android - so things are going well so far.

Maybe the newer versions of their box will support gigabit - but I don't believe any of those would be available on the market yet.

kszaq - Thank you again for providing the updated dtb for my KII Pro...

I have a question I'm hoping someone can answer. When I dumped my rom and extracted the boot.img and then the dtb file...it seemed like it was the same as the original M8S+4k file (wrong wifi info) which of course didn't work for me. What I realized during testing was the "misc" part of the nand was impacting the boot and changing dtb info.

So the question is - is there a way to convert the info in the misc block to see what device tree settings it is adjusting? I have dumped the data to a misc.img file...but I'm not sure how to extract the data from it. With the boot.img file I was able to extract the device tree using splitbootimg.pl -- is there something similar for the misc block of data??

Thanks for any info - I'm hoping to dig down to get my ATSC tuners working in LE and want to understand what is happening in the android boot/device tree.

Quote from kszaq

edit4ever Can you test this device tree: gxbb_p200_2G_m8s+_k3_pro.dtb

It can be used with 7.0.2.007 or any of the dev builds. What I changed are power_on_pin and interrput_pin bumped by 4 according to your suggestion in the other thread.

OK - Strangely that worked! I tried doing the same thing on my end but it didn't work. I'll have to compare files to see what I was doing wrong on my test version. I'm still learning!

Thank you!

P.S. If you add that to your device trees - I'm not sure what the right name for it is. k2pro_gig_update.dtb ??

My mistake -

Looks like I hadn't pushed the update to github.

That line should not be in there. I just updated the repo.

Sorry about that!

if "credits" in programs[p]:
fh.write("\t\t<credits>\n")
global sortThing1, sortThing2
sortThing1= str(p)
sortThing2 = "credits"

Take out the red line - that shouldn't be there. Or just download the new zip and update the addon.

The other reason to update is I fixed the space after ampersand issue.

Got it - I think I found the error. If you can open the zap2xml.py file you can check the following:

Open the zap2xml.py file (which is in the /.kodi/addons/script.module.zap2xml folder)...

At line 1401 (or could be 1400 on your version) change the following:

sortThing1 = p

To the following:

sortThing1= str(p)

That should take care of it.

The file is correct on my github: GitHub - edit4ever/script.module.zap2xml

You can try downloading the zip and updating to see if that fixes it. If not - let me know. I'm running this version without any issues.

Quote from Tinwarble

So, I'm having an issue with zap2xml not updating the EPG data. On the first run it it will pull the data, but when it updates there seems to be some issue that I can't figure out.

Which version are you running?

If I have ATSC running under an android build...is there a place I can find the driver/firmware files I need to bring to the LE build?

Also - since I believe the core of my dual ATSC tuner is using the same hardware as the single ATSC tuner in the older K1 Plus...I'm hoping I can build off of that. It is using the Panasonic MN88436 which is the same that is in the wetek. Those firmware files are the same as this:

meta-amlogic/recipes-kernel/linux-firmware/firmware-dvb at master · linux-meson/meta-amlogic · GitHub

I'll start with copying over these files and see where I can go from there.