Bear with me a bit... As had to do an urgent update suggest by the manufacture
2 OSCAM 1 Set Top Box, how???
-
- Android Support
- DANNYPS4
- Thread is marked as Resolved.
-
-
here is the results:
- 2018/09/16 18:54:16 701B8165 c (client) plain dvbapi-client granted (anonymous, au=off)
- 2018/09/16 18:54:16 701B8165 c (dvbapi) dvbapi channelcache loaded from /storage/sdcard/OSEbuild/OSCam/conf/oscam.ccache
- 2018/09/16 18:54:16 701B8165 c (dvbapi) ERROR: Could not detect DVBAPI version.
as you can see on the last line, the OSCAM you script build does not work for these boxes....
this the result from Fegol script, the one he posted on #97
- 2018/09/16 19:00:14 4E473CF9 c (client) plain dvbapi-client granted (anonymous, au=off)
- 2018/09/16 19:00:14 4E473CF9 c (dvbapi) dvbapi channelcache loaded from /storage/sdcard/OSEbuild/OSCam/conf/oscam.ccache
- 2018/09/16 19:00:14 4E473CF9 c (dvbapi) Detected Hisilicon{1}.
as you can see DVBAPI is detected which means it is usable for either C band, Ku Band and more...
-
We seen the patch. We know it is making changes to oscam dvbapi files. What I am saying is, if you leave all config as is I bet you may need that.
But I still wonder why do you need that?
What part of the program needs "(dvbapi) ... Hisilicon{1}."
I am no expert on oscam nor you had said what/how you use it for. My best guess is the Internal Slot Card Reader. Well the question is still up.
When you test my file, did you went to "/storage/sdcard/OSEbuildOSCam/conf/oscam.server" and comment or deleted the part for the slot card reader Like i posted?
Code
Display More#[reader] #label = myslot #enable = 0 #protocol = internal #device = /dev/hi_sci #boxid = * #detect = * #mhz = * #cardmhz = * #aeskeys = * #group = *
I bet you if you do you will not have any trouble.
Now the other area is TVHeadEnd. If TVHeadEnd may have an old protocol and maybe that is the reason for the patch.
In any case, I bet you that patch if not needed if you have an update TVHeadend and so not use the Internal Slot Card Reader.
I know you say "Bear with me a bit" I will be arround. Just keep testing and send me a PM in case you need extra help. But our buddy fegol has been given time after time good orientation and in this time even patched files. He is the champion here.
-
Also can you show us what is the dev been used for dvb on your box. Can you do
As example in ubuntu a USB PCSAT will show like this
and inside adaoter 0 we have
Be aware that it is know that in Android many dvb devices show like
what your box show?
-
We seen the patch. We know it is making changes to oscam dvbapi files. What I am saying is, if you leave all config as is I bet you may need that.
But I still wonder why do you need that?
What part of the program needs "(dvbapi) ... Hisilicon{1}."
I am no expert on oscam nor you had said what/how you use it for. My best guess is the Internal Slot Card Reader. Well the question is still up.
When you test my file, did you went to "/storage/sdcard/OSEbuildOSCam/conf/oscam.server" and comment or deleted the part for the slot card reader Like i posted?
Code
Display More#[reader] #label = myslot #enable = 0 #protocol = internal #device = /dev/hi_sci #boxid = * #detect = * #mhz = * #cardmhz = * #aeskeys = * #group = *
I bet you if you do you will not have any trouble.
Now the other area is TVHeadEnd. If TVHeadEnd may have an old protocol and maybe that is the reason for the patch.
In any case, I bet you that patch if not needed if you have an update TVHeadend and so not use the Internal Slot Card Reader.
I know you say "Bear with me a bit" I will be arround. Just keep testing and send me a PM in case you need extra help. But our buddy fegol has been given time after time good orientation and in this time even patched files. He is the champion here.
think about this way.... microsoft windows is the OSCAM.bin and the hardware would be the actual hardware of the box and the DVBAPI would be the drivers, you could have a good and an udated windows version but if your driver wont see the hardware is usesless, this is the same case, if the OSCAM wont talk to the DVBAPI then the OSCAM is usesless...
-
Also can you show us what is the dev been used for dvb on your box. Can you do
As example in ubuntu a USB PCSAT will show like this
and inside adaoter 0 we have
Be aware that it is know that in Android many dvb devices show like
what your box show?
we can talk better with *.sh file, send me the files with the comands you need and I will post it here.
-
1) Do not forget to test my file again, but when you test my file, you need to edit
"/storage/sdcard/OSEbuildOSCam/conf/oscam.server"
and comment or deleted the part for the slot card reader Like i posted? To commerny you place a "#" at the first line.
Code
Display More#[reader] #label = myslot #enable = 0 #protocol = internal #device = /dev/hi_sci #boxid = * #detect = * #mhz = * #cardmhz = * #aeskeys = * #group = *
2) I see your analogy but that is not how I believe all works.
See you should have a physical dvb device hook to I guess PCI. A "Linux driver" will make that device to show as
/dev/dvb0.frontend0 or /dev/dvb/adapter0.
Then TVHeadend will control the dvb device using /dev/dvb0.frontend0 or /dev/dvb/adapter0/frontend0
And TVHeadend will pickup ts Video at /dev/dvb0.dvr0 or /dev/dvb/adapter0/dvr0.
At this level I do not believe dvbapi is used.
I believe dvbapi will be use(see <==>) if needed between TVHeadEnd and oscam. Like in;
Video Payer <-- TVHeadend <==> oscam_emu or the other way
Video Payer <-- oscam_emu <==>TVHeadend
I think oscam may also used it for the readers. Like if you use your internal slot or a cccam/newcamd server.
So if you had both the latest svn oscam and TVHeadend then no trouble should be shown with dvbapi.
3) sh is simple
-
Upsss!!!
I guess I was wrong....
See
_https://www.linuxtv.org/docs/dvbapi/dvbapi.html
DVB Frontend API
DVB Demux Device
DVB Video Device
etc
are part of dvbapi.
But still, I will expect that a well design driver should account for the standard. I guess we need to go deep in the patch to see what part it modify in order to know better.
-
-
I will post some info in a few, i´ve been a bit busy
-
answer:
root@u5pvr-debian:~# #!/system/bin/sh
root@u5pvr-debian:~# ls /dev -R | grep "dvb"
root@u5pvr-debian:~# ls /dev/dvb/adapter0
ls: cannot access /dev/dvb/adapter0: No such file or directory
-
Since a few days has pass and you had posted very little, lets resume where we are.
You all ready have the oscam build solution you had ask. A specially build with patch for your box. Because our friend fegol posted that solution on #97. I assume that as always you tested. It is just you forgot to tell us.
SOOOooooo, at this moment we are only having fun...
Empty? That's weird. You must have a dvb device.
Again. As last script, this is to be run inside your Android TV Box.
Code#!/system/bin/sh su ls /dev -R | grep ":$" | sed -e 's/:$//' -e 's/[^-][^\/]*\//--/g' -e 's/^/ /' -e 's/-/|/'
This will print the full tree.
-
Wao I did put many hours on this. Still swimming against current. Getting not where yet.
I have run the Debian Arm emulation. Have not set top network yet. To setup please use
Oscam CPU target emulation using qemu in Ubuntu. as reference. Almost all is the same . Create your $HOME/bin. Place
- $HOME/bin/host-network-setup.sh
But now we do not use the malta script instead we will use a new one for ARM. It is attached.
- $HOME/bin/start-versatile-instance.sh
- create a new dir
- mkdir $HOME/bin/arm
- mkdir $HOME/bin/arm/versatile
Save your Arm Debian files
- $HOME/bin/arm/versatile/initrd.img-3.2.0-4-versatile
- $HOME/bin/arm/versatile/vmlinuz-3.2.0-4-versatile
- $HOME/bin/arm/versatile/debian_wheezy_armel_standard.qcow2
You need to open your drive: debian_wheezy_armel_standard.qcow2 and save the oscam binaries
- mkdir $HOME/bin/arm/versatile/mnt
- sudo modprobe nbd max_part=8
- sudo qemu-nbd -c /dev/nbd0 $HOME/bin/arm/versatile/debian_wheezy_armel_standard.qcow2
- sudo mount /dev/nbd0p1 mnt
Note this file system do open as "/" in Debian. So $HOME/bin/arm/versatile/mnt = / in Debian.
Now get the files needed from the attachment home.tar.xz. And copy them to /home/user/oscam ...
- sudo umount mnt
- sudo qemu-nbd -d /dev/nbd0p1
Press special attention. This one create the necesary devices in /dev/nd0-8
- sudo modprobe nbd max_part=8
This one translate qcow2 image format to Ubuntu system
- sudo qemu-nbd -c /dev/nbd0 $HOME/bin/arm/versatile/debian_wheezy_armel_standard.qcow2
***See now how we do the mount and umount with the handler nbdp1 instead of the qcow2. As the handler take to job to translate qcow2.
After the umount, the qcow2 image still attached to the handler. So we need to delete that
- sudo qemu-nbd -d /dev/nbd0p1
Now our qcow2 image is free for us to use. And files where saved.
Now we only need to call quemu with
- $HOME/bin/start-versatile-instance.sh
After about 1.5 minute you will get:
Code
Display MoreDebian GNU/Linux 7 debian-armel ttyAMA0 debian-armel login: #user[Enter] #user[Enter] Linux debian-armel 3.2.0-4-versatile #1 Debian 3.2.51-1 armv5tejl
Yes user = user
user password = user
root = root
root password = root.
Enjoy
A none working oscam is at /home/user/oscam/oscam
Thanks for this very useful documentation.
I am trying to make an arm7hf based busybox environment /ubunu/debian environment in QEMU .
I am fine to use any Host, Windows, Ubuntu.
I want a full blown arm emulated linux so i can develop some c++ with SDL.
I have got some success with the cross compiling simple c++ programs and its runs successfully in the Octagon SF8008.
I am facing many challenges for compiling the SDL2 program because of errors in some headers file with undefined deceleration type.
I found that a Qemu emulated environment is the best solution for me.
I will try to use your documents and will let you know the results in a few days.
In case there is a already a ready document for the emulating arm7hf or the cortex-a53 .
-
i have the same issue. (ERROR: Could not detect DVBAPI version.) i have VPS server Ubuntu 16.xx .x64 can you please guide me with complete command line to fix this issue.
OSCam-EMU Support Forum
Configs, discussion, downloads and guides for OSCam-EMU Softcam.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!