tsduck
tsduck copied to clipboard
tsduck
Anyone interested in ISDB tuners ?
Dear TSDuck users,
Is anyone interested in support for ISDB tuners ?
Being based in Europe, I do not have ISDB tuners and I do not have access to real operational ISDB networks. If anyone is interested in TSDuck supporting ISDB tuners, I will need cooperation with someone based in an ISDB country, Japan, Brazil or similar.
Linux support for ISDB-T and ISDB-S looks correct. So, Linux is a priority. Windows support for ISDB is not documented but the header files contain references to ISDB-S (not much to ISDB-T). So, I do not know if using ISDB on Windows is possible at all. Any experience in DirectShow with ISDB would be welcome.
Hello how are you? I am from Argentina, I have reception equipment in isdb tb with the ability to receive interactive applications, middleware ginga.ar (ginga argentina).
If I can collaborate with tsduck on anything, it would be a pleasure.
regards
Marco Camacho
Hi @sionjujuy,
Thank you for offering your collaboration. Do you have any ISDB tuner that can be plugged into a computer to receive a transport stream, either PCIe or USB? Do you have any Linux driver for it? Which Linux distribution are you using?
The idea is to open the dvb plugin to ISDB reception so we need devices to test. I agree that dvb is now a bad name for the tuner reception plugin. It started with DVB tuners only but ATSC tuners are also supported now.
Hi @lelegard , I have a dektec dtu 215 Usb with an isdbt license, I can get an usb tuner isdbt and linux ubutu, to do the necessary tests.
At the moment I am traveling back in two weeks and I do the tests.
Regards
Thanks. Currently, it won't work since the dvb plugin does not support ISDB yet. So, I need to add support for the required modulation parameters and then you could test.
Could anyone give a complete list of the required modulation parameters for ISDB-T (and ISDB-S if known)?
https://www.kernel.org/doc/html/v4.14/media/uapi/dvb/fe_property_parameters.html
I had read the list of LinuxTV parameters but the ISDB specificities were not clearly summarized.
Let's try to build an exhaustive list of possible modulation parameters for ISDB on Linux. Please report any error or additional useful information.
| Parameter | ISBD-T | ISDB-S |
|---|---|---|
| DTV_FREQUENCY | value in Hz | value in kHz |
| DTV_MODULATION | QPSK, DQPSK, 16-QAM, 64-QAM | 8-PSK, QPSK, BPSK |
| DTV_BANDWIDTH_HZ | 5MHz, 6MHz, 7MHz, 8MHz | unused |
| DTV_INVERSION | ? | ? |
| DTV_SYMBOL_RATE | unused | value in sym/s ? |
| DTV_INNER_FEC | unused | which values are valid ? |
| DTV_ISDBT_PARTIAL_RECEPTION | need explanations | unused |
| DTV_ISDBT_SOUND_BROADCASTING | 0, 1, -1 (AUTO) | unused |
| DTV_ISDBT_SB_SUBCHANNEL_ID | 0..41, -1 (AUTO) | unused |
| DTV_ISDBT_SB_SEGMENT_IDX | 0..12 | unused |
| DTV_ISDBT_SB_SEGMENT_COUNT | 1..13 | x |
| DTV_ISDBT_LAYER_ENABLED | 3 bits, bitmask | x |
| DTV-ISDBT_LAYER[A-C]_FEC | FEC_AUTO, FEC_1_2, FEC_2_3, FEC_3_4, FEC_5_6, FEC_7_8 | unused |
| DTV-ISDBT_LAYER[A-C]_MODULATION | QAM_AUTO, QPSK, QAM_16, QAM_64, DQPSK | unused |
| DTV-ISDBT_LAYER[A-C]_SEGMENT_COUNT | 0..13, -1 (AUTO) | unused |
| DTV-ISDBT_LAYER[A-C]_TIME_INTERLEAVING | 0, 1, 2, 4, -1 (AUTO) | unused |
| DTV_CODE_RATE_HP | which values are valid ? | unused |
| DTV_CODE_RATE_LP | which values are valid ? | unused |
| DTV_GUARD_INTERVAL | which values are valid ? | unused |
| DTV_TRANSMISSION_MODE | which values are valid ? | unused |
| DTV_STREAM_ID | unused | 1..65535, NO_STREAM_ID_FILTER |
Additional question:
- What is ISDB-Tsb ? "Sound broadcasting" ? Or something related to ISDB-Tb (Brazil) ?
- If it is sound broadcasting, what is this exactly? Is this useful to support in TSDuck?
- What are the main differences between ISDB-T and ISDB-Tb ?
- Modulation ?
- Signalization (PSI/SI) ?
- Is there any ISDB-Sb ? Or are the Brazilian / South America specificities limited to terrestrial ?
Thanks for your help.
Hello, more information Isdbt - isdb-tbs
El mié., 2 de oct. de 2019 1:09 PM, Thierry Lelegard < [email protected]> escribió:
Thanks. Currently, it won't work since the dvb plugin does not support ISDB yet. So, I need to add support for the required modulation parameters and then you could test.
Could anyone give a complete list of the required modulation parameters for ISDB-T (and ISDB-S if known)?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tsduck/tsduck/issues/425?email_source=notifications&email_token=ABK6FC5YZHCWRBN7UJ5S46DQMTBVLA5CNFSM4I4MI6AKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAFJVRA#issuecomment-537565892, or mute the thread https://github.com/notifications/unsubscribe-auth/ABK6FC3ZL44ZVJ76T2R7ZQLQMTBVLANCNFSM4I4MI6AA .
I send you an attachment where it explains about isdb and isbdtsb so you can see the differences.
I still don't have time to answer your questions from the previous email, excuse me.
El mar., 8 de oct. de 2019 8:42 AM, Thierry Lelegard < [email protected]> escribió:
Hello, more information Isdbt - isdb-tbs
What do you mean?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tsduck/tsduck/issues/425?email_source=notifications&email_token=ABK6FC37TSZAT4GDZVNAPCTQNRW2PA5CNFSM4I4MI6AKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAT3UPA#issuecomment-539474492, or mute the thread https://github.com/notifications/unsubscribe-auth/ABK6FC6AFG7E6XXM4XI7FADQNRW2PANCNFSM4I4MI6AA .
Hi @sionjujuy and all ISDB users,
I have implemented all ISDB-T and ISDB-S parameters (see the updated user's guide, plugin dvb). The Linux implementation is done (not the Windows one).
If this is possible for you, could you please test with your tuners. You have to pull the repo and rebuild in any Linux distro (instructions here).
This code was done without any test (no ISDB tuner or network here). So, there is a risk that it does not work at once. I suggest to start with tslsdvb -v. Please post the result. Please also post the name and characteristics of the tuners you use (the idea is to add it in the user's guide table at section 6.1.4, so please include all relevant details or required firmware). Make sure that there is no error message (missing driver or missing firmware) using the `dmesg' command.
Thank you all for your feedback.
First tested ISDB-T tuners: A user from Japan reported that the following two tuners work on Linux and Windows: MyGica S270 and PLEX PX-S1UD. They are internally identical.
Mygica S2780 I have confirmed the operation on raspbian buster and Windows 10. raspbian requires linuxtv.org/downloads/firmware/dvb-usb-dib0700-1.20.fw.
Greetings in advance.
I have a TDA STB for TDT (Television Digital Terrestre) in Venezuela with ISDB-Tb protocol (Japanese-Brazilian norm or standard). The equipment distributed in Venezuela is OEM assembled in Argentina.
What is the possibility of modifying the STB firmware?
Any help or advice?.
I have attached the boot of the device.
Placa: 742
Modelo de Memoria: [32-bit mode]
U-Boot 1.3.1 (Oct 18 2012 - 16:37:27) -
DRAM: 256 MiB
SPI: info: found MXIC MX25L6455E (8MiB) device (page=256,erase=4096)
In: serial
Out: serial
Err: serial
Hit ENTER key to stop autoboot: 0
## Booting image at 00120000 ...
Image Name: Linux 2.6
Image Type: SuperH Linux Kernel Image (gzip compressed)
Data Size: 2628083 Bytes = 2.5 MiB
Load Address: 80800000
Entry Point: 80801000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel console=ttyAS0,115200 root=/dev/mtdblock0 rw rootfstype=jffs2 rootdelay=2 ramdisk_size=5120 nwhwconf=device:eth0,hwaddr:00:14:49:E4:B6:49 ip=.
Linux version 2.6.23.17_stm23_A27--SDK7105_7105-STSDK (microtrol@UTE742A) (gcc version 4.2.4 (snapshot) (STMicroelectronics/Linux Base 4.2.4-56)) #1 PREEMPT 2
Booting machvec: pdk7105
Node 0: start_pfn = 0x40000, low = 0x54000
Zone PFN ranges:
Normal 262144 -> 344064
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 262144 -> 344064
STMicroelectronics PDK7105-SDK board initialisation
STx7105 version 4.x
Built 1 zonelists in Zone order. Total pages: 81280
Kernel command line: console=ttyAS0,115200 root=/dev/mtdblock0 rw rootfstype=jffs2 rootdelay=2 ramdisk_size=5120 nwhwconf=device:eth0,hwaddr:00:14:49:E4:B6:40
bpa2: partition 'bigphysarea' created at 0x40f53000, size 8000 kB (0x007d0000 B)
PID hash table entries: 2048 (order: 11, 8192 bytes)
Using tmu for system timer
Using 25.000 MHz high precision timer.
Console: colour dummy device 80x25
console [ttyAS0] enabled
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 303488k/327680k available (3731k kernel code, 846k data, 148k init)
PVR=04909200 CVR=60880000 PRR=00009e40
I-cache : n_ways=2 n_sets=512 way_incr=16384
I-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
D-cache : n_ways=2 n_sets=512 way_incr=16384
D-cache : entry_mask=0x00003fe0 alias_mask=0x00003000 n_aliases=4
Mount-cache hash table entries: 512
CPU: STx7105
NET: Registered protocol family 16
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Time: SuperH clocksource has been installed.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NTFS driver 2.1.28 [Flags: R/O].
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
JFS: nTxBlock = 2371, nTxLock = 18975
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
lirc_dev: IR Remote Control driver registered, major 61
lirc_stm: probe found data for platform device lirc
lirc_stm: STM LIRC plugin has IRQ 244 using IR-RX mode
lirc_stm: lirc_stm_calc_rx_clocks: IR clock is 100000000
lirc_stm: SCD not available in IR-RX mode. Not armed
lirc_dev: lirc_register_plugin: sample_rate: 0
STMicroelectronics LIRC driver initialized.
STMicroelectronics ASC driver initialized
stasc.0: ttyAS0 at MMIO 0xfd032000 (irq = 121) is a stasc
stasc.1: ttyAS1 at MMIO 0xfd033000 (irq = 120) is a stasc
RAMDISK driver initialized: 16 RAM disks of 5120K size 1024 blocksize
platform registration... <7>done!
GMAC - user ID: 0x10, Synopsys ID: 0x33
no valid MAC address; please, set using ifconfig or nwhwconfig!
eth0 - (dev. name: stmmaceth - id: 0, IRQ #134
IO base addr: 0xfd110000)
STMMAC MII Bus: probed
eth0: PHY ID 0007c0f1 at 0 IRQ -1 (0:00) active
SMSC LAN83C185: Registered new driver
SMSC LAN8187: Registered new driver
SMSC LAN8700: Registered new driver
SMSC LAN911x Internal PHY: Registered new driver
SMSC LAN8710/LAN8720: Registered new driver
pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver zd1201
usbcore: registered new interface driver usb8xxx
nwhw_config: (eth0) setting mac address: 00:14:49:E4:B6:49
scsi0 : sata_stm
ata1: SATA max UDMA/133 cmd 0xfe209000 ctl 0xfe209820 bmdma 0x00000000 irq 72
ata1: SATA link down (SStatus 0 SControl 300)
NAND device: Manufacturer ID: 0x98, Chip ID: 0xda (Toshiba NAND 256MiB 3,3V 8-bit)
Creating 1 MTD partitions on "stm-nand-flex.2":
0x00000000-0x10000000 : "File_System"
spi_stm_pio: PIO based SPI Driver
m25p80 spi8.122: m25p64 (8192 Kbytes)
Creating 3 MTD partitions on "m25p80":
0x00000000-0x00100000 : "U-Boot"
0x00100000-0x00120000 : "U-Boot Env"
0x00120000-0x00440000 : "Kernel"
spi_stm_pio: Registered SPI Bus 8: SCL [15,0], SDO [15,1], SDI [15, 3]
stm-ehci stm-ehci.0: st-ehci
stm-ehci stm-ehci.0: new USB bus registered, assigned bus number 1
stm-ehci stm-ehci.0: irq 169, io mem 0xfe1ffe00
stm-ehci stm-ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
stm-ohci stm-ohci.0: stm-ohci
stm-ohci stm-ohci.0: new USB bus registered, assigned bus number 2
stm-ohci stm-ohci.0: irq 168, io mem 0xfe1ffc00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
stm-ehci stm-ehci.1: st-ehci
stm-ehci stm-ehci.1: new USB bus registered, assigned bus number 3
stm-ehci stm-ehci.1: irq 143, io mem 0xfeaffe00
stm-ehci stm-ehci.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 1 port detected
stm-ohci stm-ohci.1: stm-ohci
stm-ohci stm-ohci.1: new USB bus registered, assigned bus number 4
stm-ohci stm-ohci.1: irq 142, io mem 0xfeaffc00
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
i2c-gpio: probe failed: -19
i2c-parport-light: adapter type unspecified
usbcore: registered new interface driver i2c-tiny-usb
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
Bluetooth: Virtual HCI driver ver 1.2
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
STMicroelectronics - Coprocessors st231 Init
st-coprocessor-0: No RAM reserved
st231.0 Coprocessor -------------------------------------------
not configured!
---------------------------------------------------------------
st-coprocessor-1: No RAM reserved
st231.1 Coprocessor -------------------------------------------
not configured!
---------------------------------------------------------------
stm_rng hardware driver 1.0 configured
heartbeat: version 0.1.1 loaded
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.5
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <[email protected]>
sh4 suspend support registered
stmmac_timer: TMU2 Timer ON (freq 256Hz)
IP-Config: Complete:
device=eth0, addr=192.168.99.162, mask=255.255.255.0, gw=192.168.99.254,
host=UTE742, domain=, nis-domain=(none),
bootserver=255.255.255.255, rootserver=255.255.255.255, rootpath= ....."
Hi @ljccitterio
I have a TDA STB for TDT (Television Digital Terrestre) in Venezuela with ISDB-Tb protocol (Japanese-Brazilian norm or standard). The equipment distributed in Venezuela is OEM assembled in Argentina.
What is the possibility of modifying the STB firmware?
First, this is not a topic for TSDuck. Your device is an independent set-top box, not a tuner which is attached to a computer running TSDuck.
Second, jailbreaking a consumer device is usually not permitted and, in the case of Pay-TV, illegal. This is not a topic which is allowed to be discussed here.
Hi @ljccitterio
I have a TDA STB for TDT (Television Digital Terrestre) in Venezuela with ISDB-Tb protocol (Japanese-Brazilian norm or standard). The equipment distributed in Venezuela is OEM assembled in Argentina. What is the possibility of modifying the STB firmware?
First, this is not a topic for TSDuck. Your device is an independent set-top box, not a tuner which is attached to a computer running TSDuck.
Second, jailbreaking a consumer device is usually not permitted and, in the case of Pay-TV, illegal. This is not a topic which is allowed to be discussed here.
Greetings. The device I mention is not for paid service. In Venezuela the digital television service is free. I don't know if I violate any laws or regulations by modifying these STBs for TDA. Since these STBs for the ISDB-Tb standard in Venezuela do not have support for updating their firmware, I wanted to know if it is possible to adapt other embedded software to the device. Thank you for your time.