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 #1761 zeros

  • PLi® Contributor
  • 1,635 posts

+61
Good

Posted 19 July 2018 - 19:09

It is the same DVB-T2/T/C tuner, which I tried on 2016 november! It works with dmm original image and you can try also openatv.

Edited by zeros, 19 July 2018 - 19:12.

DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB

Vertex 4K60 4:4:4 600MHz


Re: Howto build unofficial pli for your unsupported receiver #1762 blinkosm

  • Senior Member
  • 144 posts

+1
Neutral

Posted 19 July 2018 - 19:32

To MasterG and Persian Prince :

 

 

after the interruption of image build yesterday i try to build a image today  so make the command MACHINE =dm800.... and after awhile i find that the compilation continues after i leave it 10% yesterday the compitation begins in 10% today  ... i wonder is that ok???  or i must build a image without interruption 



Re: Howto build unofficial pli for your unsupported receiver #1763 bumperbee

  • Senior Member
  • 284 posts

+10
Neutral

Posted 19 July 2018 - 21:00

I think so. I got no choice as our Tv transmission provider is changing from cable to T2 transmission very soon. I am doing a lot of daily timer recordings and the feature in “Timer setting” of “Changing name & description when event changes” is very important to me. There isn’t this feature in dmm original image and openatv.



Re: Howto build unofficial pli for your unsupported receiver #1764 PhilipZ

  • Member
  • 6 posts

0
Neutral

Posted 20 July 2018 - 14:19

Multi channel downmix on NASA TV UHD works, about AC3+ audio - I have no idea how to fix this.

Yes, I know that downmix is working, but prefer to use multichannel sound. Please, let me know if you find solution.
DM920UHD DVB-S2X TRIPLE tuner

Re: Howto build unofficial pli for your unsupported receiver #1765 bumperbee

  • Senior Member
  • 284 posts

+10
Neutral

Posted 21 July 2018 - 00:35

You can make it work with PLi too if you know the chip model and related driver ;)
Give me some information about it.

Hi Master Persian Prince,is the infor ok? Anything else you need, please do let me know.
Thanks very much

Re: Howto build unofficial pli for your unsupported receiver #1766 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 21 July 2018 - 16:03

In that case I can't test it on my box through Uart since I have a k2pro with the s905 soc which the linkdroid kernel doesn't boot on

 

 

 

With you corelec bb i'm able to boot on k1pro. I replace DTS and i replace AM905 with AM905D.

[    8.759237@0] DVB FE: Init AVL6862 frontend 0
[    9.593927@0] i2c i2c-2: avl6862: found AVL6862 family_id=0x68624955
[    9.594655@0] i2c i2c-2: Load avl6862 firmware patch for DVB-S/S2 size=44000
[    9.686710@3] random: nonblocking pool is initialized
[   11.412247@2] i2c i2c-2: avl6862 patch ver 2.0 build 20621
[   11.541542@2] i2c i2c-2: r848a: Rafael R848 successfully attached!
[   11.542085@2] DVB FE: AVL6862 and R848 attached!
[   11.546667@2] amlogic-dvb dvb.49: DVB: registering adapter 0 frontend 0 (Availink avl6862)...
[   11.555830@1] DVB FE: Frontend AVL6862 registred!

No nim_sockets but is a good news



Re: Howto build unofficial pli for your unsupported receiver #1767 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 21 July 2018 - 23:20

 

In that case I can't test it on my box through Uart since I have a k2pro with the s905 soc which the linkdroid kernel doesn't boot on

 

 

 

With you corelec bb i'm able to boot on k1pro. I replace DTS and i replace AM905 with AM905D.

[    8.759237@0] DVB FE: Init AVL6862 frontend 0
[    9.593927@0] i2c i2c-2: avl6862: found AVL6862 family_id=0x68624955
[    9.594655@0] i2c i2c-2: Load avl6862 firmware patch for DVB-S/S2 size=44000
[    9.686710@3] random: nonblocking pool is initialized
[   11.412247@2] i2c i2c-2: avl6862 patch ver 2.0 build 20621
[   11.541542@2] i2c i2c-2: r848a: Rafael R848 successfully attached!
[   11.542085@2] DVB FE: AVL6862 and R848 attached!
[   11.546667@2] amlogic-dvb dvb.49: DVB: registering adapter 0 frontend 0 (Availink avl6862)...
[   11.555830@1] DVB FE: Frontend AVL6862 registred!

No nim_sockets but is a good news

 

 

I try to send an email to afl1 because into Tvheadend thread he say "I rebuilt avl6862 driver with 3 frontend and now it works!".

 

AVL6862 expose 1 frontend but with i2c connected demux for dvbt/s/c Enigma2 can support multistream tuner?



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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 22 July 2018 - 06:24

 

In that case I can't test it on my box through Uart since I have a k2pro with the s905 soc which the linkdroid kernel doesn't boot on

 

 

 

With you corelec bb i'm able to boot on k1pro. I replace DTS and i replace AM905 with AM905D.

[    8.759237@0] DVB FE: Init AVL6862 frontend 0
[    9.593927@0] i2c i2c-2: avl6862: found AVL6862 family_id=0x68624955
[    9.594655@0] i2c i2c-2: Load avl6862 firmware patch for DVB-S/S2 size=44000
[    9.686710@3] random: nonblocking pool is initialized
[   11.412247@2] i2c i2c-2: avl6862 patch ver 2.0 build 20621
[   11.541542@2] i2c i2c-2: r848a: Rafael R848 successfully attached!
[   11.542085@2] DVB FE: AVL6862 and R848 attached!
[   11.546667@2] amlogic-dvb dvb.49: DVB: registering adapter 0 frontend 0 (Availink avl6862)...
[   11.555830@1] DVB FE: Frontend AVL6862 registred!

No nim_sockets but is a good news

 

I've pushed changes to the main repo and persianprince merged them https://github.com/P...e429a3e801a1658

update your build environment (don't use my repo, use the original pli-metas/meta-amlogic) and build again with MACHINE=k2_pros905

I've added the e2procfs and nim sockets should show now.

please test and tell me if it works fine for the s905d, so I can add a config file for you s905d machine

 


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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 22 July 2018 - 06:36

 

 

In that case I can't test it on my box through Uart since I have a k2pro with the s905 soc which the linkdroid kernel doesn't boot on

 

 

 

With you corelec bb i'm able to boot on k1pro. I replace DTS and i replace AM905 with AM905D.

[    8.759237@0] DVB FE: Init AVL6862 frontend 0
[    9.593927@0] i2c i2c-2: avl6862: found AVL6862 family_id=0x68624955
[    9.594655@0] i2c i2c-2: Load avl6862 firmware patch for DVB-S/S2 size=44000
[    9.686710@3] random: nonblocking pool is initialized
[   11.412247@2] i2c i2c-2: avl6862 patch ver 2.0 build 20621
[   11.541542@2] i2c i2c-2: r848a: Rafael R848 successfully attached!
[   11.542085@2] DVB FE: AVL6862 and R848 attached!
[   11.546667@2] amlogic-dvb dvb.49: DVB: registering adapter 0 frontend 0 (Availink avl6862)...
[   11.555830@1] DVB FE: Frontend AVL6862 registred!

No nim_sockets but is a good news

 

 

I try to send an email to afl1 because into Tvheadend thread he say "I rebuilt avl6862 driver with 3 frontend and now it works!".

 

AVL6862 expose 1 frontend but with i2c connected demux for dvbt/s/c Enigma2 can support multistream tuner?

 

Yes please do, enigma2 will never happen on these device without dvb drivers and kernel changes.

I had to disable the nim_sockets detection function in the e2procfs module and hardcode a single nimsocket with DVB-T because If I tell enigma that this frontend is multistandard (DVB-T and DVB-S) It doesn't work and errors out, so I had to choose one standard and I put DVB-T because this is what most tools detect.

https://github.com/m...s_bus.c#L31-L39

If afl1 can join us here we can change this and have either a nim socket with multistandard or two nim_sockets(DVB-T and DVB-S one)

 

Thanks

 


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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 22 July 2018 - 06:37

Also does anyone here have a wetek play2 and have loaded a working image of anytype(openatv, openpli ...etc) ? I need kernel with working e2procfs on the wetek play for some tests.

 

Thanks



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

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 22 July 2018 - 06:37

@moham96

 

Please check your pm (here) and your github also your email :)


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


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

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 22 July 2018 - 06:39

Also does anyone here have a wetek play2 and have loaded a working image of anytype(openatv, openpli ...etc) ? I need kernel with working e2procfs on the wetek play for some tests.

 

Thanks

 

PLi-metas is ok for wetekplay2 (tested before):

 

https://github.com/P...tek2_3.14.29.bb

 

https://github.com/P...s-wetekplay2.bb


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


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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 22 July 2018 - 06:55

 

Also does anyone here have a wetek play2 and have loaded a working image of anytype(openatv, openpli ...etc) ? I need kernel with working e2procfs on the wetek play for some tests.

 

Thanks

 

PLi-metas is ok for wetekplay2 (tested before):

 

https://github.com/P...tek2_3.14.29.bb

 

https://github.com/P...s-wetekplay2.bb

 

Yes but I need someone with the device to boot the image, anyway I'll try to boot a wetek image on my k2pro by editing the dtb but I think the e2procfs might not work.

Thanks



Re: Howto build unofficial pli for your unsupported receiver #1774 johnny64

  • Member
  • 5 posts

0
Neutral

Posted 22 July 2018 - 07:51

Give the picture wp2!



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

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 22 July 2018 - 08:45

wetekplay2 test image: http://www.mediafire...sdcard.zip/file


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


Re: Howto build unofficial pli for your unsupported receiver #1776 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 22 July 2018 - 09:43

 

 

 

In that case I can't test it on my box through Uart since I have a k2pro with the s905 soc which the linkdroid kernel doesn't boot on

 

 

 

With you corelec bb i'm able to boot on k1pro. I replace DTS and i replace AM905 with AM905D.

[    8.759237@0] DVB FE: Init AVL6862 frontend 0
[    9.593927@0] i2c i2c-2: avl6862: found AVL6862 family_id=0x68624955
[    9.594655@0] i2c i2c-2: Load avl6862 firmware patch for DVB-S/S2 size=44000
[    9.686710@3] random: nonblocking pool is initialized
[   11.412247@2] i2c i2c-2: avl6862 patch ver 2.0 build 20621
[   11.541542@2] i2c i2c-2: r848a: Rafael R848 successfully attached!
[   11.542085@2] DVB FE: AVL6862 and R848 attached!
[   11.546667@2] amlogic-dvb dvb.49: DVB: registering adapter 0 frontend 0 (Availink avl6862)...
[   11.555830@1] DVB FE: Frontend AVL6862 registred!

No nim_sockets but is a good news

 

 

I try to send an email to afl1 because into Tvheadend thread he say "I rebuilt avl6862 driver with 3 frontend and now it works!".

 

AVL6862 expose 1 frontend but with i2c connected demux for dvbt/s/c Enigma2 can support multistream tuner?

 

Yes please do, enigma2 will never happen on these device without dvb drivers and kernel changes.

I had to disable the nim_sockets detection function in the e2procfs module and hardcode a single nimsocket with DVB-T because If I tell enigma that this frontend is multistandard (DVB-T and DVB-S) It doesn't work and errors out, so I had to choose one standard and I put DVB-T because this is what most tools detect.

https://github.com/m...s_bus.c#L31-L39

If afl1 can join us here we can change this and have either a nim socket with multistandard or two nim_sockets(DVB-T and DVB-S one)

 

Thanks

 

 

 

I find this thread:

https://forums.openp...2mn88473/page-5

 

Osmini have Enigma and AVL tuner.

 

nim_socket is this:

root@osminiplus:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-T2
        Name: FTM-4862 (Availink AVL6862)
        Frontend_Device: 0
        I2C_Device: 2
        Has_Outputs: yes
        Mode 0: DVB-S
        Mode 1: DVB-T
        Mode 2: DVB-C
        Internally_Connectable: 0



Re: Howto build unofficial pli for your unsupported receiver #1777 algdu83

  • Senior Member
  • 36 posts

+1
Neutral

Posted 22 July 2018 - 12:23


 

 

 

I find this thread:

https://forums.openp...2mn88473/page-5

 

Osmini have Enigma and AVL tuner.

 

nim_socket is this:

root@osminiplus:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-T2
        Name: FTM-4862 (Availink AVL6862)
        Frontend_Device: 0
        I2C_Device: 2
        Has_Outputs: yes
        Mode 0: DVB-S
        Mode 1: DVB-T
        Mode 2: DVB-C
        Internally_Connectable: 0

Read this

https://github.com/a.../enigma drivers

ftm4862.ko : AVL6862 Official driver from Edison os mini plus compatible enigma dvb-t includ

edision osmini plus

osminiplus-drivers-4.9.0-20170105.zip

use a same driver



Re: Howto build unofficial pli for your unsupported receiver #1778 blinkosm

  • Senior Member
  • 144 posts

+1
Neutral

Posted 22 July 2018 - 15:32

to  the masters every time i try to build an image for dm800 i get this error :

 

NOTE: Your conf/bblayers.conf has been automatically updated.
NOTE: Your conf/bblayers.conf has been automatically updated.
NOTE: /home/blinkosm/openpli-oe-core/pli-extras/meta-fulan/recipes-core/glibc/glibc_2.23.bb: glibc doesn't build cleanly with -Os, adding -Wno-error to SELECTED_OPTIMIZATION
NOTE: /home/blinkosm/openpli-oe-core/pli-extras/meta-fulan/recipes-core/glibc/glibc-initial_2.23.bb: glibc-initial doesn't build cleanly with -Os, adding -Wno-error to SELECTED_OPTIMIZATION
 

i'm in ubuntu 16.04 and 18.04  and i build the environment but same error



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

  • Senior Member
  • 175 posts

+20
Neutral

Posted 22 July 2018 - 16:38

 

 

 

 

In that case I can't test it on my box through Uart since I have a k2pro with the s905 soc which the linkdroid kernel doesn't boot on

 

 

 

With you corelec bb i'm able to boot on k1pro. I replace DTS and i replace AM905 with AM905D.

[    8.759237@0] DVB FE: Init AVL6862 frontend 0
[    9.593927@0] i2c i2c-2: avl6862: found AVL6862 family_id=0x68624955
[    9.594655@0] i2c i2c-2: Load avl6862 firmware patch for DVB-S/S2 size=44000
[    9.686710@3] random: nonblocking pool is initialized
[   11.412247@2] i2c i2c-2: avl6862 patch ver 2.0 build 20621
[   11.541542@2] i2c i2c-2: r848a: Rafael R848 successfully attached!
[   11.542085@2] DVB FE: AVL6862 and R848 attached!
[   11.546667@2] amlogic-dvb dvb.49: DVB: registering adapter 0 frontend 0 (Availink avl6862)...
[   11.555830@1] DVB FE: Frontend AVL6862 registred!

No nim_sockets but is a good news

 

 

I try to send an email to afl1 because into Tvheadend thread he say "I rebuilt avl6862 driver with 3 frontend and now it works!".

 

AVL6862 expose 1 frontend but with i2c connected demux for dvbt/s/c Enigma2 can support multistream tuner?

 

Yes please do, enigma2 will never happen on these device without dvb drivers and kernel changes.

I had to disable the nim_sockets detection function in the e2procfs module and hardcode a single nimsocket with DVB-T because If I tell enigma that this frontend is multistandard (DVB-T and DVB-S) It doesn't work and errors out, so I had to choose one standard and I put DVB-T because this is what most tools detect.

https://github.com/m...s_bus.c#L31-L39

If afl1 can join us here we can change this and have either a nim socket with multistandard or two nim_sockets(DVB-T and DVB-S one)

 

Thanks

 

 

 

I find this thread:

https://forums.openp...2mn88473/page-5

 

Osmini have Enigma and AVL tuner.

 

nim_socket is this:

root@osminiplus:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-T2
        Name: FTM-4862 (Availink AVL6862)
        Frontend_Device: 0
        I2C_Device: 2
        Has_Outputs: yes
        Mode 0: DVB-S
        Mode 1: DVB-T
        Mode 2: DVB-C
        Internally_Connectable: 0

 

 

 

 

 

I find this thread:

https://forums.openp...2mn88473/page-5

 

Osmini have Enigma and AVL tuner.

 

nim_socket is this:

root@osminiplus:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-T2
        Name: FTM-4862 (Availink AVL6862)
        Frontend_Device: 0
        I2C_Device: 2
        Has_Outputs: yes
        Mode 0: DVB-S
        Mode 1: DVB-T
        Mode 2: DVB-C
        Internally_Connectable: 0

Read this

https://github.com/a.../enigma drivers

ftm4862.ko : AVL6862 Official driver from Edison os mini plus compatible enigma dvb-t includ

edision osmini plus

osminiplus-drivers-4.9.0-20170105.zip

use a same driver

 

 

ftm4862 driver won't do us any good since the object file (ftm4862.ko) is compiled for mips and not arm64



Re: Howto build unofficial pli for your unsupported receiver #1780 ftp21_

  • Senior Member
  • 73 posts

+9
Neutral

Posted 22 July 2018 - 19:28

I had the proc entry stb/frontend/0/mode to enable multitype tuner

 

http://www.mediafire...q/procfs.tar.gz

 

Now enigma can switch the mode but i cannot scan (now i can scan only dvb-t) for this error:

[eDVBFrontend] opening frontend 0
[eDVBChannel] getDemux cap=00
[eDVBResourceManager] allocate demux cap=00
[eDVBResourceManager] allocating demux adapter=0, demux=0, source=-1 fesource=0
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBDemux] DMX_SET_SOURCE Frontend0 failed: Invalid argument
[eDVBFrontend] (0)tune
[eDVBFrontend] tune setting type to 2 from 0
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend] startTuneTimeout 5000
[eDVBFrontend] setVoltage 0
[eDVBFrontend] setFrontend 1
[eDVBFrontend] setting frontend 0
FE_SET_PROPERTY failed: Bad address

I suspect a wrong demux allocation and it can crash FE_SET_PROPERTY


Edited by ftp21_, 22 July 2018 - 19:29.



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users