-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dreambox 500 C - Tuner Problems ;D #4
Comments
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 |
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 |
@Playandrepeat This is expected. Quoting the README:
|
@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:
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). |
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? |
This method has already been used here It's not too difficult to replace tuner. It can be done with three parts. PCB hole spacing : 2mm If the original tuner is philips can be replaced directly, there is no need to transfer |
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? |
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? |
any news for dm500c? |
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 ***@***.***> 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.
|
i hope developer has time to try make image for 500c too |
@ xiaole51 |
Do you have any questions do not understand it? |
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 can't understand your intentions. I think dm500 should be abandoned, it is too old. |
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. |
Trying to compile minisatip on dm500 will be more valuable. minisatip can work on dm800se. |
Serbia |
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 You need to clone the |
I think that, too |
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.
|
thanks for info. root@ubuntu1404:/opt/dm500-satip/minisatip# ./configure --host=ppc --enable-enigma --disable-dvbca --disable-dvbcsa --disable-satipc minisatip configuration Linux DVB: enabled root@ubuntu1404:/opt/dm500-satip/minisatip# ./build.sh build.sh: #!/bin/sh CC=powerpc-buildroot-linux-uclibc-gcc /opt/dm500-satip/buildroot/output/host/usr/bin/powerpc-buildroot-linux-uclibc-strip minisatip |
Any folder will do :) |
Also, you need to use the |
Glad to hear that! ^^ It's also been pretty stable for me. |
i use dm500-satip-2.3 branch but it give me: |
You have to understand first, https://drive.google.com/open?id=11oIS1e5lFWumLLLfvFzPKer-oAgFOW62 |
cant open link |
Copy link to browser can open. |
i can try to inastall ubuntu & compiler on one mac whit ppc cpu & give a try |
What is your purpose for doing this? |
root@dm500 /var/bin # ls |
I have successfully run minisatip in the generic dm500 firmware. dm500 adapter path is /dev/dvb/card0 dvbapi version of dm500 is too low, so the adapter cannot be recognized correctly. Has been submitted to minisatip official forum, hope they can help modify. |
thaks for help |
Yes, the original firmware has a very (very) old DVBAPI. 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. |
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 :( |
enigma2 for dm500 dead end |
what do you mean by «buy 500s & change tuner» ? |
i have dm500c, there is solution from @xiaole51 to change tuner put it in dm500s & yours great image shud work i hope |
you got it wrong, sorry :( |
:( 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
oh, that might work |
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. |
can you share patch for kernel?did you try whit vtuner<>minisatip? |
find e2&tvheadend for sh4 maybe it can be usefull for ppc |
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 ***@***.***> 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.
|
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 ***@***.***> 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.
|
whit sti cpu have it 6-7 or more good for playing ;) |
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 ([email protected])
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 '
The text was updated successfully, but these errors were encountered: