Posts by edit4ever

Quote from afl1

LibreELEC-Amlogic.aarch64-KII_Pro-7.0.2.004.img - SDcard KII Pro version with fixed wifi adapter. I tested it only with KIII.

Works great on my KII Pro with dual band wifi and gigabit ethernet. Deleted the dtb.img file and just let it use the one installed in nvram and seemed to work. In order to test the k2pro.dtb, I'll have to edit the ethernet to rgmii as I have a gigabit wifi chip. I'll make the change and see if it impacts the wifi.

Thanks for your efforts! Now on to my ATSC challenge...hopefully I'll be able to provide some movement there.

Quote from afl1

In kernel is no support for ATSC:
I am using alex kernel from LE 7.0.2.003. Sources for K1 Plus dbv_tv modules are not public.

Thanks for the heads up on that before I started digging. I have a firmware from my vendor for testing ATSC - I'll see if I can pull the drivers I need from there.

Quote

Instead of nvram.txt I used nvram_bcm4335.txt and fw_bcm4335b0_ag.bin and it works. In new kernel (since 7.0.2.005) this issue disappears. I will implement it in new build.

Thanks for including in the next build!

FYI - My test version of the new KII Pro has a gigabit ethernet. I was able to change the dtb to reference the rgmii in the ethernet section and that worked...but I think I have to wait for your 005 for my wifi to work??

If I use your dtb in my KII Pro, either stock or k2pro.dtb - I get stuck on the amlogic logo. If I remove the dtb file, it will boot to LE, but wifi doesn't work. (See the dmesg excerpt below)

Any thoughts on how to address this? I was thinking of copying the BCM4335 firmware, nvram and config files to the /system/etc/firmware/ path - but is there even a /system path in LE??

dhd_bus_devreset: == WLAN ON ==
[   13.426452@2] F1 signature read @0x18000000=0x1601433
[   13.428959@2] F1 signature OK, socitype:0x1 chip:0x4335 rev:0x1 pkg:0x0
[   13.429359@2] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
[   13.429524@2] dhdsdio_probe_init: set use_rxchain 1 from config.txt
[   13.429582@2] dhd_conf_read_config: Ignore config file /system/etc/firmware/config.txt
[   13.429592@2] dhd_conf_set_fw_name_by_chip: firmware_path=/system/etc/firmware/fw_bcmdhd.bin
[   13.429599@2] Final fw_path=/system/etc/firmware/fw_bcmdhd.bin
[   13.429603@2] Final nv_path=/system/etc/firmware/nvram.txt
[   13.429608@2] Final conf_path=/system/etc/firmware/config.txt
[   13.429921@2] dhdsdio_download_code_file: Open firmware file failed /system/etc/firmware/fw_bcmdhd.bin
[   13.429927@2] _dhdsdio_download_firmware: dongle image file download failed
[   13.429952@2] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   13.429959@2] dhd_prot_ioctl : bus is down. we have nothing to do
[   13.429965@2] dhd_net_bus_devreset: dhd_bus_devreset: -35
[   13.430004@2] wifi_platform_set_power = 0
[   13.430010@2] ======== PULL WL_REG_ON LOW! ========
[   13.430015@2] wl_android_wifi_on: Failed
[   13.430022@2] dhd_open : wl_android_wifi_on failed (-35)
[   13.430028@2] dhd_stop: Enter ffffffc06020d000
[   13.430033@2] wl_android_wifi_off in 1
[   13.430038@2] wl_android_wifi_off in 2: g_wifi_on=0
[   13.430042@2] wl_android_wifi_off out

As an FYI, my KII Pro is a custom build for testing dual internal ATSC tuners - so I will have to do some work to get the dual tuners to show up...but is the ATSC hardware part of your build? Should be using similar hardware to what was in the KI Plus ATSC version.

Thanks for your thoughts!

Still hunting for my wifi issue...I did a dmesg dump from Android - interesting stuff on the wifi around 17.5 seconds into boot.

Dropbox - M8s+ 4k - Android dmesg.txt

Also - here is the zipped 4335 folder with the files referenced in the dmesg.

Dropbox - 4335.zip

FYI - had to use dropbox as attachments were not working for some reason.

I'll figure this out eventually!

I think the issue has to do with the power on and maybe interrupt pins?? I believe my power on pin is 238 and interrupt on 239. The KII.dtb that exists is set to 234 and 235.

of course - I may be heading down the wrong road.

@kzsaq - Definitely a BCM4335...not sure why it's not working in your LE build.

M8s+ 4k - Android output.txt

I think there must be something different in the bootloader or kernel as the firmware that was supplied did not get the wifi working in Android. I had to make a dd copy from a working box and dd back to the non-working android wifi box the bootloader, boot, reserved and misc blocks in order to get the wifi working again in Android.

Weird.

Still working to troubleshoot the missing wifi on my custom KII Pro box...

Did a dump of the rom...is there anything I should look for in these files to get info?

C:\Users\Jason\Desktop\TV Project\ADB>adb shell
shell@m8s_4k:/ $ ls -al /dev/block/platform/d0074000.emmc/by-num
lrwxrwxrwx root     root              2014-12-31 16:00 p1 -> /dev/block/bootloader
lrwxrwxrwx root     root              2014-12-31 16:00 p10 -> /dev/block/misc
lrwxrwxrwx root     root              2014-12-31 16:00 p11 -> /dev/block/instaboot
lrwxrwxrwx root     root              2014-12-31 16:00 p12 -> /dev/block/boot
lrwxrwxrwx root     root              2014-12-31 16:00 p13 -> /dev/block/system
lrwxrwxrwx root     root              2014-12-31 16:00 p14 -> /dev/block/data
lrwxrwxrwx root     root              2014-12-31 16:00 p2 -> /dev/block/reserved
lrwxrwxrwx root     root              2014-12-31 16:00 p3 -> /dev/block/cache
lrwxrwxrwx root     root              2014-12-31 16:00 p4 -> /dev/block/env
lrwxrwxrwx root     root              2014-12-31 16:00 p5 -> /dev/block/logo
lrwxrwxrwx root     root              2014-12-31 16:00 p6 -> /dev/block/recovery
lrwxrwxrwx root     root              2014-12-31 16:00 p7 -> /dev/block/rsv
lrwxrwxrwx root     root              2014-12-31 16:00 p8 -> /dev/block/tee
lrwxrwxrwx root     root              2014-12-31 16:00 p9 -> /dev/block/crypt
shell@m8s_4k:/ $

Thanks in advance for any insight!

@kzsaq - After looking inside my updated KII Pro box...it seems I have an RTL8211F for wifi.

The driver for this was not updated until the 4.2 kernel. linux/drivers/net/phy/realtek.c - Elixir - Free Electrons

Do your builds include this updated driver? If not - I can try to compile a build on my end, or if possible, could you add to the 008 update?

Thanks!

For my project - the improvements in pvr are what is desired in kodi 17 as the main use of my boxes is for live ota tv. However - I am totally fine working in 16 and getting a stable version with working internal tuners. That's my goal for now and I'll experiment in 17 on my Rpi3.

Quote from kszaq

edit4ever Can you please post the zip file with log when you use the latest device tree?

log-2016-09-22-23.11.01.zip

Looks like same issue with power - "no support for card's volts"

Thanks kszaq!

Unfortunately it didn't work. In fact, that dtb didn't even show wireless networks in LE network settings.

I appreciate your effort in trying to solve this, but know you have other priorities to work on. (Like DVB internal tuners!)

I have reached out to Videostrong to see what sort of "magic" they have done to this wifi installation and will continue to experiment on my end.

After trying all the varieties of device tree files as well as trying to customize my own based on my android firmware dtb.img - it seems I still can't get wifi to show any networks. The device is a Videostrong KII Pro that seems to have different/newer hardware than the common KII Pro devices that are out there.

Looking at the logs, it appears that there is a power issue with the wifi on sdio.

log-2016-09-21-20.47.57.zip

I just wanted to make sure that the BCM4335 on SDIO should be supported under the 007 build before I continue to experiment.
Thanks!

kszaq - I finally got a hold of the M8S+ 4K file from Videostrong. Actually, they have been quite helpful with information and files.

m8s+4k.zip

So while I have a KII Pro with custom ATSC hardware - they are using the firmware from the M8S+ 4K as it matches the components used in my build. It's not clear, but this may be the configuration of future KII builds, but they haven't finished the firmware yet - or it may be a one off for testing.

From what I can tell - the biggest difference seems to be in the wifi section with references for the aml_broadcm_wifi and wifi_power and of course the gigabit ethernet. Maybe others, but let me know if you need anything else to generate the dtb.

Thanks!

Quote from ekincaid

When I check the configuration I see that the EPG source list is completely blank and I will have to set each one again.

Seems strange and more of a tvheadend issue than a zap2xml problem. Next time it comes up blank, check and see what the update time is on the xmltv.xml file. That way you can narrow down if there is an issue with the file being generated - or of there is an issue with tvheadend holding your configuration. It would also help to post your hardware setup.

There has been an issue that I've read about with the epg in kodi going blank - but you mention that the epg in tvh is blank and that the epg source fields have gone blank as well. That I have not seen - but may be worth posting in the tvheadend forum.

Quote from kszaq

I think you might get booting issues with that device tree because your bootloader doesn't support multi-device device tree blobs and that's what supplied image is.

Your thought got me thinking about the strange firmware that was loaded on this box (listed as a M8S+ 4K)

As a result - I went ahead and loaded the Acemax KII Pro firmware (using USB Burning Tool) and sure enough...once it booted back up, no wireless or lan connection was available in Android. So I believe that Videostrong is using different hardware for wifi and lan than Acemax is.

The challenge now is to get Videostrong to provide their device tree or at least the M8S+ 4K firmware that they used (which looks like it may have come from Acemax anyway)...but they haven't been very responsive in the last few days.

In the meantime - I can still get up and running on lan with your LE 007 and the minimxIII dtb. Maybe I'll try to custom build a dtb while I wait for the Videostrong response.

kszaq I converted the KII Pro and MiniMxIII dtb files in your device trees to dts files to compare to the information. I was surprised to see that the KII Pro file was based on the gxb_p200_1g. This seems strange as the KII Pro is a 2G box.

Also, when I went to convert gxbb_p200_1Gbit.dtb to dts - it gave me the error: FATAL ERROR: Blob has incorrect magic number

Before I download your source and attempt to make a KII Pro patch that works on my boxes, I thought I would check with you on what I had discovered.

Acemax KIII 2G/16G 1000M 802.11ac 2.4G and 5G Dual Band WIFI
dtb.zip

As an FYI, I installed 7.0.2.005 and see the same result with wifi as I do with 007. Shows up in the LE settings as active, but does not list any available connections. Not sure if there is anything different to see - but here is the log: log-2016-09-18-04.20.41.zip

Looks like I need to get a hold of my specific device tree. Thinking about it, it may be worth checking the device from my other post to see if it is any different from the KII Pro tree you already have: LibreELEC

Thanks!

Quote from kszaq

You should note that if device tree from original firmware was compiled for older kernel, your box won't boot.

Kernel of installed firmware is 3.14.29 so I'm hopeful it will work. Won't be back in front of the box to test until tonight - but I'll update once I've tried.

Thanks again for your efforts on this project!