mildsunrise / dm500-satip

📡 Kernel & firmware image to turn a DM500 into a SAT>IP server
37 stars 11 forks source link

Dreambox 500 C - Tuner Problems ;D #4

Open Playandrepeat opened 7 years ago

Playandrepeat commented 7 years ago

Hello, ive got a problem. I want to use your image with the dm500 C but it sayd " Error: No tuner is available. Please file an issue on dm500-satip." Can you help me in anyway? Best regards Jan 1 00:00:02 dreambox syslog.info syslogd started: BusyBox v1.26.2 Jan 1 00:00:02 dreambox kern.notice kernel: klogd started: BusyBox v1.26.2 (2017-05-30 16:01:48 CEST) Jan 1 00:00:02 dreambox kern.info kernel: Using Dreambox DM500 machine description Jan 1 00:00:02 dreambox kern.notice kernel: Linux version 2.6.28-tm0-s4 (xavier@xavier-pad) (gcc version 4.9.4 (Buildroot 2017.05-rc3-g852faa4) ) #1 Tue May 30 16:03:45 CEST 2017 Jan 1 00:00:02 dreambox kern.debug kernel: Found legacy serial port 0 for /plb/opb/serial@40000 Jan 1 00:00:02 dreambox kern.debug kernel: mem=40040000, taddr=40040000, irq=0, clk=21000000, speed=0 Jan 1 00:00:02 dreambox kern.debug kernel: Found legacy serial port 1 for /plb/opb/serial@00000 Jan 1 00:00:02 dreambox kern.debug kernel: mem=40000000, taddr=40000000, irq=0, clk=21000000, speed=0 Jan 1 00:00:02 dreambox kern.debug kernel: Found legacy serial port 2 for /plb/opb/serial@10000 Jan 1 00:00:02 dreambox kern.debug kernel: mem=40010000, taddr=40010000, irq=0, clk=21000000, speed=115200 Jan 1 00:00:02 dreambox kern.info kernel: console [udbg0] enabled Jan 1 00:00:02 dreambox kern.debug kernel: Top of RAM: 0x2000000, Total RAM: 0x2000000 Jan 1 00:00:02 dreambox kern.debug kernel: Memory hole size: 0MB Jan 1 00:00:02 dreambox kern.warn kernel: Zone PFN ranges: Jan 1 00:00:02 dreambox kern.warn kernel: DMA 0x00000000 -> 0x00002000 Jan 1 00:00:02 dreambox kern.warn kernel: Normal 0x00002000 -> 0x00002000 Jan 1 00:00:02 dreambox kern.warn kernel: Movable zone start PFN for each node Jan 1 00:00:02 dreambox kern.warn kernel: early_node_map[1] active PFN ranges Jan 1 00:00:02 dreambox kern.warn kernel: 0: 0x00000000 -> 0x00002000 Jan 1 00:00:02 dreambox kern.debug kernel: On node 0 totalpages: 8192 Jan 1 00:00:02 dreambox kern.debug kernel: free_area_init_node: node 0, pgdat c0201224, node_mem_map c023f000 Jan 1 00:00:02 dreambox kern.debug kernel: DMA zone: 64 pages used for memmap Jan 1 00:00:02 dreambox kern.debug kernel: DMA zone: 0 pages reserved Jan 1 00:00:02 dreambox kern.debug kernel: DMA zone: 8128 pages, LIFO batch:0 Jan 1 00:00:02 dreambox kern.debug kernel: Normal zone: 0 pages used for memmap Jan 1 00:00:02 dreambox kern.debug kernel: Movable zone: 0 pages used for memmap Jan 1 00:00:02 dreambox kern.warn kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128 Jan 1 00:00:02 dreambox kern.notice kernel: Kernel command line: root=/dev/mtdblock5 rootfstype=jffs2 Jan 1 00:00:02 dreambox kern.warn kernel: UIC0 (32 IRQ sources) at DCR 0x40 Jan 1 00:00:02 dreambox kern.warn kernel: PID hash table entries: 128 (order: 7, 512 bytes) Jan 1 00:00:02 dreambox kern.debug kernel: time_init: decrementer frequency = 27.000000 MHz Jan 1 00:00:02 dreambox kern.debug kernel: time_init: processor frequency = 252.000000 MHz Jan 1 00:00:02 dreambox kern.info kernel: clocksource: timebase mult[9425ed1] shift[22] registered Jan 1 00:00:02 dreambox kern.debug kernel: clockevent: decrementer mult[6e9] shift[16] cpu[0] Jan 1 00:00:02 dreambox kern.info kernel: Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) Jan 1 00:00:02 dreambox kern.info kernel: Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) Jan 1 00:00:02 dreambox kern.info kernel: Memory: 30160k/32768k available (1976k kernel code, 2608k reserved, 80k data, 214k bss, 100k init) Jan 1 00:00:02 dreambox kern.info kernel: SLUB: Genslabs=10, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Jan 1 00:00:02 dreambox kern.info kernel: Calibrating delay loop... 53.88 BogoMIPS (lpj=107776) Jan 1 00:00:02 dreambox kern.warn kernel: Mount-cache hash table entries: 512 Jan 1 00:00:02 dreambox kern.info kernel: net_namespace: 288 bytes Jan 1 00:00:02 dreambox kern.info kernel: NET: Registered protocol family 16 Jan 1 00:00:02 dreambox kern.info kernel: NET: Registered protocol family 2 Jan 1 00:00:02 dreambox kern.info kernel: IP route cache hash table entries: 1024 (order: 0, 4096 bytes) Jan 1 00:00:02 dreambox kern.info kernel: TCP established hash table entries: 1024 (order: 1, 8192 bytes) Jan 1 00:00:02 dreambox kern.info kernel: TCP bind hash table entries: 1024 (order: 0, 4096 bytes) Jan 1 00:00:02 dreambox kern.info kernel: TCP: Hash tables configured (established 1024 bind 1024) Jan 1 00:00:02 dreambox kern.info kernel: TCP reno registered Jan 1 00:00:02 dreambox kern.info kernel: NET: Registered protocol family 1 Jan 1 00:00:02 dreambox kern.warn kernel: GPIO-236 autorequested Jan 1 00:00:02 dreambox kern.info kernel: JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. Jan 1 00:00:02 dreambox kern.info kernel: msgmni has been set to 58 Jan 1 00:00:02 dreambox kern.info kernel: io scheduler noop registered (default) Jan 1 00:00:02 dreambox kern.info kernel: Serial: 8250/16550 driver3 ports, IRQ sharing disabled Jan 1 00:00:02 dreambox kern.info kernel: serial8250.0: ttyS0 at MMIO 0x40040000 (irq = 20) is a 16550A Jan 1 00:00:02 dreambox kern.info kernel: console handover: boot [udbg0] -> real [ttyS0] Jan 1 00:00:02 dreambox kern.info kernel: serial8250.0: ttyS1 at MMIO 0x40000000 (irq = 21) is a 16550A Jan 1 00:00:02 dreambox kern.info kernel: serial8250.0: ttyS2 at MMIO 0x40010000 (irq = 22) is a 16550A Jan 1 00:00:02 dreambox kern.info kernel: brd: module loaded Jan 1 00:00:02 dreambox kern.info kernel: loop: module loaded Jan 1 00:00:02 dreambox kern.info kernel: nbd: registered device at major 43 Jan 1 00:00:02 dreambox kern.info kernel: ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com) Jan 1 00:00:02 dreambox kern.info kernel: Last modified Nov 1, 2000 by Paul Gortmaker Jan 1 00:00:02 dreambox kern.info kernel: NE*000 ethercard probe at 0xc3010600:00:09:34:22:52:11 Jan 1 00:00:02 dreambox kern.info kernel: eth0: NE2000 found at 0xc3010600, using IRQ 25. Jan 1 00:00:02 dreambox kern.info kernel: 7f800000.flash: Found 1 x16 devices at 0x0 in 16-bit bank Jan 1 00:00:02 dreambox kern.warn kernel: Intel/Sharp Extended Query Table at 0x0031 Jan 1 00:00:02 dreambox kern.info kernel: Using buffer write method Jan 1 00:00:02 dreambox kern.notice kernel: cfi_cmdset_0001: Erase suspend on write enabled Jan 1 00:00:02 dreambox kern.debug kernel: erase region 0: offset=0x0,size=0x20000,blocks=64 Jan 1 00:00:02 dreambox kern.notice kernel: cmdlinepart partition parsing not available Jan 1 00:00:02 dreambox kern.notice kernel: RedBoot partition parsing not available Jan 1 00:00:02 dreambox kern.notice kernel: Creating 7 MTD partitions on "7f800000.flash": Jan 1 00:00:02 dreambox kern.notice kernel: 0x00000000-0x00600000 : "DreamBOX CramFS + SquashFS" Jan 1 00:00:02 dreambox kern.notice kernel: 0x00600000-0x007c0000 : "JFFS2" Jan 1 00:00:02 dreambox kern.notice kernel: 0x007c0000-0x00800000 : "OpenBIOS" Jan 1 00:00:02 dreambox kern.notice kernel: 0x00000000-0x007c0000 : "DreamBOX CramFS + SquashFS + JFFS2" Jan 1 00:00:02 dreambox kern.notice kernel: 0x00000000-0x00800000 : "DreamBOX (with bootloader)" Jan 1 00:00:02 dreambox kern.notice kernel: 0x00120000-0x00600000 : "SquashFS" Jan 1 00:00:02 dreambox kern.notice kernel: 0x00000000-0x00120000 : "CramFS" Jan 1 00:00:02 dreambox kern.info kernel: i2c /dev entries driver Jan 1 00:00:02 dreambox kern.debug kernel: ibm-iic0: init Jan 1 00:00:02 dreambox kern.info kernel: stbx25xx-i2c 40030000.i2c: using standard (100 kHz) mode Jan 1 00:00:02 dreambox kern.info kernel: Registered led device: green Jan 1 00:00:02 dreambox kern.info kernel: Registered led device: red Jan 1 00:00:02 dreambox kern.info kernel: TCP cubic registered Jan 1 00:00:02 dreambox kern.info kernel: NET: Registered protocol family 17 Jan 1 00:00:02 dreambox kern.warn kernel: VFS: Mounted root (jffs2 filesystem) readonly. Jan 1 00:00:02 dreambox kern.warn kernel: Freeing unused kernel memory: 100k init Jan 1 00:00:02 dreambox kern.err kernel: devpts: called with bogus options Jan 1 00:00:03 dreambox authpriv.info dropbear[882]: Running in background Jan 1 00:00:04 dreambox kern.info kernel: --- STBx25xx Digital Video Broadcasting drivers --- Jan 1 00:00:04 dreambox kern.warn kernel: GPIO-253 autorequested Jan 1 00:00:04 dreambox kern.info kernel: Using interrupts: 17 18 19 23 Jan 1 00:00:04 dreambox kern.info kernel: --- STBx25xx MPEG-2 Transport Demultiplexer driver --- Jan 1 00:00:04 dreambox kern.info kernel: dvb-stbx25xx: resetting demux... done (took 1 ms) Jan 1 00:00:04 dreambox kern.info kernel: dvb-stbx25xx: Mapped 2097152 bytes of demux memory at 0xc3900000 Jan 1 00:00:04 dreambox kern.info kernel: DVB: registering new adapter (STBx25xx Digital TV device) Jan 1 00:00:04 dreambox kern.warn kernel: GPIO-238 autorequested Jan 1 00:00:04 dreambox kern.debug kernel: ibm-iic0: xfer error, EXTSTS = 0x43 Jan 1 00:00:04 dreambox kern.debug kernel: ibm-iic0: xfer error, EXTSTS = 0x73 Jan 1 00:00:04 dreambox kern.debug kernel: ibm-iic0: bus is stuck, resetting Jan 1 00:00:04 dreambox kern.debug kernel: ibm-iic0: soft reset Jan 1 00:00:04 dreambox kern.debug kernel: ibm-iic0: init Jan 1 00:00:04 dreambox kern.err kernel: stbx25xx-dvb dvb.2: could not attach frontend Jan 1 00:00:04 dreambox kern.err kernel: dvb-stbx25xx: Front-end initialization failed: error -19 Jan 1 00:00:04 dreambox kern.info kernel: dvb-stbx25xx: IBM STBx25xx digital TV hardware driver loaded successfully Jan 1 00:00:04 dreambox daemon.info : starting pid 897, tty '/dev/console': '/sbin/getty -L console 0 vt100 '

robbieb43 commented 7 years ago

Hi Playandrepeat

My understanding is the DM500C (DVB-C tuner) is not supported in the compiled image. However I think it is "just" a compiler switch. I have got as far as compiling a working DM500S image and I am just trying to work out the next step which is to try a compile with the DVB-C tuner enabled. Any tips very welcome!

Rob

robbieb43 commented 7 years ago

I might have spoke too soon. I can see another issue will be the driver for the tuner also as it looks like only the DM500s driver is there. This may not be a problem per se but I think may be stretching my fledgling build skills. There are drivers out there though - e.g. https://android.googlesource.com/kernel/msm/+/android-msm-mako-3.4-jb-mr1/drivers/media/dvb/frontends/tda10023.c

Rob

mildsunrise commented 7 years ago

@Playandrepeat This is expected. Quoting the README:

This image is currently for DM500S only. Flashing it on a DM500T or DM500C will get you a nice SAT>IP server with 0 tuners, because support for the T/C frontends is missing.

mildsunrise commented 7 years ago

@robbieb43 No, it isn't just a compiler switch (otherwise it'd be already enabled), it's a bit more complicated.

One half of the driver is shared between DM500-S/C/T and is already there. The other half (the frontend driver) is also there and is different for each version, these are the three switches to enable it:

CONFIG_DVB_STV0299=m    # DM500S
CONFIG_DVB_TDA1004X=m   # DM500T 
CONFIG_DVB_TDA10021=m   # DM500C

But in order for everything to work, some DM500-specific glue code must be put in this file. This code starts the appropriate driver (STV0299, TDA1004X or TDA10021) and makes the tuner usable. Right now the glue code only starts the STV0299 so it only works with DM500S.

Writing glue code for the other drivers requires discovering some parameters first, and is hard to get right without a DM500C or DM500T at hand. But if someone donates a box I have no inconvenience (or you can try to do it yourself, if you feel confortable modifying Linux).

xiaole51 commented 7 years ago

DM500S can implement S to C by modifying the bootloader I have successfully changed S to C (bsbe1-702b to CU1216LS)

cat /dev/mtd/2 > /tmp/dm500s.img edit this img use hex editor dm500sc Modify the number of 06 in the address position on the image The Numbers are as follows 02: 500C Philips 03: 500S Philips 04: 500T DVB-T 06: 500S Alps

06 modified to 02 can be used for dvb-c Save the modified file and upload it to the DM500 /tmp directory cp /tmp/dm500s.bin /dev/mtd/2

Stitch map dm500stoc

I hope this information is useful

mildsunrise commented 7 years ago

The information is certainly useful, but I'm not sure about buying and soldering a CU1216LS to my DM500S to turn it into a DM500C.

The data can be used to make the code cleaner, though. Where did you get the stitch map from, do you have any schematics of the DM500C/S?

xiaole51 commented 7 years ago

This method has already been used here I drew the lines. I have no schematics of the DM500C/S But this method has proved to be effective.

It's not too difficult to replace tuner. It can be done with three parts. Please refer to my revised photo

PCB hole spacing : 2mm Pin length: 19mm

1

2

3

If the original tuner is philips can be replaced directly, there is no need to transfer

robbieb43 commented 7 years ago

Apologies for the OT preamble but, my use-case for my DM500-C has gone leaving my box with little future prospect of earning its keep. The DM500-S is doing sterling service in combination with the also excellent node-ffmpeg-mpegts-proxy https://github.com/Jalle19/node-ffmpeg-mpegts-proxy so by way of thanks (and not withstanding the excellent how-to above) perhaps I could donate it to Xavier if we can find a cost effective means? Perhaps an exchange of PMs?

tech4bot commented 5 years ago

in order to compile it this for DVB-C I just need to complete that glue code you mentioned or I need also to have the driver for the tuner?

atarist commented 5 years ago

any news for dm500c?

robbieb43 commented 5 years ago

Btw - still have old dm500c up for grabs. If you want to send an address by email I will post it to you.

Cheers

Rob

Sent from my iPad

On 11 May 2019, at 07:15, atarist notifications@github.com wrote:

any news for dm500c?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

atarist commented 5 years ago

i hope developer has time to try make image for 500c too great work!

atarist commented 4 years ago

@ xiaole51 can you help me how to make dm500c to work?

atarist commented 4 years ago

dm500 shematic https://elektrotanya.com/dreambox_dm500_sch.rar/download.html#dl pcb : https://jb8a8f8.com/support/index.php?threads/dm500s-pcb-pictures.7/#post-7 info https://www.rdi-board.com/forum/receptoare/dreambox/148467-dm500s-to-dm500c-sau-dm500t

xiaole51 commented 4 years ago

@ xiaole51 can you help me how to make dm500c to work?

Do you have any questions do not understand it? I have shared all the transformation methods.

atarist commented 4 years ago

As I understand we cant build driver for CU1216LS but i can cat 19 lines for it any wire it differet whitout removing tuner. from dm500c I dont understand why you transver tuner to 500s, they have same hw becide tuner or Im wrong? I tru to kill enigma in openpli(killall start_enigma & killall enigma) & start minisatip from this git but i get : root@dm500 /var/bin # ./minisatip -sh: ./minisatip: not found ?

xiaole51 commented 4 years ago

I can't understand your intentions. I share the method of transforming DM500S to DM500C. However, the jmendeth/dm500-satip firmware cannot support the tuner of DVB-C. And this project has been abandoned.

I think dm500 should be abandoned, it is too old.

atarist commented 4 years ago

didnt find way to dont remove tuner to dm500s, dm500/600c risiver is old but it can be still use, but dvb-s is dead. it good project, i hope it can usefull for other ricivers like dm800 or new for mips cpu

xiaole51 commented 4 years ago

Trying to compile minisatip on dm500 will be more valuable. I have tried to compile, but the C library version is too old, so I can't pass.

minisatip can work on dm800se. Which country are you from?

atarist commented 4 years ago

Serbia I menage to build image whit crosscompile but not sure how to use it to compile minisatip for ppc

mildsunrise commented 4 years ago

Hmm you shouldn't need to compile minisatip, this repo has a compiled version that is automatically installed in the image.

But if you need to compile it, then:

when you have built the image, you will have a toolchain at buildroot/output/host/usr/bin (or something like that). You will have a compiler (powerpc-buildroot-linux-uclibc-gcc), a linker and other crosscompilation tools.

You need to clone the dm500-satip-2.3 branch of my repo. You will have a build.sh script showing what parameters are needed to build minisatip with the toolchain.

mildsunrise commented 4 years ago

I think dm500 should be abandoned, it is too old.

I think that, too I've currently lost interest in this, I don't think I'll be developing it further unless there's a bug or something...

robbieb43 commented 4 years ago

It may be old but it's been very stable with this software running. I leave it running for months on end and it just keeps going. I use Raspberry Pis also with minisatip but they are more prone to need reboots, which is a pain when I am 2000 miles away.

Been a great little project for me.

Cheers

Sent from my iPad

On 1 Sep 2019, at 23:20, Alba Mendez notifications@github.com wrote:

I think dm500 should be abandoned, it is too old.

I think that, too I've currently lost interest in this, I don't think I'll be developing it further unless there's a bug or something...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

atarist commented 4 years ago

thanks for info. btw i what folder can i put minisatip for compiling? @ robbieb43, i agree dm500 work better & stable then pc whit usb card, better signal too, there many dm500c for use not for trash jet

root@ubuntu1404:/opt/dm500-satip/minisatip# ./configure --host=ppc --enable-enigma --disable-dvbca --disable-dvbcsa --disable-satipc checking for ppc-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for main in -lrt... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking for stdint.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking syslog.h usability... yes checking syslog.h presence... yes checking for syslog.h... yes checking for unistd.h... (cached) yes checking for int16_t... yes checking for int64_t... yes checking for int8_t... yes checking for size_t... yes checking for uint16_t... yes checking for uint32_t... yes checking for uint64_t... yes checking for uint8_t... yes checking for stdlib.h... (cached) yes checking for GNU libc compatible malloc... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for sys/param.h... yes checking for getpagesize... yes checking for working mmap... yes checking for bzero... yes checking for clock_gettime... yes checking for dup2... yes checking for gethostbyname... yes checking for gettimeofday... yes checking for inet_ntoa... yes checking for memset... yes checking for munmap... yes checking for socket... yes checking for strchr... yes checking for strerror... yes checking for strncasecmp... yes checking for strstr... yes configure: == Checking LINUX DVB == checking linux/dvb/frontend.h usability... yes checking linux/dvb/frontend.h presence... yes checking for linux/dvb/frontend.h... yes configure: == Checking OpenSSL == checking openssl/aes.h usability... yes checking openssl/aes.h presence... yes checking for openssl/aes.h... yes configure: == Checking Embedded == checking for backtrace... yes configure: == Checking NETCVCLIENT == checking netceiver.h usability... no checking netceiver.h presence... no checking for netceiver.h... no configure: creating ./config.status config.status: creating src/Makefile config.status: creating tests/Makefile config.status: creating Makefile

minisatip configuration

Linux DVB: enabled Common Interface (needs DVBEN50221): disabled OpenSSL (AES as part of DVBAPI): enabled Embedded system: disabled DVBCSA (needs libdvbcsa): disabled Netceiver support: disabled SatIP Client: disabled Static: disabled dvbapi: enabled axe: disabled enigma: enabled

root@ubuntu1404:/opt/dm500-satip/minisatip# ./build.sh make -C src make[1]: Entering directory /opt/dm500-satip/minisatip/src' make[1]: Leaving directory/opt/dm500-satip/minisatip/src' make[1]: Entering directory /opt/dm500-satip/minisatip/src' gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c minisatip.c -o ../build/minisatip.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c socketworks.c -o ../build/socketworks.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c stream.c -o ../build/stream.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c adapter.c -o ../build/adapter.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c utils.c -o ../build/utils.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c aes.c -o ../build/aes.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c dvbapi.c -o ../build/dvbapi.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c pmt.c -o ../build/pmt.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c tables.c -o ../build/tables.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -c dvb.c -o ../build/dvb.o gcc -fPIC -Os -DVERSION=\"1.0.0-07cb6fc\" -DDISABLE_DVBCSA -DDISABLE_DVBCA -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -o ../minisatip ../build/minisatip.o ../build/socketworks.o ../build/stream.o ../build/adapter.o ../build/utils.o ../build/aes.o ../build/dvbapi.o ../build/pmt.o ../build/tables.o ../build/dvb.o -lpthread -lrt -lcrypto make[1]: Leaving directory/opt/dm500-satip/minisatip/src' /opt/dm500-satip/buildroot/output/host/usr/bin/powerpc-buildroot-linux-uclibc-strip: Unable to recognise the format of the input file `minisatip' root@ubuntu1404:/opt/dm500-satip/minisatip#

build.sh:

!/bin/sh

CC=powerpc-buildroot-linux-uclibc-gcc \ CFLAGS="-fPIC -Os" EMBEDDED=yes \ ENIGMA=yes DVBCSA=no DVBCA=no SATIPCLIENT=no make &&

/opt/dm500-satip/buildroot/output/host/usr/bin/powerpc-buildroot-linux-uclibc-strip minisatip

mildsunrise commented 4 years ago

btw i what folder can i put minisatip for compiling?

Any folder will do :) But you also need to replace powerpc-buildroot-linux-uclibc-gcc just like you did with powerpc-buildroot-linux-uclibc-strip

mildsunrise commented 4 years ago

Also, you need to use the dm500-satip-2.3 branch, otherwise it probably won't compile

mildsunrise commented 4 years ago

It may be old but it's been very stable with this software running. I leave it running for months on end and it just keeps going. I use Raspberry Pis also with minisatip but they are more prone to need reboots, which is a pain when I am 2000 miles away. Been a great little project for me. Cheers Sent from my iPad On 1 Sep 2019, at 23:20, Alba Mendez @.***> wrote: I think dm500 should be abandoned, it is too old. I think that, too I've currently lost interest in this, I don't think I'll be developing it further unless there's a bug or something... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Glad to hear that! ^^ It's also been pretty stable for me. If there's an unstability I'll be happy to fix it.

atarist commented 4 years ago

i use dm500-satip-2.3 branch but it give me: /opt/dm500-satip/buildroot/output/host/usr/bin/powerpc-buildroot-linux-uclibc-strip: Unable to recognise the format of the input file `minisatip' when i try to make image it compile it whitout error

xiaole51 commented 4 years ago

You have to understand first, This method compiled con't work in general DM500 firmware. I have compiled it, you can try it.

https://drive.google.com/open?id=11oIS1e5lFWumLLLfvFzPKer-oAgFOW62

atarist commented 4 years ago

cant open link maybe whit config ENIGMA=yes it will work whit openpli image i can try..

xiaole51 commented 4 years ago

cant open link maybe whit config ENIGMA=yes it will work whit openpli image i can try..

Copy link to browser can open. Lib library is not compatible, so it can't work. generic firmware compiler version is too old, so can't compile minisatip.

atarist commented 4 years ago

i can try to inastall ubuntu & compiler on one mac whit ppc cpu & give a try do you know what ver of compiler thet i need to install on it?

xiaole51 commented 4 years ago

What is your purpose for doing this? Compiling this project will get a toolchain. Path in : ../dm500-satip/buildroot/output/host/usr

atarist commented 4 years ago

root@dm500 /var/bin # ls firewall.sh minisatip oscam root@dm500 /var/bin # chmod a+x minisatip root@dm500 /var/bin # ./minisatip -sh: ./minisatip: not found

xiaole51 commented 4 years ago

Hmm you shouldn't need to compile minisatip, this repo has a compiled version that is automatically installed in the image.

But if you need to compile it, then:

when you have built the image, you will have a toolchain at buildroot/output/host/usr/bin (or something like that). You will have a compiler (powerpc-buildroot-linux-uclibc-gcc), a linker and other crosscompilation tools.

You need to clone the dm500-satip-2.3 branch of my repo. You will have a build.sh script showing what parameters are needed to build minisatip with the toolchain.

I have successfully run minisatip in the generic dm500 firmware. use your branch https://github.com/jmendeth/minisatip Can be run after static compilation.

dm500 adapter path is /dev/dvb/card0 I edited dvb.c to modify the adapter path edited dvb.c file: https://pastebin.com/Ny4Z4hdA

dvbapi version of dm500 is too low, so the adapter cannot be recognized correctly. logs: https://pastebin.com/aQDrpaUh

Has been submitted to minisatip official forum, hope they can help modify. Can support low version dvbapi. https://minisatip.org/forum/viewtopic.php?f=5&t=601&p=3543#p3543

atarist commented 4 years ago

thaks for help

mildsunrise commented 4 years ago

dvbapi version of dm500 is too low, so the adapter cannot be recognized correctly.

Yes, the original firmware has a very (very) old DVBAPI. That's (in part) why I had to build a firmware from scratch.

I don't think it's possible to modify minisatip for DVBAPIv3 without basically rewriting it... It is a completely different version, uses many devices instead of 1, etc.

atarist commented 4 years ago

i find some solution to install enigma2 on dm500 but not sure if it is stable&useful, i will try no other solution or bay 500s & change tuner :( https://www.sat-universe.com/showthread.php?t=155132

atarist commented 4 years ago

enigma2 for dm500 dead end

mildsunrise commented 4 years ago

what do you mean by «buy 500s & change tuner» ?

atarist commented 4 years ago

i have dm500c, there is solution from @xiaole51 to change tuner put it in dm500s & yours great image shud work i hope i can try before vtuner there is some solution for old kernel & dvbapi <v3 https://lwn.net/Articles/448472/ if someting of this work i plan to use tvheadend for decrypt chanells & transcoding

mildsunrise commented 4 years ago

you got it wrong, sorry :( changing the tuner of a dm500s won't make it work either

atarist commented 4 years ago

:( why hi change tuner then? ;) i asumsed software see alps tuner but it philips instand btw for vtuner i find: https://github.com/gdachs/vtuner https://www.digitalworldz.co.uk/threads/vtuner.274182/#post-2021012 seems to work on dm500, http://www.world-satellite.net/attachments/160340d1489512796-oscam-powerpc-tuxbox-old-dm500-500s-librt.so.1.rar only problem can be pacthing new kernel 4.xx or 5.xx to work whit vtuner for pc

mildsunrise commented 4 years ago

why hi change tuner then? ;)

changing the tuner of a DM500S would be useful for me (or anyone without access to a DM500C) to develop the support for DM500C. it is useless if you already have a DM500C

btw for vtuner i find: https://github.com/gdachs/vtuner

oh, that might work

tech4bot commented 4 years ago

I’ve managed to recompile kernel for vtuner and also for raspberry pi is AlexELEC which contains vtuner in some of older versions but is not working correctly, only some channels are working and you need to restart from time to time, so is a waste of time. Is woking ok on dbox2 but not on dm500c.

atarist commented 4 years ago

can you share patch for kernel?did you try whit vtuner<>minisatip? i think have someware dbox2 all 3 ver but not sure thay are dvb-c

atarist commented 4 years ago

find e2&tvheadend for sh4 maybe it can be usefull for ppc https://github.com/Audioniek/buildsystem

robbieb43 commented 4 years ago

Interesting... I have a couple of old sh4 (qbox mini) boxes so may give it a try once the weather turns :-) Don't think ppc has the .elf files though.

Sent from my iPad

On 20 Sep 2019, at 03:00, atarist notifications@github.com wrote:

find e2&tvheadend for sh4 maybe it can be usefull for ppc https://github.com/Audioniek/buildsystem

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

robbieb43 commented 4 years ago

Sorry Javier resent as missed the "all"

Interesting... I have a couple of old sh4 (qbox mini) boxes so may give it a try once the weather turns :-) Don't think ppc has the .elf files though.

Sent from my iPad

On 20 Sep 2019, at 03:00, atarist notifications@github.com wrote:

find e2&tvheadend for sh4 maybe it can be usefull for ppc https://github.com/Audioniek/buildsystem

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

atarist commented 4 years ago

whit sti cpu have it 6-7 or more good for playing ;) you will need sources.openelec.tv/mirror/module-init-tools/module-init-tools-3.16.tar.bz2 from git script file is emty source maybe can use it driver pack or someting for ppc