if it is possible to have TBS5530 working
Only if you build a custom LE image with the drivers for TBS5530.
The LE buildsystem still supports creating an RPi(1) image, but even if you patch the kernel to support the TBS card it's not going to run well as the board has only 512MB RAM and modern Kodi needs more. That's the reason we dropped support for all boards with under 1GB RAM. If you want to run the board as an e.g. Tvheadend server-only LE device, that should be fine, but server running in the background and Kodi doing playback will be too much.
NB: Although it's not hard to compile a custom LE image, it requires a certain skillset, so it's probably easier to run a server-only setup from a RaspiOS image as this will have a ton of HOWTO guides for the task.
Only if you build a custom LE image with the drivers for TBS5530.
Is it enough to do the steps to build a customer LE image and the drivers for TBS5530 will be automatically included?
Or is it more than that?
The LE buildsystem still supports creating an RPi(1) image, but even if you patch the kernel to support the TBS card it's not going to run well as the board has only 512MB RAM and modern Kodi needs more. That's the reason we dropped support for all boards with under 1GB RAM. If you want to run the board as an e.g. Tvheadend server-only LE device, that should be fine, but server running in the background and Kodi doing playback will be too much.
NB: Although it's not hard to compile a custom LE image, it requires a certain skillset, so it's probably easier to run a server-only setup from a RaspiOS image as this will have a ton of HOWTO guides for the task.
You're right. I plan to have a TvHeadEnd server-only LE device, and frankly, it will be used only for testing purposes, not daily use.
If you think it would be easier to use RaspiOS instead of LE then I thought I got it wrong - I was assuming LE is more plug-play solution using LE, but for some specific setups might not be the case.
Is it enough to do the steps to build a customer LE image and the drivers for TBS5530 will be automatically included?
No, you need to add the kernel patch when compiling the image. Go read the thread smp linked.
No, you need to add the kernel patch when compiling the image. Go read the thread smp linked.
He added only a link to this commit: https://github.com/tbsdtv/linux_m…9f5f604187cc616
Or Did I miss something here?
Ahh, he normally links a thread which discusses building with a patch. All you need to do is add .patch to the URL and you have the patch that's needed for the kernel in the LE buildsystem: https://github.com/tbsdtv/linux_m…4187cc616.patch
Thanks for sharing the patch but unfortunately it doesn't work:
alexiedb Clone the RPi kernel (as we use their downstream fork not true upstream for RPi boards) then cherry-pick the patches smp has linked onto the RPi kernel 6.12.y codebase and solve the Kconfig and Makefile issues (simple sort order changes in the files probably) before generating a clean patch to use in the LE buildsystem. Also don't forget to add the related CONFIG_XXXXXX entries and enable the relevant modules in packages/RPi/devices/RPi/linux.arm.conf else the modules will not be built.
Now the issues are becoming more serious:
Do you have any idea what the problem could be?
Remove/comment out this -
.set_property = cxd2878_set_property,
.spi_read = cxd2878_spi_read,
.spi_write = cxd2878_spi_write,and this
static void cxd2878_spi_read(struct dvb_frontend *fe, struct ecp3_info *ecp3inf)
{
struct i2c_client *client = fe->demodulator_priv;
struct cxd2878_dev *dev = i2c_get_clientdata(client);
if (dev->config->read_properties)
dev->config->read_properties(client->adapter,ecp3inf->reg, &(ecp3inf->data));
return ;
}
static void cxd2878_spi_write(struct dvb_frontend *fe,struct ecp3_info *ecp3inf)
{
struct i2c_client *client = fe->demodulator_priv;
struct cxd2878_dev *dev = i2c_get_clientdata(client);
if (dev->config->write_properties)
dev->config->write_properties(client->adapter,ecp3inf->reg, ecp3inf->data);
return ;
}Did you use the current version of cxd2878.c or the version from the initial commit?
I found the problem, I forgot to add:
CONFIG_DVB_TBSECP3=m
Now it looks like this:
[ 26.493015] dvb-usb: found a 'TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0' in cold state, will try to load a firmware
[ 26.534832] dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw'
[ 26.534875] tbs5530: start downloading tbs5530 firmware
[ 26.837957] dvb-usb: found a 'TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0' in warm state.
[ 26.838852] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 26.838874] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 26.846626] dvbdev: DVB: registering new adapter (TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0)
[ 26.868008] tbs5530: read eeprom failed.
[ 26.868035] dvb-usb: MAC address reading failed.
[ 26.978621] usb 1-1.3: USB disconnect, device number 4
[ 27.320403] i2c i2c-3: cxd2878:Can not decete the chip.
[ 27.320429] i2c i2c-3: cxd2878:error attaching frontend.
[ 27.320454] dvb-usb: no frontend was attached by 'TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0'
[ 27.320480] dvb-usb: TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0 successfully initialized and connected.
[ 27.320848] usbcore: registered new interface driver tbs5530
[ 27.330125] dvb-usb: TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x successfully deinitialized and disconnected.
[ 28.464725] usb 1-1.3: new high-speed USB device number 5 using dwc_otg
[ 28.539125] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 28.556463] usb 1-1.3: New USB device found, idVendor=734c, idProduct=5530, bcdDevice= 0.01
[ 28.556499] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 28.556518] usb 1-1.3: Product: TBS 5530
[ 28.556533] usb 1-1.3: Manufacturer: TBS-Tech
[ 28.558396] dvb-usb: found a 'TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0' in cold state, will try to load a firmware
[ 28.558435] dvb-usb: downloading firmware from file 'dvb-usb-id5530.fw'
[ 28.558454] tbs5530: start downloading tbs5530 firmware
[ 28.761377] dvb-usb: found a 'TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0' in warm state.
[ 28.762368] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 28.762390] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 28.770950] 8021q: 802.1Q VLAN Support v1.8
[ 28.785139] dvbdev: DVB: registering new adapter (TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0)
[ 29.095027] dvb-usb: MAC address: 00:22:ab:c0:79:03
[ 29.111636] i2c i2c-3: Detect CXD286802(SiP) chip.
[ 29.111697] usb 1-1.3: DVB: registering adapter 0 frontend 0 (TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0 DVB-T/T2/C/C2,ISDB-T/C,ATSC1.0)...
[ 29.334738] usb 1-1.3: DVB: registering adapter 0 frontend 1 (TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC DVB-S/S2/S2X)...
[ 29.337148] dvb-usb: TurboSight TBS 5530 DVB-T2/T/C/S/S2/S2x,ISDB-T,ATSC1.0 successfully initialized and connected.Now I will install TvHeadEnd and see if really works 
Thank you very much for your support!
I was too optimistic...
After installing TvHeadEnd (even before I had installed TvHeadEnd but I was not connecting the USB device before installing it) I got the same error as before:
[ 684.132333] i2c i2c-3: Deceted the Tuner chip ASCOT3 ,ID 2878A
[ 684.252637] Unable to handle kernel NULL pointer dereference at virtual address 00000020
[ 684.252676] pgd = ee80e229
[ 684.252691] [00000020] *pgd=00000000
[ 684.252721] Internal error: Oops: 17 [#1] ARM
[ 684.252770] Modules linked in: m88rs6060 8021q rfkill cxd2878 dvb_usb_tbs5530 dvb_usb dvb_core rc_core bcm2835_gpiomem fixed wireguard ip6_udp_tunnel udp_tunnel
[ 684.252872] CPU: 0 PID: 514 Comm: kdvb-ad-0-fe-0 Not tainted 4.19.127 #1
[ 684.252901] Hardware name: BCM2835
[ 684.252971] PC is at cxd2878_init+0x55c/0x9e8 [cxd2878]
[ 684.253002] LR is at 0x8dc163e0
[ 684.253025] pc : [<7f098a3c>] lr : [<8dc163e0>] psr: 68000013
[ 684.253054] sp : 8dd75e78 ip : 00000000 fp : 8dd75ed4
[ 684.253077] r10: 00000003 r9 : 8dd75e8d r8 : 00000000
[ 684.253101] r7 : 80e6b028 r6 : 00000001 r5 : 8dce0808 r4 : 8dce0800
[ 684.253129] r3 : 00000000 r2 : cc5121a8 r1 : 00000002 r0 : 00000000
[ 684.253158] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
[ 684.253188] Control: 00c5387d Table: 0debc008 DAC: 00000055
[ 684.253218] Process kdvb-ad-0-fe-0 (pid: 514, stack limit = 0x3b4b7596)
[ 684.253247] Stack: (0x8dd75e78 to 0x8dd76000)
[ 684.253274] 5e60: 00000000 00000001
[ 684.253316] 5e80: 8081d968 007b5f5c 80017a01 00001504 82a88418 40c40000 75450010 023f1c07
[ 684.253355] 5ea0: 000a2010 cc5121a8 800b9b18 953d4a00 8dce0808 00000000 8dd74000 8dce0808
[ 684.253394] 5ec0: 7f069174 94283cb0 8dd75eec 8dd75ed8 7f08438c 7f0984ec 8dce0808 952c8a00
[ 684.253434] 5ee0: 8dd75f14 8dd75ef0 7f067998 7f08433c 80013f38 80015128 80013f38 00000000
[ 684.253493] 5f00: 800428ac 8dce0808 8dd75f74 8dd75f18 7f0691dc 7f067970 8dce0808 7f069174
[ 684.253543] 5f20: 8dd75f54 8dce0a3c 800b9b18 00000000 60000013 942e8a40 00000040 ffffe000
[ 684.253590] 5f40: 8dce0808 cc5121a8 8dd75f74 942e8a40 8e9ae3e0 00000000 8dd74000 8dce0808
[ 684.253635] 5f60: 7f069174 94283cb0 8dd75fac 8dd75f78 800428b4 7f069180 942e8a58 942e8a58
[ 684.253681] 5f80: 80030130 8e9ae3e0 80042768 00000000 00000000 00000000 00000000 00000000
[ 684.253724] 5fa0: 00000000 8dd75fb0 800090ac 80042774 00000000 00000000 00000000 00000000
[ 684.253767] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 684.253811] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[ 684.253843] Backtrace:
[ 684.253929] [<7f0984e0>] (cxd2878_init [cxd2878]) from [<7f08438c>] (dvb_usb_fe_wakeup+0x5c/0x64 [dvb_usb])
[ 684.253986] r10:94283cb0 r9:7f069174 r8:8dce0808 r7:8dd74000 r6:00000000 r5:8dce0808
[ 684.254024] r4:953d4a00
[ 684.254185] [<7f084330>] (dvb_usb_fe_wakeup [dvb_usb]) from [<7f067998>] (dvb_frontend_init+0x34/0xc0 [dvb_core])
[ 684.254237] r5:952c8a00 r4:8dce0808
[ 684.254379] [<7f067964>] (dvb_frontend_init [dvb_core]) from [<7f0691dc>] (dvb_frontend_thread+0x68/0x650 [dvb_core])
[ 684.254431] r4:8dce0808
[ 684.254529] [<7f069174>] (dvb_frontend_thread [dvb_core]) from [<800428b4>] (kthread+0x14c/0x164)
[ 684.254588] r10:94283cb0 r9:7f069174 r8:8dce0808 r7:8dd74000 r6:00000000 r5:8e9ae3e0
[ 684.254625] r4:942e8a40
[ 684.254661] [<80042768>] (kthread) from [<800090ac>] (ret_from_fork+0x14/0x28)
[ 684.254700] Exception stack(0x8dd75fb0 to 0x8dd75ff8)
[ 684.254730] 5fa0: 00000000 00000000 00000000 00000000
[ 684.254773] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 684.254815] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 684.254854] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80042768
[ 684.254888] r4:8e9ae3e0
[ 684.254921] Code: e1a0c2ac e58dc000 ebfff55b e5943000 (e5933020)
[ 684.255154] ---[ end trace 2661268913abd65b ]---
Any ideas what could be the issue?
You're right. I plan to have a TvHeadEnd server-only LE device, and frankly, it will be used only for testing purposes, not daily use.
"LibreELEC is a minimalist 'Just enough OS' Linux distribution for running Kodi."
I'm just thinking... if don't need Kodi, why you don't just install a minimal raspios (without desktop), it's more easy to add drivers (in the case is necessary) and install the TVheadend... and play with that setup.
