Jump to content


Photo

Howto build unofficial pli for your unsupported receiver


  • This topic is locked This topic is locked
2740 replies to this topic

Re: Howto build unofficial pli for your unsupported receiver #2021 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 9 August 2018 - 11:05

make for k1plus. I have Error 1.cleansed cleanup-build.sh.no helped.

 

 

http://www.mediafire...pile.14420/file

are you sure you updated ? I fixed this issue in the following commit

https://github.com/P...e24f806e4acb4bf

make sure the patch was applied



Re: Howto build unofficial pli for your unsupported receiver #2022 frankviana

  • Senior Member
  • 474 posts

+4
Neutral

Posted 9 August 2018 - 11:11

Mecool devices owners:
I just pushed an update to the repo, update and build a new image, you should now be able to scan and tune into channels(no picture yet)
some updates:
1- I solved the 64 bit issue thanks to crazycat69 help, so now enigma2 can function in 64 bit mode, hopefully we won't face any problem down the road.
2- Currently the tuner is working but you don't get picture, this is probably an issue with gstreamer and amlogic codecs.
3- You can do an automtic scan for channel but the tuner will lock after some time and will not find many channel and you have to reboot the device to get the tuner working again.
 
Regards


When I did tests, few days ago, comparing alien5 image and K1 pro:

OpenAtv: media player show image ok, but sound only 5 seconds
Openpli: media player no image, no sound. Appear message: no streams found.

Vu+ Ultimo 4k, GTX Combo, GT Combo, Dreambox Two, GT-Media V8XS, GT-Media M7x, GT-Media v9 prime, Gt-Media Finder Meter 2, , TBS 6903-x v2, Octagon SF8008 single, Edision OS Mini 4k, Zgemma h9s SE, GT-Media V8UHD, Raspberry Pi 4, T95 Max + (CoreElec/Tvheadend), Freesky Triplo X, Zgemma h9 twin, Zgemma h9s, Amiko SHD 8900, Gt-Media GTC, Octagon SX88+, Octagon SX88, Vu Zero, Vu+ Zero 4K, Mecool K1/K2/K3, Azamerica s2010, Azamerica s810B, Nazabox Xgame, Koqit K1 mini, TBS 5520se, TBS 5925, TBS 6922se, Openbox X5, Openbox S9, AZBOX TITAN twin, AZBOX Premium+, AZBOX Elite , Rasp Pi, Rasp Pi 2/3, Orange Pi PC, Coolsat 5000, Dm528s, DM800se, Satlink 6933, Satlink 6960, Satlink 6932, GT-Media V8, Gt-Media V8 Meter,  PixelView PlayTV USB SBTVD ISDB-T (dib0700), Mygica S270 ISDB-T (Siano Rio). Ku dish "Embrasat" 1,80m (61ºw), C-Band Motorized dish "Antenas Santa Rita - ASR" - 5,00m (20ºE - 116.8ºW), Ku-Band Motorized dish "Gigasat"- 1,80m (3ºw - 116,8ºW)


Re: Howto build unofficial pli for your unsupported receiver #2023 wu-li

  • Senior Member
  • 28 posts

0
Neutral

Posted 9 August 2018 - 13:00

SPARK 7111

 

 

 

AFTER CHANGES

 

DEBUG: SITE files ['endian-little', 'bit-32', 'sh-common', 'common-linux', 'common-glibc', 'sh4-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2 DRIVER_TOPDIR=/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source DESTDIR=/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/image SUBDIRS=libmme_host
ERROR: oe_runmake failed
Making all in libmme_host
make[1]: Entering directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
make[1]: *** No rule to make target '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c', needed by '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo'.  Stop.
make[1]: Leaving directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
Makefile:388: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
WARNING: /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/run.do_compile.944:1 exit 1 from 'exit 1'
ERROR: Function failed: do_compile (log file is located at /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/log.do_compile.944)

 

 

 

 

1 -------------------------------------------------------------------------------------------------------

.../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c ...

 

AND

 

   .../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo ...

MISSING FOLDER - multicom -

 

ONLY:

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mme / ...

 

AND

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mme / ...

2 ----------------------------------------------------------------------------------------------------------

/ mme / mme_linux_user.c  ...
/ mme / mme_linux_user.lo ...

MISSING:

... mme_linux_user.c ...
... mme_linux_user.lo ...



Re: Howto build unofficial pli for your unsupported receiver #2024 wu-li

  • Senior Member
  • 28 posts

0
Neutral

Posted 9 August 2018 - 13:53

 

SPARK 7111

 

 

 

AFTER CHANGES

 

DEBUG: SITE files ['endian-little', 'bit-32', 'sh-common', 'common-linux', 'common-glibc', 'sh4-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2 DRIVER_TOPDIR=/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source DESTDIR=/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/image SUBDIRS=libmme_host
ERROR: oe_runmake failed
Making all in libmme_host
make[1]: Entering directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
make[1]: *** No rule to make target '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c', needed by '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo'.  Stop.
make[1]: Leaving directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
Makefile:388: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
WARNING: /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/run.do_compile.944:1 exit 1 from 'exit 1'
ERROR: Function failed: do_compile (log file is located at /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/log.do_compile.944)

 

 

 

 

1 -------------------------------------------------------------------------------------------------------

.../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c ...

 

AND

 

   .../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo ...

MISSING FOLDER - multicom -

 

ONLY:

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mm / ...

 

AND

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mm / ...

2 ----------------------------------------------------------------------------------------------------------

/ mm / mme_linux_user.c  ...
/ mm / mme_linux_user.lo ...

MISSING:

... mme_linux_user.c ...
... mme_linux_user.lo ...

 



Re: Howto build unofficial pli for your unsupported receiver #2025 wu-li

  • Senior Member
  • 28 posts

0
Neutral

Posted 9 August 2018 - 14:01

 

SPARK 7111

 

 

 

AFTER CHANGES

 

DEBUG: SITE files ['endian-little', 'bit-32', 'sh-common', 'common-linux', 'common-glibc', 'sh4-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2 DRIVER_TOPDIR=/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source DESTDIR=/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/image SUBDIRS=libmme_host
ERROR: oe_runmake failed
Making all in libmme_host
make[1]: Entering directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
make[1]: *** No rule to make target '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c', needed by '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo'.  Stop.
make[1]: Leaving directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
Makefile:388: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
WARNING: /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/run.do_compile.944:1 exit 1 from 'exit 1'
ERROR: Function failed: do_compile (log file is located at /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/log.do_compile.944)

 

 

 

 

1 -------------------------------------------------------------------------------------------------------

.../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c ...

 

AND

 

   .../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo ...

MISSING FOLDER - multicom -

 

ONLY:

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mm / ...

 

AND

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mm / ...

2 ----------------------------------------------------------------------------------------------------------

/ mme / mme_linux_user.c  ...
/ mme / mme_linux_user.lo ...

MISSING:

... mme_linux_user.c ...
... mme_linux_user.lo ...

 

 

what should it be in?

... / kernel-source / ...



Re: Howto build unofficial pli for your unsupported receiver #2026 wu-li

  • Senior Member
  • 28 posts

0
Neutral

Posted 9 August 2018 - 14:10

 

 

SPARK 7111

 

 

 

AFTER CHANGES

 

DEBUG: SITE files ['endian-little', 'bit-32', 'sh-common', 'common-linux', 'common-glibc', 'sh4-linux', 'common']
DEBUG: Executing shell function do_compile
NOTE: make -j 2 DRIVER_TOPDIR=/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source DESTDIR=/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/image SUBDIRS=libmme_host
ERROR: oe_runmake failed
Making all in libmme_host
make[1]: Entering directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
make[1]: *** No rule to make target '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c', needed by '/home/wu/openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo'.  Stop.
make[1]: Leaving directory '/home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/git/tools/libmme_host'
Makefile:388: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
WARNING: /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/run.do_compile.944:1 exit 1 from 'exit 1'
ERROR: Function failed: do_compile (log file is located at /home/wu/openpli-oe-core/build/tmp/work/sh4-oe-linux/libmme-host/2.1+gitAUTOINC+cd23474d1b-r0/temp/log.do_compile.944)

 

 

 

 

1 -------------------------------------------------------------------------------------------------------

.../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.c ...

 

AND

 

   .../openpli-oe-core/build/tmp/work-shared/spark/kernel-source/multicom/mme/mme_linux_user.lo ...

MISSING FOLDER - multicom -

 

ONLY NOW:

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mm / ...

 

AND

 

... / openpli-oe-core / build / tmp / work-shared / spark / kernel-source / mm / ...

2 ----------------------------------------------------------------------------------------------------------

/ mme / mme_linux_user.c  ...
/ mme / mme_linux_user.lo ...

MISSING:

... mme_linux_user.c ...
... mme_linux_user.lo ...

 

 

what should it be in?

... / kernel-source / ...

 



Re: Howto build unofficial pli for your unsupported receiver #2027 rantanplan

  • PLi® Contributor
  • 1,863 posts

+87
Good

Posted 9 August 2018 - 14:13

Wait a bit and stay cool.
You have already deleted the build folder?



Re: Howto build unofficial pli for your unsupported receiver #2028 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 9 August 2018 - 15:49

New test images are ready ;)

 

k1pro: http://www.mediafire...1pro_sdcard.zip

 

k2pro: http://www.mediafire...2pro_sdcard.zip

 

k2prov2: http://www.mediafire...rov2_sdcard.zip

 

k3pro: http://www.mediafire...3pro_sdcard.zip

 

k1plus: http://www.mediafire...plus_sdcard.zip

 

Special thanks to moham96 for all his hard work.


Open Vision sources: https://github.com/OpenVisionE2


Re: Howto build unofficial pli for your unsupported receiver #2029 ledtou

  • Member
  • 18 posts

0
Neutral

Posted 9 August 2018 - 16:28

New test images are ready ;)

 

k1pro: http://www.mediafire...1pro_sdcard.zip

 

k2pro: http://www.mediafire...2pro_sdcard.zip

 

k2prov2: http://www.mediafire...rov2_sdcard.zip

 

k3pro: http://www.mediafire...3pro_sdcard.zip

 

k1plus: http://www.mediafire...plus_sdcard.zip

 

Special thanks to moham96 for all his hard work.

 

Thank you  Persian Prince and moham96 for all his hard work.

how to burn image to sdcard.



Re: Howto build unofficial pli for your unsupported receiver #2030 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 9 August 2018 - 16:31

I think there might be some differences between S905 and S905D regarding dvb handling

can someone with a S905D device test the images and see if they see any picture from dvb ?


Edited by moham96, 9 August 2018 - 16:32.


Re: Howto build unofficial pli for your unsupported receiver #2031 engineerkhan15

  • Senior Member
  • 145 posts

+18
Neutral

Posted 9 August 2018 - 16:38

how to burn image to sdcard.

 

Win32DiskImager works good for me



Re: Howto build unofficial pli for your unsupported receiver #2032 frankviana

  • Senior Member
  • 474 posts

+4
Neutral

Posted 9 August 2018 - 16:56

I think there might be some differences between S905 and S905D regarding dvb handling
can someone with a S905D device test the images and see if they see any picture from dvb ?


I'm working now, but tonight, -3 GMT, I'll test with my K2 pro (V1) and k1 pro

Vu+ Ultimo 4k, GTX Combo, GT Combo, Dreambox Two, GT-Media V8XS, GT-Media M7x, GT-Media v9 prime, Gt-Media Finder Meter 2, , TBS 6903-x v2, Octagon SF8008 single, Edision OS Mini 4k, Zgemma h9s SE, GT-Media V8UHD, Raspberry Pi 4, T95 Max + (CoreElec/Tvheadend), Freesky Triplo X, Zgemma h9 twin, Zgemma h9s, Amiko SHD 8900, Gt-Media GTC, Octagon SX88+, Octagon SX88, Vu Zero, Vu+ Zero 4K, Mecool K1/K2/K3, Azamerica s2010, Azamerica s810B, Nazabox Xgame, Koqit K1 mini, TBS 5520se, TBS 5925, TBS 6922se, Openbox X5, Openbox S9, AZBOX TITAN twin, AZBOX Premium+, AZBOX Elite , Rasp Pi, Rasp Pi 2/3, Orange Pi PC, Coolsat 5000, Dm528s, DM800se, Satlink 6933, Satlink 6960, Satlink 6932, GT-Media V8, Gt-Media V8 Meter,  PixelView PlayTV USB SBTVD ISDB-T (dib0700), Mygica S270 ISDB-T (Siano Rio). Ku dish "Embrasat" 1,80m (61ºw), C-Band Motorized dish "Antenas Santa Rita - ASR" - 5,00m (20ºE - 116.8ºW), Ku-Band Motorized dish "Gigasat"- 1,80m (3ºw - 116,8ºW)


Re: Howto build unofficial pli for your unsupported receiver #2033 engineerkhan15

  • Senior Member
  • 145 posts

+18
Neutral

Posted 9 August 2018 - 16:58

I think there might be some differences between S905 and S905D regarding dvb handling

can someone with a S905D device test the images and see if they see any picture from dvb ?

I tested two images on my k1 pro, uploaded by ftp21_ and Persian Prince respectively.

ftp21_:

There were 4 tuner types visible in tuner setup, i.e, DVB-S, DVB-T, DVB-C & ATSC.

I tried DVB-S scan and it tuned and saved channels on some frequencies (not all).

No video or audio on any channel.

Signal level was visible on infobar all saved channels.

Persian Prince:

There were 2 tuner types visible in tuner setup, i.e, DVB-S & DVB-T only.

I tried DVB-S scan and it did not tune or saved any channel (as had been in earlier versions of test images).



Re: Howto build unofficial pli for your unsupported receiver #2034 engineerkhan15

  • Senior Member
  • 145 posts

+18
Neutral

Posted 9 August 2018 - 17:33

I tried to build image for K1 Pro but got following error:

engineerkhan15@EK15:~/openpli-oe-core$ MACHINE=k1pro make image
Building image for k1pro
NOTE: Your conf/bblayers.conf has been automatically updated.
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: /home/engineerkhan15/openpli-oe-core/meta-vuplus/recipes-bsp/drivers/vuplus-shutdown.bb: Unable to get checksum for vuplus-shutdown SRC_URI entry turnoff_power: file could not be foundA:  0:00:10
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:03:33
Parsing of 3105 .bb files complete (0 cached, 3105 parsed). 3916 targets, 690 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.34.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "ubuntu-16.04"
TARGET_SYS        = "aarch64-oe-linux"
MACHINE           = "k1pro"
DISTRO            = "openpli"
DISTRO_VERSION    = "pli-extras"
TUNE_FEATURES     = "aarch64"
TARGET_FPU        = ""
meta-oe           
meta-filesystems  
meta-multimedia   
meta-networking   
meta-python       
meta-webserver    = "HEAD:dfbdd28d206a74bf264c2f7ee0f7b3e5af587796"
meta              = "HEAD:93dd2f9f3edf0584f9e806c629611d645dd72dbf"
meta-openpli      = "develop:bdb59338208463dcacdc6e23dee5dec0b963997c"
meta-vuplus       = "HEAD:d6f0477dc48bad742290f588efd4d9da604cfb29"
meta-xsarius.pli5 = "HEAD:306a17cf01ab85df09d7cfbf2bda2e8d21d50e1d"
meta-qviart       = "HEAD:8da348c2596ec2d5d1d67fe0bfd115671f5e4a9c"
meta-xp           = "HEAD:2f818d2ee1efbf0a4536d8384d716a0767cf7039"
meta-xtrend       = "HEAD:ac054abbe235f33f6a69e7a8ff0fa9a7efa84f59"
meta-formuler     = "HEAD:e1d33c48edb119dcc3163855b0b1af510912ef52"
meta-gfutures     = "HEAD:4015ce2bb7c46cd10574eff3100f67fb74c38bda"
meta-xpeedc       = "HEAD:f12908a5573de8a6a06ad9f75081846a590511c4"
meta-zgemma       = "HEAD:9c0ae72060437fb6951f82e64f1e0e882cf00f95"
meta-edision      = "HEAD:7af176f81a7aca30200d6958229d56c973cee393"
meta-miraclebox   = "HEAD:d44871d4d1f357d5b38488ed505b48fa8c8feff3"
meta-spycat       = "HEAD:a19f11bbcdcad969e9f6f8d2c30df0653427d4cb"
meta-gi           = "HEAD:01fd1e8256f53d40371e65514e13a53ef53e400d"
meta-sab          = "HEAD:92262feb14e4005c8096150daac7313e9cb3d85a"
meta-gigablue     = "HEAD:7e437da8e19274143229f2c52e62917cb33d9d1c"
meta-amiko        = "HEAD:eb5c966a3ba38388abdcda61ed07fb056e4d488b"
meta-axasuhd      = "HEAD:dfc1465665f504fdc4d6fc9a401e630b04123211"
meta-local        = "develop:bdb59338208463dcacdc6e23dee5dec0b963997c"
meta-qt5          = "HEAD:c6aa602d0640040b470ee81de39726276ddc0ea3"
meta-amlogic      = "HEAD:404098d3abea8e5fe8449d687b31b2875a012559"
meta-ax           = "HEAD:1d852b4eca365ed4560643cb2e3cba09a78a3d49"
meta-azbox        = "HEAD:df30c02b07f55c3b89e7b5808eb7aa126613423f"
meta-blackbox     = "HEAD:1ac8f7ff34539dba46212e195ca1425bf093466d"
meta-ceryon       = "HEAD:2f5d5982b1cce64600bb243790cff32d9e2ab57e"
meta-cube         = "HEAD:a391b50516232375048ecfcd8f9721e495d644c5"
meta-dags         = "HEAD:7e9c816792c81f01efc93b48367c8467f316b1f8"
meta-dinobot      = "HEAD:9d18839d0d742f1b248a0d10d15baea8325ff3b5"
meta-dream        = "HEAD:fac8ffb2c49d5e3fe5f2658f821d77ef10ffb31a"
meta-ebox         = "HEAD:7a4224974eb65e38ab4282831b7f37a0bd62ca3c"
meta-entwopia     = "HEAD:ea01aaff38031cc004c22ea4f57a5cbb0eadf311"
meta-fulan        = "HEAD:cbc013e6b1c23c2d29bc68b7db8e232ff2a0ddf4"
meta-ini          = "HEAD:0fb405af5fc10ff23303d165012bddf66abed5c4"
meta-ixuss        = "HEAD:a5b6ab5c51a7e26c1d70fc6858304d73d3720432"
meta-octagon      = "HEAD:e9afb14d9cc978df98efcb04993c5900e1e88748"
meta-odin         = "HEAD:8e974d345b73a2067bf6ce22e753d8868796ab1c"
meta-protek       = "HEAD:65922f91045c2f62dd93e92fe38d1f32382c3401"
meta-raspberrypi  = "HEAD:3bbce841ef3bae1718e9e8b289fa42ec04288c0f"
meta-tiviar       = "HEAD:730f89b8bded4089a24e70a9992082c2811cb0d4"
meta-tripledot    = "HEAD:301f4a086d9e365362bc71715d2bf6d953927568"
meta-xcore        = "HEAD:3ed7062f5a476798a0bcbc6f3a472c26b5e44762"
pli-extras        = "develop:625f5309fa39ee1909cb8c6771ea79753256b542"

Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:13
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: openpli-bootlogo-1.0-r0 do_package_qa: QA Issue: openpli-bootlogo rdepends on showiframe, but it isn't a build dependency? [build-deps]
ERROR: linkdroid-initramfs-1.0-r0 do_rootfs: Error executing a python function in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
     0001:
 *** 0002:license_create_manifest(d)
     0003:
File: '/home/engineerkhan15/openpli-oe-core/openembedded-core/meta/classes/license.bbclass', lineno: 48, function: license_create_manifest
     0044:    pkg_dic = {}
     0045:    for pkg in sorted(image_list_installed_packages(d)):
     0046:        pkg_info = os.path.join(d.getVar('PKGDATA_DIR'),
     0047:                                'runtime-reverse', pkg)
 *** 0048:        pkg_name = os.path.basename(os.readlink(pkg_info))
     0049:
     0050:        pkg_dic[pkg_name] = oe.packagedata.read_pkgdatafile(pkg_info)
     0051:        if not "LICENSE" in pkg_dic[pkg_name].keys():
     0052:            pkg_lic_name = "LICENSE_" + pkg_name
Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/engineerkhan15/openpli-oe-core/build/tmp/pkgdata/k1pro/runtime-reverse/base-passwd'

ERROR: linkdroid-initramfs-1.0-r0 do_rootfs: Function failed: license_create_manifest
ERROR: Logfile of failure stored in: /home/engineerkhan15/openpli-oe-core/build/tmp/work/k1pro-oe-linux/linkdroid-initramfs/1.0-r0/temp/log.do_rootfs.24954
ERROR: Task (/home/engineerkhan15/openpli-oe-core/pli-extras/meta-amlogic/recipes-bsp/extra/linkdroid-initramfs.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5893 tasks of which 5734 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/engineerkhan15/openpli-oe-core/pli-extras/meta-amlogic/recipes-bsp/extra/linkdroid-initramfs.bb:do_rootfs
Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Makefile:125: recipe for target 'image' failed
make: *** [image] Error 1


Re: Howto build unofficial pli for your unsupported receiver #2035 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 9 August 2018 - 17:56

 

I think there might be some differences between S905 and S905D regarding dvb handling

can someone with a S905D device test the images and see if they see any picture from dvb ?

I tested two images on my k1 pro, uploaded by ftp21_ and Persian Prince respectively.

ftp21_:

There were 4 tuner types visible in tuner setup, i.e, DVB-S, DVB-T, DVB-C & ATSC.

I tried DVB-S scan and it tuned and saved channels on some frequencies (not all).

No video or audio on any channel.

Signal level was visible on infobar all saved channels.

Persian Prince:

There were 2 tuner types visible in tuner setup, i.e, DVB-S & DVB-T only.

I tried DVB-S scan and it did not tune or saved any channel (as had been in earlier versions of test images).

 

Why persian prince's images don't work !! @persian any Idea ?

 

you should see four types, if you see only two then probably the dvb drivers are not loaded and enigma is reading the hardcoded nim_sockets

try to ssh into the device and run

lsmod

also boot into the working image(ftp21_)  and run this

echo "dmx0" > /sys/class/stb/source

and then tune into a channel and see if this changes anything



Re: Howto build unofficial pli for your unsupported receiver #2036 sauna

  • Senior Member
  • 38 posts

0
Neutral

Posted 9 August 2018 - 19:17

k1 plus dark screen.telnet has a connection.

 
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.08.09 21:12:02 =~=~=~=~=~=~=~=~=~=~=~=
 openpli pli-extras k1plus
 
k1plus login: root
Last login: Thu Jan  1 01:03:40 CET 2015 on pts/0
root@k1plus:~# [6nlsmod
Module                  Size  Used by
mali                  241540  0
e2_procfs              23151  0
r848a                  34309  1
avl6862               253365  1
aml_fe                  5178  0
aml                    91002  1 aml_fe
root@k1plus:~# [6n


Re: Howto build unofficial pli for your unsupported receiver #2037 starz

  • Senior Member
  • 59 posts

+1
Neutral

Posted 9 August 2018 - 19:26

Thanks a lot moham96 and Persian Prince for all your hard working and hard efforts.

I did  some tests with Persian Prince's test image and mine own build test image on k1plus.same results for both.

 

-strange booting.(mostly not booting.when I restart booted image it doesn't boot again and no signal on tv screen.then when I change hdmi inputs from tv remote, there are two chances,first is booting and second is blank screen.but mostly is blank screen)

-when it boots.yes There are 4 tuner types visible in tuner setup DVB-S, DVB-T, DVB-C & ATSC.

-search and finding channels is ok not all of them but ok:) .no picture and sound.

-no working remote for k1 plus.

 

and can you add this remote.conf to gith-source to work k1plus remote.

#amlogic NEC remote
factory_code	= 0xff000001   #video striong
work_mode  		= 0
repeat_enable = 1
repeat_delay = 80
repeat_peroid = 39
release_delay	=	121
debug_enable 	= 1

fn_key_scancode    = 0x99
left_key_scancode  = 0x5a
right_key_scancode = 0x1b
up_key_scancode    = 0x06
down_key_scancode  = 0x16
ok_key_scancode    = 0x1a
pageup_key_scancode = 0x55
pagedown_key_scancode = 0x15

key_begin

0x59 116    #    POWER
0x19 113    #    MUTE
0x42 398    #    RED
0x40 399    #    GREEN
0x00 400    #    YELLOW
0x03 401    #    BLUE
0x4a 168    #    <<		||	KEY_REWIND
0x48 208    #    >>		||	KEY_FASTFORWARD
0x08 165    #    |<<	||	KEY_PREVIOUSSONG
0x0b 163    #    >>|	||	KEY_NEXTSONG
0x46 164    #    >||	||	KEY_PLAYPAUSE
0x44 128    #    STOP	||	KEY_STOP
0x1f 364    #    FAV	||	KEY_FAVORITES was KEY_RECORD
0x04 366    #    PVR
0x4d 365    #    EPG
0x02 358    #    INFO
0x09 370    #    SUBT
0x01 392    #    AUDIO
#0x0d 385   #    HOME	||	KEY_RADIO
#0x0d 139   #    HOME	||	KEY_MENU
0x0d 102    #    HOME	||	KEY_HOME
0x11 377    #    DTV	||	KEY_TV
0x06 103    #    UP
0x16 108    #    DOWN
0x5a 105    #    LEFT
0x1b 106    #    RIGHT
0x1a 28     #    ENTER bio OK
0x45 139    #    MENU
0x05 174    #    EXIT
0x13 115    #    VOLUME +
0x17 114    #    VOLUME -
0x58 388    #    APPS	||	KEY_TEXT
0x12 150    #    MOUSE	||	KEY_WWW
0x55 402    #    PAGEUP	||	KEY_CHANNELUP
0x15 403    #    PAGEDOWN	||	KEY_CHANNELDOWN
0x52 2      #    1
0x50 3    	#    2
0x10 4    	#    3
0x56 5    	#    4
0x54 6    	#    5
0x14 7    	#    6
0x4e 8    	#    7
0x4c 9    	#    8
0x0c 10     #    9
0x0f 11     #    0
0x18 412    #    BROWSER	||	KEY_PREVIOUS
0x51 407    #    DEL	||	KEY_NEXT

key_end

Regards



Re: Howto build unofficial pli for your unsupported receiver #2038 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 9 August 2018 - 20:10

Thanks a lot moham96 and Persian Prince for all your hard working and hard efforts.

I did  some tests with Persian Prince's test image and mine own build test image on k1plus.same results for both.

 

-strange booting.(mostly not booting.when I restart booted image it doesn't boot again and no signal on tv screen.then when I change hdmi inputs from tv remote, there are two chances,first is booting and second is blank screen.but mostly is blank screen)

-when it boots.yes There are 4 tuner types visible in tuner setup DVB-S, DVB-T, DVB-C & ATSC.

-search and finding channels is ok not all of them but ok:) .no picture and sound.

-no working remote for k1 plus.

 

and can you add this remote.conf to gith-source to work k1plus remote.

#amlogic NEC remote
factory_code	= 0xff000001   #video striong
work_mode  		= 0
repeat_enable = 1
repeat_delay = 80
repeat_peroid = 39
release_delay	=	121
debug_enable 	= 1

fn_key_scancode    = 0x99
left_key_scancode  = 0x5a
right_key_scancode = 0x1b
up_key_scancode    = 0x06
down_key_scancode  = 0x16
ok_key_scancode    = 0x1a
pageup_key_scancode = 0x55
pagedown_key_scancode = 0x15

key_begin

0x59 116    #    POWER
0x19 113    #    MUTE
0x42 398    #    RED
0x40 399    #    GREEN
0x00 400    #    YELLOW
0x03 401    #    BLUE
0x4a 168    #    <<		||	KEY_REWIND
0x48 208    #    >>		||	KEY_FASTFORWARD
0x08 165    #    |<<	||	KEY_PREVIOUSSONG
0x0b 163    #    >>|	||	KEY_NEXTSONG
0x46 164    #    >||	||	KEY_PLAYPAUSE
0x44 128    #    STOP	||	KEY_STOP
0x1f 364    #    FAV	||	KEY_FAVORITES was KEY_RECORD
0x04 366    #    PVR
0x4d 365    #    EPG
0x02 358    #    INFO
0x09 370    #    SUBT
0x01 392    #    AUDIO
#0x0d 385   #    HOME	||	KEY_RADIO
#0x0d 139   #    HOME	||	KEY_MENU
0x0d 102    #    HOME	||	KEY_HOME
0x11 377    #    DTV	||	KEY_TV
0x06 103    #    UP
0x16 108    #    DOWN
0x5a 105    #    LEFT
0x1b 106    #    RIGHT
0x1a 28     #    ENTER bio OK
0x45 139    #    MENU
0x05 174    #    EXIT
0x13 115    #    VOLUME +
0x17 114    #    VOLUME -
0x58 388    #    APPS	||	KEY_TEXT
0x12 150    #    MOUSE	||	KEY_WWW
0x55 402    #    PAGEUP	||	KEY_CHANNELUP
0x15 403    #    PAGEDOWN	||	KEY_CHANNELDOWN
0x52 2      #    1
0x50 3    	#    2
0x10 4    	#    3
0x56 5    	#    4
0x54 6    	#    5
0x14 7    	#    6
0x4e 8    	#    7
0x4c 9    	#    8
0x0c 10     #    9
0x0f 11     #    0
0x18 412    #    BROWSER	||	KEY_PREVIOUS
0x51 407    #    DEL	||	KEY_NEXT

key_end

Regards

Can you give the output of

blkid

The booting issue might be related to the faulty amlogic emmc drivers, If you have Uart cable that would be useful also

 

Regards



Re: Howto build unofficial pli for your unsupported receiver #2039 starz

  • Senior Member
  • 59 posts

+1
Neutral

Posted 9 August 2018 - 20:34

Regards

Can you give the output of

blkid

The booting issue might be related to the faulty amlogic emmc drivers, If you have Uart cable that would be useful also

 

Regards

 

Sorry but I don'T have Uart cable.

 

This is the output of

blkid

grab

 

k1plus login: root
root@k1plus:~# blkid
/dev/mmcblk0p2: LABEL="ROOTFS" UUID="1dc052af-fc5c-4690-9ce3-00ae3920916b" TYPE="ext4"
/dev/mmcblk0p1: LABEL="BOOT" UUID="D18D-D209" TYPE="vfat"
root@k1plus:~# grab
Framebuffer failed
Grabbing Video ...
Resizing Video to 127 x -1627645944 ...
Segmentation fault



Re: Howto build unofficial pli for your unsupported receiver #2040 moham96

  • Senior Member
  • 175 posts

+20
Neutral

Posted 9 August 2018 - 21:05

amlogic gstreamer plugins are getting blacklisted, why ? I have no Idea:

root@k2pro:~# gst-inspect-1.0 -b
Blacklisted files:
  libgstamlvsink.so
  libgstamladec.so
  libgstamlvdec.so
  libgstamlasink.so



3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users