-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
How to add new MyGica T230A? #224
Comments
@crazycat69 |
I don't understand, my tuner TC230A is like this:
MyGica Mini DVB-T2 USB Stick T230C v2 has idVendor=0572, idProduct=0xc68a .
|
I not have 0xc68a, 0xc69a sticks - so don't know how this marked :) Main diffrence from classic T230C (0xc689, 0xc699) some another clone Cypress FX2 controller with different TS bus clocking. |
@crazycat69 |
Hmm, look like 689a is some new. This product from AliExpress or another source? |
Yes friend happy new year! I hope your family is well. |
I wanted to test and I have the same problem as in #200
|
I compiled the driver with the patch and I get this message:
The command below produces this error.
You know what this command does?
And why is it not working? |
This POWER UP & RESET command + clock freq selection (4-6 bits in cmd[6], 24MHz in this case, but possible 16 and 27 MHz ). |
It's a fragment si2186.c :
"Initialize" is OK, bat "Power up" it generates an error -110, or -121 |
need sniff usb traffic from windows drivers |
But in my case with this stick t230a (0572:689a) these 3 procedures pass with 0 ret code. My stick stops in switch where is choosing chip_id and drops into default. It shows me: |
I bought also T230A and investigating how to sniff device initialization with wireshark+USBPcap on Windows |
I found good software which can show URB transfer requests: USBlyzer. In attachment is my dump from t230a after connection. Edit: I found my raw 2141 chip version: |
I'm trying usblyzer and sending my dump, but I don't know yet how to inspect it. |
I think that it's same board... So I tried to force these use firmwares and stick now looks fine buut it not find any channels. I don't know much about programing drivers so maybe is somewhere error with reading of output from stick. Here is my output:
|
These files are from windows where everything works fine and supports my theory it's a clone t230cv2. In my opinion, there is a problem with this piece of driver:
This definition is interesting: #define TIMEOUT 70 Why exactly 70? Not 65 or 75 ? |
Finally MyGica T230A working on linux (Raspberry Pi 4). I just compared usb dumps from Windows and Linux as I post before and changed GPIO_WRITE commands in dvbsky.c. So here is edited function in dvbsky.c which makes gpio write:
Also I made like here: 34770c6. And here is log in dmesg:
Also I tried tuner in TvHeadend and it working well, but I am not expert in drivers. So please developers test and if works add this patch to drivers and also give here feedback if it works or not for you people. |
Congratulations, good job! I confirm, the tuner is working. More thorough tests as I compile libreelec. |
OK. I confirm it's working, I Got good quality/signal strength on DVB-C, Same as T230C. |
Okay so I made pull request. |
I can confirm that it is working with LibreELEC, Amlogic 19.0 RC1-Matrix, Kernel Linux 5.11. https://forum.libreelec.tv/thread/23142-mygica-t230a/?postID=149248#post149248 Detail is not working perfectly need adjustments. |
|
So it's can be problem like mine.. can you test if in Windows you have better results? Because I have in Linux same results like in Windows. But on both OSes reception is very bad and I can't receive multiplex which I can get with Realtek stick. Tommorow I try to debug this stick again and try to enable LNA or AGC. Or have someone any suggestions what can be issue? |
First, a new firmware is needed.
Secondly, the @pego149 is right, something is wrong with the amplifier LNA or AGC. On Windows 10, one mux works on this stick from the supplier. The rest mux of the external antennas have 100% |
Yes, something is funky also on DVB-C. Some muxes work perfectly, sometimes it needs 1 retune to get a lock, others can't get a lock |
Edit: Everything is working fine on mine T230A now.. problem was too strong signal from exterior DVB-T antenna. Just pushed little piece of paper into coax connector and little isolated contact. I know it's weird solution but it works. |
Hi! Do you think that this T230a will work in a Synology DS218+ NAS? i've put fw files in /lib/firmware/ and gave permissions, Reboot, but dmesg only shows this when I connect it to usb port... usb 1-2: new high-speed USB device number 6 using xhci_hcd I'm totally noob with this (drivers). Do you know what must I do? |
I have a very strange issue. Dongle is correctly recognized, firmwares are correctly loaded, when it scans it crashes my system when starting to scan a frequency where services should be found. I need to force reset my system to make it work again. |
I confirm that this bug is only reproducible on Raspberry Pi Zero W (armv6), on Raspberry Pi 3 it works flawlessly. Any clue? On Pi Zero it just hangs, no kernel panic (so no logs), the cursor in the screen stops blinking and it closes every SSH connection. |
I still have issues with T230A running 6.4.3 kernel. I have to connect the stick to virtualbox windows after that I get picture with kaffeine without this I only get EPG texts. I did took a capture with wireshark on linux side and replay with usbrply but strangely enough this does not work. Have not examined what could be the issue with replay. Anyway this is not a very big issue for me because the state of T230A survives suspending pc connected to it so I hardly ever have to do the trip to connect virtualbox to get it working. I have only drivers for windows no other software. |
Hi,
I bought the MyGica T230A tuner. I didn't know there would be a problem with the letter A.
When I connected it to rpi with libreelec, dmesg showed something like this:
This tuner has entries in the "inf" file of the windows driver identical to the T230C v2 :
I patched the files: dvb-usb-ids.h, dvbsky.c and built a new image libreelec.
After running, dmesg shows now:
What could that mean?
Is there a problem with the firmware?
Can it be fixed somehow?
Tested on the devel version:
The text was updated successfully, but these errors were encountered: